Stop stitching starters together. Launch AI-native SaaS with a production-shaped stack on day one.
CentraKit is the template: multi-tenant SaaS, API plus MCP, CLI, docs, workflows, and the chat surface your customers expect—structured so your team and your agents can keep shipping.
- Full stack in one monorepo
- AI-native product surface included
- Swap Supabase without a rewrite
Built for teams who ship AI into the product, not just the README
What changes when the foundation is already serious
Less glue code, fewer fake demos. Each block is written as an outcome your buyer can feel in the first week of implementation.
Everything that touches production, already aligned
One purchase gives you the SaaS app customers see, the API and MCP surface integrators want, and the repo conventions your agents need—without gluing five tutorials together.
Build with AI
Build with AI from the first prompt instead of bolting agent support on later.
Ship AI into the product
Give your customers AI-native workflows on day one, not after a rewrite.
SaaS app included
Start from a real multi-tenant SaaS app with auth, organisations, roles, onboarding, and customer-facing workflows.
API plus MCP server
Pair the product app with a dedicated API app, committed OpenAPI output, typed client generation, and an MCP server surface.
Run with agents
Run AI-native operations with workflows, events, permissions, and clear ownership boundaries.
Swappable data layer
Use Supabase by default, but keep providers behind clean contracts so you can swap to Convex or your own backend later.
From template to traction in three deliberate steps
Three moves from purchase to a credible AI-native SaaS demo your team can extend—not a twelve-step checklist buried in a README.
Get the template running
Buy the tier that fits, clone the monorepo, and wire env for SaaS, API, and Supabase using the included docs path.
Shape your product boundaries
Swap branding, extend Zod contracts in packages/data, and keep provider code isolated in packages/supabase.
Launch and iterate
Ship the SaaS surface, expose API and MCP to partners, and keep iterating with the same verify pipeline your CI uses.
Pick the tier that matches your momentum.
Compare Solo, Startup, and Business on the full pricing page, then open a conversation when you are ready to move.
Proof that shows up next to the pricing decision
Composite feedback from teams who needed AI in the product, not only in the toolkit. Replace with your own customers when you ship.
We replaced three internal starters with CentraKit. The AI chat surface and API layer matched our roadmap without a month-long refactor.
The monorepo boundaries are the real product. Our agents stay inside packages/data and stop hallucinating Supabase calls in the wrong layer.
Buyers asked for MCP and a real API on week two. Having OpenAPI and the server in the same template saved our sales cycle.
Questions that usually come up early
A few of the questions teams ask before deciding whether CentraKit should become their starting point.
No. CentraKit is opinionated around AI-native SaaS: the chat surface, workflow model, API and MCP layering, and agent-ready repo conventions are part of the point.
Use CentraKit as your fastest path from AI product idea to production-shaped SaaS.
If you want a template that already thinks in terms of agents, workflows, product surfaces, and backend boundaries, this is the stack to start from.