From idea to running POC, one command.

blissful-infra is built for fast POCs on enterprise-shape infrastructure. One command and the plumbing is gone. Compose files, ports, networks, observability and a CI pipeline are generated for you. What you get back is a real Kafka, real Postgres, real Jenkins, real Grafana stack on your laptop, ready to validate the experiment in your head.

npm install -g @blissful-infra/cli
blissful-infra start my-app

Under a minute later your stack is running. Prove out the idea, throw it away, prove out the next one. No cloud account, no billing surprise.

Why I built this →

Built for POCs. Real infrastructure underneath.

Off the boilerplate

The plumbing is handled. One command scaffolds compose, ports, networks, schemas and a fresh git repo.

Observability (Prometheus scrape, Grafana dashboards, Loki, Tempo) is wired in from the start. Jenkins pipeline pre-configured. Local Docker registry pre-allocated. AI agent connected over MCP.

The POC is the first thing you touch and not the last.

Closer to the infrastructure

The pieces are real. Real Kafka, real Postgres, real Jenkins. Nothing is mocked when an OSS equivalent exists.

Config files are plain (docker-compose.yaml, Jenkinsfile, application.yml). Read them, modify them, fork them. Watch a consumer group actually rebalance. Inspect a JWT round trip. Profile a JPA cascade.

When the POC raises a question about the architecture, the answer is right there in the repo.

The system handles the parts you do not want to think about. The infrastructure underneath stays real, so the POC tells you something true.

Choose your path

One toolchain. Pick the entry point that matches what you are trying to do.

Build

POC-first. You have an architecture experiment or a product idea you need to validate. One command to a real stack you can pull apart. Skip the wiring, prove out the idea today.

Start the Build path →

Learn

Go deeper. Students, new grads and engineers who want to understand how production systems work without an AWS bill. A guided course through Kafka, Postgres, Keycloak, CI/CD and observability. The same stack real teams run.

Start the Learn path →

Deliver

Per client. Indie studios and small teams running multiple client projects on one laptop. Per-client isolated stacks with their own Kafka, Postgres, observability and CI. No SaaS bill stacking up per client.

Start the Deliver path →

Curious why blissful-infra runs real open-source services instead of bundling managed-service emulators? Read the philosophy →

What gets created

Running blissful-infra start my-app scaffolds a complete project directory and boots all services:

Service	URL	Purpose
Frontend	http://localhost:3000	React + Vite app served via nginx
Backend API	http://localhost:8080	Spring Boot REST + WebSocket API
Dashboard	http://localhost:3002	blissful-infra management UI
Grafana	http://localhost:3001	Pre-provisioned dashboards (metrics, logs, traces)
Prometheus	http://localhost:9090	Metrics scraping from /actuator
Tempo	http://localhost:3200	Distributed tracing (view traces inside Grafana)
Jenkins	http://localhost:8081	CI/CD pipelines (admin/admin)
Kafka	localhost:9092	Event streaming message bus
Postgres	localhost:5432	Primary relational database
Redis	localhost:6379	Cache layer (with postgres-redis)
Loki	localhost:3100	Structured log aggregation
Registry	localhost:5050	Local Docker image registry

Your sandbox, your rules

blissful-infra runs entirely on your laptop. Docker Desktop is the only external dependency. There are no cloud accounts to set up, no Kubernetes clusters to provision, no YAML to hand-write, and no per-hour costs ticking up while you work.

Spin up a project, experiment with the architecture, blow it away, and start fresh. The entire stack is isolated, reproducible, and disposable on demand. Everything that would normally require a DevOps team, service discovery, observability wiring, CI/CD pipelines, database migrations, is handled for you, and it all runs offline.

Deploy in two commands

Build locally. Ship with one more command.

# Build your sandbox
blissful-infra start my-app

# When you're ready to go live
blissful-infra deploy
# → Live at https://my-app.blissful-infra.com

Your local stack maps automatically to Cloudflare’s edge infrastructure, no config changes, no cloud account to set up. The same blissful-infra.yaml that defines your local environment defines your production one.

Local service	Hosted equivalent
React + Vite frontend	Cloudflare Pages
Express / Go backend	Cloudflare Worker
Postgres	Cloudflare D1
Redis	Cloudflare KV
Kafka	Cloudflare Queues

Vercel and AWS deploy targets are coming. Follow along on GitHub →