Protect live events while the audience is still watching.
Opaque session-scoped identifiers, a detection workflow and a chain-of-evidence report for premium live moments. Source identification within roughly four minutes in validated workflows; customer-controlled enforcement is a separate stage.
From unauthorized restream to attributed source.
Illustrative sequence of events during a live incident. The window from sample to attribution is what Vestigit compresses. Enforcement follows a separate customer decision.
Illustrative timeline. Actual timing depends on workflow, sample quality and enforcement policy.
Model the audience still reachable after detection.
An interactive model of how the live audience evolves during an event and how much of it is still addressable by the time a source is identified. Wires into the same illustrative dataset used across the platform.
Model the audience and revenue still within reach.
Adjust the inputs on the left. Move the REVOKE line directly on the chart. Numbers are an illustrative gross scenario — estimated pirate viewers are not proven one-for-one lost sales.
Drag the cyan REVOKE line on the chart to change the response minute.
Method: potential paid revenue = affected audience × time-adjusted paid-switch assumption × access price, using the canonical 90-minute football-match audience profile. Illustrative gross scenario output only — not guaranteed recovered revenue.
This chart uses the modeled audience distribution of a standard 90-minute football match: an opening surge, a stable first half, a half-time dip, a second-half return and a late lift.
Models for other sports and live-event formats are in development. Tell us which event type matters to you and we will contact you when the relevant model is ready.
Illustrative model. Actual outcomes depend on workflow, sample availability and customer enforcement policy.
Two views of the same detection workflow.
The operations view shows what happens minute by minute. The evidence view shows what is captured and delivered to the customer for the enforcement decision.
| Time | Operation |
|---|---|
| T+0:00 | Unauthorized restream captured by sample source |
| T+0:45 | Sample queued for analysis |
| T+1:30 | Identifier recovered |
| T+2:30 | Correlated to session / token |
| T+3:30 | Detection record delivered to customer |
| T+3:30+ | Customer decides and executes enforcement |
Illustrative. Actual timing depends on sample quality, integration and enforcement policy owned by the customer.
Fit the embedding stage into the pipeline you already run.
Three integration routes cover the majority of live-event stacks. Each route validates the same detection outputs downstream; the difference is where embedding is invoked.
Highlighted stage: where Vestigit embedding is invoked for the Embedder in cloud model.
The identifier survives what live pirates actually do.
The same forensic identifier used for live events is validated against the transformations most commonly applied to unauthorized restreams. Toggle a transformation to see the survivability profile.
This is a controlled transformation visualization, not a detector result. Outcomes are workflow-specific and validated per deployment during PoC.
Part of the picture is removed.
Cropping removes pixels from the frame edges and may then scale the remaining picture back to the output size. It changes the framing and can also change the aspect ratio.
- Fixed border removal, zoom-and-crop or asymmetric reframing.
- Cropping followed by rescaling and re-encoding.
Cropping can remove part of the marked picture and changes its spatial alignment. More aggressive crops leave less visual information available for analysis, while subsequent scaling or compression can add further loss.
15.04 s · 1920×1080 to 1728×972 · H.264 · central crop, 96 px left/right and 54 px top/bottom · 24 fps.
This transformation category is included in Vestigit's independent review. The displayed derivative illustrates the transformation; no detector outcome is claimed for this exact web sample.
PoC → Pilot → Production.
- 01PoC
Scoped technical validation with agreed acceptance criteria.
- 02Pilot
One or more live events end-to-end, with detection and evidence review.
- 03Production
Ongoing operation inside the customer workflow.
Single event, event package or always-on.
- Single event
One event or fight card protected in isolation.
- Event package
A season, series or tournament with a fixed calendar.
- Always-on
Continuous live protection across all channels.
Plan the next event protection cycle.
Workflow audit, integration path and a measurable pilot scope against your calendar.