Streamwake + X.
Named integration surfaces, grouped by what each documented surface sits next to.
Streamwake sits on top of the encode, packaging, and delivery tools you already run — same signal bus, different obligation. Every row below is a documented, conceptual, or unverified +Vendor page, with its evidence boundary stated explicitly. Below the catalog, five evaluation surfaces — PagerDuty, Splunk, MediaTailor, Bitmovin, and CMCD — expose bidirectional, inbound, and observability evaluation lanes without implying a verified vendor path.
Claim status labels: see definitions.
Compare alongside the Free Stream Check (a 5-check live probe of any playback URL) and the Partner Marketplace.
Explore Streamwake integration pages.
Browse the available detail pages below. Each card links directly to the corresponding Streamwake integration page.
Bidirectional, inbound, and observability evaluation surfaces.
These views sit alongside the data-vendor catalog as operator-facing evaluation or setup surfaces. A view, saved source, or synthetic test does not by itself establish vendor compatibility, live telemetry, or production operation.
| Surface | What it wires | Open setup page |
|---|---|---|
| Streamwake + PagerDuty | Bidirectional ITSM — V3 Webhooks seed PD incidents into the investigation timeline; Streamwake approves, escalates, and resolves back to the same incident. | Open |
| Streamwake + Splunk | Inbound ITSM — notable events, search hits, CAD triggers, and alert_action firings are pushed in as classified investigation seeds. | Open |
| Streamwake + AWS MediaTailor | Documented SSAI signal scope — adBeaconDrop, sessionInit, and scte35LateResponse can be assessed alongside CDN and AWS-side control-plane observations. | Open |
| Streamwake + Bitmovin Analytics | Unverified player-side QoE evaluation surface — no live Bitmovin account, export relay, end-to-end event path, or production operation is demonstrated. | Open |
| Streamwake + CMCD | CTA-5004 player-side evidence — CMCD-Object, CMCD-Request, CMCD-Status, and CMCD-Session landed as typed correlation inputs. | Open |
Read the forward-looking Open Player SDK integration shape — an editorial reference, not a seventh setup view.
Claim status labels: see definitions.
Evidence-bounded references, not setup surfaces.
These entries preserve correlation context without turning an unverified mention into a integration, verified connection, or live telemetry path.
Conviva Analytics
Reviewed evidence mentioned Conviva only in a correlation context. It did not establish a dedicated Conviva integration page, documented Conviva scope, verified Conviva connection, or live Conviva integration. Conviva is therefore presented only as an unverified correlation reference; no Conviva capability or compatibility claim is made.
What has been exercised locally?
For the operator-facing surfaces above, three local signals can be recorded: connected means a source row is saved with the fields an evaluation route accepts; test event sent means a page test has round-tripped a synthetic fixture through local code; and live sample received means a non-fixture inbound record has arrived in local application state. These signals do not change the report-reviewed public statuses or prove a vendor account, compatibility, production readiness, or an end-to-end customer path.
Claim status labels: see definitions.
Two other surfaces on the same signal bus.
The Free Stream Check looks at any playback URL in under a minute; the Partner Marketplace lists the partners who build alongside Streamwake. Both live one route away.
Probe any playback URL in under a minute.
Manifest, segments, bitrate ladder, CDN response, playback errors — five checks, no login, drop in the URL and read the report. The same probe lane that runs against your Mux, MediaLive, and Cloudflare Stream pipeline.
Find the partner who builds alongside Streamwake.
Browse documented partner destinations and scoped evaluation paths. The matrix does not imply that every partner has a connector, deployment, or universal signal-bus coverage.
Inbound ITSM sources — ServiceNow and beyond.
The nine rows above are vendors Streamwake reads signals FROM. ServiceNow is the mirror image: an ITSM tool that pushes incidents INTO Streamwake's detection surface via a signed webhook.
Have a vendor that fits among the nine listed today?
Encoding, packaging, CDN, or observability — if there's a tool on your shortlist that you'd want a +Vendor page for, drop the name below. We read every submission and prioritise the next two integration pages from the same list.
Encoding/Packaging → Mux and AWS MediaLive are the first two listed. Akamai and Fastly are the natural next two — the Observability lane lists Datadog, New Relic, Prometheus + OTel, and Grafana, with Splunk Observability Cloud the next observability +X still on the roadmap.