FireGEO is an open-source SaaS starter kit designed for rapid development of brand monitoring and AI chat applications. It targets developers looking to quickly launch a feature-rich SaaS product with built-in authentication, billing, and web scraping capabilities, leveraging a modern tech stack.

How It Works

This starter kit utilizes a robust, opinionated architecture centered around Next.js 15 for the frontend and backend, PostgreSQL with Drizzle ORM for data management, and Better Auth for authentication. Firecrawl is integrated for web scraping, enabling brand monitoring features. Payments are handled via Autumn, which integrates with Stripe, and AI functionalities are supported by multiple providers like OpenAI and Anthropic.

Quick Start & Requirements

• Install: Clone the repository and run npm run setup.
• Prerequisites: Node.js 18+, npm, PostgreSQL database.
• API Keys: DATABASE_URL, BETTER_AUTH_SECRET, AUTUMN_SECRET_KEY, FIRECRAWL_API_KEY, RESEND_API_KEY, and optional AI provider keys.
• Setup Time: Minimal, with an automated setup script.
• Resources: Links to Firecrawl API, Next.js Docs, Better Auth Docs, Autumn Docs, Drizzle ORM, and shadcn/ui are provided.

Highlighted Details

• Full-stack TypeScript with Next.js 15, React 19, and Tailwind CSS v4.
• Integrated AI chat with support for OpenAI, Anthropic, Google Gemini, and Perplexity.
• Automated setup script for dependencies, database migrations, and billing configuration.
• Brand monitoring powered by Firecrawl for web scraping and analysis.
• Built-in authentication via Better Auth and payment processing via Autumn with Stripe.

Maintenance & Community

The project is maintained by mendableai. Contributions are welcome via pull requests. Links to relevant documentation for core technologies are provided.

Licensing & Compatibility

The project is released under the MIT License, permitting commercial use and integration with closed-source applications.

Limitations & Caveats

The setup requires obtaining multiple API keys from various third-party services. Specific configurations for AI providers and billing features need to be completed manually within the .env.local file and the respective service dashboards.