Inexpensive WordPress hosting is for makers who already know WordPress is not magic — it is PHP + MySQL plus uploads. WPHost sells the host part: PHP 8.4, MySQL provisioning, HTTPS, deploys, logs. Plans: $9 / $30 / $65 / $130. You bring the CMS zip. There is no one-click installer, no auto plugin updates, no email, no built-in CDN. Deploy history restores files; it does not dump your database.

Who inexpensive WPHost is for

  • Bands, clubs, and local orgs with an event page.
  • Solo shops that can follow a zip install once.
  • People allergic to coupon renewals and “unlimited” fiction.
  • Anyone willing to update plugins in wp-admin after a backup.

Not for: teams that require vendor-applied plugin patches, buyers who need mailboxes on the web invoice, or stores demanding PCI SLAs (Woo can still run without that theater).

Custom-domain shopping: cheap WordPress hosting with custom domain. Writer-shaped needs: WordPress hosting for writers. MySQL clarity: WordPress hosting with database support.

The publish path, said plainly

Create a PHP site. Upload WordPress so core files sit at the web root. Provision MySQL; place credentials in wp-config or env. Finish the installer on the HTTPS preview URL. Install a backup plugin that includes the database. Build the pages. Point DNS only when preview matches reality. Attach the certificate on the custom domain. Schedule your own updates — we will not auto-update plugins for you.

Worked example: band event page

A band needs a one-page site before a Friday show: date, venue embed, ticket link, and three photos. Budget is tiny. Attention is tinier.

Inexpensive path: Starter ($9). Fresh WordPress zip, one lean theme, one page, maybe a simple embed for maps. Ticket button links to the venue or a ticket vendor — no need to invent checkout on day one. Compress photos; 2 GB is plenty if you are not uploading RAW files from rehearsal.

If they already had WordPress elsewhere with old posts, migrate files and a database dump. Skipping the dump is how “inexpensive” becomes “we lost the mailing list copy that lived in a page draft.”

Skipping the database dump on a WordPress move

File-only moves look successful: themes appear, uploads appear, the homepage template loads. Then permalinks 404, widgets are empty, and every post is missing because MySQL never traveled. Deploy history on the new host cannot invent the old database. Inexpensive hosting does not remove the need for mysqldump (or a plugin export) before you cancel the old account.

Do this on every move: put the old site in maintenance or know your cutover window; export the database; export wp-content; note wp-config secrets; import DB on the new MySQL; upload files; search-replace URLs carefully if the domain changes; test on preview; then DNS. File deploy history helps after you are live and upload a bad zip — it is not the migration tool for content.

When to pick a different product

Static event pages with no CMS editors might be happier on a static host. Bands that only need Linktree-shaped links may not need WordPress at all. Orgs that need shared mailboxes should buy email separately — we do not include it. Concierge WordPress shops win when nobody on the team will touch updates.

Inexpensive does not mean incomplete runtime

You still get PHP 8.4, HTTPS, logs, and MySQL. You do not get Softaculous, auto updates, CDN, or unlimited disk. Caps stay: 1/3/10/30 sites and 2/10/30/100 GB across the four plans. WooCommerce remains optional software you install, without a PCI SLA from us.

After the show

Update WordPress when the tour calms down. Keep the backup plugin running. If the band adds a shop merch page later, revisit caching and backups before installing Woo on a whim. Upgrade to Pro ($30) if they want a staging copy for theme experiments between albums.

FAQ

Is $9 enough for a band site?

Yes for a modest event/brochure site with compressed media. Upgrade for staging, more sites, or disk — not for a “music hosting” badge we do not sell.

Do you one-click install WordPress for non-technical members?

Not today. One tech-comfortable member (or a friend) runs the zip + MySQL path once; then others edit pages.

Can deploy history undo a bad migration?

It can restore prior file releases on this host. It cannot recreate a database you never imported.

Will you host [email protected] inboxes?

No. Keep email at a mail provider. Change web DNS carefully so MX stays put.