Name Owner's Brief
CMS hosting for content teams: who holds the registrar login?
The riskiest thing about an editorial team's infrastructure is rarely the server — it is that one person who left in March is still the only administrative contact on the domain.
The short answer
Pick the CMS your team's actual complexity justifies and put it on hosting with room for the load editorial work creates — then settle the access question, because a publishing operation is only as recoverable as the number of people who can reach the registrar account.
Our CMS plans carry every mainstream engine, so the platform choice is genuinely open. The ownership choice is the one that bites later.
Below: the access map, the hostnames a working team needs, why the admin feels slower than the site, and the plan we would order.
By the Hosting & Domains team · Reviewed 18 August 2026
Free
Move-in handled for you
24/7
Someone on the desk
Daily
Copy of site and data
$0
Charged to open an account
An editorial team meets its hosting through the administration screens rather than the public pages. Those screens go past the cache and reach PHP and the database on every single click, so back-end response time is the number that governs how much the team gets published.
They also meet it through a set of credentials that nobody has written down: the CMS logins, the hosting panel, the mailboxes, and — the one that matters most and gets checked least — the registrar account that holds the domain. Losing the last of those is the only failure on this list that a backup cannot undo.
The access map, drawn before you need it
Four rows: the domain registration, the DNS zone, the hosting account, the CMS. For each, write down who can log in, who is listed as the contact, and who finds out when a renewal notice is sent. Most teams discover at this point that the answer to at least one row is a former colleague's personal address.
Fix the registration row first. It should be registered to the organisation, with a role address rather than an individual's mailbox as the contact, and at least two people able to reach the account. A domain that lapses because a notice went to a mailbox nobody reads is a genuinely irrecoverable-feeling week, and the redemption fees are worse than the renewal.
Then fix the DNS row. Whoever edits the zone controls where the mail goes, which makes it a more sensitive permission than publishing rights and is almost never treated that way.
The hostnames a working team needs
More than the public site. A staging hostname, so a redesign can be reviewed without being published. Sometimes a separate hostname for the admin, so it can be protected differently. An asset or media hostname if images are served separately. And the mailboxes, which are hostnames of a sort too — every author who sends anything on behalf of the organisation.
Each of those wants a record, a certificate entry and a line in the access map. Keeping staging out of the index is a policy decision worth making on day one rather than after a client finds the unfinished version in search results.
Author mail is the part that reaches customers, so it deserves the SPF and DKIM records that let it authenticate. A newsletter that lands in spam is an editorial failure with a DNS cause.
Why the admin feels slower than the site
Because caching serves visitors, not editors. Every admin screen is built from scratch on request, so the figures that matter to the team are back-end response times rather than front-end scores. What an editor feels instead is the storage under the database, the opcode cache in front of the interpreter and object caching on repeated queries — NVMe, OPcache and Redis-class caching.
Four more checks, all judged from the desk rather than the homepage. Whether the roles, draft states and review step are ones the team will use instead of route around. What the media library feels like after three years of images and PDFs have piled into it. Availability measured from the writers' side, because an unreachable admin stops output entirely. And room for whichever of WordPress, Joomla or Drupal the team moves to in two years.
The characteristic mistake is a long selection process for the CMS and a five-minute decision about what it runs on — when the second choice is what the team feels on each of the next thousand working days.
What we would order
The Turbo plan. Certificate, migration and mailboxes inside the figure, a renewal identical to the order, and a tier above it reachable without moving anything.
Support means a person at any hour, and the remit covers the awkward practical questions other hosts hand straight back — including the ones about records and mailboxes that arrive at eleven at night before a launch.
Hosted somewhere else already? We move the whole site at no charge, usually within 24 hours, and it goes on answering visitors throughout.
The row in the access map nobody fills in
We take no referral fees, which is why this page spends its first section on who holds the registrar login rather than on a feature grid. It is the failure that costs the most and the one no supplier likes to raise.
Hosted somewhere else already? We move the whole site at no charge, usually within 24 hours, and it goes on answering visitors throughout.
- Registration in the organisation's name, not an individual's
- Renewal notices to a role address you choose
- Staging hostnames created from the panel
- Mailboxes at your own name for every author
Why Hosting & Domains
Standard on every plan
Support you can test before paying
Send us something difficult before you order; the pre-sale reply is the most attentive version of the service you will meet.
NVMe and LiteSpeed as the baseline
Under every tier including the smallest, which is what the uncached admin screens actually feel.
The essentials inside, not added on
SSL, the migration, mailboxes and daily copies come with the plan rather than as extras at the checkout.
Renewal notices where someone reads them
Set the contact to a role address rather than a person, so a domain never lapses because of a staff change.
An upgrade path that is real
Shared to business to VPS as an account change, with the zone and the hostnames untouched.
One rate, printed where you can read it
You renew at the figure you ordered at, which makes the hosting line a number a budget holder can sign off once.
Prices Side by Side
How our prices sit against the majors
What the market typically charges to join and to renew, set beside ours, including the renewal figure most comparison charts leave out.
| Feature | Hosting & DomainsMost popular | Typical household-name host | Typical bargain host | Typical loss-leader deal |
|---|---|---|---|---|
| Starting price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Renewal price / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Entry-level plan renews at the price you signed up at | ||||
| SSL as standard | ||||
| Migration done for you | ||||
| NVMe drives on the entry-level tier | ||||
| Backups run every day from the first tier up | ||||
| Real humans on support, 24/7 |
*Our own column shows the lowest-priced annual plan on our books, pulled live from the same catalogue that feeds the pricing page, which is why it cannot go stale. Beside it sit three columns holding the ranges that hosts in each bracket tend to advertise: introductory rates that normally ask for one to four years up front, then climb once the term runs out. Naming rivals and printing their figures is something we gave up, since a price nobody can verify on the day you happen to read this has no business on the page. Measure us against the host you are actually weighing up, and give the renewal row the hardest look of the lot.
Quick Start
Order placed to site online
- 1
Draw the four-row access map
Registration, zone, hosting, CMS. Who can log in, who is the contact, who sees the renewal notice. Do this before choosing anything.
- 2
Move the registration to the organisation
Organisation as registrant, a role address as contact, and two people able to reach the account. This is the row a backup cannot rescue.
- 3
Create the hostnames the team needs
Staging, admin if you want it separate, media if assets are split out — each with a record and a certificate entry, and staging kept out of the index.
- 4
Judge the platform by the admin, not the front page
Work inside the CMS during your busiest hour, inside the refund window. Front-end scores tell you nothing about the editors' day.
Built In
Fitted to every plan
- The name registered to your organisation, with the transfer right attached
- Renewal notices sent to a role address you nominate
- A, AAAA, CNAME, MX and TXT on one screen, edits live in minutes
- Subdomains and staging hostnames created without a ticket
- Mailboxes that answer at the name you hold
- Spam and virus screening on every mailbox by default
- Free SSL on every plan, reissued before the old one lapses
- A daily copy, with restores you run yourself from the panel
- People on the support desk every hour of every day
- Your existing site brought across by our engineers, at no charge
Frequently Asked
Questions we field again and again
Who in the team should hold the registrar login?
At least two people, and the registration itself should be in the organisation's name with a role address as the contact rather than an individual's mailbox. Domains are lost far more often to a staff change than to an attack: the renewal notice goes to someone who left, nobody acts, and recovering a name from redemption costs considerably more than renewing it would have.
Which hostnames does an editorial team actually need?
The public site, a staging hostname for reviewing work before it publishes, and often a separate name for the admin so it can be protected differently. Add a media hostname if assets are served separately. Each needs a record and a certificate entry, and staging should be kept out of the index from day one.
Which CMS suits a team publishing daily?
WordPress by default — the editor suits most teams and you can hire for it anywhere. Look at Joomla when the permission structure gets genuinely complicated, and at Drupal when the content model has real depth to it. Every one of the three runs comfortably on these plans.
Why is our admin slow when the site is fast?
Because a cache exists for visitors, and an editor is not a visitor. Every admin screen is assembled from scratch when it is requested, so the team never benefits from the thing that makes the public site quick. What reaches an editor is the storage beneath the database, the opcode cache in front of the interpreter, and object caching for repeated queries — NVMe, OPcache and Redis-class caching in that order.
Does hosting include mail?
Yes. Mailboxes on your own name come with every hosting plan — webmail, IMAP, POP and SMTP, spam filtering already on — which is how each author gets an address that authenticates. Where the website lives elsewhere, standalone email hosting takes the MX records on their own.
Keep reading
CMS Hosting
CMS hosting with room for uncached admin screens and the hostnames a team needs.
Web Hosting
Standard hosting with full DNS control and mailboxes at your own name.
Changing provider? Work through this checklist beforehand.
A straightforward running order for a migration your visitors never spot: which files travel first, how to bring the mail across without dropping a single message, the right moment to repoint DNS, and the two errors that sit behind almost every outage we get called in to fix.
Settle who holds the name first.
Registration in your organisation's name, notices to an address someone reads, mailboxes included, and a free move-in.
View CMS Hosting plans