Explore Verified Production Tech Stacks
10+ battle-tested open-source software architectures with architectural rationale, reliability metrics, and instant AI scaffolding prompts.
Benchmark developer experience for relational databases; leverages declarative schema modeling to auto-generate fully type-safe TypeScript clients backed by an optimized query engine.
The canonical modern open-source Next.js template demonstrating Server Components, shadcn/ui primitives, and Prisma schema modeling.
Specialized LLM tracing platform: high-volume generation logs streamed into ClickHouse for cost and latency analytics.
Visual node-based builder: drag-and-drop state machine with lightweight web embed runtime.
Modern open-source DocSend alternative built entirely on serverless Next.js, S3, and real-time event ingestion.
Embeddable widget and admin portal in the same repo: agents make end-to-end changes in one context.
Small team, agent-assisted workflow: unified language and strong type inference verify generated code.
Solo developer, fast MVP: single framework, single deploy target, optional ClickHouse for scale.
Thousands of click events per second: analytics offloaded to an OLAP service, OLTP kept lean.
Self-hostable SaaS: web, embed, and API packages in a single monorepo with type-safe boundaries.
Frequently Asked Questions
Everything you need to know about how this directory works.
What counts as a "verified" production stack?
A verified badge means the architecture is either a well-known curated open-source project we benchmarked directly from its public repository, or a community submission whose maintainer claimed the listing and confirmed the stack, scale, and reliability details are accurate.
Can I submit my own project to this directory?
Yes. Click "Share Your Stack" to submit your production architecture — name, tech stack, team scale, and why you chose it. Submissions are reviewed and go live as community listings; you can claim and verify them later from the project page.
What is the difference between AI-Agent, Hybrid, and Classic modes?
AI-Agent means the majority of the codebase was generated by an AI coding agent with light human review. Hybrid means agent-generated code paired with active human pair programming. Classic means the codebase was hand-written with AI used only for assistance, not generation.
How is the "Most Upvoted" sort order calculated?
Upvotes are community signals from engineers confirming a stack worked well for a production use case similar to theirs. The default sort ranks by net upvotes, then by most recently verified, so newer confirmations surface architectures that are still actively maintained.
Stack information is sourced from each project's public repository (package.json, go.mod, requirements.txt, or equivalent) and is not affiliated with or endorsed by the listed projects.