Every Client On The Same Setup.
Ten websites on one account and one bill, staging on all of them, a login each for the team, and a clean way to hand a site back. USD 80 a month billed yearly.
The Mess You Inherit
Agency hosting problems are rarely technical. They are organisational.
Ten Clients, Ten Different Hosts
Every site you inherit comes with its own control panel, its own renewal date and its own way of failing. Nobody on the team can hold all of it in their head.
Everyone Shares One Password
The hosting login gets passed around because there is only one. When somebody leaves, nobody is quite sure what to change.
One Busy Site Hurts The Rest
On most shared or reseller setups, one client’s traffic spike or runaway plugin becomes everyone’s slow afternoon.
One Process That Works For Every Client
Ten Sites, One Account, One Bill
Scale holds ten websites sharing one pool of storage and bandwidth. One invoice a month instead of ten renewal emails you forward to accounts.
A Login Each, With Roles
Invite the team to the account instead of sharing your password. Developers get the technical tabs, billing sees invoices, a viewer can look and not touch.
Caps So One Client Cannot Eat The Pool
Allowances are pooled, but you can set a ceiling on any single site. A client who uploads a video library is limited to their share rather than everyone’s.
Staging On Every Client Site
Not a premium extra on two of them. Every site can be cloned, changed and pushed live, so the same process works across the whole book.
Clean Exits
When a client takes their site in house, transfer it to their own Oxyforge account with a code. Nothing is rebuilt and nothing is held hostage.
Real Isolation Between Clients
Each site runs in its own container as its own Unix user with its own database. One client being compromised does not reach the others on your account.
Access That Survives People Leaving
Invite each person with their own login and a role rather than passing one password around. A developer sees SFTP, staging and the database. Billing sees invoices and nothing else. A viewer can look without touching.
When somebody leaves, disable their login. They are signed out everywhere at once, and nothing else has to change.
Read About Team AccessPast ten sites, look at dedicated hosting or an enterprise estate.
Ten Sites On Scale
One account, one bill, one process for the whole book.
Scale
$960 a year. That is $192 less than paying monthly.
- Up to 10 websites
- 30 GB storage
- 200 GB bandwidth a month
- A temporary address to test on
Built For A Client Book
Up to ten websites sharing one pool of resources. For agencies and studios with a client list.
- Servers In Singapore
- Free SSL On Every Domain
- Daily Backups, Kept 30 Days
- One-Click Staging
- Cloudflare CDN And DDoS Protection
- Nightly Malware Scans
- SFTP And WP-CLI
- PHP 8.3 And Redis
- Support From Real People
Every plan includes the same platform. The only difference is how many websites and how much room they have.
What Agencies Ask First
How do the pooled allowances actually work?
Storage and bandwidth belong to the account, not to each site. Scale gives 30 GB of storage and 200 GB of traffic a month across ten websites, so a small brochure site using almost nothing leaves room for the one that is busy. You can cap any individual site below the pool if you want a hard ceiling on it.
Can I give a developer access without handing over my login?
Yes. Invite them to the account with their own email and a role. Roles decide what they see, and you can disable the login when the contract ends, which signs them out everywhere immediately.
What happens when a client wants to leave?
Transfer the website to their own Oxyforge account with a code. It moves across with its files, database and domain intact. No rebuild, no export and import, and no awkward conversation about who owns the hosting.
Can we white-label it?
No. There is no reseller panel and the members area says Oxyforge on it. Most agencies here keep the sites on their own account and bill the client for a care plan rather than reselling hosting.
Do we get a separate environment for development?
Every site has a staging copy, and you can also create a dev site, which is a blank password-protected WordPress for building the next thing. A dev site draws on your storage rather than using one of your website slots.
What if we outgrow ten sites?
Talk to us before you get there. Beyond Scale the sensible answer is usually a second account per team or a dedicated arrangement, and we would rather plan it with you than watch an account run out of room.
When We Are Not The Answer
Not A Fit
- White-label reselling. No branded panel, no reseller pricing tiers, no hiding where the hosting is.
- Clients who need an SLA with penalties. We do not sell one yet, and we would rather not pretend.
- Non-WordPress client work. A Laravel app or a static build needs a different host.
- Moving the whole book across for you. Copying sites in is your own job, one at a time, onto temporary addresses.
Move One Client And See
Put a single site here, run it through a staging change and a restore, and judge the process before you move the rest.
Start On Scale