Side by side
| GitHub Codespaces | Uno | |
|---|---|---|
| What it is | A cloud dev environment. A codespace is created from a repository, a branch or a template | A Linux computer with root and Docker, plus sites, storage and Uno AI |
| It runs in | A Docker container on a virtual machine, with limited access to the VM host | Firecracker microVM, one per computer, root inside |
| Compute price | 2 core $0.18, 4 core $0.36, 8 core $0.72, 16 core $1.44, 32 core $2.88 an hour | A flat plan: Small $5, Plus $20, Pro $70 |
| Storage price | $0.07 per GB a month. Storage is billed for as long as the codespace exists | 40 GB of disk and 100 GB of cloud storage on Plus, in the price |
| Free quota | GitHub Free: 120 hours and 15 GB a month. GitHub Pro: 180 hours and 20 GB. The table counts a 2-core machine as 2 included hours for each hour it runs, so 120 hours is 60 hours of a 2-core codespace | The free account covers sites and forms; a computer starts at $5 |
| Sizes | From 2 cores, 8 GB of memory and 32 GB of storage up to 32 cores, 128 GB of memory and 128 GB of storage | From 1 vCPU and 1 GB to 32 vCPU and 48 GB |
| When idle | Stops after 30 idle minutes by default; you can set it between 5 minutes and 4 hours. Compute is billed while the codespace is active, including the idle minutes before it times out | Asleep after 10 minutes; memory and running programs are saved while it sleeps |
| Longest run | A codespace stops after 12 hours of use, even if you are working in it | No session time limit |
| After a stop | Stopping keeps your saved files; the docs do not promise running programs or memory | Disk kept, and memory and running programs are saved while it sleeps |
| What deletes it | A stopped codespace that stays inactive is deleted after 30 days by default, even with unpushed changes; you can set it from 0 to 30 days | You delete a computer; cloud storage stays when you do |
A month of work, Codespaces against Uno
Whole-month cost in $ per month for 160 active hours: 8 hours a day for 20 days, before any free quota. Codespaces memory is bigger than the Uno plan next to it.
Show as a table
| Option | $ per month | Shape |
|---|---|---|
| Uno Plus, 4 vCPU · 4 GB | 20 | Flat price, sleeps when idle, keeps memory |
| Codespaces, 4 cores | 57.60 | 160 hours at the 4-core rate, storage left out |
| Uno Pro, 16 vCPU · 16 GB | 70 | Flat price, sleeps when idle, keeps memory |
| Codespaces, 16 cores | 230.40 | 160 hours at the 16-core rate, storage left out |
How we counted
We took 160 active hours: 8 hours a day for 20 days, because a codespace bills only while it is active. A 4-core codespace: 160 × $0.36 = $57.60. A 16-core one: 160 × $1.44 = $230.40. The free quota would take off up to 120 core-hours on a free GitHub account. Storage at $0.07 per GB a month is left out. Uno is flat, whether the agent works 160 hours or all night.
Two different jobs
Codespaces is where you edit code: it starts from a repository and a dev container, and it is happy to be thrown away and rebuilt for the next branch. Stopping keeps your saved files; the docs do not promise running programs or memory. An Uno computer is where code runs for a long time, or where an agent works while your laptop is closed.
For a bot, an overnight agent or a staging server, the 12-hour stop is the wall. You can restart a codespace and the files are there; the docs promise the files, not the programs.
Where pay-per-hour wins
Hourly billing is cheap for short sessions. Uno Plus at $20 equals about 56 active hours on a 4-core codespace at $0.36 an hour. Someone who codes a few hours a week stays under that line, and a free GitHub account covers 60 hours of a 2-core codespace for nothing.
Where Uno is worse
- Under about 56 active hours a month, a 4-core codespace costs less than Uno Plus, and a free GitHub account has a quota before you pay anything.
- Codespaces is part of GitHub: it opens a branch in VS Code or the browser with a dev container, and the repository is the starting point. Uno is a machine; your repository is something you clone into it.
- Codespaces offers more memory per core and sizes up to 32 cores and 128 GB. The largest Uno computer is 32 vCPU and 48 GB.
- Codespaces suits teams: an organization can pay for its members' codespaces and set the idle timeout and retention for all of them. A Uno plan belongs to one account.
- Our vCPU are shared, not dedicated, and paid plans run in one region today: Netherlands.
A machine that outlives the session, from $5 a month
Every plan is a Linux microVM with root and Docker. Pick the size; move up or down any time.
Small
A Telegram bot, a VPN, a small backend
$5/ month
- 1 vCPU · 1 GB
- 15 GB disk
- 25 GB cloud storage
- 5 boosts a month
Plus
Agents that work with your laptop closed
$20/ month
- 4 vCPU · 4 GB
- 40 GB disk
- 100 GB cloud storage
- Uno Work in the cloud
Pro
A product in production, a second MacBook
$70/ month
- 16 vCPU · 16 GB
- 120 GB disk
- 300 GB cloud storage
- Speed of a MacBook Air M4
Max
A team and many agents at once
$200/ month
- 32 vCPU · 48 GB
- 300 GB disk
- 1,024 GB cloud storage
- 5 public IPv4
Add Uno AI to any plan: 40 h of AI work a month on Small, 100 h on Plus, unlimited on Max. Today: GLM-5.3 Flash and MiMo v2.6 Pro. Or sign in with your own Claude or ChatGPT.