Explore Verified Production Tech Stacks
16+ battle-tested open-source software architectures with architectural rationale, reliability metrics, and instant AI scaffolding prompts.
Database-centric product; most business logic lives in Postgres policies and edge functions.
The modern standard for headless content management; runs completely natively inside Next.js with Drizzle ORM and React Server Components, offering zero-latency Local API calls.
Eliminates API schema drift without code generation; TypeScript compiles client and server code together to infer procedure input, output, and error types automatically.
The enterprise React benchmark; leverages React Server Components, server actions, and a high-performance Rust compiler (Turbopack) for maximum SEO and sub-second page loads.
React framework for in-app AI copilots; bridges frontend UI state directly into LangGraph agent loops with bidirectional tool execution.
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.
High-throughput AI pipeline: visual canvas frontend with Python worker cluster for asynchronous LLM orchestration.
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.