Freelancers live in the gap between one personal site and an accidental agency. You need hosting that can hold your WordPress marketing site and, sometimes, a client origin or two — without pretending you have a DevOps team. WPHost is PHP 8.4 + MySQL hosting with clear site caps. You install WordPress via zip (no one-click). You update plugins yourself. Staging starts on Pro when client work gets risky.
Count sites before you promise
| Plan | Price | Sites | Storage | Freelancer fit |
|---|---|---|---|---|
| Starter | $9 | 1 | 2 GB | Your site only |
| Pro | $30 | 3 | 10 GB | You + two clients; staging |
| Scale | $65 | 10 | 30 GB | You became the IT friend |
| Business | $130 | 30 | 100 GB | Teams when you hire help |
Do not host five clients on Starter via clever subfolders and call it a business model. Do not put unrelated client databases on one WordPress install “to save money.” Isolate sites. Pricing detail: pricing. Agency scale-up: agencies.
Your site versus client sites
Your portfolio / freelance brand. WordPress if you need the CMS; static if you do not — portfolio. Designers and photographers have specialized notes — designers, photographers.
Client sites. Put the registrar ownership in the contract. Prefer client-owned domains. Attach DNS to WPHost; leave MX alone — transfer. Document who pays the WPHost invoice (you resell vs client direct).
Stop sharing wp-admin passwords in spreadsheets
Create per-human WordPress users. When a contractor leaves, delete them. If you have staff, Business teams beat one shared WPHost login. Even solo, use 2FA — secure.
GitHub connections are per-person. Fine for you; do not invent org-wide git theater for a solo shop.
Staging is how you keep clients
Pro’s staging exists so Elementor updates do not brick production on a Friday — staging. Copy the database when you need real content. Deploy history restores files after bad zips; UpdraftPlus (etc.) covers MySQL — backups.
We do not auto-update. Put “monthly updates” in your retainer or teach the client. Hosting is not maintenance labor — managed.
Selling Woo and memberships carefully
You can ship small Woo stores with honest limits — Woo. Membership and course plugins run as PHP; cache logged-in carefully — membership, courses. Do not promise checkout SLAs or Elasticsearch.
Economics versus coupon hosts
$2.99 unlimited client hosting is how freelancers inherit noisy neighbors and surprise renewals — cheap. Paying $30 for Pro with staging is often cheaper than one emergency restore night. Trial here is ~1 day; no Softaculous; no cPanel; no email inboxes; no nonprofit coupon.
A practical freelancer stack
- Pro plan as default once you have any client WP.
- Standardized backup plugin on every site.
- Staging before builder/Woo updates.
- SMTP checklist on every handoff (we do not host email).
- HTTPS siteurl/home checklist — custom domain.
- Migration playbook bookmarked — migrate.
- Install playbook for greenfield — how to host.
Launch discipline for go-lives: how to launch.
When to incorporate agency process
When site count approaches Scale, when you hire subcontractors, when clients demand SLAs you cannot give — graduate process and maybe plan tier. Pillar walk-away cases (concierge update shops): WordPress hosting guide.
Scoping hosting inside freelance proposals
Separate line items in proposals:
- Build — design and WordPress implementation
- Hosting — WPHost plan capacity (or client-direct billing)
- Maintenance — updates, backups monitoring, small content edits
- Email / domain — registrar and Google Workspace (never imply we include mail)
When a client says “hosting,” they often mean all four. Write the boundaries. If they insist the host auto-updates plugins, either add maintenance hours or host them on a concierge platform — do not quietly imply WPHost does it.
For Woo or membership builds, paste our honesty limits into the appendix so procurement is not surprised — Woo, membership.
Handoff packet (minimum)
On go-live day deliver:
- Custom domain with HTTPS and correct siteurl/home
- Admin user for the client; your emergency admin if contracted
- Backup plugin connected to *their* cloud folder when possible
- SMTP working for the contact form
- Staging note (Pro+) and how you use it
- Registrar login ownership confirmation
- One-page “how updates work”
Launch checklist mindset: how to launch.
Avoiding accidental data custody
Freelancers sometimes keep the only backup on their laptop. That makes you the disaster-recovery plan forever. Prefer client-owned backup destinations and client-owned domain logins. Your reputation should not depend on a disk you drop.
Local development versus preview
Build locally with Local, DDEV, or similar if you want; deploy to WPHost preview for client UAT on real HTTPS. Do not invent a long free trial expectation — ours is ~1 day. Paying Pro for staging is the professional sandbox.
Quoting hosting without eating your margin
When a client asks for “hosting included,” either mark up the WPHost plan as a line item or have them pay WPHost directly. Quietly absorbing Business-tier capacity for a $50/month retainer is how freelancers burn out. Spell renewal dates. Spell that plugin updates are maintenance hours, not free hosting fairy dust.
If you build on Starter to save money while developing, upgrade before handoff so staging exists for the first month of change requests. Clients always request “one more plugin” after launch — staging. Keep a template SOW paragraph about HTTPS, backups, and who owns the registrar.
Side projects: your personal brand site can stay on the same Pro plan as two small clients if disk allows. When a photography client arrives with 20 GB of web galleries, do not pretend Starter math still works — photographers, image-heavy.
wp-config habits freelancers should standardize
On every client origin, set salts from the official generator, prefer unique table prefixes only when starting fresh, and consider environment variables for database credentials if the zip sits in deploy history — details in how to set up WordPress hosting. Turn DISALLOW_FILE_EDIT on for production. Keep WP_DEBUG false publicly; use staging when you need debug noise.
Document the four MySQL values from the dashboard in the client's vault, not in a Slack screenshot that lives forever. When you leave a retainer, rotate the application passwords you used. WPHost will still be running PHP 8.4; the risk is leftover human access, not the language version.
Saying no to Softaculous expectations
Clients who came from cPanel often ask where the one-click installer went. Answer early: there is none here. You upload WordPress, create MySQL, finish /wp-admin/install.php, then harden. That friction is intentional honesty, not cruelty. It also means you control the first admin username — never admin — which is freelancing hygiene worth billing for.
Tooling that actually matters
Password manager shared vaults for client wp-admin (with individual logins preferred), a calendar for update windows, and a checklist issue template beat fancy agency OS software. Keep WPHost invoices labeled per client even if you pay the bill — future you will thank present you during tax season.
When a client wants “the same as WordPress.com but cheaper,” educate with beginners and what is WordPress hosting. Sometimes the right move is sending them to .com; keeping a bad-fit client on WPHost helps nobody.
FAQ
Can I put client sites on my personal Starter plan?
Only one site total on Starter. Upgrade. Do not share one WordPress for multiple client brands.
Should clients pay WPHost directly?
Either works. Direct billing clarifies ownership; reselling simplifies their invoice. Keep domain ownership clear either way.
Do I get staging on Starter?
No. Pro+.
Will you update all my client plugins?
No. That is your maintenance product or theirs.
Are GitHub deploys shared across my freelance brand?
Connections are per-person. Your account, your connection.