№ 01 What we host
If it runs on a server, it runs here.
Two standard shapes cover most of what we run. Static sites run on the edge network. Anything with a process behind it runs on dedicated compute. Queues, multi-service stacks and unusual setups get a design and a flat quote. The register below names every stack.
№ 02 The register
The compatibility register
Find your stack. See the shape it runs as and the plan it usually starts on. Some notes point you to a cheaper tier.
| 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. Check your output mode before you assume you need a server. |
| Static generators (Astro, Hugo, Eleventy, Jekyll) | Static | Static Starter | This is already the cheapest shape. A brochure site on a static build costs less and has no server to patch. |
| SPAs (React / Vue / Svelte) | Static | Static Starter | A build step and a CDN, nothing else. An app that calls its own API needs a separate dedicated instance for that API. A bigger static tier does not help. |
| Nuxt / Vue SSR | Dedicated | Dedicated S | Same as Next.js: SSR needs a standing process. Static-generation (SSG) mode runs on Static Starter instead. |
| WordPress | Dedicated | Dedicated M | PHP, MySQL and a media library need a real database from day one. A brochure install with no plugins can sometimes run on Dedicated S. Ask before you assume M. |
| Django | Dedicated | Dedicated M | A WSGI process plus Postgres, almost always. The admin and the ORM make Django one of the easiest frameworks to move in as it is. |
| FastAPI | Dedicated | Dedicated S | ASGI, and usually lighter than a full Django app. Dedicated S covers most APIs. Attach a database and it moves to Dedicated M. |
| Flask | Dedicated | Dedicated S | WSGI, and small by design. A small internal tool with no database usually fits Dedicated S. |
| Laravel | Dedicated | Dedicated M | PHP-FPM, a queue worker and the scheduler cron, on top of Postgres or MySQL. Budget for the worker process as well as the web request. |
| Plain PHP / legacy CMS | Dedicated | Dedicated S | No framework to fight, so this is often the cheapest dedicated tier. If it is static HTML with a PHP include or two, ask whether a static rebuild costs less. |
| Ruby on Rails | Dedicated | Dedicated M | Puma, Postgres and, usually, a background job runner. That is the same shape as Django or Laravel, at the same price. |
| Node / Express / Nest APIs | Dedicated | Dedicated S | One long-running process is the whole requirement. Add a database and it moves to Dedicated M. Without one, S is rarely too small. |
| Go / Rust services | Dedicated | Dedicated S | Compiled binaries use little memory, so this stack is the one most often given too much. Start at S. Move up only when the metrics say so. |
| .NET / Java (Spring) | Dedicated | Dedicated M | JVM and CLR workloads use more memory at idle than the scripting languages above. Budget for memory headroom as well as CPU. |
| Docker / Compose | Quoted | Quoted flat | One container is often a Dedicated instance with extra packaging. Several services wired together with Compose get a flat custom quote instead of a fixed tier. |
| Background workers & scheduled jobs | Dedicated | Dedicated S | No browser touches these. We size them to the job, with no per-run meter. A large fleet of queue workers moves into a custom quote. |
| Postgres-backed apps | Dedicated | Dedicated M | The app tier is one line item and the managed database is another. See the database tiers for what each backup retention gives you. |
| Realtime / websockets | Dedicated | Dedicated M | Long-lived connections need a process that stays up. A stateless edge function cannot hold one, so this is never a static fit, however small the app is. |
| Self-hosted open-source tools | Dedicated | Dedicated S | Analytics dashboards, status pages and internal tools. Most ship as one container or a small app and fit the smallest dedicated tier. |
№ 03 Included
What every stack gets
Every shape includes all of this. None of it is an add-on, and none of it needs a bigger tier.
- TLS certificates
- DNS management
- Daily backups
- Monitoring & alerts
- Security patching
- A human who answers
- No console. Everything is defined as code and stays portable.
№ 04 Not listed?
Not listed?
Ready to start?
Tell us what you're running — one fixed monthly rate, within a business day.