Last updated: October 17, 2026
Servers: from US$2 a month asleep, never more than always on
A typical month: about US$2.25 for one 512 MB server that is awake 5% of the time (about 36 hours) and asleep the rest. A server that gets a request every few minutes never sleeps and pays the always-on rate, US$7 a month.
A server's price depends on its size and on whether it is asleep or awake — per server per calendar month, the same in every region:
Size | vCPU (shared) | Asleep (base) | Awake, or always on |
|---|
512 MB | 1 | US$2 | US$7 |
1 GB | 1 | US$2 | US$12 |
2 GB | 2 | US$2 | US$25 |
4 GB | 2 | US$2 | US$46 |
8 GB | 4 | US$2 | US$92 |
| Details |
|---|
Price | A server that sleeps when idle is billed by the second: its size's asleep price while it is asleep and its size's always-on price while it is awake (the table above). Each calendar month's price is spread over that month's own seconds; as the awake price is the always-on price, no second costs more than the same server kept always on, and a month costs between the two prices — for 512 MB, US$2 asleep all month and US$7 awake all month (the examples below). Part of a month costs that part: 10 days of a 30-day month at 512 MB cost US$0.67 asleep, US$2.33 awake |
Awake | From a request that wakes the server until it is back asleep, a few minutes after the last request — a single request keeps it awake for a few minutes, and requests every few minutes (an uptime monitor, for example) keep it awake all month, at the always-on price. lavela's own requests wake it too (the check that a new deploy answers, a health check you ask for). Awake time is the time lavela's metering observes the server running; time it does not observe is billed asleep, with no minimum per wake |
Size | Every account can run 512 MB (1 shared vCPU) — the only size while an account has just the welcome credit: before its first paid top-up, and again once every paid top-up has been refunded in full, until the next one (a bigger server already running then keeps running, but must be changed to 512 MB before it is redeployed). After your account's first paid top-up, choose any size when you deploy, or change a server's size later: billed by the second from the change (the server restarts). Back to 512 MB any time, with no top-up (a stopped or paused server must be started first, and a running build of its service must finish first) |
Sleeps when idle | When nobody is using it, a server sleeps and wakes on the next request (a short start-up delay). Asleep time is billed — the server still exists — at its size's asleep price |
Always on | Optional: the server never sleeps (no wake-up delay) and pays its size's always-on price (US$7 a month for 512 MB) every second, billed the same way; switch it back to sleeping and it is billed as a sleeping server from then. Either way, a server you stop is not billed, and a server lavela pauses is not billed while it stays paused (below) |
Builds | Included — up to 60 builds a month for each server (at least 60 per account) and at most 10 builds per account per day (UTC months and days), each up to 30 minutes, one build of a service at a time. With only the welcome credit: 20 builds a month in total, each up to 10 minutes, until a paid top-up. Where lavela offers it, a build beyond the included ones that you start in a way that shows you its price first is not refused: it starts and is billed by the second (a "billed build") at a per-minute price that is listed here once lavela offers billed builds, from your balance (from the welcome credit if that is all you have) — up to 60 more a month for each server, 40 more with only the welcome credit. A billed build's price will not go above US$0.01 per minute unless you accept a later version of the Terms. A billed build starts only in a way that shows you its price first; a build beyond the included ones that is started in a way that shows no price first (for example with the command-line tool, or by uploading a folder in the browser, including from a deploy link that your agent gives you) is refused and not billed. A billed build does not start if your balance does not cover the build's time limit at that price, or if you have an unpaid amount. A billed build that fails only because lavela's own build machine or image storage failed, or that is cancelled because its project was deleted, is not billed; one that fails for another reason or reaches its time limit is billed. Once the included builds are used (and the billed ones too, where offered), further builds are refused until the count resets; a build past its time limit is stopped. A build that fails only because lavela's own build machine ran out of disk space or memory does not count toward the included builds (up to 10 such builds in any 24 hours) |
Region | New servers run in Tokyo. A server run from an image can be placed in another available region when it is created, and a server attached to a disk runs in that disk's region; builds always run in Tokyo (a server keeps its region when redeployed, unless a different disk is attached) |
What a server that sleeps when idle costs in a month
It depends on how long it is awake. For example, a whole month at each size (hours and days of a 30-day month):
Size | Awake 5% (about 36 hours) | Awake 30% (about 9 days) | Awake all month (= always on) |
|---|
512 MB | US$2.25 | US$3.50 | US$7.00 |
1 GB | US$2.50 | US$5.00 | US$12.00 |
2 GB | US$3.15 | US$8.90 | US$25.00 |
4 GB | US$4.20 | US$15.20 | US$46.00 |
8 GB | US$6.50 | US$29.00 | US$92.00 |
The console shows each server's range, what it has cost so far this month and — once it has a day of billed time this month — the share of its billed time this month billed at the awake rate (awake, or kept always on); your AI agent sees the same in lavela.project_overview.
What is billed, and what is not
- Billed: every second a server exists — at its size's asleep price while it sleeps, and at its always-on price while it is awake or set to be always on.
- Not billed: a server you stop — it can't be reached until you start it again — and a server lavela pauses or stops (for example when your balance runs out and the grace period ends) while it stays paused or stopped; no server is billed while your account is paused.
- A pause that does not take effect: if a server lavela paused keeps running while your account is active, the time lavela's metering observes it running is billed as awake time, at its size's always-on price.
- Deleting a server ends its billing, but a disk attached to it stays — and keeps being billed — until you delete the disk or its project. Deleting a disk ends that disk's billing, and deleting a project ends the billing of its servers and disks.
- One-off and scheduled jobs are billed by the second while they run, at the 512 MB always-on price (US$7 a month), whatever the size of the server they belong to. A one-off job still running after about three minutes continues on its own 512 MB server, which is billed like a server — at the asleep price once the job has ended — until it is deleted.
- Data transfer out of your servers is billed by use, by the region the traffic leaves from: US$0.023 per GB in North America and Europe, US$0.046 per GB in Asia-Pacific (Tokyo included), Oceania and South America, US$0.138 per GB in India and Africa. It includes responses to visitors and, where lavela offers it, the data your servers send on their own (files they upload to other services, calls they make to other services); traffic between your own servers on lavela's private network and data used while building are not billed.
- Disks (persistent volumes) cost US$0.1725 per GB per month for as long as the disk exists — whether or not its server runs, including while the server is stopped. A disk keeps its files across restarts; it is not a backup service.
- A server's own files are not kept. What an app writes to its server's own disk (a SQLite file, uploaded images) is erased on every redeploy, restart and sleep. Keep data in a database or on a disk.
- Managed ads (where offered): a commission of 10% of the month's ad spend in the ad account lavela set up for you (every campaign in it, including any you run there yourself), charged to your card once a month — the ad spend itself is paid to the ad platform.
- Managed Postgres databases need a funded account (the welcome credit alone can't create one) and have no usage charge. Free within these limits per database: 0.5 GB storage, 100 compute-hours a month and 5 GB of data transfer a month (10 branches, previews included). Past the compute or transfer allowance the database pauses until next month; past the storage cap, writes fail. Your data is kept. lavela takes no backups of a database, so keep your own dumps. lavela no longer creates new managed Redis: use a Redis URL from your own provider.
- There is no subscription and no monthly platform fee. lavela takes 0% of your own sales — your customers pay you through your own Stripe account.
Paying
- Everything is paid from a prepaid balance in US dollars. Top-ups start at US$10. A card issued in the United States or Canada pays lavela directly, and so does a card issued in South Korea where lavela offers it, with 10% Korean VAT added to the charge and shown before you pay (a US$10 top-up is charged US$11; the full US$10 is credited; a Korean card needs overseas payments turned on by its issuer). Where lavela offers it, funds can also be added through Stripe's Link checkout, which adds your country's tax on top. No top-up fee; paid balance does not expire.
- Card bonus: an account that holds the welcome credit earns a one-time US$2 more, added to it, when it saves a card that pays lavela directly while credit is left, or makes a paid top-up of US$10 or more with such a card — whichever comes first. For such a card it is once per card (a credit or debit card that has not earned it on another account; lavela stores a hashed fingerprint of the card to check — Privacy 2.9). It is promotional credit: used first, compute only, not refundable. See Terms 6.5A. Larger top-ups earn no extra credit.
- Automatic top-up (cards that pay lavela directly, where enabled): it is never turned on by a switch that is already set to on. Where the console's card window shows a box that names automatic top-up and the level and amount it would use, that box is required to save a card in that window and also turns automatic top-up on; everywhere else you turn it on yourself (a button on a card form, the unticked box on the Add funds screen, or a confirmation in the console). You can turn it off with one click at any time, including right after you save. You choose the balance level (US$1–US$100) and the amount added each time (US$10–US$100; a card issued in South Korea, where lavela offers it, is charged that amount plus 10% VAT); at most 3 attempts a day. There is no fixed monthly limit: if a month's automatic charges would grow beyond the larger of US$100 and 1.5 times what your running servers cost for a month (for a new payer, the larger of US$100 and that same monthly cost), it pauses and emails you, and continues when you confirm. A charge that needs your bank's confirmation is canceled if it is not confirmed within 72 hours. See Terms 6.6.
- Welcome credit: an eligible new account gets a one-time US$3 credit — about two weeks of one 512 MB server that is always on or always awake, and up to about one and a half months of one that sleeps almost all the time — after accepting the Terms and confirming its email, one per person (who is eligible). It is compute-only, runs the 512 MB size, is not refundable, and data transfer draws from it too.
- Refunds: unused paid balance is refundable on request — see Credits & Refunds.
When the balance runs out
- At a low balance we email you (unless an automatic top-up is already on its way to refill it).
- When the balance runs out we email the exact time your servers will stop; they keep running for 48 hours (or stop right away instead, if the unpaid amount during that time grows beyond US$5 or half of your paid top-ups after refunds, whichever is larger), and we remind you about 12 hours before that time. With only the welcome credit, that time is at lavela's cost, up to US$1 in total (past that your servers stop right away and we email you why); with a paid balance, it may take the balance below zero, settled from your next top-up (an automatic top-up included). Some accounts stop without a grace period (Terms Section 7.1). A payment dispute is different: it can stop your servers at once even with balance left, and hold your whole balance until it is resolved (Terms Section 7.3).
- At the end of the grace period your servers stop — not billed while they stay stopped.
- Stopped servers are kept — with their disks and data — until you delete them; lavela does not delete them automatically. Their disks keep being billed while they exist, so delete what you no longer need. One exception — an account that has used only the welcome credit: lavela removes the machine of a server that stopped because the credit ran out, or that you stopped yourself and have not started since, 7 days after it emails you (a server you stopped yourself counts only after it has been stopped 14 days); settings, image and variables are kept 30 more days, and adding funds and pressing "Start again" recreates the server. A server with a disk is never removed this way (Terms 7.1(4)). (An account still on the older monthly card plan follows that plan's schedule instead: after a failed monthly payment its servers are suspended, and deleted with their data 30 days after the failure if it stays unpaid — Terms 6.13.)
A top-up that brings your balance back above zero before the stop keeps your servers running. The full rules are in the Terms of Service (Sections 6 and 7) and the Credits & Refunds Policy; if this page and the Terms differ, the Terms control, except that for the per-minute price of a build beyond the included ones the rule of Terms Section 6.2 applies: if the price shown to you before the build starts and the price on this page when the build starts are not the same, the lower of the two applies to that build — in every case never more than US$0.01 per minute, unless you accept a later version of the Terms.