Pool sizing update
Three changes to the per-account pools, no model change. The pool contract from 2026-05-16 stays the same — what you commit across your apps is still the only thing that gets enforced.
| Tier | Apps | RAM | vCPU | Disk |
|---|---|---|---|---|
| Free | 3 | 512 MB | 0.5 | 1 GB |
| Starter | 10 | 1.5 GB | 1.0 | 5 GB |
| Maker | 20 | 4 GB | 2 | 25 GB |
| Pro | 40 | 10 GB | 4 | 75 GB |
Starter now sells a full 1.0 vCPU. The old 0.75 figure was an artifact of pool math, not anything you'd want to read on a pricing page. CPU isn't a hard kapacitetsgrind anyway (the kernel time-shares; throttling is monitored separately), so the right number to publish is the round one.
Disk pools were resized down on Maker and Pro. The previous 200 GB on Pro and 50 GB on Maker were aspirational — they didn't fit on the Hetzner VPS steps we actually run on once you add the platform, PocketBase sidecars, and a second customer to the box. The new numbers (25 GB Maker, 75 GB Pro) are honest against what the box can deliver, and the 3× progression Maker → Pro stays intact. Existing customers were all already below the new caps, so nothing changed for anyone live.
App caps doubled across the paid tiers. Starter goes 5 → 10, Maker 10 → 20, Pro 25 → 40, Free 2 → 3. The cap is still an anti-abuse backstop, not a multiplier into the pool — the pool is what actually limits resources. The previous numbers were lower than they needed to be for indie/maker accounts running many small sites.
Pricing page, plan selector, and pool widget all reflect the new numbers. If you're on Starter or higher, your pool ceiling moved or stayed; nothing in your deploys needs to change.