A resource, Usage Billing, or both
A resource is fixed capacity shared by everything on it. Usage Billing bills each workload per second. Most teams save the most by combining them - here are five common setups, priced out. For teams that moved to Miget, see the stories.
Scenario 1 SaaS: production on a resource, staging on Usage Billing
Production stays on a flat monthly plan because it runs all month. Staging only needs to be there when someone is testing against it.
Scenario 2 Traffic spikes
A 72-hour sale needs more web capacity, not a bigger plan for the other 362 days of the year.
Scenario 3 Agency with client sites
Twelve small client sites, each a 512 MiB web plus a 512 MiB Postgres, packed onto one resource. Their staging copies run separately, on Usage Billing.
Scenario 4 Nightly jobs
A cron job runs at its own size on the resource it belongs to, and draws on that resource's included cron minutes before it costs anything extra.
Scenario 5 Side project or internal tool
No resource at all - just Usage Billing, sized for what it actually is.
The $5 monthly minimum counts toward this, and a workspace spend limit caps what it can grow to.
Want this for your own bill?
Send us your current platform and monthly bill, and we will price it on Miget, line by line. Free, no commitment.
Pick the mix that fits, from the plans page.
See every resource size and the full Usage Billing rate card, or start on the free tier and decide later.