Skool True Cost: $99/Month vs Self-Hosted WordPress at 500, 1,000, and 5,000 Members
Skool looks simple on the pricing page. One plan, $99 a month, unlimited members. No hidden tiers, no per-seat charges, no usage limits. That simplicity is part of the pitch.
But $99 a month is not what you actually pay to run a Skool community at scale. Once you account for payment processing fees on every subscription you sell, features Skool does not offer that you have to build or buy elsewhere, and the long-term cost of not owning your data or your member relationships, the real number looks very different.
This post runs the math at three realistic community sizes: 500, 1,000, and 5,000 paying members. It compares Skool against a self-hosted WordPress stack built on BuddyPress and Jetonomy. And it includes an interactive calculator so you can plug in your own numbers.
What Skool Actually Charges
Skool has one paid plan at $99/month ($79/month billed annually). That covers the platform itself. But running a paid community on Skool means you are also paying Stripe processing fees on every transaction your members make.
Stripe’s standard rate is 2.9% plus $0.30 per transaction. On a $49/month membership, that is $1.72 per transaction. If you have 500 members renewing monthly, that is $860 a month in processing fees alone, on top of the $99 platform fee.
There is also what I call the ownership cost. On Skool, your member data lives in Skool’s database. Your community lives on Skool’s infrastructure. If Skool changes its terms, raises prices, or bans your account, you have limited recourse. Trustpilot reviews document exactly this problem: accounts banned with no explanation, communities deleted overnight, support unresponsive for weeks.
The Skool Trustpilot page currently sits at 1.9 out of 5. The recurring complaint is not about the product features. It is about what happens when something goes wrong. One review from a creator with 800 paying members describes losing the community with no warning and no path to recover member data.
Skool Cost Breakdown at $99/Month
| Cost Item | Monthly | Annual |
|---|---|---|
| Platform subscription | $99 | $1,188 |
| Stripe processing (500 members × $49/mo) | ~$860 | ~$10,320 |
| Stripe processing (1,000 members × $49/mo) | ~$1,720 | ~$20,640 |
| Stripe processing (5,000 members × $49/mo) | ~$8,600 | ~$103,200 |
| Custom domain email | $6–15 | $72–180 |
| Your data ownership | $0 | $0 (you don’t get it) |
The platform fee is the smallest line item once you start selling. The transaction fees grow linearly with your revenue. At 5,000 members paying $49 a month, you are paying roughly $8,700 per month just in processing costs.
The Self-Hosted Stack: What It Costs to Run Your Own
A self-hosted community on WordPress is not free to run. There are hosting costs, plugin costs, and initial setup costs. What it is not is a $99/month subscription that you cannot cancel without losing everything.
Here is the realistic stack for a community site that matches Skool’s feature set and exceeds it in several areas.
Stack Components and Annual Costs
| Component | What It Covers | Annual Cost |
|---|---|---|
| WordPress hosting (Cloudways/Vultr) | 2 vCPU, 4GB RAM, scalable | $240–$360 |
| BuddyPress | Member profiles, activity feeds, groups | Free |
| Jetonomy | Forum, Q&A, course discussions, support threads | ~$199 |
| WooCommerce | Payments, subscriptions, checkout | Free |
| WooCommerce Subscriptions | Recurring billing, dunning, trials | $239 |
| Stripe processing fees (same 2.9% + $0.30) | Payment processing | Same as Skool |
| Bunny CDN | Fast global delivery for media | ~$60–$120 |
| Email (Postmark or SES) | Transactional and community emails | $60–$120 |
| SSL, backups, monitoring | Security and uptime | ~$50–$100 |
Add those up: roughly $848 to $1,238 per year for the software stack. Stripe processing fees are the same as on Skool because Stripe rates are set by Stripe, not by the platform you use. You can also shop those rates. With Stripe’s negotiated pricing at volume, creators above $1M/year in processing often get down to 2.2% or lower. Skool cannot negotiate that on your behalf.
There is one more line item the self-hosted route requires: setup and occasional development. A clean initial build costs $1,500 to $4,000 depending on scope. Ongoing maintenance runs $100 to $300 a month for plugin updates, performance tuning, and small customizations.
That sounds like a lot until you look at what the same money buys over three years.
Three-Year Total Cost of Ownership
The year-one comparison can favor Skool at small member counts, especially if you count setup costs for the self-hosted option. The three-year picture reverses that almost entirely.
| Scenario | Skool (3 yr) | Self-Hosted WP (3 yr) | Savings |
|---|---|---|---|
| 500 members @ $49/mo | $38,700+ | ~$7,600 | ~$31,000 |
| 1,000 members @ $49/mo | $65,400+ | ~$9,200 | ~$56,000 |
| 5,000 members @ $49/mo | $311,400+ | ~$21,600 | ~$290,000 |
The self-hosted numbers include a $3,000 initial build, annual hosting, all plugin licenses, and $150/month in ongoing maintenance. The Skool numbers include the platform fee plus Stripe processing on the full revenue. Both sides pay the same Stripe rate on transactions, so the comparison is apples to apples on payment processing.
The gap widens at scale because the Skool platform fee is fixed but the processing costs grow with your revenue. At 5,000 members, you are paying $1,188 in Skool platform fees and over $100,000 in processing costs annually. The self-hosted route still costs roughly $7,200 per year at that scale.
Try the Calculator
Use this to run your own numbers. Enter your member count and monthly price. The calculator shows what you pay on Skool versus a self-hosted WordPress stack over one and three years.
Note: both sides pay the same Stripe rate. The calculator uses 2.9% + $0.30, Stripe’s standard rate. The self-hosted setup cost is set at $3,000 (a realistic mid-range build). You can adjust this in your head if you are building it yourself or if your scope is larger.
What Skool Does Well (Being Honest About This)
A fair cost comparison requires being honest about why people choose Skool in the first place. It is genuinely fast to launch. You can go from zero to a paid community in an afternoon. There is no hosting to configure, no plugins to update, no developer to hire. For someone who has never built a website and just wants to sell access to a community, Skool removes enormous friction.
The onboarding flow is clean. The course and community combination is native. The gamification system (points, leaderboards) works out of the box. And because Skool has a large base of existing creators, there is some discovery benefit from appearing in the Skool marketplace.
If you have fewer than 100 members and you are testing a new idea, the $99 entry point is reasonable. The math does not go badly wrong until you start collecting real revenue and have something to lose if the platform bans your account.
The Trust Problem
The Skool Trustpilot page is worth reading before you commit. As of mid-2026, the score sits at 1.9 out of 5, based on reviews that cluster around a few consistent themes.
- Accounts banned with no prior warning and no explanation, often after years of use
- No way to export member data, payment history, or community content after a ban
- Support tickets going unanswered for weeks while the community is inaccessible
- Charges continuing after cancellation requests
- Refund requests denied in cases where the platform itself caused the service disruption
These are not isolated complaints. The pattern in the reviews is consistent: the product works fine until it does not, and when it stops working, there is no support path that moves at the speed your business needs.
A community platform that holds your paying members, your content library, and your recurring revenue is not an area where you can afford a slow support response. When your members cannot log in, every hour of downtime is revenue you have to refund and trust you have to rebuild.
Features You Do Not Get on Skool
Beyond the cost comparison, there are capabilities that self-hosted WordPress provides that Skool simply does not offer. Some of these matter more than others depending on your use case.
SEO and Long-Term Content Value
Discussions on Skool are private and behind a login. Search engines cannot index them. Every question your members ask, every answer your team gives, every thread that documents your community’s knowledge, none of it exists for organic search.
On WordPress with Jetonomy or BuddyPress, you choose what is public. You can make your forum threads indexable. A question answered publicly once can drive inbound traffic for years. Fly.io’s community forum, n8n’s forum, Cursor’s support community, all of these generate organic traffic because they are built on open platforms with indexable URLs.
Custom Checkout and Upsell Flows
Skool has one checkout flow. You can set a price and a free trial period. You cannot A/B test checkout pages, offer order bumps, apply coupon codes with complex conditions, or integrate with external email marketing automation at a trigger level. WooCommerce Subscriptions with CartFlows or a similar tool lets you build checkout flows that would be impossible on Skool.
Data Portability
Your WordPress database is yours. You can export every post, every comment, every member record, every transaction. You can move hosts, clone environments for testing, and rebuild from scratch if you need to. Skool offers no equivalent. If you leave Skool, or Skool leaves you, the data question is an open one.
Integration Depth
WordPress integrates with almost every tool a creator business uses: Zapier, Make, ConvertKit, Mailchimp, Klaviyo, HubSpot, ActiveCampaign, Stripe, PayPal, Lemon Squeezy, LearnDash, LifterLMS, Tutor LMS. Skool has a Zapier integration and its own API but the depth is not comparable. If your business has a technology stack, WordPress fits into it. Skool asks your stack to fit into Skool.
Migrating Off Skool: What Is Involved
If you are already on Skool and thinking about moving, the process has a few moving parts but is not as complex as it sounds.
What You Can Export
Skool allows you to export your member list as a CSV. This gives you names, emails, and join dates. You do not get payment history in a portable format, and you do not get community posts or discussion threads.
The Migration Steps
- Export your member CSV from Skool before you cancel anything
- Set up your WordPress environment (hosting, WordPress, BuddyPress, Jetonomy, WooCommerce Subscriptions)
- Create membership tiers in WooCommerce that match your current Skool pricing
- Import your member list and send a migration email with a dedicated onboarding link
- Offer a free month or a discount to members who complete migration within 30 days
- Run both platforms in parallel for 30 to 60 days while members transition
- Cancel your Skool subscription after the parallel run period ends
The parallel run period matters. Some members will be slow to move, and you do not want to lose revenue while migrating. Keep Skool active, post regularly in both places, and set a clear deadline for when the Skool community goes read-only.
Re-creating Courses and Content
Course content can usually be exported as video files and reposted. Skool does not lock your video files if you hosted them externally (via Loom or Vimeo). If you uploaded directly to Skool, you will need to download each lesson video manually before canceling. Text content can be copy-pasted. There is no automated export path for community posts, so treat that content as a fresh start and use the migration as an opportunity to restructure your curriculum.
Who Should Consider Self-Hosting
Not everyone should migrate off Skool today. The decision depends on where you are in your community’s lifecycle.
Self-hosting makes sense if you have 200 or more paying members, your community is the central asset of your business (not a side product), you want your forum threads to rank in search, you need custom checkout or integration capabilities, or you want to eliminate platform risk from your revenue.
Staying on Skool makes sense if you are still testing your community concept, you have fewer than 100 paying members and the launch speed matters more than the cost structure, or you do not have a developer and cannot afford a build right now.
The crossover point in the math is roughly 100 to 150 members at a $49/month price point. Below that, the platform fee dominates and the savings are modest. Above it, the compounding advantage of self-hosting grows every year.
The WordPress Stack That Replaces Skool
The build that most closely matches and exceeds Skool’s feature set uses the following components.
WordPress core provides the foundation. BuddyPress adds member profiles, groups, private messaging, and activity feeds. Jetonomy adds the forum layer with Q&A mode, accepted answers, trust levels, and threaded discussions built for both community engagement and customer support use cases. WooCommerce handles the store, and WooCommerce Subscriptions manages recurring billing, failed payment retries, trial periods, and subscription management.
For courses, LearnDash integrates cleanly with BuddyPress and WooCommerce. For media hosting, Bunny.net delivers video at a fraction of the cost of Vimeo or Wistia. For gamification, BuddyPress Points or GamiPress can replicate Skool’s leaderboard mechanics. For email, Postmark handles transactional delivery and you can use ConvertKit or Mailchimp for broadcast.
Nothing in this stack is exotic. These are mature, well-documented tools with large support communities and years of active development. None of them can ban your account and delete your community.
Getting Started
If you want to run the cost comparison for your specific situation, use the calculator above. Plug in your current member count and monthly price and see where the crossover point falls for your community.
If you are already past that crossover point and want to understand what a migration would look like for your specific setup, get in touch. We build and migrate communities off Skool, Circle, and Mighty Networks onto WordPress stacks that you own and control. We can usually scope a migration in a single call and deliver a running environment in 30 days.
The $99/month is not the problem. The problem is what that $99 does not buy you.
