Zero-config builds
Point Nimbus at a repo and it detects the stack, picks sane defaults, and builds. No CI archaeology, no pipeline YAML.
// v2.4 — edge deploys are live
Nimbus is the zero-config CLI that detects your stack, builds in isolated sandboxes, and deploys to the edge. No YAML. No dashboards. No babysitting.
$ nimbus init
// node 20 · pnpm · 12 edge regions
$ nimbus deploy prod
▲ building… done in 42s
live → https://api.acme.dev
$
$ curl -fsSL nimbus.dev | sh
$ ls features/
Three primitives replace your entire pipeline.
Point Nimbus at a repo and it detects the stack, picks sane defaults, and builds. No CI archaeology, no pipeline YAML.
Env vars are encrypted at rest and injected only into per-deploy sandboxes — never into logs, never onto disk.
Every release is immutable and pinned. nimbus rollback v1.4.1 puts yesterday's build back live in seconds.
$ man nimbus
From clone to live URL in three commands.
$ step 01
Run nimbus auth and pick your repo. One OAuth handshake and the CLI reads your stack in a single pass.
$ step 02
Push to main. Nimbus builds in a fresh sandbox with cached layers — median cold build: 38 seconds.
$ step 03
Every branch gets a live URL. Promote with nimbus release — or roll back a bad push instantly.
$ tail feedback.log
// "Nimbus deleted 400 lines of pipeline YAML. I got my Fridays back."
// "Cold deploy in 41 seconds. Our old pipeline needed eleven minutes and a sacrifice."
// "The first infra tool my whole team agrees on. The rollback command alone sold it."
$ nimbus plans
Every plan includes the full CLI. No feature is behind a dashboard.
hobby
$0 /forever
[RECOMMENDED]
pro
$19 /mo
fleet
$99 /mo
$ nimbus --help
No. Nimbus infers your stack straight from the repo. A nimbus.toml is optional and only needed for overrides.
Node, Go, Rust, Python, and static sites work out of the box. Anything with a Dockerfile deploys too.
In isolated, per-deploy sandboxes. Build secrets are injected at runtime and never written to disk or logs.
The CLI is MIT-licensed. On the Fleet plan the control plane ships as a single binary for private clusters.
The previous release stays live. The CLI prints the error and a one-line fix, then you retry with nimbus deploy --retry.
$ nimbus early-access
Join 4,200 engineers on the early-access list. We provision a CLI key the minute your email lands.