For the person running the event
Publish a page people can register on, ask the questions you actually need answered, sell tickets straight into your own Stripe account, and walk away with the guest list. Publishing, registrations and check-in cost nothing.
A real URL with a link-preview card, so the event looks like itself when somebody pastes it into a group chat. Guests browse and answer your questions before anyone asks them to sign up, because asking a stranger to register before they can say yes loses them.
Ask what you need to run the night - dietary requirements, a company name, which session, whether they are bringing someone - alongside the standard fields. The answers arrive attached to that attendee instead of in a separate form tool you reconcile at midnight.
Set the number the room holds. Registration stops there, and anyone who arrives after it joins a waitlist rather than bouncing off a sold-out page, so a cancellation has somebody to give the place to.
Paid tiers check out on the host's own connected Stripe account, so payouts follow your schedule and refunds and disputes stay with you. Connections takes three percent of what you collect, on top of Stripe's own processing fee.
Paste your organizer page or calendar link, tick the events you want, and each one comes over as a draft for you to check and publish. On a $20 ticket, Eventbrite's US fees come to about $3.18 all-in: 3.7% plus $1.79, then 2.9% card processing on the total. Here it is $1.48 all-in: our 3% plus Stripe's 2.9% and 30 cents.
Email and SMS go out from the event itself, and one tap invites everyone who has come to any of your events. A reminder goes out before doors open and a follow-up after it ends, set when you publish and moved if you move the date.
Kiosk check-in runs in a browser, so there is nothing to buy for one night. Guests scan in, walk-ins get matched against the roster on the spot, parties arriving together are grouped, badges print from the same flow, and the list updates while the room fills.
Who registered and who actually walked in, exportable as a CSV the moment the event ends - which is exactly when a host needs it, not one upgrade later. Everyone who came stays in your contacts with the event attached.
An event repeats, every Tuesday for example, and each date gets its own page and sign-ups. Your calendar publishes as a feed people can follow, so each new date lands in the calendar app they already use.
Build pre-event questions or a VIP request as a standalone form with its own page to share or embed. A waiver needs no extra form: registration can ask for a signature.
A public page where people book one-on-one time with you, like office hours around the event, and get a confirmation email.
A public card at your own handle - link-in-bio, QR code, save-contact - to hand out before or after the event, so people can save your details and share theirs back.
Connect an assistant to your own contacts to ask about the people you met or log notes after the event, and every change waits for your approval.
Publishing an event, taking RSVPs, sending the invites and running check-in at the door cost nothing on the free account, which publishes three events a month; a weekly series counts as one. Pro publishes as many as you run. When you sell tickets, Connections takes three percent of what you collect, on top of Stripe's own processing fee, because the money moves through your own connected Stripe account rather than ours. The paid plans do not change that rate; the amount it comes to scales with what you sell.
Yours, and only once you sell tickets: a free event needs no Stripe account. Ticket payments are charged directly on the host's own connected Stripe account, so payouts follow your Stripe schedule and the customer relationship, the refunds and the disputes stay with you. Connections is not a middleman holding your ticket revenue until some threshold clears.
Yes. Each ticket can open and close for sale on dates you set, so an early-bird ticket stops when the regular one starts, and each can have a set number of spots. A members' price is a discount code you send your members, or a ticket only people with your link can see.
Yes. A registration form takes your own fields alongside the standard ones, so you can ask what you actually need to run the night - dietary requirements, a company name, which session someone wants, whether they are bringing a guest - and the answers arrive attached to that attendee rather than in a separate form tool you have to reconcile afterwards.
Set a capacity and the page stops taking registrations at it. Anyone who arrives after that joins a waitlist rather than bouncing off a sold-out page, so a cancellation has somebody to give the place to and you keep the demand signal instead of losing it.
Yes. Add a free ticket for each shift and set its spots; a shift closes when full. Each volunteer picks a shift when they sign up, and everyone lands on the same guest list.
Kiosk check-in runs in a browser on whatever screen is at the entrance, so there is nothing to buy or install for one night. Guests scan in, walk-ins can be matched against the roster on the spot, parties arriving together are grouped, and the guest list updates while the room fills. Badges print from the same flow.
Yes, as a CSV export of who registered and who actually arrived, and it stays yours. The list is not locked behind an upgrade at the moment the event ends, which is when a host most needs it.
From the event itself, by email and SMS. One tap invites everyone who has come to or been invited to any of your events, so your regulars stay one list across every night and venue. A reminder goes out before doors open and a follow-up after it ends, set when you publish and moved if you move the date.
Yes. An event can repeat, every Tuesday for example, without copies you keep by hand, and each date gets its own page and sign-ups. Your calendar publishes as a feed people can follow, so each new date lands in whatever calendar app they already use.
Yes, though a waiver does not need one: registration itself can ask for a signature and a required agreement, so it arrives with the sign-up. A standalone form, with its own page to share or embed, is for what comes separately, like pre-event questions or a VIP request.
Yes. Connect Claude, Cursor or ChatGPT and ask about the people you have met, pull up someone's history, or log notes after an event without leaving the conversation. Every query is scoped to your own records, and any change it wants to make comes back for your approval rather than happening on its own.