Skip to content
Vestigit

TECHNOLOGY / INTEGRATIONS

Protection that fits the stack you already run.

Vestigit connects at two points in the video workflow: content processing and delivery. Choose the path that matches your encoder, origin and CDN.

Explore integration pathsView architecture
Broadcast Integration Consolev1 · patch-bay
  1. Customer
    Source
  2. Customer01 EMBEDDER
    Processing
  3. Customer
    Origin
  4. Customer02 MIXER / CDN
    Delivery
  5. Customer
    Player

Two active integration points: Embedder in processing and Mixer at delivery. All other workflow stages remain customer-controlled.

Integration surfaces

Two integration surfaces. One session-specific stream.

The Embedder creates synchronized A/B variants in the processing path. The Mixer uses session context to select the appropriate sequence during delivery. Authentication, entitlement and customer identity remain in the systems that already own them.

Customer-controlledVestigitShared interface
  1. Customer
    Content
  3. Customer
    Encoder / Packager
  4. Customer
    Origin
  6. Customer
    Player
Content processing

Embedder zone

The Embedder produces two synchronized variants — A and B — that remain separate through the encoder, packager and origin. No single stream carries a session identifier at this point; only the paired variants exist in delivery-ready form.

A/B remain separate through processing and origin · Mixer alone yields one session-specific stream

Embedder paths

Choose where the Embedder lives.

Model 01Embedder in cloud
  1. Customer
    Content source
  2. Vestigit
    Vestigit Cloud Embedder
  3. Customer
    Customer Encoder / Transcoder
    A / B
  4. Customer
    Packager / Origin
    A / B
  5. Shared
    CDN + Vestigit-Mixer
    A / B
  6. Customer
    Player
Placement
Vestigit-managed cloud, between the contribution source and the customer Encoder / Transcoder.
Customer change
Route the source through the Cloud Embedder and receive synchronized A/B outputs for encoding, packaging and origin delivery.
Vestigit role
Operate the managed A/B embedding service and validate the media hand-off.
Best fit
Cloud-first workflows and teams looking for a limited operational footprint.

Detector operates as a Vestigit-side service outside the playback chain

Model 02Embedder with integrated encoder
  1. Customer
    Content source
  2. Shared
    Integrated Encoder + Vestigit A/B Embedder
    A / B
  3. Customer
    Packager / Origin
    A / B
  4. Shared
    CDN + Vestigit-Mixer
    A / B
  5. Customer
    Player
Placement
Inside the customer DC or VPC, using an integrated encoder and Vestigit A/B Embedder path.
Customer change
Configure the processing stage to produce two synchronized A/B variants inside the controlled environment.
Vestigit role
Provide and validate the A/B embedding component and its operational integration.
Best fit
On-premises or hybrid workflows that need the media path to remain inside the customer perimeter.

Detector operates as a Vestigit-side service outside the playback chain

Model 03Custom integration
  1. Customer
    Content source
  2. Shared
    Customer Encoder / Transcoder with Vestigit module
    A / B
  3. Customer
    Packager / Origin
    A / B
  4. Shared
    CDN + Vestigit-Mixer
    A / B
  5. Customer
    Player
Placement
Defined around the customer's encoder, transcoder, packager, vendor and operating constraints.
Customer change
Interfaces and component placement are designed during technical discovery and validated against a supported target workflow.
Vestigit role
Define the module or integration boundary, validate synchronized A/B output and support implementation.
Best fit
Vendor-restricted, hybrid, private or highly customised environments.

Detector operates as a Vestigit-side service outside the playback chain

Mixer / CDN paths

Choose how session logic reaches delivery.

Discovery topics — validated during PoC

  • MANIFEST / SEGMENT REQUEST
  • SESSION REFERENCE
  • CACHE BEHAVIOUR
  • FAILURE MODE
  • LATENCY BUDGET
Quick CDN adjustments

Use available edge, origin-shield or request-processing capabilities to add session-aware A/B selection with a limited change surface.

Best fit: Delivery environments where request context and routing logic can be adjusted without rebuilding the CDN workflow.

Change surface

See exactly what changes — and what remains yours.

  • Vestigit connects to
    Source or media-processing path
    Customer-side change
    A/B generation or routing
    Remains customer-controlled
    Authentication and entitlement
  • Vestigit connects to
    Origin / CDN request path
    Customer-side change
    Manifest or segment-selection point
    Remains customer-controlled
    Account, subscriber and device identity
  • Vestigit connects to
    Session or token reference interface
    Customer-side change
    Stable session context
    Remains customer-controlled
    DRM policies and licence workflow
  • Vestigit connects to
    Detection input and result interface
    Customer-side change
    Sample submission and action hand-off
    Remains customer-controlled
    Enforcement decision and customer communication
  • Vestigit connects to
    Monitoring and integration logs
    Customer-side change
    Access to agreed test and operational data
    Remains customer-controlled
    Existing business rules and platform ownership

Player and app behaviour usually remain unchanged, but token refresh, URL signing, redirects and manifest handling are validated during discovery.

Vestigit correlates an extracted A/B sequence with an agreed opaque session reference. Customer systems remain responsible for resolving that reference to an account, subscriber, device or contract and for executing any enforcement action.

Integration readiness

Five decisions define the integration.

  1. 01

    Can the processing chain produce synchronized A/B variants?

    We validate the encoder, transcoder or packager capabilities, available test environments and any restrictions on additional outputs.

    Show inputs & impact
    What we need
    Vendor, version, test environment, sample output and logs.
    What it affects
    Embedder placement and paired-ladder feasibility.
    CLIENT INPUT
  2. 02

    Where can request-aware logic run?

    The integration point may sit at the CDN edge, origin shield, reverse proxy or application layer, depending on ownership and platform capabilities.

    Show inputs & impact
    What we need
    Origin/CDN ownership, executable logic surface and request context.
    What it affects
    Mixer placement and latency.
    TO VALIDATE
  3. 03

    How do manifests and cache keys behave?

    Personalised delivery requires a clear understanding of manifest generation, URL rewriting, segment selection and cache-key rules.

    Show inputs & impact
    What we need
    Sample manifests, segment URLs and cache-key documentation.
    What it affects
    Cache efficiency, origin load and session-specific delivery.
    TO VALIDATE
  4. 04

    Which stable session reference is available?

    The selected reference must remain usable throughout playback and be resolvable by customer systems to the required account, device or contract context.

    Show inputs & impact
    What we need
    Authentication, entitlement and token-flow documentation.
    What it affects
    Selection context and attribution mapping.
    CLIENT INPUT
  5. 05

    How will detection and enforcement connect?

    The PoC should define how samples are submitted, how results are returned and which system performs the final action.

    Show inputs & impact
    What we need
    Sample path, result interface and revocation or blocking owner.
    What it affects
    Operational workflow and PoC acceptance criteria.
    POC ITEM

Delivery path

Prove the path before rollout.

  1. Stage 01

    Discovery

    Map the current stack, vendor ownership, technical constraints and target operating model.

    • Integration assumptions
    • Component placement
    • Open questions
    • Initial risk list
  2. Stage 02

    PoC

    Validate the A/B path, Mixer placement, session-reference flow and detector output on one agreed stream or asset.

    • Test architecture
    • Acceptance criteria
    • Verified sample path
    • PoC findings
  3. Stage 03

    Pilot

    Run the integration under production-like traffic, monitoring and operational conditions.

    • Operational workflow
    • Performance findings
    • Support boundaries
    • Production recommendations
  4. Stage 04VERIFIED PATH

    Production

    Add scale, observability, support procedures, SLA and operational handover.

    • Production configuration
    • Monitoring and escalation
    • Responsibility matrix
    • Continuous improvement plan
See Discovery & PoC

Integration questions

Integration questions, answered directly.

Start technical discovery

Bring your current stack. Leave with a clear integration map.

Share your architecture, vendor list, sample manifests, token flow and CDN/origin constraints. We will define the integration path, PoC scope and responsibility model.

  • HLD
  • VENDOR LIST
  • MANIFEST
  • TOKEN FLOW
  • CDN RULES
Start technical discoveryView the full architecture