Single tenant
One machine, one project. A busy neighbor can’t slow you down, and a neighbor’s mistake can’t reach your data.
Where your product lives
Your own server.
Every project we ship gets a dedicated machine of its own. Nobody else's traffic, nobody else's data, and a bill that looks the same each month. This page lays out what that server includes, how our crew keeps it healthy, and the parts of operations we never skip.
The setup
Your app gets a whole server to itself.
Every app we ship runs on a server set aside for that project alone. Your database, logs and backups live on hardware no other customer touches, so a busy neighbour can never slow you down or peek at your data. It costs a little more than shared hosting and saves a lot of guesswork later. One project, one machine, clearly yours.
Your accounts
The hosting account, the domain and the backups are registered to you. We work inside them as invited guests.
Flat monthly cost
A fixed price you can put in a budget. No metered surprises, no bandwidth bills, no “new pricing” emails.
After launch
What we look after for you.
- 01Nightly backups, copied to a second provider in another region
- 02Write-once backup storage, so nothing can quietly overwrite it
- 03A full restore rehearsed every month, with the result written down
- 04Uptime checks every minute, with alerts sent to a named person
- 05Security patches applied weekly, in a published maintenance window
- 06Firewall on, password logins off, admin access over a private network
- 07A quarterly review of who has access, and why
In practice
A typical setup.
Every project differs a little, but most launch with a setup along these lines:
Configuration lives in your repo. Deploys take one command. Access is yours to grant or revoke. Nothing is hidden below deck.
- A dedicated server sized for the app, in the region your users live
- Ubuntu LTS with a short, written hardening checklist
- Docker images built in CI and released with Kamal
- Automatic TLS certificates that renew on their own
- Encrypted nightly backups to S3-compatible object storage
- Metrics, logs and uptime checks on one dashboard
- Every setting in a Git repository that you own
Side by side
How it compares, row by row.
| Area | With Shipped | Typical shared hosting |
|---|---|---|
| Compute | With ShippedA whole machine for one project. | Typical shared hostingA slice of a shared host. Performance depends on who else is busy. |
| Accounts | With ShippedRegistered to you. We are invited users. | Typical shared hostingRegistered to the agency. Leaving means asking nicely. |
| Backups | With ShippedNightly, offsite, and restored every month to prove they work. | Typical shared hostingAssumed to exist. Rarely tested until the day they are needed. |
| Alerts | With ShippedSent to a person with a name and a phone. | Typical shared hostingSent to a shared inbox that nobody reads on weekends. |
| Pricing | With ShippedOne flat monthly number. | Typical shared hostingMetered by traffic, seats or storage, and revised every year. |
| Handover | With ShippedKeys, repo and runbook in one afternoon. | Typical shared hostingA migration project, priced by the hour. |
Good questions
Asked before every kickoff.
What happens if Shipped stops working with us?
Nothing breaks. The server, domain, code and backups are already in your accounts. We hand over the runbook and remove our access the same day, and your site keeps running exactly as before.
Is one server really enough?
For most products in their first few years, yes. A well-sized dedicated server with tested backups is simpler and often more reliable than a cluster nobody fully understands. When you need more, we add capacity step by step.
How is this different from shared or cloud hosting?
Shared and virtual hosts split one physical machine between many customers. A dedicated server gives your project the whole machine: its CPU, memory and disks are yours alone, so performance is steady and the security boundary is simple.
What if our traffic grows quickly?
We first move to a bigger machine, which usually takes under an hour. If that stops being enough, we split the database and the app across servers. Kamal keeps either change small and easy to roll back.
Who can log in to the server?
You, plus two named engineers at Shipped. Access is by personal key over a private network, every session is logged, and the list is reviewed with you every quarter.
What does it cost?
Server costs are billed by the provider straight to you, usually less than a team lunch each month. Our care plan is a flat fee on top. Tell us about your app and we will send a fixed quote.
Say hello
Want a server that is yours alone?
Describe the product and its traffic. We'll send back a plain plan: the machine we'd pick, what runs on it, the monthly cost, and who watches it after launch.
How it starts
- 01A real person reads your note before the next working day ends.
- 02You get straight answers and a few sharp questions back.
- 03If we can help, we map out a first release on a 30-minute call.