Freelance hosting for when you are the only person.
Your client's site is fine until you are on a plane, asleep, or between contracts. There is no second person, so the platform has to be the second person.
You cannot be on call forever.
Every freelance hosting arrangement eventually fails the same way: something happens while the one person who understands it is unavailable.
Patched whether or not you are working
Core and plugin updates are applied at the platform, so a month where you are heads-down on another project is not a month where five client sites go stale.
Someone your client can actually reach
If a site is down at eight in the evening and you are unreachable, there is support to answer them. Being the sole contact is a risk your client is carrying too.
A handover that ends cleanly
Contracts end. A complete export the client can take elsewhere means the last conversation is professional rather than a negotiation about access.
Sites you do not have to babysit
Backups, certificates and updates happen without you scheduling them, which is the difference between five clients and fifteen.
Staging without standing up servers
Testing an update properly needs a copy of the site. Having one per client removes the reason freelancers skip that step.
The bus factor is one.
Your clients depend on a single person, and so do you. Anything the platform handles is something that keeps working during the weeks you are not looking.
- Updates applied without you initiating them
- Support reachable by the client directly
- Complete export available at any time
- Per-site staging without infrastructure work
Working when you are not.
The useful measure for a freelancer is not response time. It is how much keeps happening correctly during a fortnight you spend on something else.
What we change for freelancers
The single constraint is that there is one of you, and the configuration assumes you will be unavailable sometimes.
| Setting | What we do | Why |
|---|---|---|
| Update handling | Applied at the platform without you initiating them | A freelancer's client sites go untouched during any month spent heads-down on a different project, and that is when they fall behind. |
| Support routing | Reachable by the client as well as by you | A site down in the evening while you are unreachable is a risk your client is carrying, and they did not agree to a single point of failure. |
| Export | Complete and available without our involvement | Contracts end, and a departure that requires the host to participate turns a professional handover into a negotiation about access. |
| Staging | Per client without provisioning anything | Freelancers skip testing updates because setting up somewhere to test them costs more time than the update itself. |
| Certificate and backup automation | Running regardless of your availability | The things that break a small site are all scheduled maintenance nobody performed, and a one-person shop has weeks where nobody performs any. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
What happens to my clients when I am unavailable?
Do my clients have to deal with MagicWP?
What if a client wants to leave?
Can I test updates before applying them?
Get a second pair of hands.
Move the client sites across - migration is free, every site included.