If you want a Skool alternative you can self-host, you have two kinds of choice. Discourse and HumHub are standalone applications you install on a server. BuddyPress, BuddyBoss and BuddyNext are plugins that run inside a WordPress site you already own. Skool itself can’t be self-hosted at all, so any of these means leaving Skool’s platform.
Which one is best depends on what your community does all day. This guide is our honest read of the field. We build BuddyNext, so we will say plainly where the others win.
What is a good Skool alternative I can self-host?
Start with what Skool gives you, because that is the list you are replacing. Skool bundles a feed, a classroom with native video, an events calendar, and points, levels and a leaderboard under one flat plan. Its own pricing page, checked on 26 Oct 2026, lists a 10% transaction fee on the Hobby plan and 2.9% on the Pro plan. Check skool.com for what it charges today.
No self-hosted option copies that bundle exactly. You will pick the parts that matter to your members and accept that some come from a separate plugin or module. That is the trade for owning the thing.
Here are the five realistic options side by side.
| Option | What it is | Runs on |
|---|---|---|
| Discourse | Open-source discussion forum | Its own Ruby and PostgreSQL stack |
| HumHub | Open-source social network and intranet | Its own PHP app (Yii) |
| BuddyPress | Free WordPress community plugin | Your WordPress site |
| BuddyBoss | Premium WordPress community platform | Your WordPress site |
| BuddyNext | WordPress community plugin with a free core | Your WordPress site |
The first two give you a clean break from WordPress. The last three assume you want WordPress, or already have it.
What does self-hosting a community actually mean?
Self-hosting means the software runs on a server you control, and the members, posts and messages sit in a database you control. That is the whole definition. Everything else follows from it, good and bad.
Here is what lands on your side of the line.
- Hosting. You pick a host and pay for it. For a WordPress community that can be managed WordPress hosting, a VPS or a server you run yourself. The bill is flat. It doesn’t grow because you added members, though a busy site will eventually need a bigger plan.
- Updates. The community software, its add-ons, your theme, WordPress itself, PHP and the server all get updates. Skipping them is how sites get hacked or broken. Someone has to apply them and check the site afterward.
- Backups. A backup you have never restored is a hope, not a backup. Take copies of the database and the uploads folder on a schedule, keep them somewhere other than the same server, and restore one to a test site now and then.
- Where the data lives. Members, posts, profile fields and settings sit in your database. Uploaded files sit in your uploads folder, or in cloud storage if you set that up. You can export, move hosts or query the data directly, because it is yours.
- Email. Notifications and invitations go out through your site. Use a proper mail-sending service so they reach inboxes, and test it before launch.
- Speed. A small community runs fine on ordinary hosting. A large, busy one wants a persistent object cache and a host that can take the load.
None of this is exotic. It is the ordinary work of running a website. But it is work, and Skool does all of it for you. Be honest with yourself about whether you want that job, or whether your host will do it.
For a longer look at the hosted-or-not question, see our post on self-hosted vs hosted community platforms.
Where does Discourse win?
Discourse is the gold standard for forums. If your community is mostly long discussion threads, questions and answers, and a knowledge base that should stay findable for years, it is purpose-built for that and few products do it better.
What it does well:
- Threaded topics and categories that scale to very large, very active forums.
- Moderation tooling that has been refined on huge public forums: trust levels, flagging, rate limits and spam handling.
- It is fully open source. You can run the whole thing for free on your own server through its Docker image, and you never depend on a vendor.
- A big ecosystem of plugins, themes and admins who already know it.
The catch is the shape and the stack. Discourse is a forum, not a social feed with profiles, following and spaces. And it is a separate Ruby on Rails and PostgreSQL application. If your site is WordPress, that means a second system to host, patch and keep in sync, usually on its own subdomain with a single sign-on bridge between the two. Discourse, Inc. also sells managed hosting if you’d rather not run the stack; check discourse.org for its current plans.
Pick Discourse when discussion is the product. See our Discourse comparison for the detail.
Where does HumHub win?
HumHub is a self-hosted, open-source social network and intranet kit. It is a standalone PHP application built on the Yii framework. It is not a WordPress plugin, and it doesn’t pretend to be.
It is excellent for internal team networks, organizations and workspace-style communities. Spaces, posts and files feel tidy out of the box. It has its own module marketplace, built over years. The paid Professional and Enterprise editions add SSO through LDAP, SAML and JWT, advanced search and commercial support, which matters to larger organizations. There is also a managed SaaS option on EU servers.
If you don’t want or need WordPress at all, HumHub is a complete platform on its own. The trade-off is that your website and your community become two separate worlds: two logins to bridge, two things to update, and no access to the WordPress plugin and theme ecosystem. The free Community Edition keeps some features, such as SSO and advanced search, for the paid editions.
Pick HumHub when you want a dedicated social network or intranet that stands apart from your website. Our HumHub comparison covers it in more depth.
ShaunSocial is a self-hosted social network script built on Laravel. You get the source code, a perpetual licence per public installation, and an optional update subscription after the first year, with a managed hosting service on offer. Its feed, groups, polls, short video and messaging suit a team that wants a standalone, TikTok-style social app and is comfortable running a Laravel stack. It is not a WordPress plugin, so it sits beside your website rather than inside it. Check shaunsocial.com for current terms.
Where does BuddyPress win?
BuddyPress is the original free, open-source WordPress community plugin. It gives you member profiles, activity streams, groups and friendships, and it is maintained by the WordPress community rather than one company.
Its strengths are real:
- It is free and has been for over a decade, with no Pro tier to buy.
- It has a huge install base and years of documentation, tutorials and developers who know it.
- It has a deep add-on and theme ecosystem, so you can assemble exactly the stack you want.
The cost is the assembly. Messaging, media, directories and moderation often come from add-ons or a companion theme, and many of those are commercial. You end up choosing and maintaining several pieces from different makers. If you enjoy that, or you already have the stack, BuddyPress is a sound choice. We cover the differences on the BuddyPress comparison page.
Where does BuddyBoss win?
BuddyBoss is a premium WordPress community platform built from a BuddyPress fork. The Platform plugin is free and GPL. Most sites buy Platform Pro and the matching theme, sold as an annual licence, and the white-label mobile app is a separate subscription on top. Check buddyboss.com for current tiers.
Where it genuinely leads:
- It has shipped since 2019 and runs on tens of thousands of live communities.
- It has a proven white-label native mobile app you can publish to the App Store and Google Play today.
- It has years of polish pairing community with LearnDash or Tutor LMS for course sellers.
- Its matching theme gives you a finished look without design work.
If a store-listed app is a hard requirement now, BuddyBoss is ahead of us on that. Our own native apps are in development, with no date. If you are weighing the two, our BuddyBoss alternative page lays out the differences.
Where does BuddyNext fit?
BuddyNext is a WordPress community plugin from Wbcom Designs, the team behind 13 years of WordPress community products. It is newer than every other name on this page, and that means fewer miles on the clock. We would rather say so than have you find out later.
What you get on the free core, with no key and nothing that expires:
- An activity feed with polls, spaces with open, private and secret privacy, member profiles with custom fields, a member directory, notifications, hashtags, reports and a moderation queue.
- A REST API, so a custom front end or an integration is a normal path.
- Direct messages, which run on WPMediaVerse, a free companion plugin.
What Pro adds, for a licence that covers updates and support rather than switching features on: paid membership plans with Stripe and PayPal checkout, coupons, gated spaces, broadcast email, drip sequences, scheduled posts, analytics and live updates. BuddyNext takes no cut of what you charge. The only fee on a sale is your payment processor’s. Pro is listed on our pricing page; for one site it’s $149 a year or $399 once.
For the Skool-style extras, you add separate plugins from the same team:
- Points, levels and a leaderboard come from WB Gamification. BuddyNext does not award points itself; it shows what WB Gamification produces on profiles and in a leaderboard.
- A classroom comes from Learnomy, a separate course plugin. The bridge between Learnomy and BuddyNext sits in BuddyNext Pro.
- Forums and Q&A come from Jetonomy, with a free bridge.
Skool’s edge is that all of this is one screen with almost no settings. BuddyNext is deeper and you configure more. That is a real difference, and for some creators Skool’s simplicity is the better deal. The Skool alternative page sets the two side by side.
How do the options compare on what you run yourself?
This table keeps to the questions that decide a self-hosting project.
| Needs WordPress | Free core | Social feed and profiles | Paid plans built in | |
|---|---|---|---|---|
| Discourse | No | Yes | Forum-shaped | No |
| HumHub | No | Yes | Yes | No |
| BuddyPress | Yes | Yes | Yes | Via other plugins |
| BuddyBoss | Yes | Platform plugin | Yes | Via other plugins |
| BuddyNext | Yes | Yes | Yes | Yes, in Pro |
A few notes on the table. “Paid plans built in” means the platform itself can charge for access. With Discourse and HumHub you would bolt payments on another way. BuddyPress and BuddyBoss lean on separate membership plugins, and BuddyNext includes membership plans in Pro and can also take a grant from WooCommerce or Paid Memberships Pro.
Which one should you pick?
Work through these in order and stop at the first one that fits.
- Your community is mostly discussion and Q&A. Choose Discourse.
- You want an intranet or a team network apart from your website. Choose HumHub.
- You need a store-listed branded mobile app now. Look hard at BuddyBoss.
- You like assembling your own stack and have a developer. BuddyPress is a good base.
- You want a social community on WordPress with a complete free core, and optional paid plans with no platform cut. Choose BuddyNext.
- You want the fewest decisions and don’t care who owns the platform. Stay on a hosted service. That is a fair answer.
If you land on step five, read on. If you land elsewhere, the next sections still apply to any self-hosted choice.
What does it cost to run?
The software is only part of the bill. For any self-hosted platform you add up hosting, any paid licences, your payment processor’s fee on sales, and your own time.
Here is a made-up example, only to show the arithmetic. Say your hosting costs $30 a month, you pay for one Pro licence, and you spend two hours a month on updates and checks. None of those numbers grows because you add a member. Compare that with your current platform’s invoice, including any transaction fee on what members pay you, which you can read straight off your Skool billing history. Then put a value on your two hours.
Two things make the sum honest. First, count your time. If you hate maintenance, it is not free. Second, check which costs scale. A hosted platform’s fee often moves with revenue or tiers. Your hosting bill moves with traffic and size, which is usually slower.
What do you need before installing BuddyNext?
Run through the requirements before you pick a date.
| Requirement | Minimum |
|---|---|
| WordPress | 6.9 or newer |
| PHP | 8.1 or newer |
| PHP memory limit | 512 MB recommended |
| Database | MySQL 5.7 or MariaDB 10.3 |
| Permalinks | Pretty permalinks (not Plain) |
BuddyNext sets itself up on activation: it creates the community pages and prepares its storage. There is a Tools and Maintenance screen that checks background tasks, the object cache and the search index, and tells you in plain words if something has fallen behind. For a community with thousands of active members, a persistent object cache such as Redis or Memcached keeps the heavy lists fast. It is a recommendation, not a requirement.
On updates: the Pro licence key gates updates only. It never switches features on or off, so an expired key doesn’t lock you out of anything you already use.
How do you move off Skool?
There is no one-click importer for Skool. The free BuddyNext Importer reads BuddyPress and BuddyBoss communities, not Skool. The real path is an export, an invitation and a rebuild.
In short:
- Check Skool’s own export options for your members list, and see what columns it gives you.
- Build the new site on staging and recreate your structure as spaces.
- Invite members by CSV, using the bulk invite on the Invites tab, up to 500 rows per upload.
- Run both platforms side by side for a few weeks, then wind down the old one.
Paying members move last, because a subscription on Skool can’t be transferred. Each payer subscribes again on the new site. We wrote the full plan in our guide to migrating from Skool.
A launch checklist for any self-hosted community
Before you tell anyone the new site exists, tick these off.
- A backup exists, and you have restored it once on a test copy.
- Updates are applied to core, plugins, theme and PHP.
- Outgoing email reaches a real inbox, including spam folders.
- You tested sign-up, a post, a reaction and a private space as a stranger on a phone.
- Registration is set the way you want: open, invite-only or approval.
- Someone knows who handles a complaint, and where members report problems.
- Your privacy policy and terms pages are published and linked from sign-up.
- A paying test member can subscribe, see the gated space, and cancel cleanly.
Who should not self-host?
Some people are happier on a hosted service, and we’d rather tell you now.
- You want to launch today and never touch a setting. Skool or Circle will serve you better.
- You can’t spare an hour a month for upkeep and have no one who can.
- Your community is small and still unproven. A free hosted group is a cheaper test of whether anyone shows up.
- Gamified courses on one screen are the entire point, and you don’t plan to need anything else.
If none of that is you, self-hosting buys you something no hosted platform can: the community stays yours when pricing, tiers or terms change.
Where to go from here
The quickest way to feel the difference is to click through a live community. The live demo is a real BuddyNext site you can use with owner access; it runs for four hours and asks for an email. The free vs Pro page shows exactly what each tier includes, and the features overview lists the free core. If you’ve decided to leave Skool, start with the migration guide.