Skip to main content
HostingSeller
Shop plans

Margin Brief

Forum hosting — The client account that cannot be cached

Every other site in your pool is mostly served from cache — a forum is mostly not, and that single fact changes what you should sell and what you should charge.

Straight answer first

Put phpBB and XenForo-class boards on a strong shared tier with NVMe and object caching, and Discourse on a VPS of its own — what you spend on the database is the real decision, and it is a decision about your pool as much as about their site.

Here is the part that matters commercially: a forum turns the usual caching arithmetic upside down. Nearly all its traffic is signed in and personalised, so database speed and PHP workers carry a load that a page cache would have soaked up on any other site. One community account can consume what a dozen brochure sites do, which means it should not be priced like one.

Written by the Hosting Seller staff · Checked 24 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 resellers and agencies who have taken on a community — a membership site, a trade forum, a support board. Communities are excellent clients: they are loyal, they renew, and they rarely leave. They are also the account most likely to quietly reshape your resource pool.

Work out early what proportion of the traffic is logged in. That single number tells you more about what this account will cost you than any specification comparison, because it is the proportion that cannot be served from cache and must therefore be served by something you are paying for.

Why it does not belong in the general pool

A thousand blog readers mostly collect a stored copy of a page. A thousand forum members each set off live queries against the database, plus session handling, plus personalised page assembly. Same visitor count, an order of magnitude more work at the back end.

Drop that into a pool sized on ordinary sites and everybody else feels it at the busy hour. Either give the community its own tier from the start or accept that you will be moving it under pressure later, which is always the more expensive version of the same conversation.

Notification email is your deliverability problem

Notifications are the retention loop of a community. If replies do not reach inboxes, members stop returning, activity falls, and the client concludes the forum is dying rather than that the mail is bouncing. You will get the blame for the first and never hear about the second.

Mailboxes come on the client's own domain with MailChannels carrying outbound mail, and spam and virus filtering is fitted as standard. Beyond the platform, keep the habits: use a sending domain that matches the site, watch for a sudden fall in click-throughs, and treat a deliverability complaint as urgent rather than cosmetic.

Where the money should go

MySQL on NVMe, object caching for sessions and hot data, discipline about how many add-ons the board runs, and email that genuinely delivers. When in doubt, spend on the database tier first — it is the component that decides whether the site feels alive at peak.

Business Standard is the shape that suits a busy PHP board, and its allowances leave room for the ancillary sites communities accumulate. Discourse and its kind want a VPS of their own, and that is a different quotation with a different margin.

Pricing an account that peaks with its community

Forums are not steady. An announcement, a controversy or a product launch produces a day of traffic unlike any other day that year, and your client will remember how the site behaved during it more than the eleven quiet months either side.

Price for the peak and say so. A community account with headroom, monitored properly, is worth a premium over a brochure site, and communities understand that better than most clients because they can see their own activity graphs.

Coworkers gathered around laptops in an office

The supplier writing this would like the account

We host, we would like the account, and stating that outright is better than a page pretending to be an independent survey. No referral fee sits behind any recommendation here.

Mailboxes on the client's own domain are part of the plan rather than an add-on you would have to itemise and defend.

  • 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

Database-first specification

MySQL on NVMe with object caching for sessions, which is where a community's performance actually lives.

Matched to this verdict

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

Mail carried properly

Mailboxes on the client's domain with MailChannels handling outbound and filtering fitted as standard, because notifications are the retention loop.

Room for the ancillary sites

Generous addon domain allowances, because communities accumulate a rules page, a shop and a blog within a year.

A ladder for the boards that grow

Shared, VPS and dedicated from one supplier, so a community outgrowing its tier is an upgrade rather than a migration.

Cover behind your helpdesk

Real engineers on the counter at every hour, which matters when a community's peak is a Saturday evening.

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

    Measure the logged-in proportion

    Ask for a month of analytics and work out how much traffic is signed in. That number sizes the account and sets the price better than any specification table.

  2. 2

    Test the notification mail first

    Send real notifications to real inboxes across several providers before launch. A community that cannot reach its members will die quietly and you will be blamed loudly.

  3. 3

    Give it its own tier from the start

    Put the community somewhere with headroom before it needs it. Moving a busy board under pressure is the same job done worse and charged for less.

In the Box

Packed with every plan

  • NVMe under the database, where a forum's performance actually lives
  • Object caching for sessions and hot data
  • Mailboxes on the client's own domain with outbound mail carried properly
  • Spam and virus filtering fitted to every mailbox
  • A backup taken daily, with restores you run yourself
  • Generous addon domain room for the sites a community accumulates
  • One-click installs for WordPress and 240+ other applications
  • Upgrades applied to the account in place, with no move between plans
  • Root available on a VPS when the platform demands it
  • Real people on the counter, every hour of every day

Across the Counter

Things people ask us all the time

Why does a community account cost me more than a blog with the same traffic?

Because it cannot be cached. Blog readers mostly collect a stored copy; forum members are signed in and each page is assembled live from the database. The same visitor count produces an order of magnitude more back-end work, and that work is what you are actually paying for.

Whose problem is it when forum notifications stop reaching members?

Yours, in practice, whatever the contract says — because the client will experience it as the community dying rather than as a mail fault. Test deliverability before launch across several providers, watch for sudden falls in engagement, and treat any report of missing notifications as urgent.

How should I price a community account against the rest of my book?

Above a brochure site, and explain why in terms of the peak rather than the average. Communities can see their own activity graphs, so an argument about the day of the announcement lands far better than an abstract one about resources.

How quickly can I get a client board live?

Minutes for the account itself. It opens the moment the order clears, the domain — free for year one on annual plans — attaches straight away, and the one-click installer puts the platform up before you leave your chair. An existing board elsewhere is a free migration, usually inside a day.

Read next

  • Hosting for Side Projects

    Keeping several small projects alive at once, and the account shape that makes it cheap.

  • LiteSpeed Hosting

    The caching arrangement that decides how much of your pool a client site actually uses.

  • Business Hosting

    Shared hosting with the developer kit: SSH, Node.js, Python and PostgreSQL.

  • Plesk Hosting

    Shared hosting on the Plesk panel for people who prefer it to cPanel.

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.

Sell the community account properly.

NVMe under the database, object caching, mail that reaches members, and headroom bought before the peak arrives.

See Business Hosting plans