Blade Cloud
On-demand cloud dev environments with Claude Code pre-installed.
Overview
Blade Cloud lets you spin up isolated dev environments from any device — phone, tablet, or browser. Each instance runs in its own isolated VM with a full Linux kernel, Claude Code pre-installed, and full terminal capabilities.
No computer needed. Create an instance, connect, and start coding with Claude Code in seconds.
Creating an Instance
Create a new cloud instance from the web client or CLI:
From the Web
- Sign in at bladeterm.com/sign-in
- Click New Instance
- Optionally enter a Git repository URL to clone
- Select a region (US-East, EU-West, or Asia-Pacific)
- Click Create — your instance boots in seconds
From the CLI
Instance Specs
| Resource | Spec | Notes |
|---|---|---|
| CPU | 2 vCPUs | Claude Code is I/O bound, not CPU bound |
| RAM | 4 GB | Node.js + Claude Code + shell + headroom |
| Disk | 20 GB | OS + tools + workspace + scrollback |
| Network | 1 Gbps shared | WebSocket is low bandwidth |
Instance Lifecycle
Instances follow a lifecycle that balances availability with cost efficiency:
| State | Billed? | Description |
|---|---|---|
Running | Yes | Instance is active. PTY connected, WebSocket live. |
Hibernated | No | Memory + disk preserved. Resumes quickly. |
Stopped | No | Instance exists but not running. |
Terminated | No | Everything deleted. Workspace gone. |
Workspace Persistence
Your workspace persists across hibernate and resume cycles:
- Git repos — Specify a repo URL when creating an instance. It's cloned into
/workspaceon first boot and preserved across sessions. - Files — Any files you create or modify persist until the instance is terminated.
- Terminal history — Scrollback buffer is preserved across hibernate/resume.
- Environment variables — Your API keys and env vars are stored securely and injected on boot.
Billing
Every plan includes cloud hours. You're only billed while instances are in the Running state.
| Plan | Included Hours | Overage Rate | Monthly Price |
|---|---|---|---|
| Free | 5 hrs/mo | N/A | $0 |
| Blade Pro | 25 hrs/mo | $0.08/hr | $8/mo |
| Blade Ultra | 100 hrs/mo | $0.06/hr | $24/mo |
Usage tips to save credits:
- Let instances auto-hibernate when you're done (no action needed)
- Manually hibernate if you know you're stepping away
- Hibernated instances cost nothing — only running time counts
- Check your usage on the account page
Security
Every cloud instance is fully isolated:
| Layer | Protection |
|---|---|
| VM isolation | Each instance runs in its own isolated VM with a dedicated kernel |
| Network isolation | Instances can reach the internet but cannot see each other |
| Disk encryption | Storage encrypted at rest |
| Auth | JWT-authenticated API + device token WebSocket auth |
| Relay auth | Relay proxy validates authentication + session ownership before routing |
| Termination | All data (disk, memory, snapshots) destroyed on instance termination |
Connecting
Connect to a running cloud instance from:
- Blade desktop app — Connect via
blade cloud connect <instance-id> - Web browser — Use the web terminal client to connect from any browser
- Mobile — Open the web client on your phone or tablet
The connection goes through the Blade relay proxy, which routes your WebSocket to the correct VM. The VM runs blade serve internally — the same protocol as local multiplayer.
Regions
| Region | Location | Endpoint |
|---|---|---|
| US-East | Virginia, US | cloud-us.bladeterm.com |
| EU-West | Frankfurt, DE | cloud-eu.bladeterm.com |
| Asia-Pacific | Singapore | cloud-ap.bladeterm.com |
If you don't specify a region, the nearest one is selected automatically based on your IP address.
Pre-installed Software
Every cloud instance comes with:
- Node.js 22 LTS
- Claude Code CLI (
@anthropic-ai/claude-code) - Git, curl, build-essential
- Blade Terminal (
blade serverunning as daemon)