1 GB of memory, awake all month
The memory part of a small app that never sleeps.
- Memory1 GB × 730 h × €0.0076
- €5.55
- Total
- €5.55
ry usage
Pay for usage.Not for plans.
Pay as you go from prepaid credit in euros. Memory while awake, CPU while it computes, storage by the gigabyte.
For businesses and freelancers. All prices excluding VAT.
| What | Price | How it is counted |
|---|---|---|
| Memory | €0.0076 per GB-hour | Only while the machine is awake. A sleeping machine keeps its memory as a snapshot, billed at the snapshot rate. |
| CPU | €0.035 per vCPU-hour | Active CPU time only. A vCPU-hour is one vCPU busy for one hour; idle time is not charged. |
| Disk (volumes) | €0.10 per GB-month | The volumes your machines and computers keep their data on, and the data and history a Postgres database occupies. |
| Object storage (S3) | €0.022 per GB-month | S3-compatible buckets. |
| Snapshots and templates | €0.08 per GB-month | The memory snapshot of a sleeping machine, for the time it sleeps, by the machine's memory size. Saved snapshots, and the templates new sandboxes start from. |
| Paused sandboxes | €0.08 per GB-month | First 5 GB per team free, kept 30 days. |
For businesses and freelancers. All prices excluding VAT.
Introductory pricing until 31 January 2027. Any increase is announced at least 30 days in advance.
Credit you buy is valid for 12 months and is not refundable.
€100starting credit, valid for 90 days, with a GitHub account at least 30 days old or a saved card
Prepaidat zero, machines stop and your data stays
Includedbuilds, TLS and domains, outbound transfer, team members
Per machinea database, a computer and a sandbox are billed as the machine they run on
Included
Included at no charge.
- Builds on our builders
- TLS certificates and custom domains
- Outbound data transfer
- Team members, as many as you like
These never draw on your credit. Fair use applies.
Postgres and sandboxes
They are machines too.
A Serverless Postgres database and a sandbox each run as a machine, and they are billed like one: by memory, CPU and disk, at the prices above. There is no separate price for a database or a running sandbox; a database pays compute only while it is awake, and storage for the data, the history and the sleep snapshot it keeps. It sleeps after 5 minutes without connections by default; you can turn sleep off per database. A paused sandbox pays only for what it stores, memory and disk, at the rate for paused sandboxes above.
Examples
What that comes to in a month.
Examples, computed from the rates above. They are not plans or bundles; you pay for what actually runs.
A month counts as 730 hours (24 × 365 ÷ 12). Amounts are rounded to the cent.
A 4 GB computer for a working month
Awake 8 hours a day on 22 working days (8 h × 22 days = 176 h), using 0.5 vCPU on average while awake. Memory and CPU only.
- Memory4 GB × 176 h × €0.0076
- €5.35
- CPU0.5 vCPU × 176 h × €0.035
- €3.08
- Total
- €8.43
A small Postgres, awake all month
1 GB of memory, 0.05 vCPU active on average, and 10 GB of data and history at the disk rate.
- Memory1 GB × 730 h × €0.0076
- €5.55
- CPU0.05 vCPU × 730 h × €0.035
- €1.28
- Disk10 GB × €0.10
- €1.00
- Total
- €7.83
Storage for a month
A 20 GB volume, 100 GB in a bucket, and a 10 GB template.
- Disk20 GB × €0.10
- €2.00
- Object storage100 GB × €0.022
- €2.20
- Snapshots and templates10 GB × €0.08
- €0.80
- Total
- €5.00
Estimate
Your month, from the real prices.
Pick what you run. The estimate uses the prices above and shows its working. Start from an example or set every field yourself.
Starting credit
€100 to start, if you qualify.
Sign up with a GitHub account at least 30 days old, or save a card, and you start with €100 of credit, valid for 90 days. Credit you buy stays valid for 12 months.
A personal invitation does not earn it by itself. Other accounts start at zero: they can sign in, create keys, read and top up, and they start machines after their first top-up. The starting credit is spent first.
Limits
What a team can run.
| Computers | 2 at a time in a team made in the console |
| Apps | 10 at a time, computers included. Databases backing apps, sandboxes and previews do not count. |
| Sandboxes | 100 running at once |
| When reached | The next create answers 403 with org-limit-computers or org-limit-apps. What you have keeps running; waking never counts. Contact us for more. |
Credit
What happens to your balance.
Prepaid means no invoice arrives for more than you loaded. It also means you should know what happens at zero.
- Balance
Usage is drawn as it runs
Memory while awake, CPU while computing, storage per gigabyte. Read the balance over the API or in the console.
- 20 %
Warned
At 20 percent of the reference top-up (your auto-recharge amount, otherwise your last top-up) the account carries
warned, and the console shows it. - Auto-recharge
Topped up for you
Set a threshold, an amount from €10 to €500 and a monthly ceiling up to €2,000. A failed charge is retried after 15 minutes.
- Zero
Machines stop. Your data stays.
Disks and volumes stay and keep being charged. Reads keep working: logs, lists and the console still answer. Starting or creating something answers
402withcredit-blocked. - Top-up
Everything starts again
A top-up or an automatic recharge lifts the block, and the machines the block stopped are started again.
Top up
An admin of the team tops up in the console under Usage & billing: a one-time card payment from €10 to €1,000, or auto-recharge. Card details are entered on the payment provider's page and never reach Rytiv.
Top-ups cannot be made over the API or with the CLI. Those routes take only the console's signed proof of an admin, so a key, and the agent that holds it, can never spend your money on more credit (billing-console-only).
Read your balance
Three read-only routes: the balance, the ledger and a priced preview of a period. A key narrowed by scopes cannot reach them; an agent key can read them.
curl "https://api.rytiv.com/v1/billing/credits" \ -H "Authorization: Bearer $RYTIV_TOKEN"
const res = await fetch("https://api.rytiv.com/v1/billing/credits", { headers: { Authorization: `Bearer ${process.env.RYTIV_TOKEN}` }, }); const { balanceCents, blocked, warned } = await res.json();
import os, requests account = requests.get( "https://api.rytiv.com/v1/billing/credits", headers={"Authorization": f"Bearer {os.environ['RYTIV_TOKEN']}"}, ).json() print(account["balanceCents"], account["blocked"])
ry usage ry usage --from 2026-10-01T00:00:00Z --to 2026-11-01T00:00:00Z
Questions
Pricing, answered.
More in the billing docs and limits and quotas.
Do I need a company to use Rytiv?
No. Rytiv is for anyone acting commercially or as a freelancer, so a solo developer with a business is as welcome as a team. You do not need a VAT ID or a company name to sign up.
Are there plans, tiers or seats?
No. Every account pays the same prices from prepaid credit. Team members are included, as many as you like.
What does a database, a computer or a sandbox cost?
Each runs as a machine and is billed like one: memory while awake, CPU while computing, and what it stores. A base computer has 2 vCPUs, 4096 MB and a 100 GB home disk; it shuts down after 10 minutes without activity, and while it is shut down only the home disk is billed, as a volume.
What does a sleeping app cost?
No CPU and no memory rate. A machine up to 2048 MB sleeps with its memory, kept as a snapshot and billed at the snapshot rate for the time it sleeps. A larger machine stops instead and boots cold; while it is stopped only its volumes are billed. An app sleeps only if you give it a sleep rule.
What happens when my credit runs out?
Your machines stop and your data stays. Disks and volumes keep being charged, reads keep working, and anything that would start or create something answers 402 with credit-blocked. A top-up starts the stopped machines again.
Will I be warned before that?
Once the balance falls to 20 percent of your last top-up or your auto-recharge amount, the account carries warned and the console shows it. With auto-recharge, the balance is topped up at your threshold.
Can my agent spend money or top up?
It can spend credit by running machines, like any key. It cannot top up: top-ups and auto-recharge are console-only, and an API key answers 403 with billing-console-only. An agent key may read the balance.
How do I see what I spent?
ry usage shows metered usage with prices and the total, line by line. Over the API: GET /v1/billing/preview and the ledger at GET /v1/billing/ledger.
Can I run more than 2 computers or 10 apps?
Those limits apply to every team made in the console, also after a top-up, and are checked only when something is created. Contact us at support@rytiv.com for more.
Do prices include VAT?
No. All prices are in euros and exclude VAT.
Will prices change?
These are introductory prices, as stated under the table. An increase is announced at least 30 days in advance; a reduction needs no notice.
Where does it run?
In the EU. Your apps, databases and files are stored and run only in the EU, and a machine never leaves the region it was created in. See security and data.
Start small, pay for what runs.
Top up when you need more, or set auto-recharge with a monthly ceiling. At zero, machines stop and your data stays.
claude mcp add --transport http rytiv https://api.rytiv.com/v1/mcp --header "Authorization: Bearer <your key>"