Adaptive transcoding
H.264, HEVC and AV1 ladders generated on demand, tuned per-title to keep bitrate low and quality high.
DVPN ingests your sources once and runs transcoding, packaging and delivery on regional edge nodes close to your viewers — behind a single, predictable API.
Ingest, transcode, package and deliver — without stitching together half a dozen services. DVPN handles the heavy lifting per region.
H.264, HEVC and AV1 ladders generated on demand, tuned per-title to keep bitrate low and quality high.
CMAF output with low-latency segments, captions and DRM hooks — ready to play on any device.
Renditions cached and served from the regional node nearest the request, with origin shielding.
Per-session signed URLs and token expiry keep your catalog protected at the edge.
Per-region job throughput, QoE and egress, streamed to the console or your own webhook.
REST + webhooks, idempotent jobs and an OpenAPI spec. Drop it into your existing pipeline.
You point us at a source and pick a region. We do the rest, close to your audience.
Send a source URL and target region to api.dvpn.info. Jobs are idempotent and queued instantly.
The regional node builds your rendition ladder and packages CMAF segments.
Outputs are stored on the node and shielded so your origin is hit at most once.
Viewers stream from the nearest node over signed, low-latency URLs.
Each region runs an independent processing node under
<region>.dvpn.info, exposing its own API console for jobs and diagnostics.
Each node terminates TLS on its own hostname and serves its regional
console at https://<region>.dvpn.info. New regions follow the same
<region><number> naming scheme.
No per-seat fees. Usage is metered per region by processing minutes and egress.
For prototypes and small catalogs.
For products shipping to real viewers.
Dedicated capacity and SLAs.
HLS and DASH over CMAF, with H.264, HEVC and AV1 ladders. Captions (WebVTT) and standard DRM hooks are supported.
Each region is an independent edge node addressed as <region>.dvpn.info. You pick a region per job; delivery is served from the node closest to the viewer.
Yes. Point a job at any reachable HTTP(S) source. Origin shielding ensures your source is fetched at most once per rendition.
The full REST API ships with an OpenAPI document and webhook signatures. Jobs are idempotent by key.