Installation or instant launch
Run Callaba Engine in the cloud or on your own Linux infrastructure. Both options provide the same live-video features and API.
Choose this whenYou need a new Engine instance: cloud for speed, self-hosted for infrastructure and data control.
Use another module whenUse General settings when the Engine already runs and only instance-wide configuration must change.
Before you start
You need administrative access to the target environment, a hostname or reachable IP address, and the network ports required by your media workflow. After deployment, sign in to the dashboard and generate an API token in General settings.
What you can do
- Provision an instance with enough CPU, memory, network capacity, and storage for the expected workload.
- Configure DNS, HTTPS, firewall rules, and media ports.
- Open the dashboard and confirm the instance is reachable.
- Create the API token and test a protected read request.
Example workflow
- Deploy the current Callaba Engine release on a supported Linux host.
- Point a hostname to the instance and enable HTTPS.
- Allow only the control and media ports the planned workflow needs.
- Create an SRT or RTMP server and validate an ingest feed.
Common use cases
- Launch a temporary cloud contribution hub for a live event.
- Install an on-premises gateway beside studio or venue equipment.
- Deploy a regional instance close to publishers and viewers.
Limits and troubleshooting
Most first-run failures come from DNS, certificates, firewall rules, unavailable ports, or insufficient host resources. Validate reachability before debugging an API request. Capacity depends on codecs, resolutions, transcoding, recording, and concurrent streams rather than instance count alone.
Next steps
Complete Authorization, then configure the ingest module required by your first workflow.