Servers, without the provider archaeology
Most server buying is a tour of provider consoles, each with its own verbs, its own console and its own bill. ProjectX Servers is one catalog: pick a compute class and a region, see the published rate on the same page, and the server is running in minutes. Dedicated hardware goes through the same lifecycle — order, provision, reinstall, decommission — with the differences that genuinely exist surfaced instead of hidden.
What you get
- One catalog across virtual and dedicated machines — same verbs, same invoice.
- The monthly price printed next to the order button, billed per hour and drawn from the same credit balance as everything else you run.
- First-boot configuration templated from an allow-listed syntax, so no secret is ever baked into an image.
- Continuous reconciliation of the record against what is actually running — drift shows up on your dashboard, not in an incident review.
How it works in practice
Choose a class by what you are running — general-purpose, compute- or memory-weighted — and a region by where your users or your data must be. The order page shows the 30-day price before you commit, and the hourly rate is what the meter charges. Stop a server and billing drops to the resources that still exist; decommission it and the charge stops that hour.
Everything the console does is one API call each, so the TypeScript SDK, the Python SDK and the prx CLI cover the same surface — the automation you write against the API is the same lifecycle the console drives.