Skip to content

Data Structures

To use Klipspringer effectively, it's important to understand how the core entities are structured, and the design philosophy behind them.

Klipspringer follows a single-event, attendee-centered model, where each instance is fully isolated and scoped to a single event. Below are the key data models you'll interact with.

Attendee

The Attendee object represents any user interacting with the system. Klipspringer does not distinguish between "attendees" and "organizers" as separate models. Instead, an attendee may hold administrative permissions, which grant additional permissions.

Every attendee may:

  • Register and purchase tickets
  • Access QR codes
  • Use Wallet integrations (Google Wallet, Apple Wallet when available)

Admin attendees can:

  • Check in other attendees
  • View and manage orders
  • Modify event settings
  • Configure payment providers

Events

Each Klipspringer deployment handles a single, isolated event.

If your organization runs recurring events (e.g. "MyConf 2025", "MyConf 2026"), you should deploy a new instance for each one. This ensures complete data separation and easier upgrades.

Tiers

A Tier represents a specific type of ticket within your event. You may create multiple tiers to support various pricing levels, eligibility requirements, or quantities. Each tier is independently configurable.

  • Label (e.g., "General Admission", "VIP", "Under 18")
  • Price
  • Minimum age or Maximum age
  • Quantity limit
  • ID Verification policy