Custom RTMP destinations: streaming to the long tail

Not every audience lives on YouTube, Twitch, or Facebook. A client portal, niche community, event platform, or private player may give you an RTMP URL and a stream key instead of a native connection. Custom RTMP is for those destinations: send the same master feed to an endpoint that is not already listed in the dashboard.

What the destination gives you

The receiving service normally supplies two values:

• an RTMP server URL, such as rtmp://live.example.com/app;
• a private Stream Key that identifies the live event.

The URL is the address. The key is the credential. Keep them together in a secure note while you configure the connection, and do not paste the key into a public message or screenshot.

Add it with a useful name

In ApexStream, open Add Connection and select Custom RTMP. Enter the URL and stream key, then choose a Friendly Name. Use a name that tells you where the feed is going: “Client portal,” “Partner event page,” or “Acme private stream” is much safer than “Custom 1.”

The Friendly Name appears with the destination controls on your dashboard. When a show has several endpoints, that label is your final check before you toggle a feed on.

Count the destination before the show

Custom RTMP connections use the same simultaneous-destination allowance as native channels. The plan limits in the source workflow are:

• Free: 2 destinations.
• Hobby: 3 destinations.
• Creator: 5 destinations.
• Scale: 8 destinations.
• Enterprise: up to 50 destinations.

If YouTube already uses one slot on Free, only one custom RTMP feed remains. Count every destination you plan to activate, including a client endpoint that is used only for a private rehearsal.

When custom RTMP is the right fit

Use it when the receiving service can accept an RTMP URL and key but does not have a native ApexStream integration. That may be a private event player, specialized community, enterprise video system, or a platform that has not been added as a button yet.

Custom RTMP is also useful when the audience needs to stay inside a client-owned environment. You can keep the same production in Web Studio or OBS while sending a copy to the place where the viewers already have access.

It is not a way to create a destination that has no functioning ingest endpoint. The receiving service still needs to provide a valid URL, key, and instructions for starting its event.

Know what you cannot see

Native integrations may return health information, chat, or other platform data to ApexStream. A custom RTMP endpoint may not send that information back. ApexStream can push the feed, but it may not know whether the receiving player is buffering or whether viewers can see it.

For that reason, monitor the custom destination directly during the test. Open its player or admin view, confirm that the event is receiving video, and ask someone on the destination side to check playback if the stream matters to a client.

A safe custom-destination routine

1. Ask the receiving service for a fresh URL, key, and event instructions.
2. Add the connection and give it a specific Friendly Name.
3. Check that the destination count fits your plan.
4. Send a short test feed and inspect the receiving player directly.
5. Activate the connection only after you know which dashboard toggle controls it.

Custom RTMP extends the places your show can go, but it also makes you responsible for checking the far end. Treat the URL, key, name, and destination count as part of the same pre-flight checklist.