Kubi vs Cua
These two are not really competitors, which is the useful thing to know. Cua is the software: an open framework, a driver that scores near the top of the public benchmarks, and a bench to measure your agent with. Kubi is the machine the software needs. Cua ended its own hosting on 2026-10-18, so running Cua means bringing a computer, and a screen is one way to do that.
Where Kubi stands out
Three differences that decide most choices between Kubi and Cua.
A machine, today, with nothing to operate
Cua's framework is yours to install, run and patch on hosts you rent. A screen arrives as a desktop with browsers, a computer-use API and a hosted MCP server, for $20 a month.
Cua stopped hosting on 2026-10-18
The question is no longer which hosted product to pick. It is which machines you point Cua's driver at, or whether you want a desktop that already has an API.
A person can take the mouse
Kubi adds the part a framework cannot: a live view in a dashboard, Take control with a clear 409 to the agent, and a view-only link for someone who should only watch.
The two products
Kubi
Kubi rents Linux desktops to AI agents. Each screen is its own virtual machine with 4 vCPU, 8 GB of memory and a 50 GB disk, Debian with a GNOME desktop and two browsers. An agent sees the screen, clicks, types, runs commands and moves files through one API, a TypeScript SDK or a hosted MCP server. A person watches live and takes control with one click. A persistent screen runs until you stop it, at one address with its disk kept, for $20 a month at the founding price. A disposable one runs by the minute for $0.035 an hour.
Cua
Cua builds open-source computer-use software: a driver that gives a model a screen to act on, an SDK, an MCP server, and Cua Driver Bench, the task set most public driver comparisons use. Its driver scores at or near the top of those comparisons, including on datasets Cua did not run. It is software, not a machine: you supply the computer, whether that is a laptop, a VM you rent, or a desktop from somebody like us.
Side by side
What each offers for a 4 vCPU, 8 GB machine, from Cua's own pages on 2026-11-12.
| Kubi | Cua | |
|---|---|---|
| What you get | A running desktop, priced per screen | Open-source software you run |
| Machine | 4 vCPU, 8 GB, 50 GB disk, its own VM | Whatever you give it |
| Hosted computers | That is the product | Hosting ended 2026-10-18 |
| Left on a month, 4 / 8 | $20 founding, $25 list, running or stopped | Your host's price, plus your time |
| Desktop | GNOME desktop, Chromium and Firefox | Whatever you install |
| Computer-use API | Screenshot, act, exec and files over one API | Its driver and SDK, open source |
| MCP | Hosted MCP server with sign-in per screen | An MCP server you host |
| Take control | Live view and Take control; agent calls wait | Not its job |
| Benchmark | We publish what we measure | Cua Driver Bench, the public task set |
| Who operates it | We do | You do |
What it costs
Four common jobs, each priced from the public price lists with the cheapest plan that runs it.
| Job | Kubi, a month | Cua, a month |
|---|---|---|
| One agent that never stops4 vCPU, 8 GB, running all month | $20 | EUR 30.49 and upA server to run it on, plus your setup |
| One agent on workdays8 hours a day, 22 days, files kept | $20Persistent; disposable would be $7.82 | EUR 30.49 and upBilled while the machine exists |
| Evals and short runs100 runs of 30 minutes a month | $1.75Disposable, by the minute | Your own fleetCua Bench runs them; you supply the hosts |
| Ten agents, always on10 machines of 4 / 8 all month | $200 | EUR 304.90 and up |
Kubi. Persistent screens are $20 a month each at the founding price ($25 list), running or stopped. Disposable screens are $0.035 an hour by the minute: 176 hours running and 554 stopped is $7.82; 50 hours is $1.75.
Cua. Cua's software is free and open source, so its cost is the machines and the work: a 4 vCPU, 8 GB server is about EUR 30.49 at Hetzner or $48 at DigitalOcean, and on top of that you install the desktop, the driver and the plumbing, then keep them running. Cua's own hosted computers ended on 2026-10-18.
Limits to know
- Cua is the better software to point at a problem; this page is about where it runs, not whether to use it.
- A Kubi screen has no GPU, is Linux only, and takes no inbound connections.
- Cua's driver preinstalled is one of Boat's selling points, not ours: on a screen you install it yourself.
Which one should you use?
Use Cua when
you want the driver, the SDK or the bench, and you already have machines or want to own that layer.
- Open source
Read it, change it, pin it. Nothing about your agent depends on our uptime.
- The public task set
Cua Driver Bench is what most driver comparisons use, which makes your numbers comparable to other people's.
- Any machine
Your laptop, your cloud, your customer's hardware.
Use Kubi when
you would rather rent the computer than operate a fleet, and you want a person able to step in.
- Nothing to run
The desktop, the API and the MCP server are ours to keep alive.
- Priced per screen
$20 a month at the founding price, or $0.035 an hour by the minute.
- They work together
Install Cua's driver on a screen if you want its loop on our machine.
Questions people ask
Is Cua an alternative to Kubi?
Can I run Cua's driver on a Kubi screen?
Does Kubi use Cua?
Where do these numbers come from?
Sources
Read on 2026-11-12. Prices change: if a number here is out of date, write to support@trykubi.com and we fix it.










