Community Engine

What Community Engine is

Community Engine is a community operations platform from Community Engine, founded in 2025 and headquartered in Barnsley, South Yorkshire, United Kingdom. Its open-source core is designed for any community or organisation, while the enterprise edition is described for corporate guilds, DevRel teams, and event businesses. The platform runs on the web, through an API, and in self-hosted deployments; it has no mobile apps. Community operations can cover a single meetup or portfolios of up to 200 chapters, including organiser succession and handover. Event tools support meetups, recurring series, multi-day and multi-track conferences, hybrid and online events, drag-and-drop scheduling, and conflict detection. Ticketing through Stripe Connect handles tiered rates, caps, waitlists, VAT, refunds, and transfers without a platform take rate. Integrations and migration adapters include Stripe Connect, Meetup, Eventbrite, Bevy, and Luma, with a versioned REST API, signed webhooks, and TypeScript and Python SDKs. Identity options include passkeys, magic links, OAuth, SAML 2.0, OIDC, SCIM, and two-factor authentication. Enterprise deployments may be managed cloud, self-hosted, on-premise, or air-gapped.

Who it suits

Community Engine suits organisations running communities, events, or chapter portfolios, with the core edition intended for any community or organisation. Its enterprise edition targets corporate guilds, DevRel teams, and event businesses needing advanced deployment, identity, compliance, or support options.

Limits

The Core plan is self-hosted, while Enterprise is priced from £8,000 per year and lists SSO, self-hosting or on-premise deployment, white label, compliance, and SLA features. Directory API costs £2,400 per year for programmatic access to four directories, and Market Intelligence costs £6,000 per year for vendor marketing, sales, and recruitment teams.

Getting started

1. Open the Community Engine website
2. Choose web, API, or self-hosted access
3. Select the Apache 2.0 Core plan or a listed paid plan
4. Deploy Enterprise as managed cloud, self-hosted, on-premise, or air-gapped if applicable
5. Connect listed integrations or use the REST API, webhooks, or SDKs
6. Configure identity, moderation, event, ticketing, and chapter operations

Verdict

Pick Community Engine when you need community governance, event management, payments, integrations, and flexible deployment from one platform. Look elsewhere if native mobile apps are essential, or if your organisation cannot self-host the Core edition or meet Enterprise pricing.