Reseller hosting with capacity you allocate yourself.
You are selling hosting, so what you need from us is not a control panel your customers will see. It is capacity, isolation, and the ability to hand a site over when somebody leaves.
Buy capacity, sell sites.
A reseller's economics are about the gap between what a pool costs and what the sites on it are worth.
One pool, many customers
Capacity is bought once and allocated across as many sites as fit, so a small customer costs a slice rather than a plan. Adding one is provisioning, not a purchase.
Customers who cannot reach each other
Sites are isolated, so one customer's compromised plugin is one customer's problem. That separation is what makes reselling defensible rather than nervous.
Handover that does not burn the relationship
Customers leave. A full export they can take elsewhere means the end of a contract is a professional exit rather than an argument about who owns the site.
Know which site is costing you
Per-site resource figures show which customer is consuming the pool, so pricing can be based on what a site actually uses.
Support that stops at your line
You own the customer relationship. We answer your questions, at your pace, without appearing in front of the people you bill.
Margin comes from allocation.
Reselling works when capacity is pooled and priced per site. It stops working when every customer needs their own plan and their own invoice.
- Capacity pooled rather than per customer
- Sites isolated from one another
- Per-site usage visible for pricing
- Full export available at any time
Every customer gets the same platform.
You are putting your name on this. What you need is that the thirty-first site performs like the first, without you having to check.
What we change for resellers
You are not the end user, so the tuning is about the pool and the boundaries inside it rather than any single site.
| Setting | What we do | Why |
|---|---|---|
| Capacity model | Pooled and allocated by you per site | Reseller margin comes from putting many small customers on capacity bought once, which per-customer plans make impossible. |
| Tenant isolation | Enforced between customer sites | You are answerable for every site you sell, so one customer's compromised plugin has to stay one customer's incident. |
| Usage reporting | Broken down per site | Pricing a customer without knowing what they consume means the heavy ones are subsidised by the light ones until the pool runs out. |
| Export | Complete and available without asking | Customers leave, and a departure that requires our involvement turns an ordinary exit into a dispute about ownership. |
| Support boundary | Directed to you rather than your customers | You own the relationship and the billing, so support arriving in front of the people you invoice undermines both. |
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.
Do my customers see MagicWP?
How is capacity priced?
What happens when a customer leaves?
Can one customer affect another?
Sell hosting without running servers.
Move your customer sites across - migration is free, every site included.