Jens Teichert

CTO and Co-Founder

Jens Teichert is the CTO and Co-Founder at vivenu, where he spearheads the company’s mission to redefine ticketing through API-first innovation and technical excellence. With a deep-rooted expertise in scalable software architecture and product-led growth, he leads the engineering teams in building a high-performance platform that replaces legacy constraints with unparalleled flexibility. Under his technical leadership, vivenu has evolved from a visionary startup into a global powerhouse, providing the robust, future-proof infrastructure that powers over 1,000 clients in more than 50 countries.

Jens Teichert

Expertise

Scalable Enterprise ArchitectureAPI-First Platform Engineering(Mission-Critical) SaaS InfrastructureTicketing Ecosystem IntegrationGlobal Engineering LeadershipProduct-Led Growth (PLG) Strategy

Experience

  • CTO & Co-Founder

    vivenu · Mar 2018 - Present

Latest Articles

Ticketing Laws to Watch in 2026: A Technical Compliance Guide

Industry Insights

Ticketing Laws to Watch in 2026: A Technical Compliance Guide

In 2026, the regulatory landscape for live entertainment ceases to be a list of legal guidelines. It effectively becomes a set of functional system requirements. While mandates like the US TICKET Act and the UK's new resale protections were legislated or proposed previously, 2026 marks the critical threshold of enforcement. Implementation phases are ending, and strict liability deadlines are converging. These laws dictate specific latency limits, data structures, and UI behaviors that legacy software was not originally architected to handle. Compliance is no longer just a legal matter; it is an engineering constraint. Below is a technical framework to assess if your current operations can execute these rules, or if they expose your organization to risk. What is Regulatory Compliance in Ticketing? Regulatory Compliance in Ticketing is defined by the ability of a software architecture to enforce legal mandates such as price transparency, data accessibility, and anti-scalping verification programmatically within the user journey. It is not merely a policy document; it is code. It requires systems to handle complex logic, such as pre-calculating taxes or verifying business credentials, in real-time without crashing under high-traffic loads. The 3 Key Laws to Watch To ensure readiness, evaluate your technology provider against these four critical engineering constraints. 1. UK Resale Cap: The End of Scalping The Regulation: In November 2025 The UK government has introduced measures to ban ticket touting and cap the resale of live event tickets. Platforms will be liable for enforcing these caps, ensuring tickets are not sold higher than their original face value (plus strictly defined "unavoidable fees") as reported by the BBC. The Fix: Hard-coded price ceilings in the resale engine. The Risk: Current secondary market platforms often allow "market-based" pricing. The new law requires the system to mathematically validate that Resale Price <= Original Price + Allowed Fees before a listing can even be published. The Audit: Does your resale platform have a "price enforcement layer" that automatically rejects listings above face value? 2. US TICKET Act: "All-In" Pricing Engine The Regulation: The TICKET Act (S.281) which is expected to be passed in 2026 mandates that the full price, including all mandatory fees, must be displayed on the very first listing page, effectively banning "drip pricing." The Fix: Pre-computed fee vectors at the event level. The Risk: Many legacy systems calculate fees only at the cart stage to conserve computing power. Moving this math to the front end, where traffic is exponentially higher, creates a massive load on the database. The Audit: Ask your provider if they pre-calculate fees or query the pricing database for every page view. Real-time calculation per user during a high-demand onsale is a single point of failure. 3. EAA: Accessibility as Code The Regulation: The European Accessibility Act (EAA) requires e-commerce services to be fully accessible and WCAG 2.1 AA compliant. With full enforcement active in 2026, non-compliant sites face market exclusion. The Fix: Don't force screen readers through the map. Instead, guide users directly to the best available seating options via a logic-based flow. The Risk: The industry standard for large seat maps is often HTML5 Canvas or WebGL. These render thousands of seats as a single image. Screen readers see this as a blank space, making the map "invisible" to blind users. The Audit: Is your seat selection a visual-only black box? If the system lacks a text-based path that automatically surfaces the best inventory, it is non-compliant by design. Challenges of Traditional Architectures The primary challenge for 2026 is technical debt. Systems built 15 years ago were designed for a different era of the internet. They prioritized caching and static displays to save bandwidth. Retrofitting these systems to handle "all-in" pricing (which requires heavy database querying) or granular transparency reporting often results in severe latency or system instability. The Shift: Traditional & “The New Standard” Regulations The following table outlines how standard ticketing operations must evolve to meet the new legal reality. Closing Thoughts For ticketing managers and CTOs, the message for 2026 is clear: compliance is an engineering problem, not just a policy one. The TICKET Act, the EAA, and the UK's new resale laws are effectively new system requirements. The organizers who succeed will be those who verify that their infrastructure can technically execute these rules. 2026 will reward those who treat adaptability as their core strategy.

Jens TeichertJanuary 8, 2026

Podcasts & Media