№ 01 What we host
If it runs on a server, it runs here.
Two standard shapes cover most of what we run: static sites on the edge network, and dedicated compute for anything with a process behind it. Everything else — queues, multi-service stacks, the genuinely unusual — is designed and quoted flat. Here's every stack named, not just the two shapes.
№ 02 The register
The compatibility register
Find your stack, see the shape it runs as and where it typically starts. Notes are honest — some rows point you to a cheaper tier, not a bigger one.
| Stack | Shape | Typical starting plan | Notes |
|---|---|---|---|
| Next.js / React | Dedicated | Dedicated S | Server-rendered routes need a process standing by. A fully static export runs on Static Starter instead — ask which output mode you’re using before assuming you need a server. |
| Static generators (Astro, Hugo, Eleventy, Jekyll) | Static | Static Starter | Already the cheapest shape there is. If it’s a brochure site, a static rebuild is cheaper and there’s no server to patch — that’s not a downsell, it’s the honest answer. |
| SPAs (React / Vue / Svelte) | Static | Static Starter | A build step and a CDN, nothing else — unless the app calls a real API of its own, which is a separate dedicated instance, not a bigger static tier. |
| Nuxt / Vue SSR | Dedicated | Dedicated S | Same story as Next.js — SSR needs a standing process. Static-generation (SSG) mode runs on Static Starter instead. |
| WordPress | Dedicated | Dedicated M | PHP plus MySQL plus a media library — a real database from day one. A brochure-only install with no plugins can sometimes get away with Dedicated S; ask before assuming M. |
| Django | Dedicated | Dedicated M | WSGI process plus Postgres, almost always. The admin and the ORM make this one of the easiest frameworks to move in as-is. |
| FastAPI | Dedicated | Dedicated S | ASGI and usually lighter than a full Django app — Dedicated S covers most APIs until a database gets attached, then it’s Dedicated M. |
| Flask | Dedicated | Dedicated S | WSGI, minimal by design — if it’s a small internal tool with no database, Dedicated S is usually more than enough. |
| Laravel | Dedicated | Dedicated M | PHP-FPM, a queue worker, and the scheduler cron on top of Postgres or MySQL — budget for the worker process, not just the web request. |
| Plain PHP / legacy CMS | Dedicated | Dedicated S | No framework to fight — often the cheapest dedicated tier of all. If it’s truly static HTML with a PHP include or two, ask whether a static rebuild is actually cheaper. |
| Ruby on Rails | Dedicated | Dedicated M | Puma plus Postgres plus, usually, a background job runner — the same shape as Django or Laravel, priced the same way. |
| Node / Express / Nest APIs | Dedicated | Dedicated S | A single long-running process is the whole requirement. Add a database and it’s Dedicated M; without one, S is rarely undersized. |
| Go / Rust services | Dedicated | Dedicated S | Compiled, low-footprint binaries — this is the stack most likely to be over-provisioned by default. Start at S and move up only if metrics say to. |
| .NET / Java (Spring) | Dedicated | Dedicated M | JVM and CLR workloads run heavier at idle than the scripting-language rows above — budget memory headroom, not just CPU. |
| Docker / Compose | Quoted | Quoted flat | One container is often just a Dedicated instance with extra steps. Multiple services wired together with Compose is where this stops being a fixed tier and becomes a flat custom quote. |
| Background workers & scheduled jobs | Dedicated | Dedicated S | No browser ever touches these — sized to the job, not a per-invocation meter. A large queue fleet moves into a custom quote. |
| Postgres-backed apps | Dedicated | Dedicated M | The app tier is one line item, the managed database is another — see the database tiers on their own for what backup retention buys you. |
| Realtime / websockets | Dedicated | Dedicated M | Long-lived connections need a process that stays up, not a stateless edge function — this is never a static-hosting fit, however small the app looks. |
| Self-hosted open-source tools | Dedicated | Dedicated S | Analytics dashboards, status pages, internal tools — most ship as a single container or a small app and fit the smallest dedicated tier comfortably. |
№ 03 Included
What every stack gets
Whatever the shape, this is folded in — never an add-on, never a reason to upsell a bigger tier.
- TLS certificates
- DNS management
- Daily backups
- Monitoring & alerts
- Security patching
- A human who answers
- No console — everything defined as code, fully portable
№ 04 Not listed?
Not listed?
Ready to start?
Tell us what you're running — one fixed monthly rate, within a business day.