Backup claims are where cheap WordPress hosting gets slippery. A checkbox that says “backups” might mean occasional file snapshots, marketing fiction, or a restore ticket that takes days. WPHost is blunt: deploy history restores previous file releases. It is not a scheduled full-site WordPress backup. You still need a plugin or process that dumps MySQL plus files off-site.
WordPress is PHP + MySQL. Plans: $9 / $30 / $65 / $130 on PHP 8.4. No one-click installer. No auto plugin updates. No email. No built-in CDN. WooCommerce can run without a PCI SLA.
Cheap capacity, honest backup boundary
Starter $9 — 1×2 GB. Pro $30 — 3×10 GB with staging (test restores here). Scale $65. Business $130. Monthly shapes: monthly WordPress hosting plans. Coupon caution: cheap WordPress hosting. Managed-infra sibling: cheap managed WordPress hosting.
Free hosts that “backup for you” often deny downloads until you pay. Owning your dumps is cheaper long-term.
What free backup theater costs
When a free site dies, you discover export limits. Cheap paid hosting plus UpdraftPlus (or similar) to S3/Drive is usually the sane beginner stack. WordPress.org is free; durable backups are an operational habit.
Worked example: restaurant PDF menu plus HTML hours
Restaurant launches on Starter. Hours live in a WordPress page; menu is a PDF in the media library. Risk: an editor overwrites the page or a bad plugin update corrupts options.
Backup plan: install a backup plugin on day one; schedule daily database + weekly full; store off-site; once a quarter restore to a staging site on Pro ($30) or a local stack to prove the dump works. Deploy history helps if someone uploads a destructive zip of theme files — it will not recreate the hours page from MySQL alone.
History-mode SPA routes with no files on disk
A different backup confusion hits teams who bolt a JavaScript SPA onto WordPress or replace the front with a builder that expects pretty routes. In history mode, URLs like /menu/lunch may not map to real files. Server rewrite rules send them to index.php (WordPress) or index.html (SPA). If you “back up” by downloading only wp-content/uploads and a theme folder, you miss the routing story and the database rewrite rules. Restores then 404 every deep link.
For WordPress, back up the database (permalinks, options, posts) and the full meaningful file tree. For SPA hybrids, also document nginx/Apache rewrite expectations — WPHost is PHP-oriented WordPress hosting, not a specialized SPA platform. Do not assume file deploy history captured your MySQL permalink settings; it did not. And do not upload a frontend dist incorrectly and call the old release a “backup” of content editors’ work.
Building a cheap but real backup habit
- Plugin that includes database.
- Off-site destination you control.
- Retention that survives noticing a problem late.
- A tested restore path (Pro staging helps).
- Updates only after a fresh dump — we will not auto-update plugins for you.
- Know that deploy history is complementary undo for files, not a replacement.
When cheap backup hosting is the wrong promise
If you need the host to guarantee point-in-time database restores as a compliance product, buy a specialist and read the SLA. If you need email backups, that is your mail vendor. If you need CDN log retention, that is your edge vendor — we do not bundle CDN.
FAQ
Do WPHost plans include automatic WordPress backups?
Deploy history keeps file releases. Scheduled database-inclusive WordPress backups are your plugin/process responsibility.
Is staging a backup?
No. Staging is a testing copy. You still copy DB content deliberately. Useful for restore drills on Pro.
Can I rely on free host backups until I “go paid”?
Risky. Export early. Cheap Starter plus off-site dumps is clearer ownership.
Will auto plugin updates reduce backup needs?
We do not offer auto plugin updates. Backups matter more when humans (or future automation you build) change production.