Explore Verified Production Tech Stacks
9+ battle-tested open-source software architectures with architectural rationale, reliability metrics, and instant AI scaffolding prompts.
Blazing-fast analytical database; processes queries orders of magnitude faster than traditional row-based engines by scanning only relevant columns with SIMD vector instructions.
Open-source GraphQL federation gateway and router written in Go. Compiles subgraphs into unified declarative execution plans with sub-millisecond routing overhead, zero-allocation request pipelines, OTEL distributed tracing, and ClickHouse-backed analytics.
Ultra-high throughput observability pipeline by Datadog; Rust guarantees minimal memory footprint and zero GC pauses during gigabyte/sec telemetry ingestion.
Open-source usage-based billing infrastructure; high-throughput Go event ingester paired with Ruby on Rails subscription ledger.
Enterprise observability; Django handles transactional models while high-volume event ingestion is streamed via Kafka to ClickHouse.
Specialized LLM tracing platform: high-volume generation logs streamed into ClickHouse for cost and latency analytics.
BEAM concurrency engine handles massive ingestion surges with minimal memory footprint into ClickHouse.
Billions of events/month: ingest through Kafka into ClickHouse columnar storage while keeping UI on Django/Postgres.
Solo developer, fast MVP: single framework, single deploy target, optional ClickHouse for scale.
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.