The Vault
Curated, admin-reviewed recipes anyone can install with one command — or submit your own for review.
API 2
Deno + Postgres + Redis: Edge API Starter
A modern edge-friendly API backend: Deno's secure-by-default runtime with native TypeScript, Postgres for relational data, and Redis for caching and rate limiting at the edge.
by @ops
Rust + Postgres + Meilisearch
A Rust API backed by Postgres with Meilisearch for fast, typo-tolerant full-text search.
by @ops
Analytics 3
Go + ClickHouse + Kafka
An event-ingestion pipeline: a Go API publishing to Kafka, with ClickHouse as the analytics store.
by @ops
Python + ClickHouse + Kafka: Data Warehouse ETL Pipeline
A data engineering ETL/ELT pipeline: Python for its rich data-tooling ecosystem, Kafka as the ingestion backbone decoupling producers from processing, and ClickHouse as the analytical warehouse built for fast aggregate queries over large volumes.
by @ops
Rust + Kafka + ClickHouse: IoT Telemetry Ingestion
A high-throughput device telemetry pipeline: a Rust ingestion API built for low-latency, high-volume writes, Kafka absorbing bursty device traffic, and ClickHouse as the analytical store for time-series queries at scale.
by @ops
Backend 6
.NET + Postgres + Redis: Fintech-oriented Baseline
A security-conscious starting point for financial and payments-adjacent backends: .NET API, Postgres for ledger/transaction records, and Redis for session and rate-limit state. This is a starting baseline only, not a certified or verified PCI-DSS/regulatory-compliant stack — your own security and compliance review is still required before handling real financial data.
by @ops
Elixir + MySQL + Mailpit
A Phoenix-style Elixir API on MySQL instead of Postgres, with local email testing via Mailpit.
by @ops
Java (Spring) + Postgres + Redis: Healthcare-oriented Baseline
A security-conscious starting point for patient-data-adjacent backends: Spring Boot API, Postgres for structured clinical/administrative records, and Redis for session state. This is a starting baseline only, not a certified or verified HIPAA/regulatory-compliant stack — your own security and compliance review is still required before handling real patient data.
by @ops
PHP + Postgres + RabbitMQ
A queue-driven PHP backend (no framework baked in) using Postgres and RabbitMQ for async job processing.
by @ops
Python + MariaDB + Redis: Legacy-friendly Baseline
A Python backend built around MariaDB — a natural fit for teams migrating off older MySQL-family systems without a database rewrite — with Redis for caching and session state layered on top.
by @ops
Ruby + Valkey + MinIO
A lean Ruby API (no Rails) using Valkey for caching and MinIO for S3-compatible object storage.
by @ops
Content 2
Bun + MongoDB + Meilisearch: Knowledge Base / Docs Search
A documentation/knowledge-base platform: Bun API for fast cold starts and low-latency responses, MongoDB for flexible article/page storage, and Meilisearch for instant, typo-tolerant search across the whole knowledge base.
by @ops
PHP + Postgres + Elasticsearch + Redis: CMS/Content Platform Starter
A headless CMS / content platform backend: PHP API, Postgres for content and structured records, Elasticsearch for fast full-text and faceted search across content, and Redis for page/query caching.
by @ops
Infrastructure 2
Elixir + Postgres: Background Jobs Microservice
A pure queue-consumer microservice, no public HTTP API surface — Elixir's native concurrency plus a Postgres-backed job queue (the same pattern as Oban) for reliable, retryable background processing. Postgres alone is the queue backend here; no separate broker like Redis or RabbitMQ is needed.
by @ops
Go + Mailpit + Redis + RabbitMQ: Notification Delivery Service
A dedicated notification/delivery microservice: Go for efficient concurrent delivery workers, RabbitMQ queuing outbound notifications so spikes never get dropped, Redis for delivery-status and dedup tracking, and Mailpit for safe local email testing without hitting a real inbox.
by @ops
Real-time 2
Go + Postgres + Redis + NATS: Real-time Chat Starter
A real-time messaging backend: Go API, Postgres for message history and rooms, Redis for presence and rate limiting, and NATS as the pub/sub backbone for live delivery across instances.
by @ops
Rust + Redis + NATS: Multiplayer Game Backend
A low-latency multiplayer game backend: Rust for predictable, high-performance tick processing, Redis for fast-changing player/session state, and NATS as the pub/sub backbone for broadcasting game state across server instances.
by @ops
