Credits

Credits are a single balance in euros that covers everything nemu meters for you. Your tokens are never part of it. Model usage is billed through the provider key you configured, and credits cover the work nemu does around it.

​

What you get

Credits are granted with your plan and reset at the start of each billing period. They do not roll over. The balance and the period it belongs to are shown under Quotas in the console.

​

What draws from it

An hour of actively building costs about €0.039, and seven web searches cost about the same. A chat that searches a few times is a rounding error next to a build that runs all afternoon.

​

How the Computer is metered

Two things are measured, and only while the machine is awake. Provisioned memory is the memory your project is allocated, which is 2 GB on every project. It is billed for as long as the container is running, whether it is compiling or idle, because the memory is reserved either way. Active processor is the processor time the container actually consumed, sampled from the container itself. Idle is close to nothing: a project sitting behind an open tab uses about five thousandths of one percent of a core, so leaving a preview up is effectively free. A cold page compile is roughly 1.7 cores for twenty seconds, and that is the part you are paying for. The machine sleeps three minutes after the last thing that touched it. Sleeping stops the meter completely. A project that exists but is not running draws nothing at all, so there is no reason to delete a project to save credits. A wake is billed for at least one minute of memory, which is €0.0003. Processor time has no minimum and is billed as measured.

​

The off peak rate

Between 00:00 and 08:00 UTC the processor rate drops by a quarter, from €0.10 to €0.075 a vCPU-hour. The hours are fixed, they are UTC, and they are the same for everybody, so you can work out what a build will cost before you start it. It applies to the processor only. Memory is billed at the same rate at every hour of the day, so an overnight preview is never charged more or less for being overnight. The discount is on work you can choose to move, not on a machine sitting still. The rates in the table above are the highest rates there are. Nothing is ever billed above them, and there is no surcharge of any kind.

​

Keeping a preview awake

Always awake in the Publish dialog exempts a project from the sleep timer and the session limit, so it runs continuously and is metered continuously. At the memory rate that is about EUR 0.02 an hour, so EUR 10 of Starter credit is about twenty days of it. Nothing else changes. When the balance reaches zero the machine stops like any other, and the setting stays on for the next cycle.

​

What you can spend

€10 of starter credit buys about 100 vCPU-hours of processor at the standard rate, which is the ceiling on what one project can consume before the balance stops it. That is deliberate: the processor meter is also what keeps one runaway project from occupying a machine indefinitely. Indexing a website does not draw from credits. It runs on the model you chose in your own workspace, so it lands on that provider’s bill like any other request.

​

What does not

Model tokens. Prompts and completions go to whichever provider you connected, on your own key, and never touch this balance. That separation is the point: credits pay for machines and retrieval, your provider bill pays for thinking.

​

When it runs out

Metered work stops. The agent will say so rather than failing quietly, and chat keeps working for anything that does not draw credits. A session already running is allowed to finish and then sleeps at its normal timeout rather than being cut off mid build; the next start is refused until there is a balance again. Nothing is deleted, and the balance returns at the start of the next period. Upgrading raises the allowance immediately. Related: Computer for what the machine actually does.