Stack directory
Opinionated starting points that explain why the tools fit together, the assumptions they make, and when a layer should change.
Use this Stack when AI is a product capability inside a conventional SaaS system rather than a standalone model-research platform.
The stack accelerates product delivery but combines identity, database, billing, model, SDK, and hosting dependencies whose usage costs and failure modes must be measured independently.
Use this Stack when customer organizations, enterprise federation, provisioning, operational workflows, and account-level billing are core product requirements.
The stack covers common enterprise SaaS infrastructure quickly, but the team must own cross-system identity mapping, tenant isolation, authorization, event consistency, enterprise support, and vendor migration.
Use this Stack when editors need a managed structured-content system and the product needs a custom Next.js frontend, dedicated search, global delivery, and managed deployment.
The Stack accelerates content operations and delivery but distributes data, indexing, cache, and runtime state across managed providers whose usage, failure, and migration boundaries must be operated deliberately.
Use this Stack when a small team wants a conventional SaaS foundation, prefers application-owned authentication, and values outsourcing seller-of-record operations.
The stack can be economical and portable at small scale, but the developer assumes more authentication and integration responsibility and must validate runtime compatibility, MoR eligibility, database behavior, and migration paths.
Use this Stack when the product needs application authentication, relational data, card payments, transactional email, and managed web deployment without operating each subsystem.
The stack minimizes initial operations but concentrates product risk across several managed vendors and leaves the application responsible for domain data, authorization, tax scope, and migration planning.