In January 2012, the first post on this site went up with the title “Introducing HostLater, Because Hosting Matters.” It was written by Pradeep, founder of HellBound Bloggers, and the argument was simple: you can settle the CMS question in an afternoon, but picking a host is genuinely hard.
That post is still live. Fourteen years later, the argument holds up better than most of the advice around it.
I bought HostLater from Pradeep a few years ago. At the time I was a full-time blogger and the plan was affiliate marketing, which is what everyone did with a hosting site. Then my attention went somewhere else. I moved into building WordPress plugins, and after that into SaaS, and HostLater sat quietly with its old posts and a sidebar full of expired coupon banners.
I’m restarting it now, and not for the reason I bought it.
What actually changed since 2012
Read the original post and you’ll see the checklist of the era: disk space, bandwidth, subdomains, cPanel or Plesk. Reasonable questions in 2012. Almost none of them predict whether your site will be fast or stay up today.
The things that decide that now are different. Whether storage is NVMe or spinning rust. How many PHP workers you actually get before requests start queuing. Whether object caching is available or you’re paying for a plan that can’t use it. What the renewal price is after the introductory term, which is frequently three times what you signed up for. And who actually owns the brand you’re buying from, because a large share of the “independent” hosts reviewed across the web are now the same handful of parent companies wearing different logos.
Meanwhile the review landscape got worse, not better. Search for any hosting comparison and you’ll find the same ranked list on forty sites, ordered by commission rate rather than performance. The scarce thing in 2026 is not information about hosting. It’s information that wasn’t arranged by someone’s affiliate payout.
The CMS question isn’t the only question anymore
The original post framed this as a two step decision: settle on WordPress, then decide where to put it. That assumed you were building a site the way sites got built in 2012.
Plenty of people now start somewhere else entirely. They describe what they want to Lovable or v0, get a working app back, and it’s live before hosting has entered their thinking. The infrastructure question never gets asked because the tool quietly answered it for them.
That holds up until it doesn’t. The bill arrives metered instead of flat, so a traffic spike costs money rather than just slowing things down. The database turns out to be a separate vendor with separate pricing. Moving off the platform is considerably harder than moving on to it was. And the mental model most people carry over from shared hosting, where a fixed monthly fee buys unlimited-ish everything, is precisely the wrong one for platforms that meter function calls and bandwidth.
So a hosting site in 2026 can’t only talk about cPanel and managed WordPress. Vercel, Netlify, Cloudflare, Railway, and wherever the AI builders deploy by default are all hosting decisions, including for the many people who never experienced them as a decision at all.
What HostLater will cover
Hosting and domains, both, the way the archive here always did. Traditional hosting and the newer deployment platforms, because increasingly the same person needs to understand both.
Practical guides for people setting up and running sites. Comparisons that state their methodology. Reviews that name the things a host is bad at, because every host is bad at something and a review that can’t tell you what is not a review.
Where affiliate links appear, they’ll be disclosed and they will not decide the order of a list. That’s an easy promise to make and a hard one to verify from the outside, so the better test is whether the recommendations here ever change when a commission does.
Why I think I can add something
I’ve been working in WordPress for about sixteen years. I run DotCamp, where we build plugins including Ultimate Blocks and WP Table Builder, and more recently a set of SaaS products.
That gives me a view of hosting most hosting blogs don’t have: the support inbox. When a plugin breaks for someone, a real share of the time the plugin isn’t the problem. It’s a memory limit set too low, a PHP version the host won’t update, an aggressive mod_security rule silently eating requests, a caching layer serving stale pages, an execution timeout on a host that advertises unlimited everything.
You learn quickly which hosts generate tickets and which ones never do. That pattern is invisible from a benchmark page and it’s most of what I’d want to know before buying.
About the name
HostLater has always been a slightly strange name, and people ask about it.
The reading I like is this one: research now, host later. Don’t buy hosting from a banner during a Black Friday sale. Work out what your site actually needs, understand what you’re being sold, and then choose. The delay is the whole point.
What’s next
New guides and comparisons are being published now, and the archive is being worked through so the old posts either get updated properly or retired.
If there’s a host you want tested, a comparison you can never find a straight answer on, or a question the existing coverage doesn’t handle, leave a comment or get in touch. That’s the fastest way to influence what gets written here.
Welcome back to HostLater.
Leave a Reply