Ship it. Promote it. Sleep.

How shipping works

1. carlos ship — packs your working tree into a content-addressed release and uploads it. You get a canary URL serving exactly those bytes, immediately.
2. carlos promote — signs that release onto a channel. Production adopts the same bytes the canary served; nothing is rebuilt on the way.
3. Roll back by promoting the previous release. Releases are immutable, so going back is the same operation as going forward.

What you get

• Signed releases every release is signature-verified before a box will run it.
• Channels with bake time canaries pick a release up first; production holds until it has baked.
• Hibernation apps sleep when idle and wake on request — a sleeping app uses no compute.
• Custom domains, automatic TLS point DNS at Carloku; certificates are minted and renewed for you.
• Sign in with Keymail passkey-backed sign-in — no passwords, on the dashboard or the CLI.