Skip to content
Docs Docs

POC Checklist

POC readiness depends on clear scope, experiment controls, security clearance, and agreed success thresholds.

  1. Goals and Scope (Define First)

    Meaningful POC results require:

    • Target concurrency (CCU) is defined and achievable
    • Trial duration includes peak traffic conditions
    • Geographic distribution reflects real audience behavior
    • Target platform and player are selected
    • Joint delivery-path goals are defined, including what the POC must prove and what may need to be shaped together

  2. Target Platform Selection

    Select a single, representative environment for initial validation.

    Define:

    • Platform(s) and device types
    • Player(s) and versions
    • Target CCU for the platform
    • Geographic region(s)
    • Live event or representative test stream

    Consider:

    • Network conditions and coverage
    • Ability to reach meaningful scale quickly
    • Stability and consistency of the platform

    Use the supported platform and player documentation to confirm the first validation environment, or engage Rilla for custom support.

  3. Delivery Architecture Alignment

    Confirm how Rilla will integrate within your existing delivery stack.

    Required visibility:

    • CDN configuration
    • Multi-CDN steering (if applicable)
    • DRM implementation
    • SSAI / ad-tech setup
    • ABR configuration
    • Buffering strategy for the target platform

  4. Experimentation and Operational Capabilities

    Ensure the required tooling exists to run and evaluate the POC.

    • Ability to run A/B tests (CDN-only vs CDN + Rilla)
    • Feature flag or controlled rollout capability
    • Access to a representative test stream
    • Access to CDN telemetry and analytics
    • CMCD enabled on the player (preferred)
    • Required CDN headers exposed

  5. Joint Delivery Path and Feedback Loop

    Rilla POCs define a joint delivery path to value, then use live telemetry and implementation feedback to refine performance, integration, and product capability.

    Define upfront:

    • Key areas to shape together, such as performance tuning, platform support, metrics visibility, or rollout controls
    • Feedback cadence, such as weekly working sessions
    • Shared success priorities for the POC

    Working model:

    • Rapid iteration based on live telemetry and test results
    • Joint debugging and performance tuning
    • Prioritized feature or platform support where required

  6. Data, Compliance, and Security

    Identify and address any risks early in the process.

    • Data handling model reviewed
    • WebSocket endpoints approved
    • Security / compliance team acknowledgment (if required)

  7. Success Criteria Alignment

    Before integration begins:

    • Success metrics are defined (deflection + QoE guardrails)
    • Thresholds and acceptable ranges are agreed
    • Measurement methodology is aligned

Ready to start signal

Section titled “Ready to start signal”

The POC is ready to begin when:

  • A target platform and event are confirmed
  • Delivery architecture is understood
  • Experimentation capabilities are in place
  • Security and compliance are cleared
  • Success criteria are agreed