Launching 7 September 2026

Community Engine

Communities have outgrown their infrastructure. We're building what comes next.

For too long, the tools running the world's technical communities have been fragmented, extractive, and fundamentally unfit for purpose. Community Engine is the response — a full-stack operating system that replaces the patchwork of platforms, spreadsheets, and manual workarounds with a single unified system built for the way modern communities actually operate, grow, and scale.

This is not another event platform. This is infrastructure.

Early access open nowLimited onboardingFounding communities shaping the platform
18 Communities
25,000+ Members
100+ Events / Year
3+ Countries

Stay updated — subscribe for launch news and early access

Why We're Building This

The community platform market is broken. We're rebuilding it from the ground up.

Technical communities are among the most powerful forces in the global engineering economy. They drive knowledge transfer, shape careers, accelerate adoption, and build the trust networks that the industry runs on. Billions of pounds of enterprise value flows through the ecosystems that communities create.

And yet the infrastructure running those communities belongs to a different era entirely.

Organisers today are duct-taping together five, six, seven disconnected tools — paying more each year for less capability, locked into platforms that reprice without warning, with no real ownership of their data, no meaningful analytics, and no path to building something financially sustainable. The tools haven't kept pace with the ambition of the people using them.

The numbers tell the story. Our own platform costs rose from $100 to over $7,500 a year on Meetup alone — and we still needed a stack of additional tools just to operate. Bending Spoons' $500 million acquisition of Eventbrite has further consolidated legacy infrastructure under a single owner with a track record of extraction over innovation. Alternatives like Luma and Bevy have attracted attention, but neither addresses the structural problem at the root of the issue. Switching tools doesn't fix fragmentation. It relocates it.

Community Engine was built because the market deserves better — and because the communities powering the global tech industry deserve infrastructure that matches their importance.

"This is not an incremental product release. This is a structural intervention into a broken market. We are building the system communities should have had from the start — not just tools, but infrastructure."

Ethan Sumner, Co-Founder & CEO

The Platform

What we're building

Community Engine is a full-stack operating system for technical communities. A single, end-to-end platform that consolidates every tool, workflow, and system a community needs to operate — from a first event to a global ecosystem spanning hundreds of chapters and tens of thousands of members.

Nine integrated capabilities. Four discovery directories. One unified system.

Built to make communities operate like products, not side projects.

The Challenge

The problems we're solving

Fragmentation

Meetup for discovery. Eventbrite for tickets. Google Forms for speaker submissions. Slack for communication. Spreadsheets for sponsors. A different tool for memberships. Another for emails. None of them connected. None of them designed to work together. Every handoff is a gap. Every gap is manual effort. Every manual effort is a cost.

Unsustainable economics

Platform costs compound as communities grow. Integration fees add up. The manual overhead of running disconnected systems consumes the time and energy of the people who should be focused on building community. And when a platform decides to reprice, as Meetup has repeatedly, there is no recourse.

No ownership. No control.

Your community lives on someone else's platform, under someone else's terms, with someone else's priorities. When those priorities shift, your community pays the price. Data locked in. Features removed. Costs raised. Community Engine is built on a fundamentally different principle: the community owns its infrastructure.

Operational invisibility

No meaningful analytics. No engagement intelligence. No way to understand what's actually happening across your community ecosystem. Just attendance numbers, if you're lucky. Community Engine replaces operational blindness with deep, actionable intelligence.

No path to sustainability

Most community platforms weren't built with organisers' financial sustainability in mind. Sponsorship is manual. Memberships require third-party tools. There is no integrated monetisation layer. Community Engine builds sustainable revenue models directly into the platform.

Capabilities

Nine integrated capabilities. One unified platform.

Discovery

The Discovery Layer

Communities don't exist in isolation. They are part of ecosystems — networks of people, knowledge, organisations, and opportunity that grow stronger when they are connected. The Community Engine discovery layer makes those connections structural, not accidental.

Four directories. One trusted ecosystem.

Communities Directory

A verified, searchable map of meetups, user groups, and community organisations designed for discoverability, trust, and ecosystem visibility. Filter by topic, location, format, and accessibility.

Register Your Community

Speaker Directory

A trusted, searchable database of practitioners, educators, and ecosystem voices — enabling organisers to find the right speakers and speakers to find the right opportunities.

Join as a Speaker

Venue Directory

A structured directory of spaces that host communities — with capability, accessibility, capacity, and location visibility built in.

Register as a Venue

Ecosystem Partners

A verified directory of organisations that invest in and support community ecosystems — responsibly connecting communities with the sponsors, partners, and supporters that align with their values.

Register as a Partner

Enterprise

Built for enterprise. Designed for depth.

Community Engine is not a community tool that enterprise organisations can adapt for internal use. It is enterprise infrastructure built from the ground up for the governance, scale, and operational complexity that large organisations require.

For enterprises with significant engineering functions, Community Engine provides the infrastructure to build, structure, and sustain internal communities of practice, engineering guilds, knowledge networks, and advocate programmes at scale. The same platform that runs a 500-person external conference runs a 10,000-engineer internal guild programme — with the security, compliance, and oversight that enterprise environments demand.

Multi-chapter management with centralised governance and regional autonomy

Internal community infrastructure for engineering guilds and communities of practice

Centre of excellence governance models with structured oversight

Internal champions programme infrastructure with participation tracking

Cross-team and cross-region coordination tooling

Organiser governance with structured approval and support workflows

Ecosystem-wide engagement tracking across internal and external portfolios

Self-hosted deployment for organisation-managed infrastructure

On-premise deployment for air-gapped and private network environments

Fully white-labelled deployment under your own brand

SSO and SAML integration with two-factor authentication

Role-based data access controls with full audit logging

GDPR and data residency controls with configurable retention

Enterprise-grade security and penetration testing programme

Dedicated account management, SLA guarantees, and custom development

"We have built Community Engine from the ground up to handle the real operational complexity that community organisers face every day. The architecture is designed to scale from a single community to a global enterprise ecosystem without the compromises that current platforms force on their users."

Mercedes Moxon-Greenfield, Co-Founder & CTO

Comparison

How Community Engine compares

The community platform landscape has failed to keep pace with the ambition of the people building communities. Here is an honest assessment of where things stand.

FeatureMeetupLumaEventbriteBevyEngine
Community ownership
Event management
Speaker management
CFP & speaker payments
Sponsorship engine
Branded microsites
Membership & monetisation
Advanced analytics
API access
Multi-community support
Internal guild infrastructure
Self-hosted / on-premise
Enterprise deployment
Accessible pricing
Discovery directories

Moving from Meetup, Bevy, or Luma? Our migration team has helped dozens of communities make the switch without losing a single member.

Roadmap

What's coming next

Community Engine launches on 7 September 2026. This is what the roadmap looks like beyond that.

Q3 2026

Public Launch

  • Full public availability
  • Expanded sponsor attribution and ROI tooling
  • Advanced analytics dashboard v2
Q4 2026

Intelligence Layer

  • AI-powered community insights and recommendations
  • Community health scoring across ecosystems
  • Automated engagement and re-engagement tools
  • Native mobile apps for organisers and attendees
2027

Global Infrastructure

  • Enterprise white-label at scale
  • Global directory expansion across regions and disciplines
  • Partner API ecosystem for third-party builders
  • Multi-language support and localisation
  • Offline-first access infrastructure
  • Impact intelligence for funders and regional bodies

Stay Updated

Subscribe for Community Engine updates

Be the first to hear about product milestones, early access openings, and launch news. No noise, just signal.

No spam. Unsubscribe at any time.

This is the infrastructure communities deserve.

Technical communities are not side projects. They are the knowledge networks, career pathways, and innovation ecosystems that the global engineering industry depends on. They deserve infrastructure that takes them seriously.

Community Engine is that infrastructure.

Launching 7 September 2026 · Early access open now · Limited onboarding to ensure quality implementations