PROVIDER Β· The veteran commercial forum platform
vBulletin
vBulletin launched in 2000 and is now owned by Internet Brands, with a huge install base and many decade-old communities still running, suited to legacy maintenance despite a dated stack and trailing mobile experience.
Pros
Cons
Product Information
Detailed Notes
Overview
vBulletin launched in 2000, originally by the UK company Jelsoft and later acquired by Internet Brands, and ranks among the most installed forum platforms on the web. Many Chinese and English communities running for over a decade still use it, which makes it a required consideration for legacy-site maintenance.
Its shape is the classic forum, thread, and post hierarchy plus add-ons and themes, with commercial licensing including vendor support. For Community & Forum legacy communities, staying on vBulletin usually has practical reasons, from migration cost to heavy customisation and settled user habits.
The limits are equally practical. The 4.x and 5.x stacks are dated with mobile experience and real-time interaction trailing, vendor focus has shifted to cloud editions and self-hosted release cadence has slowed, and third-party add-ons vary in quality, so upgrades need full testing.
Core Strengths
- Operating since 2000 with a huge install base, still maintained across many long-running communities
- Mature forum, group, and permission models supporting complex segmented operations
- Commercial licensing includes vendor support for upgrade and data issues
- A long-standing add-on and theme ecosystem covers most legacy community needs
Product Ecosystem
Forums and permissions
Read, write, and moderation rights configure by group and forum with moderator queues. Legacy communities often carry overly complex permission matrices, so audit before planning an upgrade or migration.
Add-ons, themes, and upgrades
Most add-ons are third-party and need per-item compatibility checks against the target version. Run registration, posting, uploads, and search end to end on a copy before upgrading.
Drawbacks
- Dated 4.x and 5.x stacks with mobile and real-time experience trailing newer products
- Vendor focus on cloud has slowed self-hosted releases and ecosystem activity
- Third-party add-on quality varies, making compatibility issues costly to trace
- Licensing is version and term based, and upgrading old versions may cost extra
Use Cases
- Legacy communities still running (β β β β ) - Maintaining usually costs less than migrating
- Commercial communities needing vendor support (β β β β ) - Licensing includes support for data issues
- Greenfield community projects (β β ) - The stack is dated, so newer options serve new builds better
- Mobile-first and younger audiences (β β) - Interaction and notifications fall short of modern expectations
Pricing
| Plan | Price | Scope |
|---|---|---|
| Self-hosted licence | By version and term | Update access plus time-limited support |
| Cloud edition | Monthly | Vendor hosted, tiered by community size |
| Upgrade services | On demand | Legacy migration and version upgrades assessed separately |
Licensing is version and term based, with upgrades and cloud editions billed separately. Compare migration cost against maintenance cost first, since legacy data structures, add-ons, and user habits inflate migration effort in ways usually under-estimated.
FAQ
-
Is vBulletin still worth using? Yes for legacy communities worth maintaining, while new projects fit Discourse, XenForo, or hosted community products better. The deciding question is whether growth depends on the community, which favours modern interaction and governance.
-
Can it migrate to Discourse? Community-maintained importers move posts and users, but permissions, attachments, and customisations need rebuilding. Archive low-value sections first so years of noise do not come along.
-
Do upgrades lose data? A proper upgrade does not, but add-on compatibility and theme overrides break. Upgrade a copy first and keep full backups plus a rollback image.