Production-ready stacks.
One command.
An open registry of full-stack starter kits with auth, databases, Docker, and deployment — all verified by CI.
The problem
Every new project starts the exact same way. You spend days setting up authentication, configuring a database, wiring up payments, writing Docker configs, and wrestling with CI pipelines. By the time you're ready to write your actual app, you're already exhausted.
The openenv way
openenv is an open registry of production-ready starter kits powered by an ultra-fast CLI. Pick a stack, and we scaffold everything you need in seconds. Every kit comes pre-configured with:
- Working authentication (NextAuth, Supabase, JWT)
- Database with migrations (Prisma, Drizzle)
- Docker Compose for local dev
- Idempotent setup scripts
- Deployment-ready configurations
Production-ready starter kits
Stop reinventing the wheel. Start with a verified stack that includes auth, databases, payments, and deployment.
How it works
Every kit follows the same strict standard so you can trust it before you run it.
Verified by CI
Every kit is tested in CI before it reaches the registry. Setup scripts, health checks, and dependency installs are validated on every commit.
Docker by default
Each kit includes a pre-configured docker-compose.yml for databases, caches, and any infrastructure dependencies your stack needs.
Idempotent setup
Run the setup script as many times as you want. It handles migrations, seed data, and dependency installs without breaking.
Open specification
Every kit follows a strict, documented spec: kit.json for metadata, .env.example for variables, setup.sh for one-command bootstrapping.
A bulletproof CLI
Everything you need to manage your environments, built into a single fast binary.
openenv list
Browse all available kits from the registry directly in your terminal.
$ openenv list --tag saasopenenv init
Scaffold a kit into your project directory. Interactive by default.
$ openenv init saas-nextjs-supabaseopenenv doctor
Diagnose your local environment for Docker, Node, and port conflicts.
$ openenv doctor --fixopenenv deploy
Generate deployment configurations (Dockerfiles, CI/CD) instantly.
$ openenv deploy --provider renderThe Kit Specification
Every kit in the openenv registry adheres to a strict, open specification. This ensures predictability across all stacks.
- kit.jsonMetadata, dependencies, and health check definitions.
- .env.exampleFully documented environment variables required to run.
- docker-compose.ymlInfrastructure definitions (databases, caches).
- setup.shAn idempotent script that handles migrations and installs.
kits/saas-nextjs-supabase/ ├── kit.json ├── .env.example ├── docker-compose.yml ├── setup.sh ├── README.md └── template/ ├── src/ ├── package.json └── ...
What's next
We are constantly improving openenv. Here is our roadmap.
openenv add <feature>
Inject features (Stripe, Redis, Tailwind) directly into existing projects without scaffolding a full kit.
Custom GitHub Repositories
Run openenv init username/repo to scaffold from any public repository using openenv's robust checks.
Cloud Environment Sync
Securely pull secrets from Vercel or a centralized vault so you never have to copy-paste API keys.
Auto-provisioning
Native integrations with Vercel and Railway APIs to automatically provision live databases and hosting.
Get started in seconds
Install the CLI globally, then initialize your first project.
$ npm install -g Sparkyyy45/openenv$ openenv init
Open source
The registry, CLI, and all starter kits are fully open source. Contributions are welcome.