Skip to content
HexCorp.io

HexCorp / Docs / Clubhaus

Documentation

Clubhaus documentation

Current version 1.0.0 · WordPress 6.6+ · PHP 8.1+ · Updated October 18, 2026

Clubhaus is a paid community platform that runs inside your own WordPress site: feed, courses, members, notifications and a mobile-first community app, with Clubhaus Pro adding paid tiers, spaces, direct messages and events. This guide gets a community running in under an hour.

Requirements

  • WordPress 6.6 or newer, PHP 8.1 or newer.
  • Any host. Background work runs through Action Scheduler and polling, not websockets; a persistent object cache helps beyond about 10,000 members.
  • For paid tiers (Pro): a Stripe account.

Install

  1. Download the free plugin from the Clubhaus product page, or install it from the WordPress plugin directory once listed.
  2. In wp-admin go to Plugins → Add New → Upload Plugin, choose the zip, install and activate.
  3. Open Clubhaus in the admin menu. Name your community, pick an accent color and choose which modules to run (feed, courses, notifications, profiles, moderation each switch on and off independently).

Quick start

  1. Create a page for visitors and add the Community Landing block, with the Join Form block if you want signups there.
  2. Send members to /app/, the mobile-first community app. It has a web manifest and offline fallback, so members can add it to their home screen.
  3. Add Onboarding Questions if you want to learn something about each new member, and decide whether new members’ posts wait for approval (Clubhaus → Settings → Moderation).
  4. Build your first course under Clubhaus → Courses: modules, lessons, optional drip schedule. Place the Course Catalog block on a page.
  5. Post a welcome in the feed. Members get it in the app and, by preference, by email.

Moving from Skool or Circle

Clubhaus → Migrate imports a Skool members CSV, mapping Skool levels to Clubhaus points, and pulls members, spaces and posts from the Circle API. Every import runs as a dry run first and shows exactly what will be created. Courses from Skool are rebuilt by hand; the migrate screen links a guide.

Clubhaus Pro: activation and updates

  1. Buy a plan on the Clubhaus product page. The receipt from Lemon Squeezy contains your license key and the Pro zip.
  2. Install clubhaus-pro.zip through Plugins → Add New → Upload Plugin and activate it. The free plugin must stay active.
  3. Go to Clubhaus → License, paste the key and click Activate. The key is checked weekly.
  4. Updates arrive in Dashboard → Updates like any plugin, signed and served from hexcorp.io after a license check.

Pro adds paid tiers with Stripe (Clubhaus → Tiers), multiple spaces, direct messages, events with RSVP, waitlists, reminders and a calendar, analytics, custom branding and real-time transport. If a license lapses, Pro features keep working; only updates stop.

  1. Clubhaus → Settings → Payments: connect Stripe with your publishable and secret keys and add the webhook endpoint shown there to your Stripe dashboard.
  2. Clubhaus → Tiers: create a tier, set the price and billing period, and choose which spaces and courses it unlocks.
  3. Place the Gate block around anything that should require a tier.

Your data

Members are WordPress users; courses and events are post types; feed posts, comments, reactions, notifications and memberships are custom tables prefixed clubhaus_. The free plugin makes no external requests. Export or erase anyone with WordPress’s own privacy tools. Uninstall keeps everything unless you opt in to deletion.

For developers

REST API under clubhaus/v1, more than 130 documented actions and filters prefixed clubhaus_, theme-overridable email templates, PSR-4 code following the WordPress Coding Standards. The hooks reference is generated from the code and ships in the repository’s docs folder.

Getting help

Email hello@hexcorp.io with your site URL and what you expected to happen. Pro customers get priority replies. Bugs in the free plugin are welcome too; include the WordPress and PHP versions from Tools → Site Health.