The Complete Picture of BuddyNext: WordPress’s Community Layer, and How Fast It Keeps Growing

A month ago we shipped the first public build of BuddyNext, the community system we rebuilt from scratch after more than a decade of building on BuddyPress. What we did not fully brace for is how fast it compounds. Five releases later, and the thing is meaningfully more capable than the one we launched, in weeks, not years.

So this is not a changelog. Version numbers are the wrong lens for something moving this quickly; by the time you finish reading a list of what one release did, another has landed. What we want to give you instead is the complete picture: what BuddyNext actually is right now, and the shape of what keeps getting added.

The core is a real social layer, not a bolt-on

Start with what every member touches. BuddyNext gives WordPress a genuine activity feed, the kind people actually scroll, not a list of admin notices. Around it sits everything a social network is made of:

• A rich post composer with reactions, comments, hashtags, polls, shares, and bookmarks.
• Member profiles with customizable fields, plus a searchable member directory.
• Unified search across the whole community.
• Connections and follows between people.
• Notifications and branded transactional email.

None of this is stitched together from a dozen plugins. It is one system, and it does not depend on BuddyPress to run.

That was the whole point of rebuilding rather than extending. When the feed, the profiles, and the directory share one data model, they stay consistent as they grow instead of drifting apart at the seams.

Spaces are groups, done properly

Communities are not one big room. BuddyNext organizes people into Spaces, groups with membership, roles, and their own content, and Spaces nest, so a space can hold sub-spaces, each with its own members and access. A member gets a My Spaces view of everywhere they belong. Directory cards show how many sub-spaces sit inside a space, counting only the ones that member is allowed to see, because visibility should never leak structure a person cannot access.

This is also where a lot of the recent momentum lands. Spaces gained per-space settings that developers can extend with their own fields, saved automatically and exposed over the REST API. Member lists inside large spaces and their nested sub-spaces were tuned to stay fast when a community is genuinely big. Growth here is not cosmetic; it is the difference between a demo and something that survives its own success.

---

Messaging, media, and the parts that feel alive

Direct messaging is built in, powered by the WPMediaVerse companion, and it recently learned the small human touches that make a chat feel real, a live typing indicator while the other person writes, media and albums, the full share menu when you send a photo from the viewer. These are the details you only notice when they are missing, and they are the kind of thing that keeps arriving cycle after cycle.

There is a design principle hiding in those details. A photo you drop into the composer is shared only when you actually click Post, remove it, or leave the page, and it never publishes on its own. That sounds obvious until you have used the tools where it is not true, and someone’s half-finished image goes out to the whole community by accident. The small, careful behaviours are where a community product earns trust, and they are most of what a release quietly carries.

It knows who each member is now

This is the addition we are most pleased with, because it changes the first five minutes for every new member. BuddyNext now runs on interests. During onboarding a member picks the topics they care about from your space categories, and they can edit them any time from their profile, where each interest links straight to the matching spaces.

From there, personalization threads through everything:

• People and space suggestions are tailored to a member’s interests, so their very first session shows relevant people to follow and spaces to join instead of a wall of strangers.
• The For You feed ranks posts from a member’s interest spaces higher.
• Explore surfaces popular spaces in those interests, not only the newest ones.

A community lives or dies on whether a newcomer finds their corner fast. BuddyNext went from generic to personal here in a single stretch of releases.

From sign-up to belonging

Put those pieces in order and you can see the journey we actually care about, not “features,” but the path a stranger walks to becoming a regular:

• They arrive on a branded auth page, not the bare WordPress login, and sign up through onboarding or a social login.
• They pick their interests, and BuddyNext immediately suggests people and spaces worth their time.
• They land in a For You feed already tuned to what they chose, with a My Spaces view of where they now belong.
• Their first post, message, or reaction happens in minutes, because there was somewhere obvious to put it.

Every one of those steps used to be generic. Closing that gap, making the empty-community problem disappear for a new member, is exactly the kind of work that keeps landing, release over release.

Moderation that trusts members first

We built the moderation model to be reactive, not suspicious. Members post freely; reports flow to a review queue where a moderator acts. On top of that sit automatic rules:

• Keyword rules, where a block always outranks a hold.
• Hashtag rules that actually reject a banned tag instead of silently dropping it while the post publishes.
• Domain rules that catch links pasted into the body of a post and subdomains of a blocked entry, not just an attachment field.

A moderation log records what was acted on, with correct timestamps even on servers whose database runs on a non-UTC clock. Security sits alongside it: optional, opt-in two-factor authentication with an in-house TOTP implementation, so a member can protect their account without you installing anything extra.

Layer	What it is
Core (free)	Feed, profiles, directory, search, connections, Spaces, messaging, moderation, 2FA, onboarding
Companions	WPMediaVerse (media + messaging), Jetonomy (discussions), WB Gamification (badges, points, leaderboards)
Pro	Memberships + checkout, content protection, AI moderation, email automation, analytics

Branded down to the last email

A community should feel like your community from the first click, not like a bare WordPress install wearing a skin. Guest-facing login and register links route through branded auth pages. Onboarding, invites, and social login are built in.

Transactional email carries your sender identity even when another plugin tries to override the site-wide sender, uses the templates you actually edit in the admin, and now writes to an Email Log so an owner can answer “did that email go out” without guessing. Small thing, endless support tickets saved.

---

REST-first, so the app is not a rewrite

Everything above is exposed through a REST API, around two hundred endpoints, and that is not a developer footnote, it is the architecture. The same data that powers the web experience powers the native app.

We proved the pattern when we shipped a native iOS app for Jetonomy, and BuddyNext is built to the same standard, so taking a community mobile is a client project rather than a second implementation of the whole thing. When we say BuddyNext is REST-first, we mean the browser is just one more client.

The application layer, in Pro

The free plugin is the community operating system. BuddyNext Pro is the layer that turns a community into a business, and it has been filling in just as quickly.

Memberships are the spine: create plans with a price and entitlements, members buy on-site, and access is gated by those entitlements in a way that does not care whether you are selling courses, content, or space access. Payments are gateway-agnostic, with a no-keys Test gateway so you can exercise the entire checkout and provisioning flow before wiring up the embedded Stripe gateway for live charges. Members-only content shows a teaser plus a checkout call to action instead of a blank space, and gated spaces honor the plan entitlement.

Then the operational tools:

• Advanced moderation, scheduled AI review of the report queue, editable default rules, and retention house-cleaning.
• Email automation, a shared composer with a live branded preview, segment pickers, and proper UTC scheduling for both campaigns and drip sequences.
• Analytics and member surfaces, pricing, my-membership, and thank-you pages, all under their own REST namespace.

Community on one side, the business that funds it on the other, one system.

Why owning the whole stack lets it move this fast

People ask how five releases land in a month without the wheels coming off. The honest answer is unglamorous: we own every layer, so nothing waits on someone else’s roadmap and nothing has to be negotiated across a plugin boundary we do not control.

When personalization needed interests to exist on the profile, feed into the For You ranking, and drive Explore all at once, that was one coordinated change across surfaces we already own, not three separate plugins each shipping on their own schedule and hoping the contracts still line up. The feed, spaces, messaging, and profiles are one codebase. The companions and Pro ride the same REST spine and a shared manifest, so a change in one place cannot quietly break another without the contract audit catching it before we tag a release.

That ownership is also what lets velocity stay honest. We do not get to move fast by cutting the scale work, because we are the ones who answer the support ticket when a 50,000-member directory crawls. So big-community readiness goes in with the feature, every time. Fast and durable are not in tension here precisely because the same team owns the data layer up through the app, and we would rather fix the foundation once than paper over it five times.

The pace is the actual feature

Here is the thing we keep coming back to. In about a month, BuddyNext went from launch to interests-based personalization, extensible per-space settings, typing indicators, member-type-specific profile fields, help text and placeholders on every field, an admin that behaves on an iPad, and a long tail of correctness work, required fields actually enforced, redirects actually honored, emails actually sent.

Much of that last category reads as bug fixes, but look closer and most of them are the same theme: the software behaving honestly at the size real communities reach.

That is deliberate. We do not ship the demo-scale version and wait for someone to hit the wall. Member lists staying fast in very large communities, per-space settings that do not reload on every request, background cleanup that runs in batches so a big site stays responsive, that work goes in as the feature goes in, not as a follow-up. It is why five releases in a month is not five rounds of patching. Each one makes the picture more complete without loosening the foundation under it.

BuddyNext is one piece of the larger stack we wish we had started building ten years ago, community here, media in WPMediaVerse, discussions in Jetonomy, learning in Learnomy, all sharing the same REST-first spine. Community is the layer everything else plugs into, which is exactly why it gets this much attention.

So, the complete picture?

The honest answer is that it is complete the way a living thing is complete: whole today, and different in two weeks. What we can tell you is that BuddyNext right now is a full social layer for WordPress, feed, profiles, spaces, messaging, personalization, moderation, and security in the free plugin, and memberships, payments, AI moderation, and automation in Pro, with a native app riding the same API and a release cadence that keeps closing the gaps almost as fast as we find them.

If the last time you looked at community on WordPress you saw a pile of plugins duct-taped together, look again. And then check back in a month, because it will have grown.