Deploy the live RTMP/SRT ingest and restream template with OpenTofu
Deployment · Updated Jun 2026
Coming from another cloud?
▸AWS·IVS
This Quake AI feature maps to AWS’s IVS.
▸Google Cloud·Live Stream
This Quake AI feature maps to Google Cloud’s Live Stream.
Deploy the live RTMP/SRT ingest and restream template with OpenTofu
Stand up a CPU ingest VM that accepts an RTMP push and fans out to downstream RTMP endpoints using the validated OpenTofu templatelive-ingest-restream. The template provisions NGINX-RTMP or SRS on CPU only; multi-rung ABR ladders are bounded on CPU, so prefer pass-through restream where possible.
Monthly total for the required template above. Use the configurator below to add optional pieces and see the total update.
What each resource is for
Ingest
c2a.large · 2 dedicated vCPU, 4 GiB RAM, 0.5 Gbps
$62.00/mo
Compute shown per role at custom-package rates ($29/dedicated vCPU, $7.25/shared vCPU, $1/GiB RAM). The headline above is the billed total: the cheaper of a named plan and the custom package, plus add-ons.
Private networks, subnets, Neutron routers, and security groups are included with the plan.
VPC objects are usually free to create elsewhere, but NAT gateways bill hourly plus per-GB processed. Quake AI uses router SNAT with no separate NAT line item.
$0.00
Control-plane API requests
OpenStack API calls for provisioning and management are included.
Some managed services on other clouds meter API calls or charge for premium control-plane features.
$0.00
Dev/test vs production
Start on shared CPU for dev/test, then promote to dedicated for production with a flavor resize. The network, storage, and template stay the same.
Dev/test on shared CPU
Burstable s1a flavors; suited to prototyping and low or bursty load.
$14.70/mo
Production on dedicated CPU
The headline estimate above; predictable steady-load performance.
$60.20/mo
Saves $45.50/mo while you build on shared CPU.
Shared flavors carry less RAM (c2a.large (4 GiB RAM) -> s1a.small (2 GiB RAM)). A resize reboots the instance; data on attached volumes persists. Size the dedicated flavor for the RAM your production workload needs.
Pricing data last validated: . For current rates, check quake.ai/pricing.
Click to zoom
Live ingest topology: one floating IP accepts RTMP from your encoder; the ingest VM restreams to downstream platforms
Replace CIDR values with your studio egress IP. Defaults for ingest_server, ingest_flavor, and HLS replay options are documented on the Live RTMP/SRT ingest and restream reference page.
Type yes when prompted. Provisioning takes a few minutes while cloud-init installs the ingest software.
When the run finishes, note rtmp_publish_url and ingest_floating_ip from the outputs. Append your stream_key to the URL when you set one in terraform.tfvars.