Curated stacks,
for common use cases.
A handful of opinionated picks for shipping in 2026. Every choice links into the catalog with the reason it was selected and the graduation path when you outgrow it.
The AI SaaS MVP Stack
A TypeScript-first stack for shipping an AI-backed SaaS to paying users fast, without gluing together a dozen services. Postgres and auth handled, payments that deal with tax for you, and a model layer you can swap without a rewrite.
The Edge Stack
A stack with no obvious home region. Code runs next to the user, the database lives at the edge too, and there are no cold starts to design around. Built for global, latency-sensitive products.
The Enterprise SaaS Stack
A stack tuned for a funded team selling B2B, where closing deals depends on SSO, billing depth, and a security posture procurement will sign off on. The deliberate opposite of an MVP stack: more control, less managed convenience.
The Laravel SaaS Stack
A batteries-included PHP path for shipping a SaaS without assembling a dozen JavaScript services. Auth, queues, ORM, and billing ship with the framework, and one developer can hold the whole app in their head.
The Python AI Backend
A Python-first stack for teams whose product is the model, not the web app. Async API, a database that branches per experiment, serverless GPUs, and open-weight models you host yourself for control and cost.
The Real-time Collaborative Stack
A stack that makes keeping every client in sync the default rather than a feature you build. Reactive backend, the React ecosystem on top, team-aware auth, and zero-config hosting for the front end.
The Self-hosted Indie Stack
A stack for builders who would rather own their infrastructure than rent managed everything, with costs that do not scale punitively with success. Portable pieces, no per-seat auth bills, no proprietary database API.