Vucos Logo

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.

5
Monetization models on one engine
< 100 ms
Entitlement decision latency
20+
Payment integrations out of the box
0
Code releases to change pricing

SVOD, AVOD, and TVOD on a single plane

The Vucos Monetization Engine is the commercial core of the platform. It unifies subscription management, transactional purchases, ad decisioning, entitlement, and payment orchestration behind a single API and event model. Operators can run any combination of SVOD tiers, AVOD free-with-ads, TVOD rentals or EST, PPV windows, and dynamic bundles — with one catalog, one identity, and one set of business rules. Pricing, promotions, and packaging can be changed by product teams without engineering releases, and every transaction is published to analytics and finance in the same stream.

Why this matters

Most OTT operators stitch together a billing platform, an ad server, a CRM, and a bespoke entitlement service. Each system has its own catalog, its own price model, and its own idea of what a subscriber is. The result is that every new bundle, price test, or regional tier requires weeks of integration work and produces numbers that never quite agree at the end of the month.

Vucos collapses those layers. Subscriptions, transactions, ad impressions, coupons, and entitlements share one catalog and one ledger. A product manager can launch a new hybrid tier — for example, a discounted ad-supported plan with one hour of premium live sports per week — as a configuration change. The engine enforces it at the player, books the revenue in finance, and measures it in analytics without a ticket being opened.

What the engine does

Subscription management

Recurring billing across multiple tiers, trials, grace periods, proration, dunning, and involuntary churn recovery — with native support for yearly, monthly, weekly, and prepaid plans.

Integrated ad server

VAST 4.2 / VMAP server-side ad insertion and client-side ad insertion, with header bidding, waterfall, frequency capping, and ad-podding under a single decisioning layer.

Entitlement & authorization

Real-time entitlement checks at play, download, and casting — keyed to subscription tier, geography, device class, concurrency limit, and content window.

Payment orchestration

Pluggable payment gateways, mobile operator billing (DCB), in-app purchase reconciliation (Apple, Google), wallet and voucher redemption, and multi-currency settlement.

Dynamic bundles & packaging

Compose bundles from SVOD tiers, AVOD access, sports add-ons, PPV credits, and linear packs — with dependencies, upgrade paths, and cross-sell rules defined as configuration.

Promotions & pricing experiments

Coupons, referral codes, seasonal campaigns, A/B price tests, and retention offers — targeted by cohort, region, device, or acquisition channel with audit trails.

How operators use it

Telco operator

Bundle-with-tariff launch

Bundle OTT subscriptions into mobile and fixed tariffs without a billing migration. The engine accepts entitlement grants from the BSS, handles proration, and reports commercial outcomes back as a clean line item finance can close the month on.

Broadcaster

Hybrid SVOD + AVOD launch

Launch a free ad-supported tier alongside an existing SVOD catalog in a single weekend. Ad slots, frequency caps, and upgrade prompts are served from the same engine that enforces SVOD entitlements — no second integration.

Sports rights holder

PPV windows with season pass

Sell individual match PPVs and a season pass that grants every fixture, with automatic entitlement rollover. Refund rules for postponed fixtures, partial passes, and regional blackouts are handled by configuration rather than custom code.

Technical details

Monetization models
  • SVOD (tiers, trials, annual, monthly, weekly)
  • AVOD (free, ad-supported, freemium)
  • TVOD (rental, EST)
  • PPV and event passes
  • Hybrid and dynamic bundles
Ad standards
  • VAST 4.2
  • VMAP 1.0.1
  • OM SDK for viewability
  • SSAI and CSAI
  • Prebid / header bidding
  • IAB OpenRTB 2.x
Payment & billing
  • Stripe, Adyen, Braintree, Worldpay
  • In-app purchase (Apple, Google)
  • Direct carrier billing
  • Voucher and gift codes
  • PCI-DSS scope minimized via tokenization
Entitlement
  • Sub-100 ms play authorization
  • Concurrency enforcement
  • Geoblocking and content windows
  • Device limits and family sharing
  • Offline download licenses
Finance & reporting
  • Revenue recognition (ASC 606 / IFRS 15 compatible)
  • Multi-currency and tax per region
  • Settlement files to ERP
  • Daily, monthly, and real-time ledger exports
APIs & extensibility
  • REST and GraphQL
  • Webhook events for every lifecycle transition
  • SDKs for apps and servers
  • Headless checkout and pricing

Key Takeaways

  • Unified engine for SVOD, AVOD, TVOD, PPV, and hybrid bundles
  • Integrated ad server with VAST 4.2, SSAI, and header bidding
  • Real-time entitlement with concurrency, geo, and window enforcement
  • Pluggable payment gateways, DCB, and in-app purchase reconciliation
  • Pricing, bundles, and promotions changed without engineering releases
  • One ledger feeding finance, BI, and analytics from the same events

Frequently Asked Questions

Do we have to run all monetization models on Vucos at once?
No. Most operators start with a single model — typically SVOD or AVOD — and layer in TVOD, PPV, or hybrid tiers later. The engine is designed so additional models are configuration work, not a re-platforming project.
Can we keep our existing billing or ad server?
Yes. The engine is modular. You can use Vucos subscription management with an external ad server, or Vucos ad server with an external billing platform. Integrations are API-first and webhook-driven, so replacing or coexisting with an incumbent is straightforward.
How does entitlement enforcement work across devices?
Every playback, download, and cast action calls an entitlement endpoint that evaluates the subscriber's plan, active session count, device class, geography, and the content window in under 100 ms. The result is cached briefly at the player and revalidated on heartbeat and on session changes.
How do you handle in-app purchase reconciliation for Apple and Google?
The engine ingests Apple App Store Server Notifications and Google Real-time Developer Notifications, reconciles them against internal entitlement state, and handles edge cases like grace periods, billing retry, and family sharing. Revenue is booked net of store fees with configurable rules.
Can product managers change pricing without engineering?
Yes. Pricing, bundles, promotions, and regional variants live in a configuration surface with audit logging and scheduled rollouts. Engineering is involved only when a genuinely new capability is needed — not for routine price or packaging changes.
Is the ad server suitable for high-concurrency live events?
Yes. The ad server supports server-side ad insertion with pre-stitched ad pods for live, low-latency decisioning for linear break boundaries, and frequency capping at millions of concurrent sessions. It integrates with external SSPs through OpenRTB for additional demand.

Related

Ready to learn more?

Talk to an architect about how this fits your deployment.