Skip to content
Industries

Events Software Development

Event software has an unusual load profile: almost nothing, then everything at once when tickets go on sale, then a hard operational peak at the door where failure is immediately visible to a queue.

  • Reply within one business day
  • NDA on request
  • No obligation

Helps us propose a realistic scope.

What makes this sector different

Constraints specific to events

The problems that shape software here, and that generic engineering tends to discover late.

On-sale is the whole year in ten minutes

Ticket releases concentrate demand into minutes, with inventory that must not oversell and a queue that must be fair.

The door has no tolerance for failure

Entry scanning happens with a queue forming behind it, often in a venue with poor connectivity, so offline operation is mandatory.

Inventory is genuinely finite

Unlike most commerce, overselling a seated event cannot be resolved with a backorder, which makes reservation and hold logic unforgiving.

Resale and fraud

Tickets carry value, which attracts duplication and fraudulent resale, so validation has to assume adversarial conditions.

What we build

Software we build for events

Ticketing platforms

Inventory, reservation and checkout designed for on-sale conditions, with queueing that is fair and visible.

Registration and attendee management

Multi-track registration, sessions and attendee data for conferences and multi-day events.

Door and access control

Offline-capable scanning applications that validate and reconcile without depending on venue connectivity.

Attendee applications

Schedules, wayfinding and updates, built to work in venues where the network is saturated by everyone else's phone.

Regulatory context

Standards that apply to software in this sector

What the software has to be built to satisfy. Which of these apply to you depends on your jurisdiction, your data and your customers.

[ 01 ]

Payment data

  • PCI DSS

[ 02 ]

Personal data

  • GDPR
  • CCPA

[ 03 ]

Accessibility

  • WCAG 2.2
  • Accessible seating provision

[ 04 ]

Consumer protection

  • Ticket resale rules
  • Price transparency requirements

These are the standards we design and build to meet. Certification or attestation of your organisation is a separate exercise, carried out by a qualified assessor — we can support that process with documentation and evidence, but we do not certify it.

Tell us about your on-sale and your door

Discuss an events project
Services

How we'd approach it

The service lines this sector most often needs.

All services
Web Application Development

Web Application Development

Scalable web applications on modern frameworks, engineered for first-load performance and sustained load.

Mobile App Development

Mobile App Development

Native and cross-platform iOS and Android apps, built for real network conditions rather than office Wi-Fi.

Cloud & DevOps

Cloud & DevOps

Migration, deployment automation and infrastructure on AWS, Azure and Google Cloud, built to be operated.

Custom Software Development

Custom Software Development

Bespoke systems shaped around your operations, integrated with the tools and data you already run on.

Our work

Projects in this space

All case studies
PlacePass case study

Travel & Experiences Marketplace

PlacePass

A travel experiences marketplace spanning 300,000 activities in 800+ destinations, later acquired by Hopper.

300,000
Experiences available across the marketplace
800+
Destinations covered
Acquired
By Hopper in October 2021, forming its travel experiences division
ActivityHub case study

EdTech and Activity Management

ActivityHub

A SaaS platform connecting parents with children's activity providers across web, mobile and iPad.

94 min/week
Time saved for activity providers managing activities
863K
Messages sent between users
39K
Sessions hosted on the platform
IAMPLAY case study

Sports Technology & Recreation

IAMPLAY

A football and sports lifestyle app for booking venues, discovering players and following real-life activity.

Questions

Events: common questions

Something specific to your operation?

Send it over — sector questions are the ones we most like getting.

Ask us
  • 01

    How do you handle a high-demand on-sale?

    With a queue that is fair and honest about waiting position, inventory reservation that holds during checkout so nobody loses a seat mid-payment, and load testing against the actual expected curve. Static content is offloaded so the only thing under pressure is the transactional path.

  • 02

    Will door scanning work without connectivity?

    It has to, so yes. Scanning applications hold the validation set locally and reconcile when connectivity allows, with duplicate detection handled so a ticket scanned on two offline devices is still caught.

  • 03

    How do you prevent overselling?

    By reserving inventory at the point of entering checkout rather than at payment completion, with a hold expiry that returns unsold inventory. The alternative — allocating on payment — reliably oversells under contention.

  • 04

    Can you integrate with our existing ticketing provider?

    Usually. Many events keep an incumbent ticketing platform and need the surrounding experience — attendee applications, registration, access control — built around it, which is straightforward where the provider exposes an API.

Related

Adjacent sectors

All industries
Next step

Tell us about your on-sale and your door

Describe your events, your volumes and your venue conditions. We'll come back with an approach.

  • Reply within one business day
  • NDA on request