microsandbox cloud is in private beta, and currently requires you to explicitly request access. If you already have access, you can get your API key from the dashboard.
msb CLI are the same ones you use locally: the same builders, the same commands, the same code. An API key is the only thing that changes; there is no URL, daemon, or extra configuration.
Same code, different backend
Everything from the quickstart works unchanged. With the API key exported, this creates a sandbox on cloud instead of your machine:msb doctor checks apply to the local runtime only.
REST API
The same key also authenticates the REST API directly, so you can manage sandboxes, volumes, and usage over plain HTTPS without an SDK. Command execution, file transfer, and SSH ride the sandbox command channel, which the SDKs and CLI handle for you.What to know
- Backend selection. The API key alone selects the cloud. For explicit control (forcing local, choosing in code, per-project profiles), see Backends.
- Compatibility. Almost the entire SDK and CLI surface behaves identically. The exceptions and their alternatives are listed on the compatibility page.
- Networking. Cloud sandboxes get a cloud-assigned hostname. SSH works through the same
msb sshand SDK SSH clients you use locally. - Images. Specify any OCI image on create; the cloud resolves and pulls it for you. Local image-cache commands don’t apply.
- Keys and billing. API keys, usage, and invoices live in the dashboard.
Next steps
Cloud compatibility
What works today, what’s limited, and what to use instead.
API reference
The REST API behind the SDKs, authenticated with your API key.
Backends
Force local, select in code, or switch with profiles.
Quickstart
New to microsandbox? Start here; everything carries over.