How it is built

Every company runs in a sealed space of its own, on the same software AVEO runs its own events on.

A database for each company

Each company has its own database with its own login. That login opens the company's own database and nothing else: not another company's, not EOS's platform records, not the ticket engine's.

Every request to EOS is tied to exactly one company before any code runs, and the data layer refuses to run without one, so a request can never reach the wrong company's records.

Its own ticket engine account

Tickets, orders and check-ins are held in the company's own account on EOS's ticket engine, with a key of its own. The engine itself refuses one company's key on another's events.

Its own Stripe account

Card payments are taken directly on the company's own Stripe account and paid out by Stripe to its bank. The booking fee buyers pay on top of their tickets, AVEO's only fee, is passed to AVEO by Stripe at the moment of payment. See Payments and Stripe.

Sign-in

  • Staff sign in with their work email, which names their company. One email belongs to one company.
  • Passwords of at least 12 characters; passwords found in known data breaches are refused.
  • A human check on the sign-in form, and accounts that lock for a while after repeated wrong passwords.
  • Two-step sign-in with an authenticator app or a passkey (Face ID, Touch ID, Windows Hello or a security key). Admins, managers and security managers must use one, and custom roles can be set to need it.
  • Each company's sign-in keeps its own session, so a company's console and its sandbox stay apart even in one browser.

Apart from AVEO's own events

AVEO's own events and data run on separate database servers and networks. AVEO's staff set companies up, and manage their plans and fees, through a private, signed connection.

Everything recorded

An audit trail records who changed what across the console, and every API key keeps a log of its requests for 30 days.