Estates & Custody
Drupal vs WordPress — The content model is the easy part. The domain estate is the one nobody owns.
You are balancing serious content modelling against a comfortable editing experience, and somewhere in the same organisation sit a dozen campaign names, an acquired brand and two registrations paid for by a card belonging to somebody who left in 2021.
The short answer
Choose WordPress for the overwhelming majority of organisational sites, and Drupal where structured content, editorial workflow and deep system integration are written into the brief, with our hosting running either comfortably — and, whichever wins, appoint one owner of the domain estate at the same time, because that is the governance gap the CMS decision will not close.
Below: how to audit an estate you have inherited, who the registrant of record ought to be, what to do with names that exist only to redirect, and how one renewal calendar changes the risk profile.
By the Hosting & Domains team · Reviewed 24 August 2026
NVMe
Disks under every tier
Free
Year one of the name
99.9%
Uptime we aim at
Flat
Renewals, year on year
Most writing on this subject is a league table funded by referral fees. This brief accepts that the CMS question is usually answered by the brief itself, and spends its time on the problem that outlasts it: custody of the names.
Entities, fields and views give Drupal an architecture able to model almost any content relationship you can describe. That is exactly why public bodies and universities standardise on it — and those same organisations are the ones most likely to hold thirty domains with no single list of them.
Audit the estate before you scope the build
Start with a list, because most organisations do not have one. Every name the institution uses or has ever used, where it is registered, who can log in, when it expires, and what it currently serves.
Three categories always emerge. Names in use and accounted for. Names in use and registered by somebody nobody can reach. And names nobody remembers buying, quietly renewing on a card that will stop working.
The second category is the dangerous one. A name serving live traffic from an account only a departed agency can access is an outage waiting for a renewal date, and no CMS migration will discover it for you.
Who the registrant of record ought to be
The registrant should be the organisation, named exactly as it is named in the company or public register, with a role address rather than an individual's mailbox as the contact.
Individuals leave. Agencies are replaced. A registrant record naming a person is a single point of failure that only reveals itself when that person is unreachable and a transfer needs approving.
Fixing it is administration, not engineering. But mind the timing: at many registries rewriting the registrant details starts a sixty-day freeze against transfers, so do the consolidation and the tidying in an order that leaves nothing frozen when you need it to move.
The names that exist only to point somewhere
Every institution accumulates redirect-only names: an old campaign, a rebranded department, a shortened URL printed on something physical. They serve no content and they still cost a renewal and a certificate.
Keep the ones with links or printed material behind them and be ruthless about the rest. What matters is that the decision is deliberate: a redirect quietly lapsing takes traffic with it, and the printed poster does not know.
Serve them from one place, on one certificate arrangement, with one owner. A redirect estate scattered across four providers is four chances a year to be surprised.
One calendar, one owner
The single highest-value change available here is consolidation: every name in one account, with real registry expiry dates visible and auto-renew set as policy rather than case by case.
It removes the failure mode that actually happens to institutions. Not a compromise, not a hardware fault — an expiry nobody was watching, followed by a grace period, then redemption at several times the price, then an auction.
Put a role, not a person, on the account. The renewal calendar should survive a resignation as easily as the content model does.
What we would buy in your position. WordPress for the overwhelming majority of organisational sites, and Drupal where structured content, editorial workflow and deep system integration are written into the brief, with our hosting running either comfortably.
In concrete terms that is our Turbo option: one flat rate carrying the essentials (SSL, migration, copies, mail) this market prefers to bill separately, with in-place upgrades ready when the work picks up.
The rate you register at is the rate you renew at, so year two costs precisely what year one did — nothing lying in wait on the invoice.
Check every word of this yourself. Ask any supplier how consolidation is handled, whether expiry dates are shown against every name, and how fast an auth code is issued. Those three answers describe how well an estate can be governed there.
The company here is Azaanex Inc., federally incorporated in Canada, on the public register — a record of exactly the kind your own registrant details should match.
The refund window covers the rest — bring a live site over, run it for two real weeks, and let ordinary use answer what no sales page can.
Our interest, declared up front
Consolidation happens to suit us, since it usually means more names in one account here. It also happens to be the advice we would give an institution that consolidated somewhere else entirely.
A copy is taken daily on every plan, and putting a file or a database back is one click in the panel rather than a support ticket.
- Every name in one account with real expiry dates
- Role contacts rather than individuals
- Auth codes issued on request, no argument
- Renewal figures published, not footnoted
Why Hosting & Domains
Standard on every plan
The essentials inside, not added on
SSL, the migration, backups and mail come with every plan rather than appearing as checkout extras.
One account for the whole estate
Live names, redirect-only names and the acquired brand all in one list, with registry expiry dates shown against each.
The verdict, turned into an order
The Turbo plan is this page's conclusion in product form — one rate, essentials inside, upgradeable in place.
A refund without an argument
If we are not the fit, leaving is one request rather than a negotiation — which is why we invite the test.
Contacts that survive a resignation
Role addresses on the registrant record, so no transfer ever waits on somebody who left in 2021.
A company you can look up
Azaanex Inc., federally incorporated in Canada — a host whose filing you can read before committing to anything.
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
Build the list nobody has
Every name, its registrar, its login, its expiry date and what it serves. The gaps in that table are the findings, and they are usually alarming.
- 2
Put the organisation on the registrant record
Legal name as it appears in the register, with a role address as contact. Individuals leave; the estate should not notice.
- 3
Consolidate in an order that leaves nothing frozen
Rewriting registrant details can start a sixty-day freeze against transfers. Sequence the moves so nothing you need to relocate is locked when you need it.
Built In
Fitted to every plan
- Every name in one account with real registry expiry dates
- Role contacts rather than individual mailboxes on the record
- Auth codes issued on request, with no retention script
- A daily copy, with restores you run yourself from the panel
- Mailboxes that answer at the name you hold
- Your existing site brought across by our engineers, at no charge
- Free SSL on every plan, reissued before the old one lapses
- cPanel, which is what most of the industry already runs
- Money back within 30 days on hosting plans, 7 on reseller
- SSH, Git and Composer on the developer plans
Frequently Asked
Questions we field again and again
How do we find names the organisation has forgotten it owns?
Work outwards from the evidence: card statements and purchase orders, printed material, old campaign links, and the mail archive for renewal notices. Then check each one's registrar and expiry. The names nobody remembers buying are the ones that lapse.
Who should the registrant be on an institutional domain?
The organisation, named exactly as it appears in the public register, with a role address as the contact rather than an individual's mailbox. A person named on the record is a single point of failure that only surfaces when they are unreachable.
Is it worth renewing names that only redirect?
Keep the ones with inbound links or printed material behind them and retire the rest deliberately. What you must not do is let one lapse by accident, because the traffic disappears and the poster on the wall carries on advertising it.
What is the risk in tidying up our domain records?
Timing. At many registries rewriting the registrant details starts a sixty-day freeze against transfers, so a well-meant tidy-up can block a consolidation you had planned for next month. Sequence the moves and nothing gets stuck.
Keep reading
Drupal Hosting
Drupal with Composer, Drush and per-site PHP control, on a name the organisation properly holds.
Secure Hosting
Imunify360, account isolation and hardened defaults for an estate you cannot afford to lose.
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.
Get the estate into one account.
Every name, every real expiry date, role contacts on the record, and auth codes issued on request.
View Drupal Hosting plans