How the recommendation is made
Each answer adds or subtracts points for each hosting type; the highest score wins. Hard rules come first: needing GPUs selects GPU hosting, and needing root access rules out shared hosting. The main weights:
| Answer | Pushes towards | Pushes away from |
|---|---|---|
| No server skills | Managed, shared | Bare metal, VPS |
| Spiky traffic | Cloud | Bare metal |
| High consistency | Bare metal, virtual server | Shared |
| Strict isolation | Secure hosting, bare metal | Shared |
| Large scale | Bare metal, cloud | Shared |
| Database workload | Virtual server, bare metal | (none) |
The full rules are in calc.mjs, served with this page at /assets/js/calc.mjs.
What to do with the answer
- Read the product page. Each has a “who it is not for” section; check you are not in it.
- Size it. Use the VPS sizing or GPU memory tool.
- Ask for a quote. Paste the answers into the quote form.
How we test this tool
Unit tests check four reference profiles: a GPU workload always gets GPU hosting; a non-technical website owner gets managed or shared hosting; requiring root never returns shared hosting; a spiky app with a strong team gets cloud hosting.
Frequently asked questions
Is the recommendation final?
No. It is a starting point. Edge cases (licensing, data residency, existing contracts) need a conversation, which is what the quote process is for.
Related
Inputs stay in your browser. Tool maths last reviewed ; the unit tests that pin these formulas are listed in the evidence hub.