Corporate events
Invitation-only, approved, and accounted for.
Closed registration, formal approvals on the record, invoice billing, and reporting your finance team can reconcile — with attendee and guest data in a system your organisation controls.
Closed by default
Registration forms that are not public: a URL you send to the people you invite, with a sales window that opens and closes when you say. Allocate tickets to a department or a partner and let them fill in the recipients themselves.
Approvals that leave a record
When something needs a formal yes or no — a supplier's terms, a booth design, an agency's deliverable — the decision goes on the record with who made it and when, rather than being buried in a mail thread.
Billing and documents
Invoice as a payment method, sales documents from your own billing identity, and exports that go to whoever needs them in the format they asked for.
Everything anyone changed
Three roles enforced on every action, and an activity log recording who changed what and through which channel — the app, a device, or an AI tool. Useful the day someone asks.
What runs on the day
Questions we are asked
- Can we keep registration private?
- Yes. A form is only reachable by its URL and can be opened and closed on a schedule. Nothing is listed publicly.
- Can departments manage their own allocation?
- Yes. Allocate tickets to an organisation, and they fill in the recipients and send the tickets from their own portal login.
- Who can see what internally?
- Admin, Editor and Viewer, checked on the action rather than by hiding a menu. A stakeholder can be given visibility without edit rights.
- Where does our attendee data live?
- In your own database — one per organisation, not a shared table. Card payments run through Stripe, so card numbers never reach Event Base.