Docs API reference
Sign in

Core concepts

In building IO, we’ve taken lessons from 10 years working on Tito Classic and built with the principle in mind that if we build something that Tito Classic does, we try to improve it in some way. This has added up to a product that has many small conveniences.

Alongside this Kaizen-inspired approach, there are some core ideas driving our product development:

Everything is customizable

Every touchpoint your attendees see — registration pages, emails, digital passes, domains — can be fully branded and customized. You can start with sensible defaults and progressively customize as much or as little as you need.

Events are self-contained

Each event has its own settings, ticket types, attendees, and content. This keeps things clean when you're running multiple events under one account. Account-level settings like team members, integrations, and billing are shared across all your events.

Data moves freely

You can import attendees from CSV files and export invitations, orders, attendees, and reports. Data is also available programmatically via the API.

Invitations and tickets work together

IO uniquely handles both open registration (ticketed events) and closed registration (invitation-only) in the same event. You can run a hybrid model where some attendees are invited while others purchase tickets publicly.

On this page

Next → Test mode