Stride is a vertically-integrated event ticketing and intelligence platform. It combines ticket sales, ad campaign management (Meta + TikTok), on-site vendor payments (tabs), email campaigns, analytics, and attribution tracking into a single dashboard for event organizers. No competitor connects the full funnel — from the ad impression that sells the ticket, to the drink the fan buys at the bar, to the data that makes the next campaign smarter.

Mid-market event organizers: independent venues, mid-size festivals, club promoters, and conference organizers. These organizers are underserved by Ticketmaster (which focuses on arenas) and frustrated by Eventbrite (high fees, poor tools, fund holds).

For organizers: “One dashboard to sell tickets, run ads, manage event-day ops, and see exactly which $50 of ad spend generated which $5,000 of revenue — including what those fans spent on-site.” For fans: “Buy tickets in 2 taps. Link your card once. Walk into any event, scan your QR code, and your tab is open.”

Ticketmaster is under DOJ antitrust prosecution (trial began March 2026) and doesn't serve mid-market. Eventbrite charges 10–14% effective fees vs. Stride's ~6–8% all-in, holds organizer funds, and is rated 1.6/5 on Trustpilot. Dice was acquired by Fever (June 2025) with uncertain direction. Shotgun is niche European electronic music only. None offer the full-funnel integration Stride provides.

Global online event ticketing is ~$85B (2025), growing 4–7% CAGR. A 1% share = $850M GMV, generating $30–50M in blended platform revenue.

Full event management with draft/publish lifecycle, multi-tier ticketing engine with Redis-backed holds, Stripe Connect payments (Apple Pay/Google Pay), rotating QR tickets with anti-screenshot security, ticket transfers, promo codes, organizer analytics dashboard, Meta + TikTok ad campaign management with attribution, Google Analytics integration, on-site tab system with vendor POS, staff check-in, email campaigns, embeddable widget, webhook system, org roles & permissions, hype scoring with waitlist, and refund processing.

Tier 3 (differentiation): AI assistant (Claude-powered proactive intelligence), fan persona engine, loyalty system, AI creative generation, Embed SDK v2, smart pricing suggestions, post-event AI reports. Tier 4 (platform/network effects): P2P resale marketplace, seat map builder, dynamic pricing (ML), multi-currency/i18n, public developer API, app marketplace, white-label enterprise tier, NFC wristband integration, fan mobile app (React Native).

Primary revenue: platform fee of 2.0% + $0.99 per ticket transaction (on top of Stripe’s standard processing fee). For a $50 ticket, the platform earns $1.99. Planned secondary revenue: managed ad spend margin as organizers run Meta/TikTok campaigns through the platform. The infrastructure for campaign management and attribution is already built.

Yes. The fee formula lives in a single file (src/lib/fees.ts) and a display string in the settings page. It’s a one-line change plus a UI text update. The handoff checklist documents the exact files and lines.

Stripe Connect with destination charges. Each organizer connects their own Stripe Express account through an in-app onboarding flow. When a ticket is purchased, Stripe routes the organizer’s share directly to their account. The platform fee is retained by the platform’s Stripe account. There is no fund-holding — organizers receive payouts on Stripe’s standard schedule.

Next.js 15 (App Router) with React 19, TypeScript 5 (strict mode), tRPC v11 (13 routers), PostgreSQL via Supabase with Drizzle ORM, Redis (ioredis) for caching/queuing, Inngest v3 for background jobs, Stripe (Connect, Payment Intents, SetupIntents), Clerk for auth, Resend for email, Vercel for hosting, Tailwind CSS 4.2 with Radix UI Themes, Recharts for visualizations, and Sentry for error tracking.

Single Next.js application (modular monolith), organized by concern: App Router pages (dashboard, events, tickets, check-in, tabs, vendor, embed), database schema (18 tables) with Drizzle ORM, 13 tRPC routers, utility libraries (Stripe, email, Redis, QR, fees, attribution), Inngest background jobs, and React components. The module boundaries are designed for eventual microservice extraction.

Redis-backed inventory holds prevent overselling (atomic decrements, 5-minute auto-expiry). Rate limiting with Redis sliding windows. Vercel auto-scales serverless functions. Stripe handles payment volume scaling. Inngest decouples background jobs. Stateless API layer with no session affinity required. Comfortable handling up to ~50K concurrent on-sale before needing architectural changes.

Vercel auto-deploys from the main branch. Feature branches trigger CI but not deployment. The CI pipeline (GitHub Actions) runs lint, type check, unit tests, build, and E2E tests with automatic concurrency cancellation.

All services are usage-based or have generous free tiers. Vercel Pro ($20/mo), Supabase Pro ($25/mo), Stripe (2.9% + $0.30 per transaction, passed through), Clerk (free up to 10K MAU), Resend ($20/mo for 50K emails), Upstash Redis (pay-per-request), Inngest and Sentry (free tiers). At low volume, the platform can run for under $100/month. Costs scale linearly with usage.

Clerk provides JWT-based authentication with webhook sync to a local users table. Supported sign-in methods are configurable (email, Google, etc.). Protected routes are enforced by middleware. Public routes (embed, check-in, webhooks, tracking) are explicitly allowlisted.

Anti-screenshot design: QR codes contain HMAC-SHA256 signed tokens that rotate every 30 seconds. A screenshot of a QR code becomes invalid within 30 seconds. The signing secret is a server-side environment variable.

All database queries are scoped by orgId. tRPC procedures enforce organization membership via roleProcedure. There are no cross-org data leaks by design — unit tests verify data isolation.

Straightforward. A detailed handoff checklist documents every step. The majority of the work is creating accounts with third-party services and swapping environment variables.

Minimal. Brand name: 7 files (layout, landing page, sign-in/up, sidebar, email footer, embed event name). Logo: single file replacement. Email sender address: 2 files. Platform fee formula: 1 file + 1 display string. Inngest project ID: 1 file.

Low. Stripe is deeply integrated (switching would be a significant rewrite). Clerk could be replaced with another auth provider with moderate effort. Vercel is standard Next.js deployment — any Node.js host works. Supabase is used only as managed Postgres (any PostgreSQL provider works). Redis uses standard protocol (any provider works).

The codebase is well-organized, fully TypeScript, and follows standard Next.js/tRPC conventions. A senior full-stack developer familiar with the stack could be productive within a few days. The product architecture doc, priorities doc, and handoff checklist provide comprehensive onboarding context.

The modular monolith architecture with clear domain boundaries (ticketing, payments, ads, on-site, analytics) means multiple developers can work in parallel without stepping on each other. The tRPC router structure naturally partitions backend work by domain. The product architecture doc outlines eventual microservice extraction paths as volume warrants.

The platform is feature-complete for running paid events today. Onboard organizers (self-serve sign-up + Stripe Connect), earn 2.0% + $0.99 per ticket sold, layer in ad spend margin as organizers adopt campaign management tools, and on-site tab charges generate additional processing volume.

Yes. The platform is built on open-source frameworks and libraries (Next.js, React, Drizzle, tRPC, etc.) with all application logic written from scratch. There are no proprietary third-party code licenses to transfer beyond standard open-source dependencies (MIT, Apache 2.0).