Skip to content
Event Technology

A white-label event platform under your brand

The Eventify engine with your identity on every touchpoint: registration on your domain, apps under your name, badges and emails that never mention us. Custom modules where configuration stops.

  • Vanity domains
  • Your app store accounts
  • Tenant-isolated data
  • Custom modules on request
Who this is for

Organisations whose brand is the product

Event agencies

Run every client's event on one platform, each under the client's brand, with your agency's margin built into the model.

Associations and membership bodies

One members' app that carries the annual conference, regional meetings and webinars, with member pricing built in.

Venues and exhibition organisers

Offer registration, check-in and lead retrieval to every show you host as a branded service line.

Tenancy

One engine, many brands, no leaks

The platform core serves every tenant: API, data, feature flags, push gateway and billing. Each tenant owns a configuration layer, which is brand, domains, feature set and app store identity. Attendees only ever see the tenant layer.

Isolation is enforced below the configuration, not by convention. A tenant id travels with every record and every request. Push tokens are scoped to tenant and event, and a domain resolves to exactly one tenant. The Eventify story explains why the push guard exists.

Agencies and venues can nest clients as sub-tenants with their own reporting, so one agreement with us covers many brands.

Multi-tenant white-label platform: one shared core serves three tenants, each with its own brand, domain and app store listing, and each rendering its own attendee touchpoints Platform core, shared API · tenant-isolated data · feature flags · push gateway · billing Tenant A · agency brand · domain · features own app store accounts sub-tenants per client Tenant B · association brand · domain · features member pricing groups one app, many events Tenant C · venue brand · domain · features check-in and leads per show dedicated hosting option serves, with tenant id on every request events.agency-a.example "Agency A Events" on iOS and Android emails and badges in Agency A brand conference.association-b.example "B Members" app, members' pricing emails and badges in B brand register.venue-c.example kiosks and lead retrieval per show emails and badges in C brand renders the tenant's brand on every touchpoint
Attendees see the top row only. The core at the bottom is shared; the tenant layer in the middle is what makes it yours.
Configure or build

What is configuration and what is custom

The honest version of the feature list. Configuration is included in the platform licence; custom is scoped and priced as a project.

CapabilityConfigurationCustom development
Branding: logo, colours, fonts, splash, email and badge templatesIncluded—
Vanity domains for registration, event site and web appIncluded—
App store listings under your developer accountsIncluded; we publish for you—
Registration forms, ticket rules, coupons, approval flowsIncludedRule engines beyond the built-in options
Feature toggles per event (networking, Q&A, lead retrieval, kiosks)Included—
Email templates, push campaigns, attendee groups and permissionsIncluded—
Standard integrations: Stripe, CSV import and export, API, webhooksIncludedMapped CRM, SSO, finance and member-database integrations
Sub-tenants for agencies and venuesIncludedCustom billing and reporting hierarchies
New modules: abstract review, awards, hosted-buyer rules, exhibitor manualsNot configurableBuilt as modules on the platform API
Dedicated hosting, data residency, custom retentionShared cloud by defaultDedicated environment
Bespoke app screens and native featuresTemplates onlyNative development in Swift and Kotlin
App store publishing

Your name on the listing, our hands on the submission

Apps are published under your Apple Developer and Google Play accounts. You own the listing, the reviews and the install base. We prepare builds, screenshots, metadata and privacy declarations, submit, and handle reviewer questions.

  • Container app for all your events, or a dedicated app for a flagship, or both.
  • Review usually takes days; we submit at least two weeks before registration emails go out.
  • Content updates never need a new build, so agenda changes go out instantly.
  • Annual platform updates are submitted for you before each major OS release.
Vanity domains in practice

Registration, the event site and the web app run on subdomains you control, with certificates managed by us. Emails are sent from your domain with proper authentication, which keeps confirmation emails out of spam folders. One DNS change per domain is all your IT team needs to make.

Process

From brand guidelines to a live tenant

  1. Scope

    Brands and sub-tenants, domains, feature set, integrations and anything in the custom column above.

  2. Provision

    Tenant created, branding applied, domains and email authentication set up, developer accounts linked.

  3. Build custom modules

    Scoped modules and integrations developed on the platform API in sprints, with the first event as the target.

  4. Publish

    Apps submitted under your accounts, registration opened on your domain, admin training for your team.

  5. Operate

    Platform updates, OS releases and support handled by us; your team runs events without tickets to a developer.

FAQ

Frequently asked questions

What does white-label actually include?

Your logo, colours and typography across registration pages, emails, badges and apps. Registration and event sites on your own domain. iOS and Android apps published under your developer accounts. No Eventify branding anywhere attendees look, unless you choose to show it.

Who owns the app store listings?

You do. We publish under your Apple Developer and Google Play accounts. Ratings, reviews and the listing stay with your brand even if you change platform later. We handle submissions and review correspondence on your behalf.

How is our data separated from other tenants?

Every record carries a tenant id enforced at the API layer. Device push tokens are scoped to tenant and event, and domains map to one tenant only. Dedicated database or hosting is available for organisations that need it contractually.

What is configurable and what needs custom development?

Branding, domains, forms, ticketing rules, email templates, feature toggles and app content are configuration. Unusual workflows, bespoke integrations, SSO and new modules are custom development on top of the platform. The table on this page lists both.

Can we resell the platform to our own clients?

Yes. Agencies and venues run multiple clients as sub-tenants under their own brand. Each has its own events, domains and reporting, billed through your agreement with us. See engagement models for how partnerships are structured.

Ready to make AI work in production?

Tell us about your systems, your data and your constraints. We reply within one business day with a straight answer and a suggested next step.