A machine that's yours, at a price that doesn't move
Anything dynamic — an API, a database, a full application — runs on a dedicated instance sized to the workload and billed at one fixed monthly rate. No per-request metering, no surprise invoice after a busy week.
What it's for
If it needs to hold state, run continuously, or answer on its own address, it belongs on dedicated compute rather than the edge network.
APIs
A backend that needs to hold state, run a queue, or answer requests around the clock — sized to the load, not rented by the request. See Files for the state it writes to disk.
Databases
Postgres, a cache, a queue broker — anything that wants a disk and a stable address instead of a serverless cold start.
Full applications
A monolith, a small cluster of services, an admin panel — whatever your product actually is, running on hardware that is only yours.
Background workers
Scheduled jobs, webhooks, long-running processes that never see a browser but still need to stay up. See Background jobs for how one actually runs on this instance.
Sized to the workload
Three tiers cover most workloads. Anything bigger gets a bespoke quote instead of a tier that doesn't fit.
Dedicated S
2 vCPU · 1 GB RAM · 40 GB SSD · static IP
Small APIs, background workers
$29/mo
- Recommended
Dedicated M
2 vCPU · 2 GB RAM · 60 GB SSD · static IP
Production apps with a database
$59/mo
Dedicated L
2 vCPU · 4 GB RAM · 80 GB SSD · static IP
Heavier workloads, multiple services
$99/mo
Full rate detail, add-ons and fair-use limits live on the rate card →Pricing. Outgrow a tier later? See Scaling for the move.
SSH posture
Access if you want it, or never — either way it's hardened and least-privilege.
Keep exploring
- Pricing
The full rate card — flat, predictable, and posted in the open.
- Platform
How the edge network, storage, and dedicated compute fit together.
- Static hosting
Static sites and SPAs served from the edge network, deployed on every push.
- Databases
Managed databases, backed up nightly alongside the rest of your stack.
- Patching
The "we keep it patched" claim above, backed with the layer inventory and the downtime you can expect per shape.
- Background jobs
The "background workers" row above, worked in full — where the worker runs, the clock, and what happens when a job fails.
- Move to us
Already running somewhere else? Point us at it — we do the lift, on a dedicated instance.
- Guide: static or dedicated?
Not sure this is the right fit? A decision guide to the question underneath the question.
- In service
A register of what we actually run — including dedicated APIs and databases like this.
Ready to start?
Tell us what you're running — one fixed monthly rate, within a business day.