Architecture

Built in Rust. Owned end to end.

From the API gateway to the egress network, every layer of the pipeline is ours: no rented proxies, no third-party downloaders, no intermediate storage. This page is the honest tour.

400+ TBdaily throughput

500+worker nodes

38.4 Gbpsmeasured network peak

AS200546our own network (ASN)

<0.002%failure rate

Life of a job

The API answers with a job_id instantly. Everything after that is asynchronous, monitored and retried until the file is confirmed in your storage.

POST /jobsValidated, deduplicated, answered in ~38 ms with a job_id

queueRedis-backed, at-least-once, 90-second worker heartbeats

downloadCascade across owned ingress routes, blocks rerouted live

muxFFmpeg on the worker: consistent MP4/MKV, clean metadata

uploadMultipart, direct to your bucket, no intermediate storage

webhookFired only once the file is confirmed in storage

The four layers

01API & scheduling

A Rust gateway validates and deduplicates requests, then schedules jobs onto the fleet. Crashed jobs are detected by heartbeat and rescheduled in seconds: at-least-once delivery, idempotent by design.

Rustp95 84 msidempotent retries

02Ingress network

A dedicated network we own and operate, IPv4 and IPv6 pools with managed rotation. An automatic feedback loop reroutes around blocks in real time, so they never reach your jobs.

AS200546owned IP poolsauto rerouting0.4% block rate

03Processing

500+ worker nodes download, verify and mux with FFmpeg. Output is normalized: consistent containers, clean metadata, original quality up to 4K.

500+ nodesFFmpegup to 4K

04Delivery & security

Multipart uploads stream directly to your bucket: S3, GCS, Azure, R2, OSS, Drive or Tornado-hosted R2. Credentials are encrypted at rest in Key Vault, scoped per bucket, never logged.

6 providerszero egressKey Vault

The anti-bot layer is the part we don't document publicly. Full architecture details, including the ingress network design, are shared on founder calls under NDA.