Deployed mode

BRING YOUR OWN CLOUD

You deploy your own clanking machine, in your own accounts, from your own repository. One file and one workflow, and it comes up. We hold nothing of yours.

Read the quickstart

How it comes up

  1. 01One file. A standard dev-container file per repository says what a workspace is; one fleet file per machine says which repositories it runs.
  2. 02One workflow. Your own CI runs our engine, pinned to a version you have read, under your permissions, with credentials only you hold.
  3. 03Your machine. The host, a workspace per engineer and the coordination gateway come up in your accounts.

Yours, not ours

We hold nothing of yours. Nothing to revoke: we were granted nothing.

YOUR ACCOUNTS

Compute, network, storage and secrets live in accounts you own. Secrets are named, never copied.

YOUR NAMES

Every workspace answers on your own domain, over your private network. No inbound path from us, no telemetry back.

YOUR PRODUCT

What runs in your cloud is a factory for your product, never one of ours. Every change is a run in your own CI.

Get started

The quickstart has the files and the workflow; what you need and what ends up in your state is on the bring-your-own-cloud page.

Want us to run it for you? Talk to us: [email protected]