Explore Verified Production Tech Stacks
6+ battle-tested open-source software architectures with architectural rationale, reliability metrics, and instant AI scaffolding prompts.
Self-hosted real-time push notification service (Pushover / Pusher alternative). Built in Go with Gin and WebSockets for low-latency message streaming from CI/CD webhooks, server scripts, and IoT alerts directly to desktop/mobile devices.
Unofficial Bitwarden compatible server written in Rust; replaces the heavy multi-container C#/.NET stack with a lightweight single-binary service consuming under 50MB of RAM.
Compiles PostgreSQL database schemas, functions, and Row-Level Security (RLS) policies into an instant, high-performance GraphQL API without N+1 query overhead. Generates optimized single-query SQL execution plans directly from incoming GraphQL ASTs.
Production-grade headless browser grid for automated web scraping, PDF generation, and synthetic testing. Wraps Chromium instances in isolated Docker sandboxes with WebSocket multiplexing, connection pooling, and memory-leak auto-restarts.
Unified document, graph, and relational cloud database written in Rust. Replaces complex backend stacks with schema-full/schema-less flexibility, real-time WebSocket live queries, granular row-level permissions, and distributed key-value storage backends (TiKV/RocksDB).
Omnichannel real-time support inbox connecting WhatsApp, Twitter, Email, and Webchat over WebSockets.
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.