maxPerformance
Community & Matching

A community that finds itself by substance.

Event ticketing, algorithmic participant matching, QR entry. For a format that doesn't run off the shelf.

An event with custom participant logic fits no standard software. Ticketing platforms do tickets, not matching. Matching tools don't know about entry handling. Payment providers don't know about partner areas. In the end you glue three systems together - and the data frays.

What it does

Ticketing with profile capture, algorithmic matching between participants based on those profiles, QR entry at the venue, payment via Stripe and bank transfer, partner and recurring community management. All in one system.

How it's built
Next.js + TypeScriptSupabaseStripe + bank transferMatching algorithmQR entry
Community & matching system - backend (matching and participant management)
Community & matching system - frontend (ticketing and profile capture)

The demo runs in a closed circle. We share it on request.

Request a demo

By submitting you agree to our Privacy Policy .

Frequently asked

What's a custom matching system compared to standard Eventbrite ticketing?

Standard ticketing solves the sale. When the core of the event is what happens between participants - who meets whom, who gets paired with whom - the sale is just the entrance. We build the logic behind it: profiles, matching, entry, and follow-up community in one system.

Do I need a community platform with member management?

If the relationship reaches beyond the single event - recurring participants, partner tracking, member status - then yes. Otherwise an external platform carries. We tell you what you need before we build anything.

Can Stripe and classic bank transfer run side by side in one ticketing system?

Yes. Both payment channels land in the same booking view; the bank transfer reconciliation runs semi-automatic, with manual confirmation kept in the workflow. The system stays lean, with no special-case fixes for individual payment types.