Forum hosting for sites that write more than they read.
A forum breaks the rule every other WordPress site follows. The busiest pages change constantly, most visitors are signed in, and the thing people do most is post.
Where a forum actually spends its time.
Page caching barely helps here. What matters is how fast a write lands and how fast a thread renders afterwards.
Writes that do not queue
Every reply is an insert plus a handful of updates to thread and forum counters. The database is tuned for that mix rather than for a read-mostly brochure site, so a busy thread does not slow down the whole board.
Search that does not table-scan
Forum search is the single most expensive query a community runs, and it runs constantly. Indexing and query limits are set so one person searching does not stall everybody else posting.
Signed-in by default
Members are logged in, so page caching does not apply to the pages they actually use. Those come from the object cache and a database that was expecting them.
Moderation stays usable
A spam wave is a write storm plus a moderator trying to work through it. Admin capacity is kept out of the front-end pool so the queue is workable exactly when it is full.
Undo a bad bulk action
Bulk moderation is one click away from deleting the wrong thing. Daily backups mean a mis-clicked mass delete is recoverable rather than final.
The failures a community notices first.
Forums do not fail by getting slow for anonymous visitors. They fail when posting is sluggish, search times out, or the moderation queue becomes unusable during the exact hour it fills up.
- Post and reply latency, not just page load
- Search kept off the slow path
- Admin capacity reserved for moderators
- Restore after a bulk action goes wrong
Measured in posts, not pageviews.
The number that matters on a forum is how long a reply takes to land while a few hundred other people are reading and writing at the same time.
What we change for forums
A forum is the one WordPress workload where the write path matters more than the read path, and every row here follows from that.
| Setting | What we do | Why |
|---|---|---|
| MySQL configuration | Tuned for a write-heavy mix | Every reply inserts a post and updates several counters, which is the opposite of the read-mostly profile most WordPress tuning assumes. |
| Search queries | Indexed, with a bounded result set | Forum search runs constantly and unbounded, and it is the query most likely to take the whole board down with it. |
| Page cache | Anonymous thread views only | Members are signed in, so the pages that carry the community are pages a cache is never allowed to serve. |
| Admin capacity | Held outside the front-end pool | A spam wave makes the moderation queue busiest at the exact moment the front end is under load. |
| Revision storage | Capped on posts | Edited replies accumulate revisions faster than articles do, and the table grows until queries against it slow down. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Which forum plugins do you support?
Why is my current forum slow only at peak?
Can you handle a spam wave?
Do you cap how many members or posts I can have?
Give the community somewhere fast to talk.
Start in minutes, or let us move the board across - free on every plan.