Zero-Config Runtime
No daemons, no YAML soup. One static binary that boots in 40ms and speaks pure POSIX.
ASCII art banner spelling NIMBUS in block characters.
One 9MB binary. Zero config drift. Nimbus compiles your whole stack — pipelines, secrets, rollbacks — into a single auditable command line.
core: nimbus-kernel v2.6.0 online
uplink: 40Gb/s mirror handshake complete
vault: 0 leaks // 0 drift // 0 excuses
root@nimbus:~$
No daemons, no YAML soup. One static binary that boots in 40ms and speaks pure POSIX.
AES-256 vault compiled into the core. Keys never touch disk — injection happens in-memory only.
Every push is an immutable signed snapshot. Rollback is one command: 300ms flat, zero drama.
$ step-01 --install
Pull a 9MB static build from any mirror. No package manager, no root, no ceremony.
$ step-02 --init
Nimbus derives the full dependency DAG and compiles a deploy plan you can actually read.
$ step-03 --ship
One command pushes an immutable snapshot. Watch the diff stream live in your terminal.
<kernl> replaced 4,000 lines of terraform with one 12-line plan file.
<kernl> i don't trust computers. i trust this one.
<mira_0x> rollbacks so fast my pager got bored and quit.
<mira_0x> uptime streak: 214 days and counting.
<dvorak> the deploy log reads like a novel. a short one.
<dvorak> every chapter ends "ACCESS GRANTED".
solo scripts & side quests
$0 /mo
teams shipping daily
$29 /operator/mo
fleets, SLAs & air-gaps
$99 /mo
Yes. 9MB, statically linked, zero runtime dependencies. If it fits on a floppy's ghost, it ships.
In an AES-256 vault compiled into the core. Secrets are injected into memory at deploy time — never written to disk, never printed to logs.
Fully. Host the mirrors on bare metal inside your perimeter; the binary never phones home.
On MAINFRAME, yes: "nimbus relay init" and the whole plane is yours, audit trail included.
Run "nimbus revert" — the last signed snapshot is restored in ~300ms. Then "nimbus doctor" names the exact layer that lied.
Operator keys are minted in batches. Drop a valid address and yours rides the next uplink window.
~/nimbus/access/request.sh
Operator keys are minted in batches. Leave a valid address and we'll drop yours on the next uplink window.