VibeInfra — production incident simulations for infrastructure engineers
VibeInfra is an incident-readiness platform for infrastructure engineers. It runs production-realistic outage simulations — Linux kernel, Docker, Kubernetes, Nginx, PostgreSQL, Kafka and AWS — in live disposable multi-container sandboxes, where engineers diagnose the fault from real logs, metrics and a terminal, then prove recovery under automated grading.
Continue to VibeInfra in English · Lanjut ke VibeInfra dalam Bahasa Indonesia
What VibeInfra is
Each lab is a real outage in a disposable multi-container environment. There are no slides and no multiple choice: you get logs, metrics, a topology view and a terminal attached to a system that is genuinely broken. You diagnose the fault, apply a fix, and an automated evaluator checks the system actually recovered — then hands back an after-action report. Progress is tracked as an XP ladder across nine domains.
When to use VibeInfra
- An engineer wants hands-on practice diagnosing a specific production failure mode, not an explanation of it.
- Someone is preparing for an SRE or platform-engineering interview and needs live troubleshooting reps.
- A team wants incident-response drills against realistic systems before the next on-call rotation.
- An engineer is moving into infrastructure and needs to build diagnostic instinct on real signals.
When it is not the right tool
- Managing or monitoring your own production infrastructure — VibeInfra runs disposable practice environments, not your systems.
- Video courses or certification exams: every lab is a live environment that grades the fix you actually applied.
Domains covered
Database & caching · Networking & edge · Async systems & streaming · Linux kernel & OS · Cloud infrastructure · CI/CD & deploy · Security · Observability · Kubernetes
Representative incidents
- Incident #37 - The Query That Never Finishes — Beginner tier (PostgreSQL, Slow Query Log, Indexes). Diagnose unindexed sequential scans on high-traffic orders tables causing connection pool saturation.
- Incident #21 - Checkout API Latency Regression — Advanced tier (Go, Redis, PostgreSQL, Docker Compose). Diagnose P99 latency spikes under 150 RPS baseline customer traffic breaching SLOs.
- Incident #29 - Replica Failover Gone Wrong — Expert tier (PostgreSQL, Streaming Replication, HA). Diagnose automated failover split-brain and verify replication LSN consistency on a 3-node cluster.
- Incident #43 - The Redirect Loop — Beginner tier (Nginx, HTTP Headers, Edge Gateway). Isolate HTTP 301/302 circular redirection loops at the edge proxy layer.
- Incident #23 - API Gateway 5xx Errors Under Load — Intermediate tier (Nginx, Reverse Proxy, Upstream Keepalive). Resolve intermittent 502/503/504 errors between edge reverse proxy and upstream services.
- Incident #33 - Internal DNS Resolution Flapping — Intermediate tier (DNS, dnsmasq, resolv.conf). Troubleshoot intermittent name resolution drops in microservice container environments.
- Incident #27 - Flash Sale Load Balancer Fleet Imbalance — Advanced tier (Nginx, Upstream Load Balancing, Health Checks). Diagnose traffic starvation across a 10-instance autoscaled backend fleet during traffic surges.
- Incident #45 - The Job That Runs Twice — Beginner tier (Worker Queue, Idempotency, Visibility Timeout). Fix duplicated background worker execution caused by visibility timeout expiration.
- Incident #24 - Background Worker Queue Meltdown — Advanced tier (Go, PostgreSQL, Async Workers, Deadlocks). Troubleshoot silent async email job processing stall while all services report healthy.
- Incident #36 - Kafka Consumer Group Falls Behind — Expert tier (Apache Kafka, Consumer Groups, Partition Skew). Diagnose consumer group partition skew and rebalance storms under peak event streams.
- Incident #56 - Zombie Processes Pile Up — Beginner tier (Linux Kernel, PID Allocation, Process Reaping). Diagnose PID table exhaustion caused by orphaned defunct child processes.
- Incident #31 - Disk Full: Silent Write Failures — Intermediate tier (Linux Filesystem, df, du, Unlinked Open Files). Recover from 100% disk usage and diagnose unlinked open file descriptors consuming disk space.
The full catalog of 30 published incidents and labs is at /labs/, and machine-readable at api.vibeinfra.id/api/v1/courses.
Frequently asked questions
- What is VibeInfra?
- VibeInfra is an incident-readiness platform for infrastructure engineers. It gives you production-like outage drills in disposable environments so you can diagnose, patch, and prove recovery before a real pager event.
- What open-source infrastructure tools does VibeInfra build?
- We build production-grade tools including ⚡ OneInfra (multi-cloud orchestrator), security-hardened Terraform & OpenTofu modules, Helm charts, interactive production flight simulators, and pre-configured Prometheus/Grafana monitoring stacks.
- How can I join the VibeInfra developer community?
- You can join our GitHub organization at github.com/ridwansswnto/vibeinfraid, practice interactive sandboxes at vibeinfra.id/labs/, subscribe to our weekly newsletter, and follow our technical publications.
- Is VibeInfra free and open-source?
- VibeInfra offers a generous Free Tier with foundational interactive labs, structured course chapters, open-source repositories, and technical documentation. Advanced P1 Flight Simulators and Verified Skill Certificates are available under our Pro Tier.
- How does VibeInfra evaluate incident resolution?
- VibeInfra runs automated multi-checkpoint evaluators against live container states across the canonical 7-step production incident lifecycle (traffic shedding, blast radius isolation, pool unclogging, root cause patch, queue drain, scale-up, and sustained zero-error loadgen).
For developers and agents
The catalog is a public, unauthenticated index. There is a REST API described by OpenAPI 3.1, an MCP server for AI agents, SDKs for JavaScript and Python, and agent-facing instructions at /agents.md and /llms.txt. Start at the developer portal.
About VibeInfra
About · Contact · Privacy · Pricing · Engineering blog · GitHub