Explore Verified Production Tech Stacks
4+ battle-tested open-source software architectures with architectural rationale, reliability metrics, and instant AI scaffolding prompts.
Leading self-hosted Zapier alternative; combines an intuitive Vue visual canvas with a high-throughput Node.js execution engine and built-in AI agent reasoning nodes.
Durable execution platform allowing developers to write resilient, long-running distributed workflows in code without worrying about network partitions, crashes, or server restarts. Backed by Go gRPC cluster nodes and persistent event-history replay logs in PostgreSQL/Cassandra.
Modern Airflow alternative; YAML-based workflow orchestration built on Java Micronaut for microsecond execution overhead and massive horizontal scaling.
Open-source Zapier alternative; combines an Angular graph UI with Fastify and sandboxed V8 execution workers for high-volume webhook triggers.
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.