Streamwake for
streaming platforms.
A scoped partner-evaluation path for platforms and tech vendors considering Streamwake. Review the documented player telemetry contract and REST reference; branding, telemetry availability, integration fit, and any delivery outcome depend on the named scenario and approved evidence.
Three questions a partner review can examine.
These are discovery topics, not generally available outcomes. The review stays tied to the platform surface, permissions, and evidence available for the named scenario.
Stream-health evidence in a partner surface
Discuss whether probe-level health, latency, and anomaly classes can be represented in your product surface. The documented dashboard and telemetry contract are reference points, not a blanket branding or availability commitment.
Documented player telemetry
The documented player telemetry contract defines typed event payloads. A scoped evaluation can examine whether the available evidence supports replay, comparison, or attribution to specific edges, devices, and streams.
Incident-review questions
A review can compare probe evidence with the partner's incident workflow and ask whether the available trail supports triage. It does not promise faster MTTR, fewer tickets, or a customer outcome.
The partner's POV.
Use these as discovery prompts for a named customer scenario. They are not forecasts of what users or support teams will experience after launch.
Viewer-QoE evidence to review
Review whether the configured probe and player evidence can describe playback failures. No claim is made here about viewer retention, support volume, or competitor behavior.
Support workflow fit
A scoped review can compare a classified anomaly and action record with the partner's support workflow. Whether it reduces reproduction work or changes customer handling depends on the evidence and permissions available.
Observability scope
Discuss the monitoring cadence, evidence volume, and ownership model that a named scenario would require. This page does not promise continuous coverage or replace an internal monitoring team.
One SDK.
One REST surface.
How a Streamwake integration sits inside your stack. The exact field names, sample payloads, and curl live on the linked reference pages — this page stops at the shape of the wire so it can never drift.
A player event on your page traverses five hops. The arrows below show the direction of the wire — not a timing diagram.
- Hop 1PlayerYour browser player
- Hop 2@streamwake/player-sdklocal contract · bearer-key init
- Hop 3Telemetry endpointPOST /api/v1/telemetrybearer
- Hop 4Agents dashboardStreamwake — inspection loop
- Hop 5Stream registrationPOST /api/v1/streamscookie
Wire-format details and sample payloads live on the API reference and the player SDK reference.
API reference
The three cookie-authed endpoints that own the stream lifecycle — POST /api/v1/streams, GET /api/v1/streams, and GET /api/v1/agents. Every sample is rendered from the same contract the route handlers emit.
Player SDK (@streamwake/player-sdk)
The checked-in SDK source and in-app contract reference for player telemetry. Public npm and CDN distribution are not currently verified; the reference covers bearer API key auth, four-line init, eight typed event payloads, and batched delivery to /api/v1/telemetry.
Claim status labels: see definitions.
Three ways we grow together.
Potential commercial paths for discovery only. Specific terms, availability, and any revenue share require an approved partner arrangement; this page stays informational.
Partner economics, if approved
A revenue-share path may be discussed for an approved partner scenario. No plan name, standard percentage, customer entitlement, or generally available commercial term is published here.
Co-marketing, if approved
A joint post or changelog entry may be considered after discovery and approval. Launch timing, channels, and general availability are not promised by this page.
Co-sell, if approved
A co-sell path may be considered when a partner scenario and account fit are approved. Account ownership, coordination, and any commercial split remain discovery items.
Four tiers, one ladder.
The pricing components below are discussion aids for partner discovery, not a public availability or entitlement statement. Any tier, wholesale, or revenue-share shape is confirmed only for an approved scenario.
Registered Partner
IT consultants, streaming consultants, independent engineers, small system integrators.
- Free training
- Demo environment
- Sales kit
- API documentation
- Marketing materials
- Lead registration
Silver Partner
Consultancies and integrators ready to close their first five customers.
- 5 customers
- Complete certification
- Annual business review
- Everything in Registered
- 25% recurring commission
- Joint webinars
- Co-marketing
- Priority technical support
- Deal registration protection
- Shared customer success resources
Gold Partner
Established regional partners with a certified engineering bench.
- 20 customers
- Certified engineers
- Annual revenue target
- 30% recurring commission
- Dedicated Partner Manager
- Joint marketing campaigns
- Custom onboarding
- Early feature access
- Beta participation
- Marketplace listing
Platinum / OEM Partner
Large streaming platform companies (e.g. Brightcove, Vimeo OTT, Uscreen, Muvi, OTTera, ViewLift, Deltatre).
- Per active customer$10–25 per active customer / month
- Platform license$2,500–10,000 monthly platform license
- Enterprise annualCustom enterprise annual agreement
End customers never know Streamwake is running behind the scenes, unless the partner wants to co-brand it.
Talk to OEM salesResell Streamwake as a managed service.
For MSPs running observability or delivery as a managed practice. A flat monthly fee, white-label reporting under your brand, and a partner dashboard to roll up every customer account you administer.
Managed Service Provider pricing
Resell Streamwake under your own brand with a flat recurring cost — no per-seat mathematics on your customer's bill. Designed for MSPs running observability, delivery, or video operations as a managed practice.
- Up to 100 managed customer organizations
- Unlimited incidents handled by the Streamwake partner team
- White-label reporting rendered under the MSP brand
- Priority AI processing lane on shared infrastructure
- Partner dashboard with managed-org roll-up
- Full API access for hands-on automation
One math example, not a guarantee.
A planning sketch for an MSP that onboarded eighty customers at $75 per customer per month, against the flat $1,500 partner fee.
- Customer base
- 80 managed organizations
- Resell price
- $75 / customer / month
- Monthly revenue
- $6,000
- Partner fee
- $1,500
- Gross margin
- $4,500 / month
Illustrative example — not a guarantee of revenue, margin, or unit economics. Real partner margins depend on resell pricing, contract length, and customer mix.
Run Streamwake under your own brand.
For partners who want the full Streamwake platform as a white-labeled product. Three tiers by managed organization count, plus the customer MSRP partners resell against with their contracted discount applied.
Startup Platform
New white-label partners onboarding their first 250 customer organizations.
Growth Platform
Established white-label operators with a scaled customer base.
Enterprise Platform
Large operators and OEMs with custom volume and governance requirements.
What every white-label tier ships with
The capabilities that come baked into the white-label platform subscription. Custom integrations are scoped during the discovery call and contracted alongside the platform license.
- Full white labeling under the partner brand
- Full API access for hands-on automation
- SSO with the partner identity provider
- Contractual SLA backed by the partner team
- Custom integrations scoped against the partner stack
The MSRP partners resell against
The list prices partners quote on Streamwake customer plans. Partner discounts off MSRP are applied at the partner tier shown below — the partner books the discount, not the customer.
| Customer plan | MSRP | Action |
|---|---|---|
| Starter | $149 / month | |
| Professional | $499 / month | |
| Business | $999 / month | |
| Enterprise | Custom | Contact sales |
Partner discounts off MSRP: Registered 20%, Silver 25%, Gold 30%, Platinum negotiated OEM pricing.
Five steps, end to end.
An illustrative path from first contact to a possible launch. Timing, launch channels, and approval depend on the named integration scenario; no schedule is promised here.
- 1
Apply via the form
Send a short note about your platform and the integration shape you have in mind. We read every submission.
- 2
Discovery call
A human-led discussion of the integration shape, any proposed launch window, and commercial fit; no timing or launch commitment is implied.
- 3
Dev sandbox + bearer key
If enabled for the evaluation, use the documented account and bearer-key path described in the API keys guide.
- 4
Build against the SDK & API reference
Evaluate the documented player telemetry contract alongside your platform surfaces and the REST endpoints. Public SDK distribution remains unverified.
- 5
Co-launch
Discuss whether a joint changelog entry or blog post fits the approved scenario; no launch channel or date is guaranteed.
The questions
partners ask first.
Integration requirements, technical support, revenue terms, timeline to go live, and the support channels that come with the program.
See all partner questionsPut a number on it.
A planning calculator for streaming-platform partners sizing a Streamwake rollout. Slide to your team's current incident load and average MTTR — the projected annual return shows up on the right. No data leaves your browser until you decide to share it via the form below.
ROI in 60 seconds.
Slide to your team's current incident load. The math runs entirely in your browser — nothing is saved until you decide to share it with us.
Annualized cost saved
$29,260/yr
Send a partner note with these numbers attached — the team replies within two business days.
Send me this breakdownNone of the five inputs is a measured customer or industry benchmark.
The completed incident-outcome findings provide bounded workflow context, not a universal ROI dataset. The synthetic DRM license-path record shows a simulated 18-minute event clock, and the synthetic viewer-recovery record shows simulated player-side recovery gates. Both records explicitly label their telemetry as illustrative and not customer evidence, so they do not validate the calculator's input values or its projected savings.
- Monthly incidentsIllustrative
- The findings document bounded incidents, not a recurring monthly incident rate.
- Average MTTRIllustrative
- The bounded scenario clocks show an outcome shape, not a measured Streamwake average.
- On-call engineer costIllustrative
- The findings report no measured labor cost or industry cost benchmark.
- Autonomously investigatedIllustrative
- Synthetic governed actions show a workflow pattern, not a measured production share.
- AI-assisted time savedIllustrative
- The findings do not measure engineer time saved, so this remains a directional projection.
Read the bounded source records: DRM license-path recovery and viewer-recovery validation.
Beyond streaming: the partner marketplace.
A complete list of recommended third-party tools — alerts, BI, warehouses — that fit alongside Streamwake. The page doubles as the application for vendors who want their tool listed.
Run the partner walkthrough before the call.
A five-phase demo script for the next partner call — what to open first, what to say, what to listen for, and the observable artifact that proves each phase landed. ~30 minutes; share it with your team before the call.
Send a note.
We'll come back fast.
Tell us about the platform you're integrating with and the shape of the integration you have in mind. The first reply comes from a person on the partner team — not a queue.
Human-led review; response timing is not guaranteed.
Prefer a direct conversation? Use the contact form.