Vucos Logo

Integrations

Vucos is built to plug into the systems you already run — billing, CAS/DRM, CDN, ad servers, BSS/OSS, identity, and payment — through a consistent API-first, webhook-driven surface that turns vendor swaps from quarters of work into days.

50+
Pre-built vendor adapters
< 2 weeks
Typical time to onboard a new vendor
100%
APIs documented in OpenAPI
0
Proprietary lock-ins

API-first, webhook-driven, vendor-neutral

Every commercial and technical boundary in the Vucos platform is exposed as a REST and GraphQL API, paired with a signed webhook stream for every lifecycle event. Adapters ship out of the box for the vendors operators most commonly run — Stripe, Adyen, Widevine, FairPlay, PlayReady, Akamai, CloudFront, Google Ad Manager, SpringServe, and more — but none of them are hard-coded. When you need to replace an incumbent, you swap an adapter without rewriting the product layer above it.

Why this matters

OTT operators rarely start from a blank slate. A launch typically has to interoperate with an existing billing stack, a carrier BSS, a federated identity provider, a preferred CDN contract, and at least one ad server the sales team has already sold into. Platforms that hide those boundaries behind proprietary SDKs look simple in a demo but produce painful migrations at renewal time.

Vucos takes the opposite stance. Every integration is a versioned API with a documented webhook contract, so operations teams can replace a CDN at peak season, change payment gateways for tax reasons, or onboard a new CAS vendor for a regional rollout without opening a multi-quarter program. The platform stays stable while its edges move.

What connects

Billing & payment gateways

Stripe, Adyen, Braintree, Worldpay, Recurly, Chargebee, Zuora, and regional gateways. Direct carrier billing (DCB) and in-app purchase reconciliation for Apple and Google.

CAS & DRM

Google Widevine, Apple FairPlay, Microsoft PlayReady, Verimatrix, Irdeto, Nagra, and NDS/Synamedia. Multi-DRM license orchestration with common encryption (CENC).

CDN & multi-CDN

Akamai, CloudFront, Fastly, Cloudflare, Limelight/Edgio, Lumen, and Tencent. Multi-CDN steering based on cost, QoE, and regional performance, with origin shielding.

Ad servers & SSPs

Google Ad Manager, FreeWheel, SpringServe, Magnite, PubMatic, and Xandr. Prebid Server, OpenRTB 2.x, and server-side ad insertion vendor pass-through.

BSS/OSS & CRM

Amdocs, Netcracker, Oracle BRM, Salesforce, SAP, Microsoft Dynamics, HubSpot, and custom ESBs. Entitlement grants and usage events flow in both directions over signed webhooks.

Identity providers

OIDC, SAML 2.0, OAuth 2.1, Keycloak, Auth0, Okta, Azure AD, Google Workspace, and operator SSO. Federation with telco auth (MSISDN-based) and age-gating providers.

How operators use it

Telco integrating the BSS

Entitlement from a legacy billing stack

Connect a 15-year-old Amdocs BSS to Vucos entitlement without a migration. Subscriber grants, tier changes, and suspensions flow in as webhooks; usage, QoE, and churn signals flow back into CRM reports the carrier already uses.

Broadcaster with multi-CDN

Cost-and-QoE-based CDN steering

Load-balance across three CDNs with rules that prefer the cheapest origin while QoE stays within threshold, then fail over on rebuffer spikes. Contracts are renegotiated annually without touching the player or the ad stack.

Operator rolling out in a new market

Local CAS and payment onboarding

Add a regional CAS vendor and a local payment gateway to launch in a new country. Both plug in as new adapters; existing markets keep running on their incumbents while the new region goes live within weeks.

Technical details

API surface
  • REST with OpenAPI 3.1
  • GraphQL federated schema
  • Server-sent events
  • gRPC for high-throughput server-to-server
  • Consistent OAuth 2.1 / PAT auth
Webhooks
  • Signed with HMAC-SHA256
  • At-least-once with idempotency keys
  • Dead-letter queue and replay
  • Fan-out to multiple endpoints
  • Version pinning per subscriber
DRM & CAS
  • Widevine L1/L3
  • FairPlay Streaming
  • PlayReady SL150/SL2000/SL3000
  • Verimatrix, Irdeto, Nagra, Synamedia
  • CENC multi-DRM packaging
CDN
  • Akamai, CloudFront, Fastly, Cloudflare
  • Limelight/Edgio, Lumen, Tencent
  • Multi-CDN steering with live QoE data
  • Signed URL and token auth per edge
Identity
  • OIDC and SAML 2.0
  • OAuth 2.1 with PKCE
  • JWT with rotating keys
  • Telco MSISDN header enrichment
  • Age-gating provider integration
Observability
  • OpenTelemetry traces on every integration
  • Structured JSON logs
  • Prometheus metrics
  • Per-adapter SLO dashboards

Key Takeaways

  • REST, GraphQL, and signed webhooks on every integration boundary
  • Pre-built adapters for billing, CAS/DRM, CDN, ad servers, BSS/OSS, and identity
  • Multi-DRM and multi-CDN steering without player rewrites
  • Vendor swaps in days or weeks, not quarters
  • OpenAPI 3.1 specs and versioned contracts published for every endpoint
  • OpenTelemetry-native observability across every outbound call

Frequently Asked Questions

Can we keep our existing billing platform?
Yes. Vucos exposes a billing integration contract that has been validated against Stripe, Adyen, Recurly, Zuora, Amdocs, and multiple custom BSS stacks. Entitlements, usage events, and reconciliation files flow both ways over documented APIs and signed webhooks.
Does Vucos force a specific DRM or CAS vendor?
No. The platform is multi-DRM by default and supports every major CAS vendor. You can run Widevine, FairPlay, and PlayReady together for OTT while keeping an existing CAS for STB, under a single license orchestration layer.
How do you handle multi-CDN?
Vucos includes a CDN steering layer that decides per session which CDN to serve from, based on cost tier, live QoE telemetry, and regional policy. Failover is automatic, and swapping a CDN is a configuration change at the manifest origin — not a player release.
What happens when a vendor changes their API?
Each adapter is versioned and owned by Vucos. Breaking changes from upstream are absorbed in the adapter, not passed through to your integration. You get a release note and, when needed, a coordinated migration window — not a production outage.
Can we integrate with our existing identity provider?
Yes. Vucos supports OIDC, SAML 2.0, and OAuth 2.1 against Keycloak, Auth0, Okta, Azure AD, Google Workspace, telco SSO, and custom IdPs. Federation keeps the user record in your identity system while entitlements live in Vucos.
Is every webhook secure and replayable?
Yes. Every webhook is signed with HMAC-SHA256, carries an idempotency key and a monotonic sequence number, and can be replayed from the dead-letter queue for any window. Subscribers can pin to a specific contract version until they are ready to upgrade.

Related

API-First Integrations

Every capability on the platform is a contract — REST, GraphQL, and webhooks — published first as an OpenAPI specification and distributed as typed SDKs. Your engineering team integrates Vucos the same way they integrate Stripe or Twilio.

Read more

Vucos Monetization Engine

One engine for every revenue model you run — subscription, ad-funded, transactional, and hybrid — with entitlement, billing, and ad serving wired into the same data plane so you never reconcile three systems again.

Read more

Cloud & On-Prem Deployments

Run Vucos the way your regulator, procurement, and network team need it — fully managed SaaS, dedicated single-tenant cloud, hybrid with on-prem components, or entirely inside your own data center — from the same versioned code base.

Read more

Ready to learn more?

Talk to an architect about how this fits your deployment.

Book a CallDownload Whitepaper