AudienceView runs a commerce platform for live events - ticketing, fundraising, CRM, marketing automation, analytics - all in one stack. The threat model here is high-stakes and high-volume: over 2,400 venues across 12 countries process more than $3 billion in annual ticket revenue through the system. That kind of transactional load on a single unified platform means payment data integrity, availability under peak surges (think on-sale moments for major acts), and API security across a sprawling ecosystem are non-negotiable operational concerns.
Founded in 2002 and headquartered in Toronto, the company serves theaters, performing arts centers, museums, universities, and enterprise-scale organizations. The product surface area is broad - AudienceView Platform bundles ticketing with fundraising and marketing tools - so the attack surface spans web front-ends, mobile interfaces, third-party integrations, and backend data pipelines handling personally identifiable information and financial records at scale.
For security practitioners, the draw is the combination of fintech-adjacent transaction volumes with the complexity of a multi-tenant SaaS serving diverse venue types. The platform has to stay PCI-compliant while supporting dynamic pricing, presale access controls, and real-time inventory across global deployments. It's a problem set where uptime, fraud detection, and data privacy collide in production - no hypotheticals required.
