Broadcasters and live platforms
Teams planning peak capacity, origin protection and operational support for sports, concerts or channels, with ownership of encoder configuration, playback and event rehearsals.
mainstreaming.com · Italy
MainStreaming delivers live and on-demand video for broadcasters, OTT services and network operators. It offers public, private and hybrid edge deployments alongside origin protection, anti-piracy, playback analytics and media management. Services are quoted per project, with a two-week trial available by request.
MainStreaming was co-founded in 2016 by Antonio G. Corrado, Philippe Tripodi and Giovanni Proscia and is headquartered in Milan, Italy. It builds live and on-demand video delivery infrastructure for broadcasters, OTT platforms and internet service providers, bringing delivery capabilities closer to viewers through infrastructure at the network edge.
Venture investment has supported its development. In 2019, MainStreaming raised a round led by Indaco Venture Partners with participation from Sony Innovation Fund and United Ventures. It closed another investment round in September 2025 with United Ventures and Indaco funds, supporting technical development and market expansion. Milan remains the location of its research and development centre.
The operating company is MainStreaming S.p.A., whose headquarters and registered address are at Viale Sarca 336/F in Milan. Subsidiaries maintain offices in London, San Francisco and Munich. MainStreaming continues to provide managed video delivery for professional media services; ITV selected it in 2026 as part of the multi-CDN delivery strategy for ITVX.
The Intelligent Media Delivery Platform (IMDP) brings together live and on-demand delivery, edge orchestration, media management and analytics. Public Edge uses MainStreaming’s existing network; Private Edge allocates dedicated capacity around a service’s audience and ISP relationships. Hybrid deployments combine a private footprint with ready public capacity for new regions or event peaks.
MainStreaming manages private deployments and coordinates ISP integration, placing dedicated capacity within access networks or making it available through peering. A proposal should specify audience regions, target ISPs, concurrency, bitrates and headroom for peaks, together with delivery scope, data location and service commitments for each target market.
Media Manager provides upload, transcoding, library management, publishing and player embeds, while REST APIs connect those tasks to an existing content system. Live workflows accept an encoder feed and produce HLS or DASH using the selected configuration. The technical guide lists RTMP, SRT and MPEG-TS inputs; teams should validate the chosen protocol, redundancy and player combination during integration.
On-demand workflows can create multiple renditions in H.264, H.265 or AV1, then distribute them through HLS, DASH or progressive download. Live content can also be recorded for replay and clipped. Encoding profiles, retention of source files and recordings, and processing charges belong in the project scope. Media Manager administration uses desktop browsers; viewer compatibility depends on the actual codecs, packaging and player.
Origin Shield sits between an origin and one or more CDNs to consolidate origin requests. It addresses live traffic surges and repeated reads of on-demand content, with caching storage available for VOD. This suits teams retaining an existing origin while delivering through several networks.
EdgeGuard detects suspicious access, credential sharing and proxy-related behaviour at the delivery layer. It can consume existing allowlists and blocklists and apply configured tracking, blocking, throttling or quality changes. These delivery controls should be planned alongside content rights, DRM, authentication and procedures for handling legitimate viewers affected by a rule.
The analytics suite covers requests, traffic, cache performance and response metrics, with breakdowns by content, device, geography and ISP. CMCD-Powered QoE Analytics connects client playback data with delivery performance to investigate buffering and bitrate changes across networks. Player reporting, available metrics, retention and exports should be included in the integration plan.
MainStreaming builds video-delivery offers for businesses using public, private or hybrid edge deployments. Private Edge pricing is based on agreed delivery capacity, expressed in Gbps or Tbps. A hybrid deployment can combine dedicated capacity with the public network, with separate volume charges for overflow as agreed. Audience locations, live-event peaks and on-demand traffic help define the capacity and service scope for a quote.
Businesses can apply for two weeks of free access to all iMDP features. Confirm activation, traffic or capacity allowances and what happens at the end when arranging the trial. Trial services are provided as is and may be changed, suspended or ended; this is not a permanent free plan.
Purchases are arranged with the business team; the website does not take direct purchases or payments. Agree payment methods, invoice terms, minimum commitments, currency and taxes before signing. For deployments across regions, also specify service territories, available capacity and the contracting and invoicing entities.
Agree the service term, renewal, early termination, refunds and content-export arrangements in the service agreement before signing.
Teams planning peak capacity, origin protection and operational support for sports, concerts or channels, with ownership of encoder configuration, playback and event rehearsals.
Services considering dedicated capacity in their main networks while using public capacity for expansion or peaks, and comparing that investment against ongoing volume charges.
Network operators bringing video delivery closer to subscribers and coordinating interconnection, dedicated capacity and operating responsibilities with content providers.
Businesses combining upload, transcoding, live recordings, media libraries and API automation, with a defined scope for features, retention and support.
For a major live event, map the audience’s networks, expected concurrency and bitrate before comparing public volume, dedicated capacity and hybrid delivery. Rehearse redundant ingest, origin failures, playback and anti-piracy rules, and agree how temporary expansion and capacity overruns are handled.
Explore products by use case: what they do, how to use them and whether they are billed separately.
Orchestrates and delivers live streams and video libraries through public, private or hybrid deployments. Regions, capacity, origin integration and peak expansion are defined per project.
Consolidates origin requests for live and VOD workflows using one or several CDNs. VOD deployments can add caching storage; capacity, storage and integration are included in the proposal.
Uses suspicious-access detection, lists and APIs to configure tracking, blocking, throttling or quality policies at the delivery layer. Enablement and policy scope are agreed for the project.
Correlates CMCD player data with delivery metrics to investigate buffering, bitrate, regional and ISP trends. Requires suitable player reporting and agreed metrics, retention and export arrangements.
Supports VOD rendition workflows and live ingest, transcoding, HLS/DASH output and recordings. Confirm protocols, codecs, processing capacity and charges in the integration proposal.
Upload, organise, clip and publish videos through desktop administration or integrate the workflow with REST APIs. Features and storage scope depend on the service configuration.
Video services using shared capacity or handling demand peaks
Request a public-edge offer for the workload. The order defines traffic measurement, regions, commitments and peak-demand charges.
Broadcasters and OTT teams planning dedicated capacity for sustained traffic
Commercial arrangements are built around agreed delivery capacity in Gbps or Tbps. Deployment and operating commitments follow the project.
Teams combining dedicated regional capacity with public-network flexibility
Dedicated capacity and public delivery are combined, with separate agreed measurement and charges for the baseline, public usage and peak overflow.
| Product | Allowance / base fee | Usage prices |
|---|---|---|
| Private edge delivery capacity | Agreed capacity in Gbps/Tbps;deployment, service term and expansion conditions follow the project. | Custom quote |
| Public delivery and peak overflow | Volume and overflow scope follow the order;a capacity commitment does not include unlimited public traffic. | Custom quote |
Ask for a quote that separates committed capacity, public-network usage and peak overflow, with the selected origin protection, security, analytics, transcoding and support scope. Recurring charges, volume rates, commitments and taxes are set in the order. Private deployments can use a project-specific capital or operating expenditure model.
Public, private and hybrid deployments can be combined with origin protection and playback analytics to suit an existing video workflow.
Allow time for capacity planning and a commercial proposal. Separate public traffic, dedicated capacity, overflow, storage, transcoding and support charges, then agree regions, protocol and player compatibility, the SLA and anti-piracy policies. The two-week trial helps assess integration; production scope and payment terms require a separate agreement.
Explore MainStreaming products, use cases and buying advice