Terminal
codaracloud ssh dev
Opens the box in tmux. If the connection drops, run it again and you are back in the same session.
Codara Boxes · Beta
Codara Boxes are persistent Linux machines that live next to your apps on Codara Cloud. Connect from a terminal, VS Code or Zed, let Claude Code or Codex keep working when you close your laptop, and come back to the same home folder.
Included in Starter, Standard, Pro and Scale, from €5/month before tax · In beta
# on your computer$ codaracloud boxes create dev --project website --env staging --wait$ Box created: dev in my-workspace/website/staging (hel1)$ Status: Running$ Connect with: codaracloud ssh dev$ codaracloud ssh dev# in the box, tmux session main$ claudeCoding agents work for minutes or hours. On a laptop they stop when the lid closes or the connection drops, and every machine needs its own setup. A box is a Linux machine in the cloud, inside one of your projects, that keeps your code, your settings and your agent sign-ins between sessions.
Start a task, disconnect and come back later. A busy box stays awake for up to 24 hours after your last connection, and tmux keeps your session.
A box belongs to a project environment, like your services, and reaches that environment’s databases from inside Codara Cloud.
Add up to 10 members of your organization to a box, so a teammate can pick up where you or your agent left off.
How it works
01
From the console (Boxes, then New box) or the CLI. Pick a project, an environment and a size.
$ codaracloud boxes create dev --project website --env staging --wait02
Opens a shell in a tmux session called main. The first time, the CLI creates an SSH key and registers it for you.
$ codaracloud ssh dev03
Claude Code and Codex are installed. Run one and sign in with your own account; the sign-in stays in your home folder.
$ claude04
A box has no public address. Forward a port and open the dev server on your own computer.
$ codaracloud boxes forward dev 3000Every box starts from the same Codara image, with the usual development tools installed and nothing signed in.
Sizes
Or set CPU and memory yourself, up to your plan’s largest box. Mini is enough for one Claude Code session.
One command writes an SSH host for the box, so the tools you already use connect through Codara.
$ codaracloud boxes ssh-config devcodaracloud ssh dev
Opens the box in tmux. If the connection drops, run it again and you are back in the same session.
codara-dev
Install Remote - SSH, run Remote-SSH: Connect to Host and choose this host.
zed ssh://codara-dev/home/codara
Opens the box’s home folder in Zed.
With the next Studio release: choose New remote workspace (SSH), find the box under Codara Cloud boxes, and Studio wakes it and connects.
A box that nobody uses goes to sleep and frees its CPU and memory for your apps. Connecting wakes it again, often in a few seconds; when Codara has to start a new server, it takes several minutes.
Or choose anything from 5 minutes to 24 hours, and put a box to sleep yourself at any time.
A build or an agent run keeps the box awake for up to 24 hours after your last connection. After that it sleeps when idle, so a forgotten box never runs forever.
codaracloud boxes keep-awake holds a box awake for 1 to 24 hours.
Kept while it sleeps
Gone when it stops
You get sudo inside the box, and the box runs in its own gVisor sandbox on servers reserved for boxes. There is no public address to protect: every connection goes through Codara with your sign-in and an SSH key registered to your account.
gVisor gives each box its own application kernel between your code and the server. A box that cannot run in the sandbox is refused, never started without it.
A box has no public address. SSH reaches it only through Codara’s tunnel, and your key works nowhere else.
A Codara sign-in with access to the box, checked again every few seconds while you are connected, and an SSH key registered to your account.
HTTP, HTTPS, DNS and your environment’s databases. Port 22 and port 25 are closed; git over SSH to GitHub, GitLab and Bitbucket goes through port 443.
Codara does not sign in to Claude Code, Codex or GitHub for you. Sign-ins live in the box’s home folder.
Boxes run in Helsinki, Finland, on Hetzner Cloud.
Pricing
Boxes share your plan’s CPU and memory while they are awake, and its storage for as long as they exist. Prices do not change: Starter €5, Standard €20, Pro €50 and Scale €100 a month before tax.
5 boxes
10 boxes
30 boxes
50 boxes
Boxes opened to every plan on 16 October 2026 and are in beta, like the rest of Codara Cloud. Know these limits before you rely on one.
A box’s home folder is not part of Codara’s backups and is deleted with the box. Push your work to git.
Boxes are available in Helsinki, Finland.
Codara updates can end your SSH connection; reconnect and tmux is still there. Server updates can restart a box, which stops its processes and tmux sessions. /home is always kept.
If a process needs more memory than the box has, the whole box restarts, not just that process. /home is kept; resize the box for heavier work.
Members share one user with root and can read the whole home folder, including agent sign-ins. Do not put production credentials in a box.
A connection closes after 60 minutes without data.
What a box is, what it costs and what to know before you rely on one.
A persistent Linux machine in the cloud that belongs to one of your Codara Cloud projects. You connect over SSH from a terminal, VS Code or Zed, and everything in its home folder is kept when it sleeps. Boxes are included in Starter, Standard, Pro and Scale, in beta.
No. Each plan includes a number of boxes at no extra price: Starter 5, Standard 10, Pro 30 and Scale 50. They use your plan’s CPU and memory while awake and its storage while they exist. If box homes need more storage, extra storage costs €0.12 per GiB per month before tax.
Yes. Both are installed in every box. Connect, run claude or codex and sign in with your own account; Codara does not sign in for you. The sign-in is stored in the box’s home folder, so it survives sleep. A Mini box (0.5 vCPU / 1 GiB) is enough for one Claude Code session.
Yes, while the box is busy. A box that is using CPU stays awake for up to 24 hours after your last connection, and codaracloud boxes keep-awake holds it awake for 1 to 24 hours. After that it sleeps when idle, so a forgotten box does not run forever.
Everything in /home stays: code, shell history, tools installed there and sign-ins. Running processes and tmux sessions stop, and packages installed outside /home are gone; list them in ~/.codara/startup.sh to install them again at every start.
No. A box’s home folder is not backed up and is deleted with the box. Push your code to git and keep a copy of anything else you cannot lose.
You, and up to 10 members of your organization that you add to it. Organization owners and admins can see, resize or delete a box but cannot connect unless they are added. Everyone who connects shares one user with root, so only add people you trust.
No. A box has no public address. To preview a dev server, forward its port to your computer with codaracloud boxes forward; only you can reach it while the command runs.
Request beta access. Codara Boxes come with every plan, from Starter at €5 a month before tax.