Agencies rarely need a faster server. They need fewer logins, a staging copy that takes seconds, and a handover at the end of a project that does not turn into a migration.
None of this is a different server. It is the tooling that decides whether twenty sites is twenty times the work.
Clone a live site into a fresh environment, or clone it back over an existing one once the work is signed off. Same plugins, same content, same database, without an export or a migration plugin.
Open wp-admin as an administrator from your dashboard. Nothing shared in a password manager, and nothing to rotate when a contractor's engagement ends.
When a project ends, transfer the site to the client's own account. They get the site and the invoice; you stop carrying infrastructure for work you finished months ago.
Resource limits are applied per site, so a campaign that goes well for one customer does not slow down the other nineteen.
Per-site SFTP, database access, PHP version switching and search-and-replace. The things you would otherwise ask someone for a server to do.
The overhead of running client sites is rarely technical. It is accounts, invoices, credentials and the question of who owns what when the relationship changes.
Each site runs in its own containers with its own CPU and memory allocation, so the portfolio does not share a fate.
This page is not about a different server configuration. What differs is which features earn their keep at twenty sites instead of one.
| Setting | What we do | Why |
|---|---|---|
| Clone site | Into a new site, or over an existing one | Build on a copy and push it back when approved, without an export file or a migration plugin. |
| Magic login | One click into wp-admin as an administrator | It removes shared client passwords entirely, including the problem of rotating them when staff change. |
| Site transfer | Move a site and its billing to the client's account | Project handover should not be a migration, and should not leave you paying for finished work. |
| SFTP and WP-CLI | Per site, on every plan | Theme and plugin work should not require asking anyone for access to a server. |
| Resource limits | Applied per site from the plan | Client sites share a plan but must not share a failure — one campaign spike cannot slow the rest. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Move one site to see how it feels. We handle the migration, and no card is required to start.