Agency Brief
Wiki hosting — A client's knowledge base is a ten-year asset you are now holding
Nobody thinks hard about wiki hosting until year four, when the thing contains everything the organisation knows and somebody asks whether it can be got out.
Straight answer first
Put MediaWiki or DokuWiki on a standard plan — installed in one click, on the client's own domain, exportable for as long as they keep it — and add a second layer of access control when the wiki is internal rather than public.
The reseller angle is custody. A knowledge base accumulates for years and then becomes the most valuable thing you host for that client. Everything about how you set it up should assume that one day somebody senior will ask two questions: who can see this, and can we have it back. Have both answers ready from the first week.
Written by the Hosting Seller staff · Checked 24 August 2026
24/7
Support that replies, day or night
1-click
WordPress setup, one click
Free
Certificates on every client site
Daily
Backups across the pool
Written for agencies and resellers asked to host a wiki for a client — an internal handbook, a support knowledge base, a public reference site. It is a small job that turns into a long relationship, which makes the setup decisions unusually durable.
Because DokuWiki keeps everything in files, it needs no database whatsoever. That makes it a badly underrated choice for a small team on modest hosting, with the full version history sitting right there in plain files — which also makes backing it up and proving an export trivially easy, and that is worth more than it sounds.
Private in two layers, not one
Accounts inside the application handle who edits what. For anything genuinely internal, add a second layer at hosting level — a password-protected directory or an IP allowlist in front of the whole thing. Both fittings come as standard here, and together they mean a misconfigured permission inside the wiki is not immediately a public disclosure.
Then keep the list current. Every organisation acquires former staff with live logins, and a knowledge base is precisely the sort of asset nobody audits until there is a reason to. Agree with the client who tells you when somebody leaves, and how quickly you act on it.
The storage curve nobody budgets for
A wiki is an edit-heavy workload where writing to disk matters as much as reading, and its attachments grow forever. Nobody deletes anything from a knowledge base — that is the point of one — so plan for the storage line to climb steadily and unremarkably for years.
Size the account with that curve in mind and mention it to the client at the outset. A modest annual increase agreed in advance is administration; the same increase sprung in year four is a difficult email about a bill nobody expected.
Which engine, and who has to support it
MediaWiki when the client wants public scale and an editing culture people already recognise. DokuWiki for team simplicity, with no database and trivial backups. BookStack when they want something modern and structured. All three run happily on our standard plans, so the choice is genuinely the client's needs rather than your platform's limits.
Weigh the support side honestly, though. The engine you install is the one you will be answering questions about for years, and simplicity has a real ongoing value that rarely appears in a feature comparison.
Prove on day one that it can leave
Run the export before the wiki has anything in it worth losing, check the result opens somewhere else, and write down how you did it. That five-minute exercise is the difference between a promise and a fact, and it is the answer to the question that eventually gets asked.
Wiki farms whose export leaves half the content behind are the failure mode to avoid on the client's behalf. A knowledge base is a decade-long asset and deserves a home it can leave, which is also the sentence that wins you the account against a hosted platform.
We sell the hosting. That is the whole disclosure.
This is the supplier's own page rather than an independent survey, and we would rather say so. No referral fee sits behind the recommendation, so nothing here bends towards whoever pays most.
SSL comes free with every plan and reissues itself before it lapses, so an internal site never greets the client's staff with a browser warning.
- 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
Two layers of privacy
Application accounts inside, plus a password-protected directory or IP allowlist in front, both fitted as standard.
Matched to this verdict
The Pro plan is this page's recommendation made concrete — one flat price, essentials included, upgradeable in place.
One-click installs for every engine
MediaWiki, DokuWiki and the rest go up from the installer, so trying two before deciding costs an afternoon rather than a project.
Backups that make an export trivial
A daily backup and a panel restore in minutes, which is also how you prove custody to a client who asks.
Room for the storage curve
Generous allowances and in-place upgrades, so years of accumulated attachments do not force a migration.
A supplier with a company number
IGI Security Services Ltd, registered in England and Wales — the sort of thing an organisation asks about before trusting you with its knowledge.
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.
| Line item | Hosting SellerBest seller | Typical big-brand host | Typical budget host | Typical 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
Run the export before it matters
Export an empty wiki, open the result elsewhere, and document the procedure. Five minutes now converts a promise into a demonstrable fact.
- 2
Agree the leavers process
Who tells you when somebody departs, and how fast their access goes. A knowledge base is the asset nobody audits until there is a reason to.
- 3
Warn about the storage curve early
Say at the outset that attachments accumulate and the plan will step up occasionally. Agreed in advance it is administration; sprung later it is a complaint.
In the Box
Packed with every plan
- One-click installs for the mainstream wiki engines
- A password-protected directory or IP allowlist in front, as standard
- Free SSL on every site, reissued before it lapses
- A backup taken daily, with restores you run yourself
- PHP versions picked per site from the panel
- Generous storage allowances with upgrades applied in place
- NVMe SSD storage on every shelf, not just the top one
- Free site migration handled by our staff
- A 99.9% uptime target, watched by monitoring day and night
- Thirty days' money back on hosting, seven days on reseller
Across the Counter
Things people ask us all the time
How do I keep a client's internal wiki genuinely private?
Two layers. Accounts inside the application decide who edits and reads, and a password-protected directory or an IP allowlist in front of the whole site catches anything a misconfiguration inside the wiki would otherwise expose. Both come as standard, and together they are far stronger than either alone.
Which engine should I put a client team on?
MediaWiki for public scale and a familiar editing culture, DokuWiki for team simplicity with no database and trivial backups, BookStack for something modern and structured. All three run on our standard plans, so decide on the client's needs and on who will answer questions about it in three years.
What do I say when they ask whether they can get it out?
Show them, rather than telling them. Run the export, open the result somewhere else, and send a screenshot. A supplier who can demonstrate custody in five minutes is treated very differently from one who says the right words.
What uptime should I quote for an internal site?
The same 99.9% target, backed by a pro-rated credit on any month that falls short through a fault at our end — ask and we apply it. We call it a target rather than a contractual SLA on purpose, and hardware and network faults are flagged to us by the platform we run on, usually before the first person notices.
Read next
Hosting for Freelance Web Designers
Running your own site alongside a stack of client builds, and the account shape that keeps both tidy.
DirectAdmin vs cPanel for Resellers
Two reseller panels compared on licence cost and on what your clients will already recognise.
Web Hosting
cPanel hosting on NVMe disks, with SSL, migration and year-one domain included.
WordPress Hosting
WordPress looked after for you — LiteSpeed caching, staging copies and daily backups.
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.
Hold the knowledge, and prove you can hand it back.
One-click installs, two layers of access control, daily backups and an export you can demonstrate in five minutes.
See Web Hosting plans