Lineupo event ticketing sells the night and leaves the money with you.

One system from the buy page to the door.

A night depends on four surfaces, and Lineupo runs all of them.

• The buy page

  Built from your poster, with your tiers, at your own address. Buyers pay by card, Apple Pay or Google Pay, or on another payment rail you connect.

• Guest lists

  Every guest gets a scannable pass. Hosts get their own link and their own allowance.

• The door

  Guests, tables, the scanner and door sales, all on one phone.

• Tonight

  Every scan is written against the event as it happens, so the door and the panel agree.

You hold the money from every ticket sold.

Buyers pay into a payment account you own, on every plan including Free, and it settles to your bank on your processor's schedule. Lineupo sits outside the payout path. It cannot hold or delay your money, and it takes no percentage. Lineupo is as open about the other side: it cannot release money your processor is holding either.

Eventbrite publishes a service fee of a percentage plus a fixed amount on every paid ticket, on top of payment processing. Lineupo charges no per-ticket fee on either plan, and your payment provider bills its own fee at its published rate.

The providers you can connect today are listed on lineupo.com/payments. Tap Payments covers the Gulf's local card schemes, and bank transfer or cash works in any country.

The door keeps scanning when the wifi drops.

Each phone scans from its own copy of the guest list and syncs the moment the connection returns. Nobody is counted twice, and every comp is recorded as a decision.

Door staff join by scanning a single-use code that expires. Their staff role works the door and reads the roster, and it cannot see revenue, discount codes or guests' email addresses.

Lineupo Pro also runs on your own server.

The price matches the hosted plan. You get the same versioned images Lineupo's own cloud runs, in Docker with PostgreSQL, behind your domain, with payments going to your own account.

Your server pulls a new version when you choose. No channel runs from us into your machine, so we cannot read your database, sign in to your instance or push a change. Each update backs up the database first and rolls itself back if a step fails, the same principle our own platform's release gate is built on. Requirements are listed on lineupo.com/own-server.

The database keeps each organiser's data apart.

Every table holding customer data has row-level security enabled and forced in PostgreSQL. The application connects as a role that cannot bypass it and sets the tenant inside each transaction, so a bug that forgets the tenant gets an empty result. Payment keys are encrypted with AES-256-GCM, and card numbers never reach Lineupo's servers.

Lineupo also publishes what it lacks: no SOC 2, ISO 27001 or PCI attestation of its own, no third-party penetration test and no bug bounty. It narrows the PCI question by never touching a card number.

Free sells real tickets, up to a monthly allowance.

Free needs no card and has no trial period or expiry, with guest lists, RSVP and offline door check-in included. Pro removes the limits and adds your branding, unlimited team and door staff, tables and seat maps, promoter links, an audience CRM, an API and the own-server option.

Prices appear only on lineupo.com/pricing, which keeps the two sites in step.