WordPress hosting for agencies

Agencies need more than “WordPress hosting” as a vibe. You need several origins, a way to test changes without lighting production on fire, clear responsibility for updates, and access control that is not a shared password in a Slack canvas. WPHost fits agencies that treat WordPress as client-owned software on a modern PHP host — not agencies that need the host to be a white-label concierge updating Elementor under an SLA.

Plan math for multi-site stables

Count sites, not “environments you invent via folders.” Staging on Pro+ is a proper extra environment pattern — staging — and staging still needs a DB copy if you want production content.

Trial ~1 day then paid. No nonprofit agency coupon. No email hosting for clients (they keep Google Workspace). No built-in CDN. No cPanel. No one-click Softaculous — upload zips / deploys. Full pricing framing: pricing.

Teams on Business

Business unlocks teams so humans get their own access instead of sharing one owner login. That matters for offboarding staff and for not leaking every client in one browser profile. Pair with WordPress-level roles per site; hosting seats ≠ wp-admin roles, but both layers matter.

GitHub connections are per-person

Read this twice: GitHub connections are per-person. Do not overclaim agency-wide git magic in sales decks. If your workflow is zip deploys of themes, say so. If each developer connects their own GitHub, plan for that. Tokens do not become a mystical org bot just because you pay Business.

File deploys still do not move databases. Migrations remain files + SQL + serialized replace — migrate.

Staging discipline (the actual agency product)

Clients judge you when production breaks after a plugin update. On Pro+:

1. Copy files/theme to staging as your process dictates.
2. Copy the database when you need real content (we do not pretend one-click full clone).
3. Update plugins on staging.
4. Smoke test checkout/forms/membership.
5. Promote carefully to production with a backup taken first.

Deploy history restores files if a theme deploy fails. It will not restore a mangled orders table — backups.

Who updates plugins — write it in the SOW

WPHost does not auto-update core or plugins. Your retainer must say who clicks Update. If the client refuses and wants the host to own updates, sell them a maintenance product you staff — or host them on a concierge WP platform. Do not imply WPHost does it — managed spectrum.

Domains, MX, and handoff

Keep client domains at their registrar when possible. You attach web DNS to WPHost; leave MX alone — transfer. Document login ownership at handoff. Agencies that “hold the domain hostage” create legal and reputational debt.

Custom domain + siteurl/home HTTPS: custom domain.

Woo, memberships, and overselling

You can ship small Woo stores here with honest limits — no checkout SLA, no PCI product, no Elasticsearch — Woo. Membership and course sites need cache care — membership, courses. Do not sell enterprise search on a Scale plan sticker.

Freelancers versus agencies

Solo freelancers often live on Pro (3 sites) until they are accidentally an agency — freelancers. Designers who build in page builders: builders are plugins, not hosting — designers.

Security baseline you should standardize

• 2FA for all staff admins
• No shared admin users named after your agency on every client
• DISALLOW_FILE_EDIT on production
• Monthly update windows
• Off-site backups per client

See secure hosting. PHP 8.4 is the runtime floor — fast.

When WPHost is the wrong agency platform

• You need white-label concierge update SLAs from the host
• You need Softaculous + cPanel to match junior staff training
• You promised unlimited client sites on one cheap coupon
• You need org-level GitHub app installs we do not describe as available

Pillar including walk-away criteria: WordPress hosting guide.

Packaging hosting in retainers

Healthy retainers spell out: plan capacity, who pays WPHost, update cadence, staging usage, backup ownership, and emergency hourly rates. Unhealthy retainers say “we handle hosting” with no mention of plugin updates — then blame the host when Elementor breaks. Align words with what is managed.

Reselling: some agencies bill clients a flat hosting fee while consolidating on Business. That is fine; still count sites against 30 and storage against 100 GB. Image-heavy clients need offload strategies — image-heavy.

Onboarding a client site in one afternoon

Checklist your juniors can run:

1. Create PHP site; deploy zip or pull agreed files
2. Provision MySQL; import; serialized URL to preview
3. Backup plugin to client-owned bucket
4. 2FA for agency admin; client editor user
5. SMTP documented
6. Staging note and update calendar
7. DNS change window scheduled with MX screenshot

Migration detail: migrate. Launch: how to launch.

QA beyond “looks fine in Chrome”

Test forms, language switchers, carts, and membership gates on staging. Check PHP logs after builder updates. Confirm no indexable staging. Phone network check on the custom domain after cutover — custom domain.

Junior training without Softaculous

Train juniors on zip + MySQL + installer once using how to host. It is slower the first time and faster forever after. Softaculous hides the skills they need when migrations go sideways.

Agency process on visible plan math

Agencies fail hosting when site count is wishful. Starter ($9) is one site. Pro ($30) is three with staging. Scale ($65) is ten. Business ($130) is thirty with teams. Put those numbers in the SOW. Isolate clients per site and database. GitHub connections are per-person — plan human access accordingly.

Standardize wp-config.php patterns (salts, DISALLOW_FILE_EDIT, env credentials where appropriate) — setup. Standardize backup plugins to client-owned buckets. Standardize “we do not auto-update; retainers cover updates.” Softaculous is not available; teach zip installs once per onboarding doc.

Staging and handoffs

Use Pro+ staging with DB copies before page-builder and Woo updates. Deliver handoffs with registrar ownership, SMTP proof, HTTPS siteurl/home, and a one-pager on update cadence. We are not a white-label concierge update desk unless you sell that labor yourself — managed. Trial ~1 day per account reality; build locally when demos need longer.

FAQ

Can each client get their own invoice?

Billing models vary by your agency process; platform plans are capacity subscriptions. Many agencies resell hosting as a line item on their invoices while paying WPHost wholesale-style on Business/Scale.

Is staging included on Scale?

Staging is a Pro+ capability — Scale and Business include the higher plans’ features in this product ladder. Confirm in-dashboard for your account; product intent is staging from Pro upward.

Do team seats replace WordPress users?

No. Teams help with WPHost dashboard access. Each WordPress site still has its own users.

Can we clone production to staging in one click including DB?

Not as a marketed full-clone product. Persistent staging yes; DB copy is your procedure.

Are GitHub org tokens supported as a shared agency integration?

Connections are per-person. Design process around that constraint; do not pitch magic you do not have.