Explore Verified Production Tech Stacks
14+ battle-tested open-source software architectures with architectural rationale, reliability metrics, and instant AI scaffolding prompts.
Universal observability platform; Go backend queries disparate time-series databases and streams real-time telemetry to customizable React panels.
Ultra-lightweight server resource and Docker container monitoring hub with minimal CPU/RAM footprint. Single-binary Go agents stream CPU, memory, disk I/O, temperature, and container metrics to a central Go/PocketBase hub with interactive React visualizations.
Lightweight Sentry-compatible application performance monitoring and error tracking platform. Built on Python Django and PostgreSQL with async Celery task queues for high-volume exception ingestion and Redis message buffering.
Ultra-low-cost, high-throughput unified observability for logs, metrics, and traces. Written in Rust for zero-overhead stream ingestion, compiling telemetry directly into compressed Apache Parquet columnar shards stored on S3, querying via Apache DataFusion vector execution without maintaining expensive search indices.
Ultra-high throughput observability pipeline by Datadog; Rust guarantees minimal memory footprint and zero GC pauses during gigabyte/sec telemetry ingestion.
Lightweight developer status page; compiled into a single binary where Go performs zero-allocation concurrent health checks and serves an embedded Vue interface.
Self-service business intelligence and analytics; compiles visual query builder inputs into optimized SQL across 20+ database dialects.
Enterprise observability; Django handles transactional models while high-volume event ingestion is streamed via Kafka to ClickHouse.
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.
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.