If you wanted a scoreboard, you already have one. The 2026 matrix compared nodes to categories and tags, groups to trust levels, widgets to theme components, add-ons to plugins, license-plus-VPS to Docker RAM, and the ugly fact that XenForo officially imports Discourse 3.x while the other direction is a Discourse-side project. This article will not reprint that table. It will take a side — sometimes two sides — on what you actually gain and lose in operations, then name who should pick which.
This is also not the stay-or-migrate framework (lock-in, staff, URLs, cost, size) and not the Discourse versus traditional forums category essay. Those stay linked because a “pro” that costs you your volunteer moderators is not a pro. Read them. Then use this as the close: Discourse if you want automation, modern defaults, and a hosted off-ramp. XenForo if you want widget and style depth, the gaming-and-forum add-on culture, and a cheap PHP box. Everything else is taste.
I have run and watched both. The following is opinion grounded in official docs, not a vendor brochure.
A fair close still needs a clock. Features do not operate themselves. Someone has to patch the box, answer a flag at 21:00, explain to a veteran why their favourite room is now a tag, and sign the invoice. The rest of this article is written for that person.
A week in each chair
Monday on XenForo. You check Tools jobs, glance at Appearance → Outdated templates after last week’s add-on bump, and answer two reports. A member cannot see the donor forum; you open Groups & permissions → Analyze permissions, find a Never on Registered that a well-meaning admin set in 2024, and fix it without guessing. Someone wants the homepage to feature three article threads; you clone a New posts widget, give it a stable key, assign it to the page-node position. Evening traffic is members plus Discord unfurls. If guests are cheap, Redis and the page-cache context are doing their job. If the board feels sticky, you look at cron before you look at a new product.
Monday on Discourse. You open Latest. Flags sit in the review queue. A TL0 user cannot embed the four screenshots their support post needs; that is the sandbox working. You point them at the welcome topic that says “read five topics, hang around ten minutes.” A regular lost TL3 after a quiet month; you decide whether to lock them or let the 100-day window do its job. Nobody asked you for a sidebar widget. Someone asked why there is no last-post column. You do not have Analyze permissions; you have a category security table and a group membership. If you are hosted, you did not SSH. If you are self-hosted, you are hoping you will not need ./launcher rebuild app this week.
Neither Monday is morally better. One is a forum operator’s Monday. The other is a modern-community operator’s Monday. If you read those two paragraphs and only one feels like a job you can staff, you already have the answer. The lists below exist to make the feeling precise.
What you gain if you pick Discourse
1. Trust levels that run while you sleep
XenForo will sandbox nobody you did not sandbox. Registered can post in every public node the day they confirm, unless you built promotions, a validating group, and a staff habit. Plenty of good boards do that. Plenty more never get around to it.
Discourse’s TL0 → TL3 machine is on when you finish the wizard. New accounts read before they get the full toolbox. Invited people start at TL1. Regulars (TL3) earn extra tools on a 100-day rolling window and can lose them. TL4 is staff-only — Meta 2026 is explicit. You can lock a level, and groups can grant a minimum, but you do not have to design the first four rungs.
The operational gain is not “gamification.” It is fewer first-day spam incidents and a path for regulars to help without you inventing Trusted Member II. The cost of that gain is cultural: quiet months demote TL3, and veterans who think in post-count ranks will ask where their ladder went. If that conversation sounds healthy, this is a real pro. If it sounds like a civil war, it is not.
2. Modern defaults you do not have to assemble
Latest as home. A composer that drafts while you keep scrolling. Quote-by-select. @ mentions. Oneboxes. Notification levels per topic, category, and tag. A mobile-first reader. PWA-shaped install. Markdown plus a rich editor. Official Docker that provisions Let’s Encrypt. An installer that will let you skip SMTP and use Discourse ID (social + id.discourse.com) so day one is not an SPF ticket.
XenForo can approximate almost all of that. Widgets, 2.3 style variations, friendly URLs, PWA setup, Google OAuth mail, a portal — the pieces exist. They are pieces. Discourse’s gain is that a competent person who has never seen a forum ACP can open Latest and behave. XenForo’s gain, later in this piece, is that a competent forum person can make the homepage look like a magazine. Decide which competent person you have.
3. Official hosted is a product, not a hope
This is the Discourse advantage XenForo cannot honestly match today. discourse.org/pricing in 2026 lists Free / Pro / Business / Enterprise. Pro has been publicly listed around $100/month, Business around $500/month; staff seats and monthly email caps change — read the live grid. Hosted means someone else owns PostgreSQL, Redis, rebuilds, and the next Let’s Encrypt surprise.
XenForo is a license you put on a host. There are excellent third-party XenForo hosts. There is not a first-party “XenForo Inc. runs the box” tier with the same gravity as Discourse’s own cloud. If your organization wants a community and wants to fire the sysadmin role, Discourse hosted is the pro that ends the meeting.
Self-hosted Discourse is not that pro. Official recommended RAM is 2 GB+ (1 GB only with swap). You will learn ./launcher rebuild app. That is a different product shape: open source, heavier than typical XenForo, still yours to drop.
Three-year money, spoken as operations rather than as a pricing-page screenshot:
| Path | What you are really buying | Who this is “cheaper” for |
|---|---|---|
| XF license + modest PHP VPS | Software you already know how to restore | Hobby and mid-size trees with a PHP person |
| XF license + add-ons + ES box | Search and extras on the same mental model | Large XF that skipped rungs in the scaling ladder |
| Discourse official hosted | Staff seats, email cap, no Docker | Orgs that will pay to fire the sysadmin role |
| Discourse Docker on 2 GB+ | Free software, paid RAM and a rebuild person | Teams that already run containers |
If your CFO hears “Discourse is free” and approves a $6 VPS, you have a project failure before the first topic. If your CFO hears “XenForo is expensive” and ignores the hosted Discourse line that is larger than the XF license plus VPS, you have the same failure with different stickers.
4. A flat IA that matches how new people already search
Categories plus tags is how a lot of 2026 users already think, because they grew up in Slack, GitHub Issues, and Discord channels — not in “Forum 7, Subforum 3.” If your work is cross-cutting (version, region, status), tags are the honest model. Maintaining a XenForo tree that is really a tag system is possible (prefixes, thread fields, discipline). It is also how you get 80 nodes and a permission rebuild that locks the site.
The gain is less tree to moderate. The loss is less tree to inhabit. I will not pretend both are wins.
5. Open source, exportable, harder to hostage
Discourse the software is open source. Official hosted is a vendor relationship you can leave with an export. XenForo is proprietary. You own your database; you do not own the application. For some procurement teams that is a Discourse pro all by itself. For others it is irrelevant next to “can our guy restore internal_data.” Both reactions are adult.
What you lose if you pick Discourse
1. Widget and style-property depth
XenForo’s layout system is an ACP product: widget definitions, instances, positions, display conditions, cache lifetimes, <xf:widgetpos>. Combined with style properties (palette, 2.3 light/dark variations, CSS-type properties, @xf-stylePropertyName in Less) you can build a homepage that is still XenForo after five years of child-style edits. We already wrote the widgets and 2.3 pieces. That depth is why “forum plus magazine plus landing page” sites stay.
Discourse’s equivalent is themes and theme components (Ember front end) plus plugins (Rails). There is no Appearance → Widgets. You will install a component, write CSS, or live with Latest. That is not a skill issue. It is a shallower official layout model. If your brand is the first screen — hero, three columns, campaign landing, sidebar stats — Discourse is a step down unless you budget a front-end developer who likes Ember plugin outlets.
People who say “we’ll just theme it” are describing a job. XenForo already hired that job into the ACP.
2. The gaming and “forum extra” add-on ecosystem
This is the loss that should end most game-community daydreams.
XenForo’s third-party culture is why this site has working patterns for a server directory, a whitelist application, credits and user upgrades, Discord OAuth and webhooks, ranks, and custom fields that promotions can read. Some of that is core. Some is named add-ons. All of it assumes a node tree and groups.
Discourse can do games communities. People do. They do it with fewer purpose-built listing/shop/application products, more plugins you must keep rebuilt, and more “that is just a category.” If XenRio-shaped live-stream directories, donor shops, or application boards are load-bearing, Discourse is not a lateral move. It is a product abandonment. Call it that.
XenForo also loses, in the other direction: Discourse’s official and official-adjacent catalogue (chat, assign, documentation categories, hosted extras) is stronger for support + knowledge shops. “Ecosystem” is not a single trophy. It is your three features.
3. A cheaper, more familiar typical VPS
A small XenForo lives on a PHP 8.3 box with MySQL. That is the same species as WordPress. Shared hosts still understand it. A 1–2 GB VPS is a normal starting point. You can find a contractor in any city.
A small self-hosted Discourse wants the official Docker stack and 2 GB+ RAM to be pleasant. Contractors who will ./launcher rebuild app without making it worse are a smaller set. Hosted Discourse flips the comparison (you pay monthly, you stop owning the box). If you were hoping to “save money by using free software on the same $6 VPS as the old phpBB,” you will have a bad month.
XenForo’s license is not free. Three-year math still often favors XF + cheap VPS for a hobby or mid-size classic forum, especially if you already know the stack. Discourse wins the money argument when you value hosted or when you were about to hire a PHP person you do not have.
4. Analyze-permissions-shaped access control
XenForo permissions are a language: Never > Yes > No, inherit, private node only affecting View node, Analyze permissions, user permissions as a last group of one. It is fiddly. It is also how you build a 15-year tree of private children without guessing.
Discourse category security via groups is enough for “staff,” “customers,” “public.” It is not the same diagnostic. If your community is an ACL — game factions, regional officers, application stages, donor wings — you will miss Analyze permissions the first time someone cannot see a room and nobody can say why in one screen.
Trust levels do not replace that ACL. They replace the ladder. You still need groups for walls. You just get fewer knobs on the walls.
5. An official one-click path back
If you leave Discourse for XenForo, official XenForo importers list Discourse 3.x. If you leave XenForo for Discourse, you are on Meta threads, scripts, and partners. That asymmetry is a XenForo pro and a Discourse con for anyone who wants a return ticket. Operations people should care more about this than about which composer is prettier.
Permalink shape is part of the same loss. Years of /threads/title.12345/ become a redirect project. If those URLs are the business, the stay-or-migrate article already told you to stay.
6. Staff who already think in boards
This is not nostalgia. It is bus factor. A moderator who can do XenForo warnings, prefixes, and “move thread to the right node” in their sleep will be slower and angrier on Discourse for a quarter. Maybe they come around. Maybe they leave. Count them before you count the likes on a Discourse screenshot.
Retraining is a calendar, not a vibe. Budget, at minimum:
- A week where staff use Discourse as members (TL0/TL1 view, notifications, flags) before they get a moderator grant.
- A written glossary: topic not thread, category not forum, tag not child board, personal message not conversation, TL4 not “admin.”
- A parallel flag rota so the old XenForo queue is not abandoned on cutover day.
- Permission to keep one veteran as “tree ambassador” whose only job is to tell you when a tag should have been a category.
If you cannot staff that calendar, the “modern defaults” gain is a fiction. Defaults only help the people who show up.
False pros (things people claim, then regret)
“Discourse will make the community active.” No. Latest with three staff posts is as dead as a phpBB index with three staff posts. Onboarding is still human work.
“We will keep our 80 forums as categories.” Then you did not pick Discourse’s IA. You picked Discourse’s CSS. Members will say it is confusing, and they will be right.
“We will rebuild the credits shop as a plugin.” Name the maintainer and the rebuild budget. If you cannot, you are donating the shop.
“XenForo cannot do modern UI.” 2.3 already has variations, deferred JS, WebP, a PWA setup. A dated XF site is usually a dated style and a 90-node tree, not a 2012 engine.
“Hosted Discourse means we never think about mail.” Hosted plans have monthly email caps. A mailing-list-shaped community will hit them. Read the live pricing grid.
“Open source means free as in lunch.” Open source means you can leave. Lunch is still RAM, SMTP, and a person.
What you gain if you stay on XenForo (the same list, inverted)
Say it in the affirmative so it does not sound like fear.
- A node tree that can be the product, plus page nodes and help pages for the FAQ you do not want as a topic.
- Widgets and style properties deep enough to ship a portal without a plugin developer.
- Add-ons for the forum extras game and hobby communities actually buy.
- PHP hosting you can buy anywhere, plus a license model you pay without a meter on staff seats.
- Permission math you can analyze.
- Official imports in from phpBB, vBulletin, IPS, MyBB, SMF, Discourse 3.x, and XenForo itself.
You do not gain a first-party hosted cloud. You do not gain TL0-by-default. You do not gain a culture that wants you to have five categories. If those three sentences are your strategy, you are on the wrong product.
Who should pick Discourse
Pick Discourse when most of this sounds like your next year:
- Greenfield, or a tree nobody uses.
- Public or semi-public discussion where new-user sandboxing is the daily incident.
- Success looks like Latest + tags, not a board index.
- You will pay official hosted to not own a server, or you already like Docker.
- Staff are community people, not ACP stylists. They will accept theme components.
- You do not need a listing/shop/application stack.
- You want TL3 regulars to carry a slice of moderation.
- Procurement likes open source and a clean export.
Typical good fits: open-source project support, a company’s public discussion site, a modern association that is fine with tags, a new hobby community with no 2008 veterans to negotiate with.
Do the first week properly. Do not import the graveyard on day two.
Who should pick XenForo
Pick XenForo when most of this sounds like your next year:
- The rooms are the product (factions, regions, products with legal walls).
- You need a homepage that is a page, not only a topic list.
- Load-bearing features live in the XF add-on culture (or in core patterns this site already documented).
- Staff restore PHP and MySQL in their sleep, and you do not want to teach Docker.
- Three-year cost should be license + a modest VPS, not $100–$500/month.
- You care about Analyze permissions and a deep private tree.
- You might need to absorb a phpBB, vBulletin, or Discourse 3.x later — official importers exist in that direction.
- Veterans will leave if you take the index away.
Typical good fits: long-lived hobby and game communities, classic big boards modernizing off phpBB/vBulletin, any site whose brand is a styled forum plus a portal.
If you are on XenForo and merely unhappy, stay and do the stay projects: flatten nodes, kill dead add-ons, turn on cache, write onboarding. Unhappiness is not a product defect.
Four communities, one paragraph each
The 12-year racing forum. Tree of series, regions, and a classifieds board. Two volunteer mods who know prefixes. XenForo. Discourse would delete their map and not replace the classifieds pattern. If the code they are on is phpBB 3.3, import into XenForo; do not change category.
The SaaS support room. Public docs-adjacent discussion, version tags, a staff who already pay for SaaS. Discourse hosted. Trust levels sandbox throwaway accounts. You will not miss widgets until marketing asks for a magazine homepage — and then you tell marketing the homepage is Latest plus a documentation category.
The Minecraft network. Server list, whitelist apps, Discord, donor ranks. XenForo. This is not close. The listing and whitelist articles exist because that is where those products live.
The new local-history society. Forty people, no sysadmin, a chair who can pay a small monthly bill and cannot SSH. Discourse hosted (even Free/Pro, after reading the live limits). XenForo is a better forum, and they would still break it on a cheap shared host.
If your community is not one of those four, write the fifth paragraph yourself before you buy anything. One paragraph. If it takes a page, you are still shopping.
Who should pick neither (this week)
- You need forums + blogs + files + commerce in one ACP. That is still IPS versus XenForo, not this close.
- You need a chat app. Discord is not a forum; the Discord article is an integration, not a replacement.
- Nobody will operate the result. Hosted Discourse can save you. A self-hosted anything cannot.
- You want both a 40-node tree and trust-level automation and a $0 host. You want three products. Buy one.
A close you can use in a meeting
Do not list twenty features. Say one of these paragraphs and sit down.
Discourse paragraph: “We want new accounts sandboxed without a promotion engine we will forget to maintain. We want Latest and tags, not a board map. We will pay Discourse to host it, or we have a person who can own Docker. We accept that the homepage will not be a widget portal and that our gaming extras will not come with us. TL4 stays a staff grant.”
XenForo paragraph: “We are a forum with rooms, a style we tune, and two add-ons we cannot lose. We have PHP hosting and people who understand Never/Yes/No. We will not pay a hosted-Discourse bill to get a worse tree. If we ever absorb another site, XenForo already lists the importer. We will sandbox new users ourselves or live with the risk.”
If the room cannot choose a paragraph, they are not ready to choose a platform. Give them the matrix and the stay-or-migrate filters, and schedule a date.
What this close will not do
It will not invent a Discourse “widget ACP.” It will not invent XenForo official hosted. It will not quote add-on counts that will be wrong next month. It will not tell you Discourse is kinder or XenForo is more professional. Kindness is moderation culture. Professional is backups and a runbook.
It will also not tell you to migrate because 2026 is a year that ends in six. Years do not pick software. Operators do.
Takeaways
- Discourse’s real gains versus XenForo are trust-level automation, modern defaults, and official hosted. Self-hosted Docker is a different, heavier gain.
- Discourse’s real losses are widget/style depth, the gaming/forum add-on stack, a cheaper typical VPS, Analyze-permissions ACL, and a symmetric official importer.
- Pick Discourse when the community is a stream and you want the sandbox and/or the hosted bill.
- Pick XenForo when the community is a tree (or a styled portal) and you want PHP, add-ons, and permission math.
- A feature matrix cannot override missing operators, permalinks, or a load-bearing add-on. Use the other two articles for that.
- If you cannot say the Discourse paragraph or the XenForo paragraph out loud, you are not deciding. You are browsing.
Pick the product whose default week matches the week you are willing to live. Then stop comparing it to screenshots.