Solutions / Developers
Hosting built for developers
Web hosting for developers who'd rather deploy from a terminal than an upload form. Use shared SSD hosting for client sites, and a Linux VPS with root access when the project needs its own server.
Shared hosting or your own server?
The table shows where each option fits.
| Shared SSD plans | Linux VPS | |
|---|---|---|
| Best for | Client sites, WordPress builds, brochure and landing pages | API back ends, workers, custom runtimes, server-level settings |
| Root access | No — the server is shared and we run it | Yes — full root access |
| Who maintains the server | We do | You do, or add Managed Services |
| Isolation | Your account shares a server with other accounts | KVM virtual server with its own CPU, RAM and NVMe storage |
| Backups | Optional backup and restore add-on | Optional cloud backup, billed per GB |
| Status | Available now | Coming soon |
Shared hosting for client work
Most developer hosting needs are client sites: a WordPress build, a brochure site, a landing page.
- Free SSL on every site
- An optional backup and restore add-on for files and databases
- Daily malware scanning on every account
- Up to 10 sites on Pro, so client projects share one bill
Need shell access or a particular tool? Ask our team before you order and we'll tell you what the plan supports.
A VPS for your own stack
Choose a VPS when you need resources nobody else touches, server-level configuration, or a runtime shared hosting does not offer.
Linux VPS plans run on KVM with NVMe storage, full root access, a dedicated IP and reverse DNS. VPS hosting is coming soon — request it on demand when you are ready to size a server.
A deploy workflow for your VPS
With root access, a simple flow looks like this:
- Push to your repository's main branch
- SSH into the server and pull, or let a deploy script do it
- Run your stack's install step and any migrations
- Clear caches and check the site
Take a backup before step 2 the first few times, until the routine is boring.
Moving projects over
For projects with custom build steps or environment variables, include those details in your ticket so we can match your setup as closely as the plan allows.
What hosting features do developers need?
The usual list is shell (SSH) access, Git, a choice of language versions, databases, cron jobs, and a staging copy for testing. Developers running their own applications also want root access and their choice of runtime, which points to a VPS. Check the table above, and ask our team about any tool you rely on before you order.
Do you offer SSH and Git access?
Every VPS comes with full root access over SSH, so you can install Git and anything else your stack needs. For SSH or Git on a shared SSD plan, ask our team before ordering and we'll confirm what the plan includes.
When should I choose a VPS over shared hosting?
Choose a VPS when you need to install your own software, change server settings, run background processes, or keep your workload separate from other accounts. If you're hosting standard websites and don't want to maintain a server, shared hosting is cheaper and less work.
Can I create a staging site?
A common approach on any plan is a subdomain such as staging.yourclient.com with its own database, protected by a password, which you sync to production when changes are approved. On a VPS, you can also run staging as a separate site on the same server.
Pick the right box for the job
Shared hosting for client work, a VPS for your own stack. Compare plans side by side.