Box: work that survives your laptop
A persistent cloud workspace that mounts your CelDrive bucket. Start a task, close the laptop, re-attach from any device — the session is exactly where you left it.
What it does
One command creates a small cloud server that mounts the same bucket your laptop mounts. No cloning, no syncing, no setup script — your files are simply there, because the Box and your Mac share a filesystem. Inside runs a persistent terminal session (tmux): builds, data jobs, long-running AI coding agents keep working after you disconnect.
✓ box created: 65.x.x.x (rclone + bucket mount + tmux, ~2 min)
$ celdrive box attach
→ persistent session. detach: Ctrl-b d — it keeps running
The feeling this delivers: your laptop stops being the ceiling. The heavy job runs on cloud cores against cloud files; your Mac is just the window. Close the lid mid-task; tomorrow, attach from the same Mac, a borrowed machine, or a tablet with an SSH app — mid-keystroke, same session.
Who it's for
- Developers: run builds, tests, and AI coding agents that outlive your terminal window. Your editor stays local; the horsepower doesn't.
- Analysts: kick off the long computation, go home, check the result from your phone.
- Anyone with a thin laptop: 4, 8, 16 GB of cloud RAM and dedicated cores, rented by the month for less than a coffee.
Honest framing: where it is today
- Bring-your-own-cloud. Today the Box runs in your Hetzner account with your API token (default size ~€4/month).
celdrive box setupwalks you through it in two minutes. Managed boxes — one click, on your CelDrive bill — are the roadmap. - Terminal-first. Attach is SSH/tmux today. VS Code Remote and a browser terminal are natural next steps; if you live in a GUI-only workflow, wait a release or two.
- Stopped ≠ free. A powered-off server still bills a few cents/day for its disk at Hetzner.
celdrive box destroydeletes it entirely — costs nothing, loses nothing, because your files live in the bucket, not the box. Recreate in ~2 minutes.
How it's different from Compute
Compute is job-shaped: send a build or an export, get the result back. The Box is place-shaped: a persistent machine that is yours, stays warm, and holds a live session. Compute is a courier; the Box is a second desk that happens to be in the cloud.