Compatibility

microsandbox cloud is in private beta. This page was last reviewed on August 2, 2026. Capabilities that are limited or unavailable today are actively being worked on, and will move up this page as they become available on cloud.

Fully supported

The core workflow (create, execute, connect, persist) is identical on both backends.

Capability	SDK	CLI
Backend auto-selection	✅	✅
Sandbox: lifecycle (create, configure, list, inspect, reconnect, start, stop, restart, remove)	✅	✅
Sandbox: execution (exec, shell, streaming, interactive PTY)	✅	✅
Filesystem: guest access	✅	⚠️
Filesystem: copy from the host	✅	✅
Networking: policies and profiles	✅	✅
SSH: client sessions	✅	✅
SSH: SFTP (no dedicated CLI command)	✅	N/A
Logs: live follow	✅	❌
Volumes: create, mount, tmpfs (named volumes, tmpfs, manage)	✅	✅

Capability

SDK

CLI

Backend auto-selection

✅

Sandbox: lifecycle (create, configure, list, inspect, reconnect, start, stop, restart, remove)

✅

Sandbox: execution (exec, shell, streaming, interactive PTY)

✅

Filesystem: guest access

✅

⚠️

Filesystem: copy from the host

✅

Networking: policies and profiles

✅

SSH: client sessions

✅

SSH: SFTP (no dedicated CLI command)

✅

N/A

Logs: live follow

✅

❌

Volumes: create, mount, tmpfs (named volumes, tmpfs, manage)

✅

Capability	Use instead
Sandbox: disk snapshots	Named volumes for state that must survive sandbox replacement
Sandbox: force kill and drain	Graceful stop
Sandbox: ping and touch	N/A
Sandbox: modify and resize	Recreate with the new configuration
Sandbox: resource metrics	External monitoring of the workload itself
Logs: historical reads	SDK live follow, persisted externally
Images: cache management	Specify an OCI image on create; cloud pulls it for you
Networking: published ports	N/A
Networking: custom nameservers	Platform-managed DNS
Networking: TLS interception and host-CA trust	N/A
Volumes: host-side access to unmounted volumes	Mount the volume, then use the sandbox filesystem

Capability

Use instead

Sandbox: disk snapshots

Named volumes for state that must survive sandbox replacement

Sandbox: force kill and drain

Graceful stop

Sandbox: ping and touch

N/A

Sandbox: modify and resize

Recreate with the new configuration

Sandbox: resource metrics

External monitoring of the workload itself

Logs: historical reads

SDK live follow, persisted externally

Images: cache management

Specify an OCI image on create; cloud pulls it for you

Networking: published ports

N/A

Networking: custom nameservers

Platform-managed DNS

Networking: TLS interception and host-CA trust

N/A

Volumes: host-side access to unmounted volumes

Mount the volume, then use the sandbox filesystem

Limited

Capability	SDK	CLI	Guidance
Sandbox: duration and idle policies	⚠️	⚠️	Stop and remove sandboxes explicitly
Sandbox: custom hostname	⚠️	⚠️	Cloud assigns the hostname
Images: pull progress	⚠️	⚠️	Use normal create; cloud reports no per-layer progress
SSH: reusable server	⚠️	❌	SDK works with explicit key material; otherwise use `msb ssh`
Volumes: bind and disk-image mounts	⚠️	⚠️	Host paths resolve against your org’s host volume, not the machine running the SDK or CLI
Volumes: metadata	✅	❌	Use the SDK

Legend: ✅ available · ⚠️ limited · ❌ unavailable · N/A not applicable

Getting Started

Cloud

Sandboxes

Networking

Observability

Images

Troubleshooting

Fully supported

Not yet available

Limited

​Fully supported

​Not yet available

​Limited

Fully supported

Not yet available

Limited