A machine that's yours, at a price that doesn't move
An API, a database, a full application: anything dynamic runs on a dedicated instance, sized to the workload. It bills at one fixed monthly rate. There is no per-request metering, and 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. It is 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, and 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.
The next change is a sentence, not a project
A dedicated instance is not the end of the build. When the app needs to change, you say what to change, and The Loop carries it the rest of the way. CustomLabs briefs it. A CodeHerder agent opens the pull request. See Brief a change for how to write a good one.
- 1
You notice itYou
An endpoint needs a new field, or a report should show something it doesn’t. Nothing here watches for this. A person using the app sees it.
- 2
You describe itYou
Say what should happen instead, in plain language. No ticket template, and no technical wording needed.
- 3
Briefed as a changeCustomLabs
Written up the same way any other change request is. The iteration add-on is what covers it.
- 4
An agent opens the pull requestCodeHerder
The change lands as a real pull request against the repository, with the test suite run against it.
- 5
A human reviews and mergesCustomLabs
Someone reads the diff before it goes anywhere near production — nothing here is auto-applied blind.
- 6
It ships through the same pipelineCustomHosted
The same pipeline that deploys everything else on your stack ships this too — no separate process to babysit.
- 7
You're told it's doneCustomHosted
A note confirming what changed and that it merged, in the same shape as every other note on this site.
The CodeHerder iteration add-on covers each change, at $25/mo. A single dedicated instance has no second copy standing by to take traffic while the new version starts. A release is a short, health-checked restart, not an instant handoff between two running copies. See Deploys for what a release does to the instance.
Keep exploring
- What visitors see
What a visitor gets while a dedicated instance restarts, and the honest floor when it is not answering at all.
- 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
Worked examples of the loop, including dedicated APIs and databases like this.
Ready to start?
Tell us what you're running — one fixed monthly rate, within a business day.