The Revolt Was Real. The Birth Story Is Less Certain.
In October 2009, vBulletin announced a new pricing structure ahead of vBulletin 4.0. The reaction was immediate, loud, and — for a subset of paying customers — punitive. The Register reported on 28 October 2009 that vBulletin had banned multiple paying customers from its own support forums after they complained about the pricing overhaul. Some of those customers also said they lost access to product updates and to the vbulletin.org modification site.
That much is documented. The part that usually follows — that the revolt “birthed XenForo” — is a causal claim the retrieved record does not establish. XenForo exists, its developers have a history with vBulletin, and a lawsuit was filed. But the clean cause-and-effect story is folklore until someone reads the primary documents. This article separates the two.
What Changed, in Numbers
The old model, as The Register described it: a one-time owned license at roughly $160, renewed annually for $40–$60 to keep receiving upgrades, support, and security updates. The new model, in vBulletin’s own quoted language: “a one-time owned license fee for each major point release. That means no more annual renewal fees. Once you purchase a major point version, you’ll receive maintenance, security, and minor point releases for the life of 4.x.”
vBulletin 4.0 was priced at $250. A discounted pre-release offer of $130 was available until the end of that week. The announcement came on 13 October 2009, in the run-up to the 4.0 release.
The arithmetic is not complicated. An operator who had renewed at $40–$60 per year was now looking at $250 for the next major version, with the prior license’s value tied to the end of its term. The Register quoted one customer: “my owned license is now worthless, and I am being forced to pay for something that is not available.” That is a customer’s characterization, not a legal finding. But it captures the operator’s actual problem: the thing you paid for — continuity — had been repriced.
The Moderation Response Is the Durable Lesson
The pricing change is the headline. The more instructive event is what happened to the complaint channel. The Register reported that vBulletin rescinded support forum credentials for at least a handful of users, and that one customer said his “quality-forum support” was deactivated, cutting off downloads from vbulletin.org. Another customer, holding multiple licenses, said the credentials associated with each were rescinded.
When update access and community participation share the same credential, a moderation decision becomes a licensing decision. That is the operator-relevant fact. It does not matter whether the bans were intended as punishment or as forum hygiene; the effect was that a paying customer could no longer reach the files and support that the license fee was supposed to buy. The Register’s report notes that vBulletin’s general manager did not answer questions about the bans within 36 hours of being contacted.
A contemporaneous MacRumors forum thread adds secondary complaints: that support via ticketing was no longer complimentary and cost $80 more; that the presale window was under three weeks; that multi-license holders received no discount. These are forum-user claims, not verified company statements. Treat them as evidence of customer perception, not as audited pricing.
The XenForo Question
The standard narrative goes like this: Internet Brands bought vBulletin in 2007, the original developers left, the 2009 pricing change enraged customers, and those developers launched XenForo as the lifeboat. The retrieved record supports some pieces and not others.
Supported: Internet Brands purchased vBulletin in July 2007, and most of the original developers left that summer, per The Register. A blogger, Kevin Muldoon, states that XenForo was developed by the original developers of vBulletin and that Internet Brands filed a claim with the High Court of Justice a few hours before the first XenForo beta on 4 October 2010, alleging copyright infringement and misappropriation of trade secrets. That is a secondary account, not a court record.
Not supported by the retrieved sources: that the pricing revolt caused XenForo’s creation. The timeline is suggestive — 2009 revolt, 2010 beta, 2010 filing — but sequence is not causation, and the developers’ departures predate the pricing announcement. The causal claim requires Kier Darby’s declaration, the XenForo launch thread, and the court filings. Those retrievals failed. Until they are read, the “birthed” framing is a story operators tell, not a fact they can rely on.
What is documented about XenForo today is its license structure, which is worth reading as a contrast. The current XenForo license grants a single-instance license per URL, requires the deployment URL to be registered in the customer area, and includes support and updates for an initial twelve-month period, with additional payments required to extend beyond it. That is a renewal model, not a per-major-version model. Whether that is better or worse depends on your release cadence and your tolerance for annual line items.
How to Read a License Change as a Risk Signal
The 2009 event is often filed under “vendor drama.” For an operator running a board with 10,000 or more users, it belongs under continuity risk. The relevant questions are not about price alone.
What is coupled to the license credential? If support forum access, update downloads, and modification-site access all hang off the same account, then a dispute over billing can become a dispute over your ability to patch. Ask the vendor, in writing, what happens to update access if a billing dispute is open.
What is the exit cost? A license change is a good moment to price the migration you have been deferring. That means: a full database export you have tested restoring, a redirect map for thread URLs, an inventory of plugins and custom templates, and a moderator tooling gap analysis. If you cannot produce those in a week, the license change is not your biggest risk.
What does the contract actually promise? “Owned” is a word with a specific meaning in the agreement, and it is rarely the meaning customers assume. Read the termination, transfer, and update clauses before the announcement, not after.
What is the release cadence? A per-major-version model front-loads cost at release boundaries. A renewal model spreads it. Neither is inherently predatory; the question is whether your budget cycle and the vendor’s release cycle are compatible.
A Hypothetical Planning Exercise
The following is a planning exercise, not a report of an actual migration. An operator running a 15,000-member board on an owned license could model three scenarios before any announcement forces the decision:
- Stay and pay. Budget the new major-version fee, assume the renewal cadence continues, and price the staff time for an upgrade. Include the plugin rewrite cost, which is usually larger than the license.
- Stay and freeze. Run the last paid version until end of life. Price the security risk of unpatched software and the moderator burden of a board that cannot be upgraded. Set a hard review date.
- Migrate. Price the export, the redirect work, the theme rebuild, and the moderator retraining. Compare against the stay-and-pay number over the same horizon.
The point of the exercise is not to pick migration. It is to have the numbers before the announcement, so the decision is made on cost rather than on the emotion of a support-forum thread.
What the Record Does Not Settle
Several claims that circulate around this event are not supported by the retrieved sources and should not be repeated as fact. That vBulletin 4’s CMS was defective is a blogger’s opinion, not a measured finding. That forum threads were systematically deleted to cover up complaints is a forum poster’s assertion. The outcome of the Internet Brands litigation is not established here; only the filing is described, and only by a secondary source. The causal link between the pricing revolt and XenForo’s founding is unproven.
What the record does establish is narrower and more useful: a vendor changed its license economics, customers objected, and some paying customers lost access to the support and update channels their licenses depended on. That is enough to justify treating license terms as infrastructure, and support-forum access as a dependency to be documented rather than assumed.
FAQ
Did the 2009 pricing change cause XenForo to be created?
The retrieved sources do not establish causation. They establish that the pricing change and customer backlash occurred in October 2009, that most original vBulletin developers had left by that summer, and that a blogger reports XenForo’s first beta in October 2010 and an Internet Brands claim filed shortly before it. The causal claim requires primary documents that were not retrieved.
What exactly did the new vBulletin license change?
Per The Register’s quotation of vBulletin’s announcement, the prior annual renewal fee was replaced by a one-time owned license fee per major point release, with maintenance, security, and minor point releases included for the life of that major version. vBulletin 4.0 was priced at $250, with a $130 pre-release discount.
Were paying customers actually banned from the support forums?
The Register reported that multiple paying customers were banned after complaining about the pricing scheme, and that at least one said his modification-site access was deactivated. vBulletin’s general manager did not respond to questions about the bans within the reported window.
Is XenForo’s license model the same as vBulletin’s new model?
No. XenForo’s current license grants a single-instance license per registered URL and includes support and updates for an initial twelve-month period, with additional payments to extend. That is a renewal model, not a per-major-version model.
What should an operator do when a vendor announces a license change?
Price the exit before reacting to the price. Confirm in writing what the license credential controls, test a full export and restore, inventory plugins and custom templates, and model stay-and-pay, stay-and-freeze, and migrate scenarios over the same horizon. The license fee is usually the smallest number in the comparison.
