A framework, not a boilerplate
Indigo is the foundation we wished existed every time we started a new product — so we built it, in the open.
A boilerplate ages. A framework grows.
Most SaaS projects start the same way: a month wiring together auth, billing, a CMS, email, jobs and real-time before a single customer-facing feature exists.
A boilerplate hands you a snapshot of that work and walks away — you inherit the glue code and maintain it forever. Indigo is built as a framework instead: a cohesive foundation, extended through config and modules, that keeps evolving under you.
That difference is the whole point. New content types, features and modules register themselves — they never edit shared code. So the core can be upgraded without unpicking your work, and a new engineer — or an AI agent — can extend the system without first understanding all of it.
What Indigo optimises for
Cohesion over assembly
One type-safe system where auth, billing, the CMS, jobs and real-time already know about each other — not a dozen libraries held together by glue.
Legible to agents
Nested CLAUDE.md docs and a config-driven architecture so AI coding agents can read, navigate and extend the codebase on their own.
Open and ownable
degit ships no history; bun run init makes a fresh repository. The code is yours from the first commit — fork-free upgrades, no lock-in.
Open source, sustainably
The core framework and the essential modules are free and open source under the AGPL-3.0 license. For teams that need to ship proprietary software, a commercial license removes the AGPL's copyleft obligations.
Premium modules — e-commerce, AI chat, support and more — fund continued development, so the open-source core stays maintained and keeps improving. It's a model designed to keep Indigo healthy for the long run.
Build on Indigo
Explore the live demo, read the docs, or clone the starter and ship.