A sandboxed machine where the agent
builds, runs and hosts your app.
Ask for something in a chat and the agent does the work in a container: it writes the code, installs dependencies, runs the build and serves the result at its own address on nemu.page. Nothing runs on your laptop.
Available on Starter and above. The Free plan does not include the Computer.
- 2 GB
- the same machine on every project
- 3 min
- after the last touch, it sleeps and the meter stops
- about €0.039
- for an hour of actively building
The agent installs, builds and serves on the machine itself.
The machine is attached to a chat. When you ask for something that needs to run, the agent runs it there instead of handing you code to run yourself.
Install packages
Dependencies land in the project on the machine. Nothing is installed on your laptop.
Scaffold with a framework CLI
For a stack no template covers, such as Astro, it runs the framework's own CLI in an empty container.
Run builds and tests
It reads the output it produced, which is also what it checks when you say something is broken.
Read and write files
Edits you make in the editor are the same files it reads, so it picks them up rather than overwriting them.
Serve a live preview
A development server that stays up at its own address, private until you say otherwise.
Call the internet
Any public address through the machine's proxy. Private and internal addresses are blocked.
bunnodenpmgitcurlopensslpython3One size
2 GB
Every project gets the same machine, sized for a development server. There is nothing to pick and nothing to approve halfway through a build.
If a command runs out of memory, the agent says so and retries with a smaller step. It will not ask you to pay for a bigger machine, because there is no bigger machine.
Memory and processor time, metered while the machine is awake.
The model doing the work runs on your own provider key, so your provider bills those tokens. The Computer meters two things, and only while the machine is awake.
- Provisioned memory
- €0.01per GB-hour, at any hour
- Billed for as long as the container runs, compiling or idle, because the memory is reserved either way.
- Active processor
- €0.10per vCPU-hour
- The processor time the container actually consumed, sampled from the container itself. Idle is close to nothing.
- Processor, 00:00 to 08:00 UTC
- €0.075per vCPU-hour
- A quarter lower. Fixed hours in UTC, published in advance and the same for everybody.
What the units come to in practice
One page compile
Roughly 1.7 cores for twenty seconds
about€0.0009
An hour awake, being viewed, building nothing
Close to the memory rate alone
about€0.02
An hour of actively building with the agent
Memory plus the processor it burns
about€0.039
The same building hour, 00:00 to 08:00 UTC
The processor part is a quarter lower
about€0.034
Seven web searches cost about the same as an hour of building, so a chat that searches a few times is a rounding error next to a build that runs all afternoon.
The off peak rate
UTC
- Processor, 00:00 to 08:00 UTC
- €0.075
- Processor, the other hours
- €0.10
- Memory, every hour
- €0.01
Memory is never discounted
An overnight preview costs what a midday one costs. The discount is on work you can choose to move.
Prepaid, with no overage
The meter can only spend credits you already have, and there is no surcharge above these rates.
Estimate what a month of the Computer would cost.
Move the sliders to describe how you would use it. Every figure is computed from the published rates, so treat it as an estimate rather than a quote.
Installing, compiling and editing with the agent.
The processor costs a quarter less in those hours.
Someone has it open. That costs close to the memory rate alone.
Kept up round the clock with Always awake.
Estimated for a month
60 hours awake and metered
Where it goes
- Memory
- €1.20
- Processor
- €0.71
Leaves about €8.09 for search, page reads and research, or about 1,348 web searches.
Uses the modelled building hour, about €0.039, or €0.034 between 00:00 and 08:00 UTC, and €0.02 for an hour awake without building. Your real processor time is measured and will differ. Count each hour in one slider only.
The machine sleeps when nobody is using it.
The machine sleeps 3 minutes after the last thing that touched it. Nothing is metered while it sleeps, and the project keeps its files.
One project on Starter, minute by minute
- Session by plan
- Starter 30 min
- Pro 30 min
- Max 60 min
- Enterprise 120 min
1Nobody opens the link
You stop working at minute 10. It sleeps 3 minutes later and the meter stops.
2Someone has the link open
The visitor keeps it awake, but it still stops 30 minutes after you last worked on it.
3You come back and work again
Working at minute 32 starts the clock again, so it stops at 62 instead of 40.
Want one to stay up anyway? Always awake exempts a project from both the sleep timer and the session limit, for about €0.02 an hour. See Publish
If the host is full, new starts wait in a queue.
There is a fixed amount of memory across every project running at once, so a start can arrive when there is no room for it.
It waits in line
A start that finds no room holds a place in order and begins as soon as another project sleeps. If no room appears within 20 seconds, it says the machine is at capacity.
Nobody is pushed off
A project already running is never stopped to make room for somebody else's, and that includes your own.
A refusal names the project
At your plan's limit for projects running at once, a start is refused and the message names the project to stop first.
What Starter shows, with a sample project running
Your plan runs one project at a time. Stop totals first, or move to Pro for two.
Choose who can open a preview and whether it stays awake.
Publish sets who can reach a preview and whether it is exempt from sleeping. Change it with /publish in the composer or from the toolbar.
You, in the Computer panel
Publish
Who can open it, and whether it stays awake.
Someone opening your link
This preview is private
Sign in with your nemu account to open it. Only people with access to the project can view or wake it.
Sign in with nemuPick a setting on the left to see what a visitor gets.
Private until you share it
Every project gets its own address at
<project>.nemu.page. Public and Password links need Pro or above.Traffic does not change the bill
A visitor keeps the machine awake at close to the memory rate, about €0.02 an hour. A hundred people cost about what one does.
Kept out of search
Previews carry noindex and nofollow, so a shared link stays out of search results and a crawler cannot keep it awake.
Each template starts with its toolchain installed.
The agent picks the template from what you asked for. Every template except workspace starts with its dependencies installed, so the agent goes straight to writing your code.
nextDefaultNext.js 16, TypeScript, Tailwind CSS 4
viteReact, TypeScript and Tailwind CSS 4 on Vite
apiA TypeScript HTTP API on Bun with Elysia
pythonPython 3 with uv and FastAPI
rustRust stable with cargo and axum
goGo with a standard library HTTP server
cppC++20 with clang, CMake and Ninja
staticPlain HTML, CSS and JavaScript on nginx
workspaceAn empty Node and Bun container, for anything else
Project notes carry over from one chat to the next.
The agent keeps short private notes about each project: what it built, bugs and their real causes, and decisions you made. It reads them before it starts work in a later chat.
The notes are stored in your account, not on the machine, so they survive the project being moved or the host being replaced.
The Computer reads only its own notes for that project. To let it read what your coding agents saved on your own machines too, share a Context project with it in the console. Sharing is read only and can be undone. Privacy and control
Project notes · totals
PrivateBuilt
Totals dashboard on the next template. The CSV is parsed in lib/parse-csv.ts and charted in components/totals-chart.tsx.
Bug
The chart was empty because the export starts with a byte order mark. Strip it before parsing the header row.
Decision
Amounts stay in cents until display. Months are grouped in UTC, as the person asked.
Every paid plan gets the same machine. Higher plans run more at once.
Every paid plan gets the same 2 GB machine. What changes is how many projects you keep, how many run at once, how long a session lasts and how many credits arrive each period.
| Limit | Free | Starter | Pro | Max | Enterprise |
|---|---|---|---|---|---|
| Price | €0 | €7.99 a month | €19.99 a month | €59.99 a month | on request |
| Credits each period | none | €10 | €25 | €90 | unlimited |
| Projects | none | 3 | 10 | 25 | unlimited |
| Running at once | none | 1 | 2 | 3 | 4 |
| Session length | none | 30 min | 30 min | 60 min | 120 min |
| Hours of building | none | about 250 | about 640 | about 2,300 | unlimited |
| Total disk | none | 8 GB | 25 GB | 60 GB | unlimited |
| Public and password previews | no | no | yes | yes | yes |
Hours of building is your credits divided by a modelled building hour, so it is an estimate rather than an allowance. Credits also pay for search, page reads and research. The Computer is not part of the free plan. Compare every plan
Ask for something that needs to run.
Open a chat and the agent creates the project on its own. There is no setup step and nothing to install.