Getting started
Start with a focused proof of concept.
Choose a service, a delivery path or an operational question. We connect the relevant data, configure FOCUS around your teams and review the findings together.
Start with CDN logs · Add CMCD where available · No proprietary player SDK required
A practical first scope
1. Agree what matters
Select the streams, applications or delivery paths to cover. Agree the operational questions and how to assess data coverage, evidence and usefulness to your teams.
2. Connect data and context
Start with suitable CDN logs and available telemetry. Add service context, known behaviours and responsibilities to help FOCUS interpret findings.
3. Put investigations into the workflow
Review the generated tickets and configure your feeds in natural language. Route relevant findings to Slack, Teams, Jira or email.
4. Review and expand
Assess the first scope together. Extend to further services, data sources or teams where it adds value.
What the first scope delivers
Connected data: agreed sources, with their coverage and available signals made clear.
Configured workflows: operational context, incident feeds and destinations for the selected teams.
Evidence to review: playback behaviour and investigated findings from your data, reviewed together with your team.
A next-step recommendation: what to retain, extend or improve, with the corresponding deployment and commercial scope.
Clear responsibilities from the start
Your team
Provides data access, service context and the people who own the relevant systems. Enables agreed log forwarding or player configuration and decides which operational changes to make.
EINBLIQ.IO
Establishes the agreed data processing, configures FOCUS and helps set up context and feeds. Reviews the findings with your team and supports the agreed next steps.
Start with the data you have
CDN logs: delivery evidence and reconstructed sessions, including when CMCD or an explicit session ID is unavailable.
CMCD in requests: player context alongside the delivery record in CDN logs.
Direct CMCD v2 events: playback events sent to SPECTRA's endpoint and joined with request data through a consistent session ID.
We review available fields and reporting modes during onboarding. Suitable existing data platforms can also provide input.
Deployment that fits your environment
Hosted service: EINBLIQ-operated infrastructure.
Your cloud: deployment in your cloud environment.
On-premises: deployment within your infrastructure.
The architecture is cloud-portable. We agree sizing, data access, operating responsibilities, support and model access for the selected setup.
Pricing aligned with your streaming volume
Pricing is normally based on monthly streaming hours, typically at volumes of millions of hours. Unit prices decrease as agreed volume increases.
Playback sessions or log and telemetry data volume can be used where they fit your business better. We agree the volume basis, deployment and any additional integration or services in your offer.
Share your approximate monthly volume and deployment requirements so we can scope an appropriate offer.
Additional expertise when you need it
Optional professional services help you follow up on incidents and turn the evidence into longer-term improvements.
- Incident follow-up and coordination with delivery or technology partners.
- Technical support for escalations and cross-team investigations.
- Strategic recommendations for streaming quality, delivery and observability.
Scope and responsibilities are agreed separately from the automated service.
Practical questions
Do we need a new SDK in our apps?
No proprietary EINBLIQ SDK is required. CDN logs provide a starting point. Compatible players can supply CMCD, with reporting modes and fields depending on the player and configuration.
Which players can send CMCD v2 events?
Examples include supported versions of dash.js and hls.js. Available reporting modes, metrics and events depend on the player, version and configuration. We review your setup during onboarding.
Can you include encoder, packager or origin logs?
Yes, through a scoped integration. Where you provide access, we can connect those sources and investigation tools to add evidence from further upstream.
Can our team configure the feeds?
Yes. Describe in natural language which findings should go where, and configure the feeds around your team's responsibilities.
Can we use the data for other purposes?
Yes. You have access to the full-fidelity log and telemetry data available in your deployment for your own analysis and other use cases.
Will every signal generate a notification?
No. FOCUS agents investigate signals and assess their impact and relevance before findings reach your configured feeds.
Bring one operational question.
Tell us what you want to understand and which data is available. We will define a focused first scope together.