Question 1

What is a sandbox?

Accepted Answer

A sandbox is an isolated, fully managed compute environment where developers and AI coding agents can write, run, and test code without affecting production systems. Think of it as a disposable virtual machine spun up on demand.

Question 2

Can I run Docker inside a sandbox?

Accepted Answer

Yes. Full VM-based sandboxes support Docker, system packages, and background services. This makes them ideal for integration tests and workflows that mirror a CI/CD environment exactly.

Question 3

How fast do sandboxes start?

Accepted Answer

Tenki provisions sandboxes from custom images in under a second, including your tools and dependencies. Sandbox disks are mounted directly from our dedicated Ceph storage cluster instead of provisioned from the compute node’s local drive. This keeps provisioning fast for your own environment as well as our base images.

Question 4

Can I customize the environment with my own dependencies?

Accepted Answer

Yes. Define a typed template with your repository, dependencies, and build steps, then build it into a reusable image. You can also snapshot a running sandbox and start new sessions from that saved state. Templates do not currently accept Dockerfiles.

Question 5

What architectures and platforms are supported?

Accepted Answer

Sandboxes run full Linux VMs on x86 hardware, and the SDKs are available for macOS and Linux (including Apple Silicon). Multi-region availability keeps access low-latency.

Question 6

What happens when I pause or terminate a sandbox?

Accepted Answer

Pausing stops compute charges and preserves memory and durable files so you can resume later. Active connections close and /tmp is cleared; keep durable files under /home/tenki or on a volume. An idle timeout can pause non-sticky sessions automatically. Terminating ends the session permanently; saved snapshots and persistent volumes are managed separately.

Question 7

How does pricing work?

Accepted Answer

Usage is metered per second across CPU, memory, and disk. Pausing a sandbox stops compute charges. An idle timeout can pause non-sticky sessions automatically; a running sandbox continues to accrue compute charges until it pauses or terminates. The first 5 GiB of disk is included, and resource limits scale with your workspace plan.

Question 8

How do I connect to my sandbox?

Accepted Answer

Sandboxes support multiple connection methods including SSH, streamed shell output, and exposed preview URLs. Connections are tunneled securely, with no public IPs or open ports required.

Question 9

Is this a good fit for AI coding agents?

Accepted Answer

Full VM sandboxes are a great fit for agents that need to run tests, compile code, or interact with Docker. Every agent task gets its own isolated workspace, so agents can work with root access without ever touching your host machine.

Question 10

How do I get started?

Accepted Answer

Spin up your first environment in seconds with the TypeScript, Go, or Python SDK, or the CLI.

Compute	Per Hour	Per Second
CPUCore	$0.0504	$0.000014
MemoryGiB	$0.0162	$0.0000045
DiskGiB	$0.000108	$0.00000003

Full Linux computers
for your AI agents.

Prepare, run, pause, branch, share.

Start with your tools installed

A real VM, not a container

Pause and continue later

Branch from a checkpoint

Share a working preview

Keep data across sessions

Your custom image, running in under a second.

Owned end-to-end.

Mount the disk. Skip the copy.

Drive sandboxes from your terminal or code.

Pay for what runs.
Upgrade your workspace to raise limits.

Enterprise-grade security.

Hardware-isolated VMs

Wiped on teardown

Secrets never cross boundaries

Encrypted in transit

Don't believe us.
Believe them.

Questions? Answered!

Full Linux computersfor your AI agents.