These docs are a work in progress. Some pages may be incomplete or change as we get ready for launch.

Servers and destinations

The server dialog is where you tell CeraLive where to send your stream. Open it from the Live screen by tapping the server card. Everything here is about the destination: where the video goes, how it gets there, and what address it connects to.

You can’t change these settings while a stream is running. If you need to switch destinations, stop the stream first.

Choosing a destination

The dialog opens with a destination choice. There are two options.

My cloud account (managed relay)

If you’ve paired your device with a CeraLive Cloud account (or another supported managed cloud), this option connects your stream to a relay server that your account controls. You pick the server from a list; CeraLive handles the connection details automatically.

This is the recommended path for most setups. The relay list comes from your cloud account, so the servers shown are the ones you actually have access to. If the list is empty or still loading, the option is greyed out until it populates.

See Cloud for how to pair your device and set up a managed account.

Custom receiver

This option lets you enter a server address manually. Use it when you’re connecting to your own SRTLA receiver, a self-hosted relay, or any endpoint that isn’t part of a managed cloud account.

The custom receiver path is always available, regardless of whether you’re paired to a managed cloud.

Adding a custom endpoint

When you select Custom receiver, a form appears with the fields you need to fill in.

Server address

The hostname or IP address of your receiver. This is where CeraLive will send the stream.

Examples: relay.example.com, 203.0.113.42

Port

The UDP port your receiver is listening on. Your receiver operator will give you this number. The valid range is 1 to 65535.

Stream ID (optional)

Some receivers use a stream ID to route your connection to the right channel or account. If your receiver requires one, enter it here. If it doesn’t, leave this field blank.

Passphrase (optional)

If your receiver is configured with a passphrase for encryption, enter it here. Leave it blank if your receiver doesn’t use one.

Validating a custom endpoint

After filling in the address and port, tap Validate to test the connection before saving. CeraLive runs through a series of checks:

Input — confirms the address and port are in a valid format
Protocol — checks that the transport is supported
Endpoint — verifies the address resolves
DNS — confirms the hostname can be looked up
Probe — attempts a real connection to the receiver

Each stage shows its result as it completes. If a stage fails, the label turns red and shows which step stopped. You can still save without validating, but validating first saves you from discovering a typo after you’ve started a stream.

SRT latency

Below the destination and endpoint fields, there’s a latency slider. This controls the buffer size for the SRT transport.

Higher latency = more stable, more delay. A larger buffer gives the protocol more room to recover from packet loss and network jitter. If your connection is unreliable or high-latency (satellite, long-distance cellular), increase this value.

Lower latency = less delay, less tolerance for disruption. A smaller buffer reduces the end-to-end delay but leaves less room for the network to recover. Use lower values on stable, low-latency connections.

The slider shows the current value in milliseconds. The label on the left marks the lower end (less delay), and the label on the right marks the upper end (more stable). The default is a reasonable middle ground for most cellular bonding setups.

Transport options

The Transport section shows how your stream reaches the receiver. For most setups you won’t need to change this, but it’s worth understanding what the options mean.

SRTLA (default)

SRTLA is the bonded transport. It splits your stream across all your active network links simultaneously and reassembles them at the receiver. This is what makes CeraLive resilient: if one link drops, the others keep the stream alive.

When SRTLA is active, the transport badge shows whether you’re bonded across multiple links or running on a single link. Bonded is the normal state when you have more than one network interface active.

RIST

RIST is an alternative single-link transport. It’s available when your receiver supports it and your device’s engine advertises RIST capability. If RIST isn’t available on your setup, the option appears greyed out with a note explaining why.

RIST doesn’t bond across multiple links the way SRTLA does.

Changing the transport

Tap Advanced under the transport badge to expand the protocol selector. The options shown reflect what your device and receiver actually support. Unsupported options appear disabled with a reason, not hidden.

Managed relay options

When you’re using a managed cloud account, the server section shows a relay server picker instead of the manual address form.

Server — the relay server you want to connect to. The list comes from your cloud account. If you’re paired to more than one managed cloud, a provider picker appears above the server list so you can choose which cloud’s servers to show.

Account — some relay setups associate your stream with a specific account or channel. If your relay requires this, select it here.

Stream ID override — if you need to override the stream ID that your relay normally assigns, you can enter a custom value here. Most users won’t need this.

If you need to connect to a specific address instead of the one your relay server normally uses, tap the override option to enter a custom host and port. Note that using a manual override clears the relay server association when you save.

Hosted receiver

CeraLive Cloud includes a hosted receiver option that handles the server side for you. Instead of running your own SRTLA receiver, you connect to a receiver that CeraLive manages. Your stream arrives at the receiver and is available for the platform to distribute.

For details on setting up a hosted receiver and connecting it to your account, see Cloud.

Going live

Once you’ve saved your server settings, go back to the Live screen. The Start button becomes active when you have both a video source and a server destination configured.

If something isn’t set up yet, the Live screen shows a hint pointing to what’s missing. Fix it, come back, and tap Start.

See Go live for the full first-stream walkthrough.