Skip to content
Flareforge

Why Flareforge?

Flareforge is the web framework for generating and deploying full-stack applications. It is engineered specifically for the Cloudflare ecosystem to automate the creation of scalable products.

Some highlights include:

  • The entire application stack, from database schemas to UI and pricing, is defined in a single flareforge.jsonc file, serving as the source of truth.
  • Provides a complete queue system for managing long-running background tasks, such as AI data processing or media transformations, leveraging Cloudflare Queues.
  • User management that abstracts away the complexity associated with building secure authentication flows, powered by WorkOS.
  • Stripe integration for payment processing and invoicing, including webhooks management.
  • Generates the necessary configurations and provides the hooks for complete internationalization support from the start.

and much more…

Design Principles

Section titled “Design Principles”

Five core design principles explain why Flareforge was built and the problems it solves.

  1. Zero-to-SaaS in Minutes: Drastically reduce the time from concept to a billable product.
  2. Edge-Native: Maximize performance, scalability, and cost-efficiency.
  3. Single Source of Truth: Maintain integrity by deriving the application from one config.
  4. Ejectable: Provide high-level conventions with the option to take low-level control.
  5. No Lock-In: Generate standard, idiomatic code that the developer owns completely.

Zero-to-SaaS in Minutes

Section titled “Zero-to-SaaS in Minutes”

Flareforge automates the most time-consuming aspects of new development.

The framework was created to solve the problem of repetitive setup for authentication, billing logic, database migrations, and basic UI structure, which are common across multiple projects.

Instead of spending days or weeks on this foundational work, a developer can use the flareforge setup command to configure all third-party services and then generate a complete application skeleton from their flareforge.jsonc file.

This allows development to start immediately on the core features that differentiate the product, making it possible to test new business ideas with minimal upfront time investment.

Edge-Native Architecture

Section titled “Edge-Native Architecture”

Flareforge is purpose-built for the Cloudflare ecosystem. It is not a general-purpose framework retrofitted for the edge; its architecture is predicated on the services Cloudflare provides.

This includes Cloudflare Workers for compute, D1 for databases, R2 for object storage, and Queues for background jobs.

This deliberate, tight integration provides two key advantages.

  • It ensures applications are scalable and performant by default, leveraging Cloudflare’s global network.
  • It yields significant cost-efficiency, allowing for the deployment of complex applications that can operate on Cloudflare’s free or low-cost tiers. The framework handles the wrangler.jsonc configuration and resource bindings, abstracting away the DevOps complexity.
Cloudflare Integration Guide Learn how Flareforge utilizes Cloudflare services.

A Single Source of Truth

Section titled “A Single Source of Truth”

The entire application architecture is derived from the flareforge.jsonc file. This declarative approach prevents configuration drift and simplifies maintenance.

When managing multiple boilerplate projects, making cross-cutting changes like adding i18n support or altering a database schema is inefficient and error-prone. Flareforge solves this by centralizing these definitions.

A change to a task definition, pricing plan, or theme color in the JSON file is propagated throughout the entire codebase upon regeneration. The engine ensures that the database schema, API handlers, UI components, and internationalization files all remain consistent with the single, authoritative definition.

Configuration Reference Dive into the full schema and options for flareforge.jsonc.

Ejectable Abstractions

Section titled “Ejectable Abstractions”

Flareforge provides conventions and pre-built components, not rigid limitations. While the framework generates a complete UI and backend, developers are never trapped by the initial abstractions.

The unforge CLI command is the designated escape hatch. If a developer needs to customize a specific UI block beyond what the configuration allows, they can use this command to eject the component’s source code directly into their project directory.

At that point, they take full ownership of that piece of code and can modify it without restriction, while the rest of the framework continues to manage other parts of the application. This allows the project to scale in complexity without being hindered by the framework’s initial design.

Unforge Reference Detailed guide on how to use the unforge command.

No Proprietary Lock-In

Section titled “No Proprietary Lock-In”

The output of Flareforge is standard, idiomatic code. The generated backend uses Hono, the frontend is react-router 7 with Vite, and the database logic is Drizzle ORM. There is no Flareforge-specific runtime or language to learn.

This principle ensures that developers are always in control of their codebase. The framework is a tool for acceleration, not a permanent dependency. A team can use Flareforge to launch their product and, as they scale, choose to manually manage the generated code, evolve it independently, or even migrate away from the generation process entirely.