Festival production intelligence.
Turn artist riders into a shared workspace for schedules, equipment, conflicts, crew, hospitality, changeovers, and delivery-ready production exports.
The rider problem
Every festival production manager knows the pain: dozens of artists, each with a PDF technical rider in a different format. Stage dimensions, input lists, equipment requirements, power needs — all buried in unstructured documents.
Someone has to read each rider, extract the relevant data, and enter it into spreadsheets manually. It takes hours, introduces errors, and has to be repeated every event.
From rider inbox to a production workspace
TRACE reads riders, preserves source evidence, and turns their requirements into structured artist records. Production teams can then coordinate stages, timetables, backline, crew, hospitality, and changeovers in one place.
Claude structured outputs handle extraction, with OCR fallback for scanned files. TRACE is a connected cloud service: rider PDFs and extracted production data are processed by the documented cloud pipeline.
See it in action
Architecture
TRACE runs as a cloud-native pipeline. The React frontend on Vercel handles uploads and the festival dashboard. FastAPI on Cloud Run manages parsing orchestration and business logic.
Claude API extracts structured data from PDF riders — stage plots, input lists, equipment requirements, crew assignments. Cloud Tasks handles async batch processing.
All data lives in PostgreSQL via Supabase. PDFs are stored in Google Cloud Storage. Stripe handles per-festival billing.
What TRACE includes
Everything a production team needs to process technical riders at scale.
PDF parsing
Reads any technical rider PDF — text-based, scanned, or mixed. Handles tables, diagrams, and free-form text.
Timetable and run of show
Build stage schedules, print-ready timetables, changeover plans, and a shared run of show.
Artist workspaces
Keep contacts, technical requirements, hospitality, documents, notes, and source evidence together.
Equipment requirements
Pulls backline, monitoring, and power requirements into structured fields.
Conflict and changeover planning
Compare requirements across artists, expose equipment clashes, and coordinate stage transitions.
Production exports
Generate PDF, XLSX, and CSV outputs for crews, suppliers, stages, and festival operations.
One production workspace
React dashboards connect rider evidence to schedules, logistics, communications, and delivery.
Stack
A cloud-native application with asynchronous document processing and source-aware extraction.
- Runtime
- Python 3.12 · FastAPI · SQLAlchemy
- AI
- Claude structured outputs
- PDF Parsing
- PyMuPDF · pdfplumber · OCR fallback
- Export
- PDF · XLSX · CSV
- Application
- React 19 · FastAPI · PostgreSQL
- License
- AGPL-3.0
Get started
Self-host the development stack with Docker Compose. An Anthropic API key is required for rider extraction.
# Clone and configure TRACE
git clone https://github.com/formray/trace.git
cd trace
cp .env.example .env
# Add ANTHROPIC_API_KEY to .env
# Start API, web app, database, and workers
docker compose upPricing
TRACE is open source. Managed tiers for production companies and festivals that need cloud features.
Free
Free
Try it out
Explorer
€49/mo
Small production companies
Builder
€149/mo
Growing production companies
Scale
€399/mo
Large festivals and agencies
Enterprise
Custom
Multi-org, custom SLA
Base subscription + measured consumption. Monthly billing.
The name
TRACE — TRACE — Technical Rider Automated Content Extraction.
Like tracing a signal path through a mixing console, TRACE follows the structure of a technical rider and extracts what matters. From document to data, precisely.
Open source
AGPL-3.0 licensed. The complete extraction engine is free and open source. Use it, improve it, contribute back.