Skip to main content
HostingSeller
Shop plans

Agency Brief

Your client's editors are the people who actually judge your hosting

The public site can be fast and the account still be a failure, because the people typing into it all day are the ones who ring you.

Straight answer first

Host the CMS your client's complexity actually calls for on an account with headroom for editorial load, because the back end is what the people paying you sit inside all day — our CMS plans cover all the mainstream engines.

For a reseller this reframes the whole purchase. Visitors are served from cache and cost you almost nothing; editors bypass the cache on every click and generate the tickets. Buy for the second group, and the first group is looked after as a side effect.

Written by the Hosting Seller staff · Checked 4 August 2026

Free

Client migrations, per site

24/7

Cover behind your helpdesk

Daily

Backups on the client account

$0

Setup on any reseller plan

Written for agencies and resellers who host publishing clients — a magazine, a charity's news operation, a company with a genuinely busy blog. You are not being judged on a speed test. You are being judged by six people who log in every morning and notice when the editor takes four seconds to save.

A content team experiences hosting through the admin screens rather than the public site. Editorial pages skip the cache entirely and land straight on PHP and the database, which makes back-end speed the number that governs how much work gets done — and how many emails you get about it.

Buy for the people typing, not the people reading

Caching serves visitors, not editors. Admin screens are rebuilt from scratch on every click, so NVMe under the database, OPcache and object caching are what speed up the people who sit inside the CMS all day. That is where your money should go.

It is also the answer to give when a client complains that their site is fast on a testing tool and slow to work in. They are not imagining it, and knowing why puts you on the right side of the conversation rather than defending a number they do not care about.

Logins, roles and the leavers list

Editorial teams change. Freelancers arrive for a project, a staff writer leaves, an intern needs access for six weeks. Every one of those is an account somewhere, and on a badly run client relationship, several of them are still active two years later.

Keep two habits. Inside the CMS, give each person the smallest role that lets them work. Outside it, keep a single cPanel account per client under your WHM rather than handing out shared credentials — so when somebody leaves, revoking access is one action, not an archaeology dig through four systems.

Which engine, and who has to support it

WordPress unless a specific structure says otherwise; its editing experience and its ecosystem fit most teams. Joomla earns a look where permissions get complicated, Drupal where the content model runs deep. All three are at home on our plans, which means the choice can be made on the client's needs rather than on your platform's limits.

Make it honestly, though. The engine you pick is the one your team will support for years, so factor in who on your side actually knows it. A technically superior choice that nobody can maintain is a commercial mistake wearing an architecture diagram.

Costing a publishing account

Editorial accounts generate more support contact than brochure sites and always will, because more people touch them more often. That is not a fault to be engineered away; it is a characteristic to be priced.

Quote the platform, an allowance of editorial support hours, and a rate beyond it. Then keep the allowance visible in your reporting, because a client who can see they used four of six hours renews without argument, and a client who cannot see anything assumes they are paying for nothing.

Coworkers gathered around laptops in an office

We sell the hosting. That is the whole disclosure.

There is no affiliate table behind this page and no fee for the recommendation it makes. We are the supplier, we would like the account, and saying so leaves the rest free to be useful.

Bring an existing site and we shift it across at no charge — usually inside 24 hours, with nothing going dark while we work, which matters more when a newsroom is waiting.

  • Tests you can run before you commit a client
  • One trade price, held at renewal
  • Free migration for the sites you already host
  • A refund policy with no small print

Why Hosting Seller

On every plan, as standard

Back-end speed, deliberately bought

NVMe under the database, OPcache and object caching, aimed at the editors rather than at a testing tool's score.

One cPanel account per client

Under your WHM, so access is granted and revoked in one place when a team changes shape.

Matched to this verdict

The Pro plan is this page's recommendation made concrete — one flat price, essentials included, upgradeable in place.

Every mainstream engine at home

WordPress, Joomla, Drupal and the rest run on the same plans, so the client's needs choose the platform rather than your supplier's limits.

Free migration, no dark hours

Our staff move an existing site across at no charge, usually inside a day, with the old site serving until the new one takes the traffic.

Cover behind your helpdesk

Real engineers on the counter at every hour, so an editorial deadline at midnight is not one person and a laptop.

Price Tags Compared

How we compare with the household names

Typical sign-up and renewal prices across the market, set next to ours — the second number most comparison charts leave off.

What Hosting Seller charges and what it includes, lined up against three rival hosts
Line itemHosting SellerBest sellerTypical big-brand hostTypical budget hostTypical loss-leader
Entry price / mo*$2.42/mo$4–$6$2–$4$1–$3
Price at renewal / mo$2.42/mo$10–$15$8–$12$4–$6
Renewal price on the entry plan is unchanged
SSL on every plan
Site migration included
The entry plan uses NVMe storage
Entry plan gets a backup daily
Live human support, 24/7

*The number in our column is the cheapest plan on our shelf, priced on an annual term and pulled live from the very catalogue that feeds the pricing page, so it cannot drift out of date. Other columns show the ranges shared hosting tends to advertise inside each bracket: introductory rates that normally ask for a one-to-four-year commitment, then climb once that term expires. Naming individual competitors and printing their prices is something we have stopped doing. A figure we cannot re-check on the day you read it has no business sitting in front of you. So compare us with whoever you are genuinely weighing up, and read the renewal line first. That line tells you more than the headline ever will.

First Steps

From choosing to live

  1. 1

    Ask how many people log in daily

    That number, not the visitor count, tells you what account to buy and what support allowance to quote. Ask it before you price anything.

  2. 2

    Agree a leavers process on day one

    Who tells you when somebody goes, and how fast access is revoked. Write it into the retainer, because nobody remembers to mention a departing freelancer.

  3. 3

    Report the support hours you use

    A visible allowance makes renewal simple. An invisible one makes every renewal a negotiation about value you cannot evidence.

In the Box

Packed with every plan

  • NVMe under the database, where admin screens actually live
  • One-click installs for WordPress and 240+ other applications
  • PHP versions picked per site from the panel
  • A separate cPanel account per client under your WHM
  • A backup taken daily, with restores you run yourself
  • Mailboxes on the client's own domain, included
  • Webmail plus IMAP, POP and SMTP for a newsroom's own clients
  • Spam and virus filtering fitted to every mailbox you create
  • Real people on the counter, every hour of every day
  • Thirty days' money back on hosting, seven days on reseller

Across the Counter

Things people ask us all the time

My client says the site is fast but the editor is slow. What do I tell them?

That they are both right. Visitors are served from cache; editors are not, so every admin click rebuilds the page from PHP and the database. The fix is back-end speed — NVMe, OPcache and object caching — rather than anything that would show up on a public-facing speed test.

How do I handle logins for a client's freelancers?

Inside the CMS, give each person the smallest role that lets them do the job, and set an end date in your own diary when the project ends. Never hand out the cPanel login for that. The account under your WHM stays yours, and the client's people only ever hold application-level access.

Which CMS should I steer an editorial client towards?

WordPress unless a specific structure argues otherwise. Joomla where permissions get complicated, Drupal where the content model runs deep. The honest second question is who on your team will support it in two years, because that decides more about the account's profitability than the feature comparison does.

How quickly can a client account be live?

Minutes, not days. The account opens the moment the order clears, the domain — free for year one on annual plans — attaches straight away, and the one-click installer puts WordPress or any of 240+ applications on the page before you leave your chair. An existing site elsewhere is a free migration, usually inside a day.

Read next

  • WordPress Hosting for Small Business

    The small-business client who wants the site to work while they get on with the business, and what that means for your retainer.

  • Hosting Control Panels Compared

    cPanel, Plesk, DirectAdmin or none — compared on what your clients and contractors will already recognise.

  • CMS Hosting

    A quick, guarded home for WordPress, Joomla, Drupal and every major CMS.

  • Web Hosting

    cPanel hosting on NVMe disks, with SSL, migration and year-one domain included.

Moving your site to another host? Start with this checklist.

A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.

One email brings the checklist, then now and again a note about running a site properly. Leave the list whenever you feel like it. Our privacy policy spells out the rest.

Host the newsroom, not just the website.

Back-end speed, one account per client under your WHM, daily backups and free migration with nothing going dark.

See CMS Hosting plans