Pricing
Free today. Honest about tomorrow.
Free during the beta. Draft prices below, shown early.
Plans
Three plans, one of them live.
Not in effect. Only Free exists today, and it costs nothing. Hobby (€10) and Pro (€20) are draft prices per month, excluding VAT (yearly billing is cheaper per month), sized to cover the server. Free and Hobby limits are lower than today’s beta limits. They and the limits can change before anyone is charged.
Free Live
€0
during the beta
Hobby
€10
per month
Pro
€20
per month
Monorepo as one deploy
Custom domains
Priority support
Projects
Services per project
Memory per project (shared)
Deployments kept
DB · Redis
DB · PostgreSQL
DB · MySQL, MongoDB
Every plan: all languages, automatic HTTPS, secrets and deploy logs.
DB rows: whether the database fits the project's shared memory. An estimate from typical use, not a benchmark. “Small apps” means light traffic. “Tight” means it starts but can restart under load. Deploys that need more memory than a service can use stop with a clear message. MariaDB, Valkey and Memcached also run, but only through prongo.yaml, not as one-click presets.
| All limits (draft) | Free | Hobby | Pro |
|---|---|---|---|
| Projects | 1 | 3 | up to 6 |
| Services per project | 3 | 3 | 4 |
| Memory per project (shared) | 768 MB | 1.5 GB | 3 GB |
| CPU per service | 0.25 vCPU | 0.5 vCPU | 2 vCPU |
| Temporary disk per service | 512 MB | 1 GB | 2 GB |
| Database volume | 1 GB | 3 GB | 10 GB |
| Deployments kept | 20 | 200 | 500 |
| Memory per account (ceiling) | – | – | 4 GB |
Memory is shared by all services of a project, so a light service like Redis leaves room for a heavy one. CPU and temporary disk apply to each service separately. Temporary disk is scratch space and is cleared on every deploy. The database volume is persistent storage. Extra replicas count against the project maximum. Pro also has an overall ceiling of 4 GB of memory per account.
Looking ahead
Why a paid plan might show up.
Servers cost money every month, and this is a one-person project without outside funding. A fair paid plan is how it stays around.
Pay for the server, not for me
Any price covers the machines and the time to keep them healthy.
→ No profit-driven upsells.
A real free tier stays
Whatever plans exist, a useful free tier remains.
→ Small projects never need a credit card.
Plenty of notice
Beta users hear about paid plans well before they start.
→ No surprise charge, time to decide.
Revenue goes back in
Money funds capacity, faster builds and requested features.
→ The platform improves with its users.
Nothing is locked in. If you have thoughts on what a fair plan looks like, the feedback form in the dashboard reaches me directly.
In context
How the cost model compares.
Not a price sheet. This is how each option charges you, and how that grows.
What you actually pay for
Cloud servers, load balancers, and the hours to keep them healthy.
A per-seat subscription, plus usage-based add-ons that stack up.
One plan per account. Your whole monorepo is inside it.
Adding a database, worker, or second API
More manifests, same cluster bill.
Each is a separate paid product or external add-on.
A few more lines in the same file. No new bill.
Cost as the team grows
Flat. It tracks infrastructure, not headcount.
Per seat, so it climbs with every collaborator.
The aim is to track what you run, not who logs in.
Who runs the servers
You do.
They do.
We do.
Competitor details are general on purpose; their plans change often. For a feature-by-feature breakdown, see the comparison in the docs.
Questions
Quick answers.
Do I pay anything today?
No. Everything is free during the beta, with no card and no trial clock.
When do paid plans start?
There is no date. The plans and prices on this page (Hobby €10, Pro €20 per month, excluding VAT) are a draft, as is the cheaper yearly billing, and nothing here is in effect. You will get plenty of notice before anything changes.
Will the limits and plan names change?
Probably. These numbers are a draft, lower for Free and Hobby than today’s beta limits, and they will be checked against real load before anyone is charged. Nothing changes during the beta.
What happens to beta users?
The intention is a fair deal for early users, such as free months or a locked-in discount. It is not decided yet.
What about refunds and cancelling?
The draft policy is on the refunds page. It also applies only once paid plans exist.
Try it while it's free.
Connect a repo and see the whole thing deploy as one. No cost, no catch, during the beta.