# Free tier & pricing Every Koo account includes an always-free allowance: one web service, one Postgres database, and one Redis cache, each at 0.5 vCPU / 1 GiB. This page explains how the allowance works, what the paid plans add, and how a monthly bill is composed. ## Free, for life When you sign up, your account can run — at no cost, with no card on file: - - - Each runs at the **free unit**: 0.5 vCPU and 1 GiB of memory. There is no trial clock and nothing to cancel. > **Note:** > > This isn't a trial — the allowance never expires. Run the free services for a month or a decade; the price stays $0. ## How the free allowance works The allowance is a **price deduction, not a reserved shape**. Each free credit is worth the free unit (0.5 vCPU / 1 GiB) and attaches to one running service of its type. At billing time the credit deducts `min(price(free unit), price(service))` from that service's monthly line: - - You get one free service of each type, and it applies to your **largest running service of that type** — so the free share always lands where it saves you the most. If you run several services of a type, only the largest is covered; no line goes below $0. The credit is a monthly amount and doesn't carry over between periods. Paid plans keep the same allowance — upgrading never takes the free services away. Paid plans also include a **monthly compute credit**: a fixed dollar amount that comes off your compute bill after the allowance. See the _Monthly compute credit_ row in the comparison table below. ## Worked example: upsizing your free service 1. 2. 3. Today, the Free plan's resource ceilings cap at exactly the allowance, so step 2 requires a paid plan. Self-service upgrade from the console is rolling out (Coming soon) — until then, the Free plan lets you run the free-unit services but nothing larger. ## Compare plans Plans differ in [seats](/docs/collaboration/teams-and-roles), app and resource ceilings, features (custom domains, private apps, auto-deploy from Git), and log and metrics retention. Every number below renders live from the current pricing config: | Plan | Free | Plus | Pro | Enterprise | | --- | --- | --- | --- | --- | | Base price | $0 | $20/mo | $60/mo | $null/mo | | Seats included | 1 | 3 | 10 | 25 | | Projects | 1 | 10 | Unlimited | Unlimited | | Locations per service | 1 | 2 | 5 | 10 | | Free web service | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB | | Free Postgres | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB | | Free Redis | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB | 0.5 vCPU / 1 GiB | | Custom domains | — | 3 | 25 | 100 | | Auto-deploy from Git | — | Yes | Yes | Yes | | Priority support | — | — | Yes | Yes | | Log / metrics retention | 1 d | 7 d | 30 d | 90 d | ## Service resources & prices Every service picks explicit CPU and memory from a discrete ladder (memory up to 8 GiB per vCPU), with a predictable monthly price linear in CPU + memory. Some example combinations: | vCPU | Memory | Price | | --- | --- | --- | | 0.25 vCPU | 512 MiB | $5/mo | | 0.5 vCPU | 1 GiB | $10/mo | | 1 vCPU | 2 GiB | $20/mo | | 2 vCPU | 4 GiB | $40/mo | | 4 vCPU | 8 GiB | $80/mo | Pick any CPU + memory (memory up to 8 GiB per vCPU). Postgres and Redis price their compute the same way; disk is a separate volume provisioned with the service. | vCPU | Memory | Price | | --- | --- | --- | | 0.25 vCPU | 512 MiB | $5/mo | | 0.5 vCPU | 1 GiB | $10/mo | | 1 vCPU | 2 GiB | $20/mo | | 2 vCPU | 4 GiB | $40/mo | | 4 vCPU | 8 GiB | $80/mo | Pick any CPU + memory (memory up to 8 GiB per vCPU). ## What a monthly bill looks like Your bill has two parts. Your **subscription** — the plan's base price plus any seats beyond the plan's included count — is charged up front each period (monthly, or annually at about 17% off, applied to the plan and seat lines only). **Compute** is billed separately at the end of each month, in arrears: the monthly price of each running service × the fraction of the month it ran, minus the free allowance, then minus your plan's monthly compute credit. On the Free plan running within the allowance, compute works out to $0 — a real but no-charge invoice, nothing to think about, and no card required. You manage your plan and payment details from [billing](/docs/account/billing). ## FAQ ### Is it really free forever? Yes. The allowance is part of the pricing model, not a promotion — it has no expiry date and no usage clock. The free services keep running and keep billing $0 for as long as your account exists. ### What happens when I upsize? You pay only the difference above the free unit: the credit keeps deducting `price(free unit)` from the service's line no matter how large the service gets. Downsize back to the free unit and the service is fully covered again. ### Does a second account get free services too? No. Free credits attach to your **primary account** — the first account created for you at signup. Any additional accounts you create pay list prices from their first service. This is what lets the allowance be unconditional on the primary one. ### Do I need a credit card? No. Signing up and running the free allowance requires no payment method. You add one only when you move to a paid plan or run services beyond the allowance. ### What are the limits? The comparison table above lists each plan's ceilings — apps, seats, resources, retention, and features. Separately, abuse limits exist and are enforced: services used for cryptomining, attacks, or other resource abuse are suspended per the [acceptable use policy](https://koo.io/legal). Ready to claim the allowance? Deploy your first app in the [quickstart](/docs/get-started/quickstart).