Compute on Miget no longer has one shape. Buy a resource and share its CPU and RAM across every app, worker and database on it, the way Miget has always worked - or put a workload on Usage Billing and pay for the seconds it actually runs, no resource underneath it at all. A workspace can run both at once, and an app on a resource can scale past its plan, with the extra replicas billed by the second.
Three ways to pay for compute
- On a resource. A flat monthly plan. Every app, worker, database and cron job on it draws from the same CPU and RAM, and none of them adds a fee of its own.
- Usage Billing. No resource. Each app, service, bucket or stack is billed for what it reserves while it runs, by the second, with no minimum per run.
- Both. Keep a resource and put other workloads on Usage Billing in the same workspace, or let an app on a resource scale past its plan - replicas beyond the first are billed by the second instead of needing a bigger plan.
The choice is made once, when a workload is created, and does not change afterward - an app stays on its resource or on Usage Billing for its life.
What it costs
Usage Billing rates, for a full month of running:
| Resource | Rate |
|---|---|
| RAM | $5.00 / GiB |
| CPU, shared (Hobby) | $8.00 / vCPU |
| CPU, dedicated (Pro) | $24.00 / vCPU |
| Storage | $0.15 / GiB |
| Object storage (buckets) | $0.02 / GiB, for what it holds each hour |
There's a $5/month minimum, and only in a cycle where nothing else on the subscription - no resource, no seat, no add-on - costs more than a cent. Past that, Usage Billing charges automatically once a cycle's usage crosses a threshold, rather than waiting for the renewal: $25 the first cycle, or $5 for the first charge during the free trial, rising with each paid renewal.
One app or PostgreSQL database per account runs free on Usage Billing, at 0.1 vCPU / 256 MiB.
Builds are free either way. They run on Miget's own build machines, never on the resource or the Usage Billing size they're building for, so they're never billed.
Worker processes, sized and billed on their own
A Procfile's other processes - sidekiq, clock, a queue worker - are no longer invisible to the dashboard. Each one is recorded, sized from app.json, and shown on the app page with its own pods, logs and (for a Usage Billing app) its cost this cycle.
- Scale a worker on its own, from the dashboard or the API, independently of the web.
- On a resource, a worker takes RAM the way the web does. On Usage Billing, it's billed the way the web is, at its own size.
- A free-tier app's workers wait for Usage Billing to start before running - held with an issue of their own, and started at one replica the moment it does.
# Scale the "worker" process on its own
curl -X PUT https://app.miget.com/api/v1/apps/$APP_UUID/workers/worker \
-H "Authorization: Bearer $MIGET_API_TOKEN" \
-d '{"replicas": 3}'
An Issues history
Why something stopped - out of room on its resource, a crash loop, killed for memory, waiting on Usage Billing to start, or a cron job's last run failing - is now a record of its own instead of a line buried in a mail. It covers the web, workers, add-ons and services, kept as a history you can scope to one app, one service or one resource, in the dashboard and at GET /api/v1/issues.
Workspace limits, visible before they refuse
The handful of limits that used to surface only as a 422 - replicas on one process, mounts on one shared volume, databases and buckets per workspace - now live in one place, with what you're using against each:
- 20 replicas per process
- 10 apps mounting one shared storage volume
- 40 databases and 100 buckets per workspace
Every one of them can be raised on request. Ask, and an admin approves at a value of their own choosing.
Cron jobs: sized, with minutes included
Every paid resource plan now includes 1,000 cron minutes a cycle, at the plan's own size, shared across every cron job running on it. Past the pool, per cron job:
- Pause until the renewal - the default - or
- Bill the overage at the job's own size.
You're mailed at 75% and 100% before anything pauses, and a renewal resumes exactly what the pool paused. Every run is kept - the latest 100 per cron job - with a run history in the dashboard and at GET /api/v1/apps/{uuid}/cronjobs/{id}/runs, and a maximum run time from one second up to 24 hours stops a run that's gone too long.
The enterprise workspace pool
An enterprise contract gets an agreed CPU, RAM and storage capacity instead of a bill that grows with use. Workloads placed in that pool aren't billed by the hour at all - growing past what's left in the pool is refused, and shrinking never is. A contract workspace doesn't run Usage Billing: it has the pool instead.
The October 2026 price list
Resource, add-on and cron prices moved for new purchases, and nothing an existing resource already pays moves with them. A plan or add-on whose price changes is archived under its own code and replaced by a copy at the new price under the old one - the resources already on it keep running at what they already pay, and you move only by choosing a plan in your resource's settings. The smallest Hobby tier grew from 512 MiB to 1 GiB at the same $5 for everyone; the tier it now matches was retired, with the resources on it kept at their price. The full catalogue, at today's prices, is on the plans page.
Referral credits and spend limits
Credits on a workspace now pay for its Usage Billing beyond the $5 minimum before your card does, whatever other discount your subscription carries, and what's left still comes off the rest of the bill at renewal. Referral credits - 30% of what the people you refer spend - collect on your own account until you transfer them to a workspace where you manage billing; a transfer cannot be undone, and the credits then belong to that workspace.
Two limits keep a Usage Billing cycle from running away on their own: a workspace spend limit caps the whole cycle's bill, and a per-app monthly budget caps what one app can spend by itself. You set both.
How to use it
Every app, service, bucket and stack form offers Usage Billing next to a resource, with a region and a size to pick from instead of a slider. The API takes the same choice on create:
# Create an app on Usage Billing instead of a resource
curl -X POST https://app.miget.com/api/v1/apps \
-H "Authorization: Bearer $MIGET_API_TOKEN" \
-d '{"name": "api", "billing": "pay_per_use", "size": "hobby-1c-1g"}'
Compare plans · See use cases priced out · Open the dashboard · Read the changelog