Bivvy scans your project, detects your tools and runtimes, and generates a declarative config that gets your team running with zero friction. Customize it, version it, and use it anywhere you or your teammates go.
$ curl -fsSL https://bivvy.dev/install | sh
Define your entire dev environment in a single, readable .bivvy/config.yml file. Version it, share it, forget about it.
A polished terminal experience with progress indicators, prompts, and helpful error messages. Setup that feels good.
Node, Python, Ruby, Go, Rust, and more. Bivvy speaks your stack's language and handles dependencies gracefully.
Point bivvy at a project and it scans your machine for installed tools, runtimes, and services - then generates a config to match. Run it again and it only does what's needed.
Bivvy reads your project's .bivvy/config.yml and walks through each setup step interactively. Dependencies, environment variables, databases, services - all handled.
Templates, watches, dependencies, workflows. One file, version-controlled.
# .bivvy/config.yml steps: ruby: template: bundle-install check: type: change target: "Gemfile.lock" node: template: yarn-install check: type: change target: "yarn.lock" db: command: "rails db:prepare" depends_on: [docker]
Changed Gemfile.lock? Ruby step is stale. Didn't change it? Skip.
❯ bivvy status ⛺ myapp — Status Environment: development (default) Steps: ✓ brew 2h ago ⚠ ruby stale ✓ node 2h ago ✓ docker 2h ago ◌ db never run
When something breaks, context-aware suggestions. Not "figure it out yourself."
✗ ruby failed: bundle install exited 1 How do you want to proceed? [r] Retry - run the step again [f] Fix - bundle update nokogiri [s] Skip - continue without this step [x] Shell - drop to shell to debug
Built-in support for popular runtimes and package managers
Source maps in production. Secrets baked into build output. Debug symbols shipping to users. These aren't edge cases - they're what happens when your build environment drifts and nobody checks the artifacts.
Bivvy ships with built-in audit templates for Node, Rust, Python, Go, Java, .NET, Docker, Ruby, PHP, Elixir, and Swift.
They run as post-build safety gates - automatically checking your /dist for source maps, .env files, debug symbols, and hardcoded secrets before anything gets published.
steps: deps: template: npm-install build: template: vite-build depends_on: [deps] audit: template: node-artifact-audit depends_on: [build] inputs: dist_dir: dist # Catches source maps, .env files, # secrets in JS/JSON, node_modules # in dist, and TypeScript source leaks.
Bivvy gets you running right away and keeps things consistent with smart, shareable, idempotent configs.
Get started →