Hosted transcoding

Brutus Cloud

IPTV, OTT and FAST channels with nothing to install

SRT, RTMP or HLS in; H.264, H.265 or AV1 at several resolutions out to SRT, RTMP, HLS and DASH at once, for every channel in your lineup. It is the Brutus engine as a managed, elastic service, with hosting and bandwidth included in the price.

  • SRT
  • RTMP
  • HLS
  • DASH
  • H.264
  • H.265
  • AV1
  • SCTE-35
Brutus Cloud dashboard with an ABR ladder and a delivery map, illustrationBRUTUS CLOUDLIVEABR LADDERNEWS HD1080pH.2651080pH.264720pH.264540pH.264360pH.264DELIVERYORIGINOUTPUTSHLSDASHSRTUDP MULTICASTSCTE-35DRMWIDEVINEFAIRPLAYPLAYREADYFAILOVER READY
outputs at once from one ingest: SRT, RTMP, HLS, DASH
4
video codecs out: H.264, H.265, AV1
3
closed captions passed through
608/708

Overview

Brutus without the hardware

Brutus Cloud is the Brutus transcoding engine under a managed, elastic deployment model. The capability is the same and there is nothing to install: live ingest, multi-bitrate transcoding, SCTE-35 ad markers, DRM, captions, recording for catch-up TV and VOD packaging.

It is built for three jobs: live events that need multi-destination restreaming without a rack of encoders on site, FAST channels where SCTE-35 accuracy and multi-bitrate output carry monetization and reach, and OTT channel distribution where live and VOD share one delivery path.

Capacity follows the workload. Brutus Cloud allocates GPU and CPU resources as channels start and releases them when traffic falls, and redundant nodes keep a single node failure from taking a channel down.

Where it fits

How a channel moves through Brutus Cloud

One ingest, several outputs, with recording and ad signaling on the way through.

Brutus Cloud: a live channel arrives over SRT, RTMP or HLS, or as MP4 files for VOD, through input failover; hosted Brutus Cloud transcodes to H.264, H.265 or AV1 at several resolutions in one pass, writes SCTE-35 cues into the manifest and applies DRM, records live channels for catch-up and rewind, and restreams SRT, RTMP, HLS and DASH at the same time to a CDN, a social platform and a partner.BRUTUS CLOUD, HOSTED1INGESTSRTMP4WEB UI, APILive channelSRT, RTMP, HLSVOD filesMP4IngestInput failover2TRANSCODEBrutus CloudH.264, H.265, AV13MARK AND PROTECTABRSCTE-35, DRMCues in themanifest4RECORDRecordCatch-up,rewind5RESTREAMCATCH-UPHLS, DASHRTMPSRTCDNHLS, DASHSocial platformRTMPPartnerSRTIPDELIVERY, CLOUDFILESDVEO PRODUCTTHIRD PARTY
A live feed enters over SRT, RTMP or HLS, is transcoded to several resolutions, marked for ads and protected, recorded for catch-up, and restreamed to CDNs, platforms and partners. See it in the OTT delivery and playout and FAST workflows.
  1. Stage 1: Ingest

    Live channels over SRT, RTMP or HLS; MP4 files for VOD.

  2. Stage 2: Transcode

    H.264, H.265 or AV1 at several resolutions in one pass, with captions and subtitles carried through.

  3. Stage 3: Mark and protect

    SCTE-35 splice_insert and time_signal cues written into the manifest, DRM applied inline.

  4. Stage 4: Record

    Live channels record as they run, which backs catch-up and rewind TV.

  5. Stage 5: Restream

    SRT, RTMP, HLS and DASH at the same time, to a CDN, a social platform and a partner.

Features

What runs in the pipeline

Every live channel in Brutus Cloud gets the same processing chain.

Multi-destination restream
One ingest feeds SRT, RTMP, HLS and DASH outputs at once, so a CDN, a platform and a partner need no separate encode jobs.
Multi-resolution transcode
H.264, H.265 or AV1 across several resolutions in one pass: a legacy-compatible feed and an ABR ladder from one source.
SCTE-35 in the manifest
splice_insert and time_signal cues land in HLS and DASH manifests or the UDP output, where the ad decision server expects them.
Inline DRM
Encryption runs in the transcoding path, for titles whose license requires encryption at the point of transcode.
Captions kept
608/708 closed captions, DVB subtitles and teletext pass through the transcode.
Catch-up and rewind
Live channels record as they run, with no separate recording workflow.
VOD packaging
MP4 uploads convert to HLS and DASH, the same formats as the live side.
Input failover
A backup input keeps the channel running when the source goes down.
API access
Set up and control channels from your own systems.

Options

Two ways to run Brutus Cloud

Run your channels yourself, or have the team that builds Brutus run them for you.

  • Quote only
    Brutus Cloud dashboard with an ABR ladder and a delivery map, illustrationABR LADDERNEWS HD1080pH.2651080pH.264720pH.264540pH.264360pH.264DELIVERYORIGINOUTPUTSHLSDASHSRTUDP MULTICASTSCTE-35DRMWIDEVINEFAIRPLAYPLAYREADYFAILOVER READYBRUTUS CLOUD

    Brutus Cloud, self-managed

    You configure and run your channels

    Price on requestSend inputs, outputs, codecs and channel count for a quote.

    • Hosting and bandwidth included
    • Elastic GPU and CPU capacity
    • API access for your own tools
  • Quote only
    Brutus Cloud dashboard with an ABR ladder and a delivery map, illustrationABR LADDERNEWS HD1080pH.2651080pH.264720pH.264540pH.264360pH.264DELIVERYORIGINOUTPUTSHLSDASHSRTUDP MULTICASTSCTE-35DRMWIDEVINEFAIRPLAYPLAYREADYFAILOVER READYBRUTUS CLOUD

    Brutus Cloud, operated by DVEO

    DVEO runs the channels for you

    Price on requestSend inputs, outputs, codecs and channel count for a quote.

    • Run by the team that builds and runs Brutus
    • Little more than the self-managed price
    • Same features and outputs

Request a quote

What to send for a quote

Send these details with your request so DVEO can price your lineup with hosting and bandwidth included.

  1. Step 1: Channels and inputs

    How many live channels, the ingest protocol for each (SRT, RTMP or HLS), and any MP4 VOD library.

  2. Step 2: Outputs and protocols

    Destinations and protocols: SRT, RTMP, HLS or DASH to CDNs, platforms and partners.

  3. Step 3: Codecs and resolutions

    H.264, H.265 or AV1, and the resolutions in each ladder.

  4. Step 4: DRM and ad insertion

    DRM requirements and the SCTE-35 markers your ad decision server expects.

  5. Step 5: Delivery formats

    Catch-up and rewind windows, VOD packaging and caption or subtitle needs.

  6. Step 6: Operation and timeline

    Self-managed or operated by DVEO, and your launch date.

Specifications

Brutus Cloud specifications

Inputs

IP input typesUDP unicast, UDP multicast, RTSP, RTMP (pull and push), SRT, HLS
Live ingestSRT, RTMP, HLS
VODMP4 upload
FailoverInput failover when the source is down

Outputs

IP output typesUDP unicast, UDP multicast, RTSP, RTMP (pull and push), SRT, HLS, DASH
RestreamingSRT, RTMP, HLS and DASH at the same time
RecordingCatch-up and rewind TV from live channels

Video

InputMPEG-2, H.264, H.265
EncodeH.264, H.265, AV1, several resolutions in one pass
Captions608/708 closed captions passed through
SubtitlesDVB subtitles, teletext

Audio

InputMPEG-2 audio, AAC, AC3
EncodeAAC, AC3, MPEG-2 audio

Transport and protocols

Transport streamsSPTS and MPTS
SCTE-35splice_insert and time_signal into HLS and DASH manifests, or the UDP output
DRMInline in the transcoding path

Control and management

APIAPI access for integration
ScalingElastic GPU and CPU allocation, redundant nodes
RegionsData centers in the Americas and Europe
OperationSelf-managed or operated by DVEO
PricingHosting and bandwidth included

Need SDI or RF input, or MPEG-2 output? Those run on Brutus on DVEO hardware.

FAQ

Brutus Cloud questions

It runs the same transcoding engine. Brutus runs on DVEO hardware you install; Brutus Cloud runs it as a managed, elastic service, so you provision channels instead of servers. SDI and RF inputs and MPEG-2 output need Brutus on site.

Hosting and bandwidth are included, and the management layer is part of the same price. Having DVEO operate the service costs little more than running it yourself. Ask for a quote for your channel lineup.

Yes. Brutus Cloud restreams one SRT, RTMP or HLS ingest to SRT, RTMP, HLS and DASH outputs at the same time.

Yes. SCTE-35 splice_insert and time_signal cues are written into the manifest, and closed captions and subtitles pass through the transcode.

Yes. Upload MP4 files and Brutus Cloud converts them to HLS and DASH. Live channels also record as they run, for catch-up and rewind TV.

Brutus Cloud lists input failover: a backup input keeps the channel running when the primary source goes down. For contribution redundancy, send two feeds from two encoders on separate uplinks.

On GPU-accelerated nodes in data centers in the Americas and Europe, with redundancy so streams can move between servers or regions.

After the sale

How support works

  • One-year warranty

    Every DVEO product carries a one-year warranty.

  • DVCare, 1 to 4 years

    Extended warranty with priority phone and email support, advance replacement units shipped within 24 hours and firmware notifications with release notes.

  • Repairs and RMA

    Email rma@dveo.com (or info@dveo.com) for an RMA number and ship the unit to San Diego. Repairs usually come back within a week unless parts are short.

  • Spare parts

    Spare parts are available for DVEO products. Ask for the part with the model and serial number.

Map Brutus Cloud to your channel lineup

Tell us how many channels, which inputs and which outputs, and DVEO prices it with hosting and bandwidth included.