When your player cannot reach your computer directly, a compatible relay can forward the connection. You can configure your own TURN service in Beebo. This guide shows the existing Cloudflare setup route and the standard shared-secret option. External account costs and terms are separate from Beebo. Privacy depends on the actual route; check costs before enabling a fallback.
A direct connection can work without a relay. Some networks use shared public addresses, restrictive firewalls or other policies that prevent it. The result depends on both the home network and the player’s current connection; no fixed percentage of households is promised.
Find out first: run Will Beebo work on your internet? with your home computer and your phone. If it says you connect directly, you don’t need a relay. If it says a relay is needed, or you sometimes can’t connect from one particular place, carry on below.
You’ll create a Cloudflare account, review its service and billing terms, make a TURN key (TURN is the technical name for this kind of relay), and paste two values into Beebo. Cloudflare sometimes renames menus. If something looks different, follow Cloudflare’s official TURN guide.
Go to dash.cloudflare.com/sign-up, enter your email and a password, and select Create Account. Cloudflare emails you a link to verify your address, so open it. You don’t need a website or domain name for this. (Cloudflare’s account guide)
This is your provider account. Review its included allowance, charges and any payment-method requirement. Create that account with the provider directly; enter only the required TURN credentials in Beebo, not your provider account password.
In the Cloudflare dashboard, find the Realtime section (it used to be called Calls) and choose TURN Server. Cloudflare’s docs link here, and it should take you to the right place once you’re signed in: open Realtime in the dashboard.
Select Create and give the key a name you’ll recognise, such as Beebo. The name is just a label for you. A TURN key is a long-lived secret that lets your Beebo PC make short-lived passes for your viewers. (Cloudflare: generate credentials)
Cloudflare shows two values for the new key. The labels may differ slightly:
Copy both straight away, because the token may not be shown again. If you lose it, just create a new key. This token belongs to the TURN key. It isn’t an account-wide Cloudflare API token, and you don’t need to make one of those.
Treat the token like a password. Anyone who has it could run up relay usage on your account. Don’t email it or post it anywhere.
On your home PC, open Beebo and go to Settings → Away from home → Use my own relay. Choose Cloudflare, paste the key ID and the API token, and save.
The computer stores the long-lived TURN credentials and uses them to request short-lived relay credentials from the provider. The viewing device receives the short-lived credentials for the connection, rather than your long-lived API token.
Turn off Wi-Fi on your phone so it uses mobile data, then open your yourname.beebo.tv address and play something. Ideally, try from the place that wouldn’t connect before. Remember, Beebo only uses the relay when it has to, so a working direct connection is still the normal result.
Good habit: set a spending alert in Cloudflare under Manage Account → Billing → Billable Usage → Create budget alert. It emails you if your usage-based spend passes an amount you choose. Alerts only notify you and don’t switch anything off. (Cloudflare budget alerts)
When your home computer and player are the endpoints of the encrypted WebRTC transport, the TURN server forwards encrypted payloads without terminating that transport. This statement applies to that route; it is not a claim that every Beebo request uses it.
A TURN provider can process IP addresses, ports, connection times and traffic volume. Account coordination, sign-in, metadata lookup and other internet features have their own data flows outside the media transport.
A reverse proxy or other relayed HTTP route can have different encryption endpoints. An HTTPS label alone does not mean every intermediary is unable to read content. Check which route you selected and review Beebo’s privacy policy.
The external provider’s own terms apply. Read its TURN FAQ, connection analytics documentation and privacy policy.
Beebo Relay has been used successfully in owner testing. Account coverage, final limits and paid activation are still being verified. Its paid plans are Planned and not available to buy yet. They are not a checkout or a guarantee that every account is ready. See current pricing status and testing evidence.
Connection settings offer different relay preferences. A preference is not proof that the selected fallback worked on your network; test it from outside your home.
Beebo services process account, connection and usage information needed for access and operations. The media or proxy path determines where encryption ends. Do not assume that every managed route has the same visibility as a TURN-only WebRTC transport. See the privacy policy and data-flow guide.
Beebo does not add a managed-relay charge merely because you configured your own compatible relay. Your provider can charge for its account, traffic or server. The owner sets capacity based on the actual connection and equipment. Account discovery and sign-in on these routes are still undergoing end-to-end validation.
Check the provider’s current account allowance, billing currency, traffic accounting and overage charges before creating credentials. A free allowance is not a spending cap. Budget alerts notify you but do not necessarily stop usage. This page does not promise that a particular household stays within an external free tier.
Read the TURN provider’s pricing and inspect your account’s usage dashboard.
The planned Relay plans are separate from video quality, household profile count and data transferred. Final limits, currency, taxes and cancellation terms must be shown before paid activation. See pricing.
To estimate traffic, a continuous 1 Mbps stream uses about 0.45 decimal GB per hour before protocol overhead and retries. Use the actual source or converted bitrate, including audio. See Beebo’s conversion-profile examples. Traffic estimates are not a bill or a speed guarantee.
A reverse-proxy tunnel can terminate the visitor’s HTTPS connection and open another connection to the source server. That differs from a TURN service forwarding an encrypted transport between its endpoints. Review the actual configuration rather than assuming both products expose the same data. Provider encryption-mode documentation.
A provider can apply different traffic rules to its CDN, tunnel and TURN products. Confirm that the current agreement for the specific service permits your intended media traffic. A free plan is not automatically an unlimited video-delivery plan. Read the provider’s current service terms.
Beebo’s Use my own relay setting also accepts a standard TURN server that uses shared-secret credentials (the “TURN REST API” style). Examples are coturn with use-auth-secret or eturnal. Enter your server’s address (for example turn:relay.example.com:3478, and turns:relay.example.com:443 for strict networks) and its shared secret. If you run your own, lock it down so it can’t reach private or internal addresses. This coturn hardening guide is a good start.
Will Beebo run a relay for me? Yes. Beebo Relay has been used successfully in owner testing; paid plans and limits are being finalized, so you don’t need your own. You can choose your own compatible relay instead; its provider terms and charges apply.
Check that the key ID and API token were pasted in full, with no extra spaces at the start or end. Make sure you used the token for the TURN key, not a general Cloudflare account API token. If you’re not sure, create a fresh TURN key in Cloudflare and paste the new pair into Beebo.
The home PC also needs to be on, running Beebo, and online. A relay can’t reach a PC that’s asleep.
In Cloudflare, open Realtime → TURN Server and look for usage on your key, or check Manage Account → Billing → Billable Usage. Provider traffic on that key is one useful signal. Confirm the session route in Beebo; successful playback alone does not prove which route was used. (TURN analytics)
Some networks allow almost nothing except ordinary secure web traffic. Cloudflare’s relay also accepts connections over TLS on port 443, the same port websites use, which can work where ordinary UDP traffic is blocked (Cloudflare TURN ports). Some networks block streaming or peer-to-peer traffic on purpose, and no relay can fix that.
If the TURN key was deleted in Cloudflare, or the Cloudflare account was closed or restricted, the relay stops. Create a new key and paste it into Beebo. Also check your email for billing notices from Cloudflare.
Relayed video takes a longer route, so it depends on the internet speeds at both ends, especially your home upload speed. Try a lower quality for away-from-home viewing.
Check Manage Account → Billing → Billable Usage in Cloudflare. If it looks wrong, delete the TURN key (see below). That stops it being used, and you can make a new one later. Then set a budget alert so you hear about it early next time. (Billable usage)
Cloudflare says its TURN relay runs on its global network but not its China Network, so it may not help there. (source)
On your home PC, go to Settings → Away from home and turn off Use my own relay (or clear the key ID and token). Then verify the remaining connection preferences; any separately enabled managed fallback is a different setting.
In the dashboard, open Realtime → TURN Server, find your key and delete it. After that, the key can no longer be used to create relay passes. (Cloudflare: delete a TURN key)
If you don’t use Cloudflare for anything else, you can close the account from Cloudflare’s dashboard. Nothing in Beebo depends on it.
Cloudflare, Cloudflare Realtime and Cloudflare Tunnel are trademarks of Cloudflare, Inc. Beebo isn’t affiliated with or endorsed by Cloudflare. Setup labels and provider terms can change. Review the linked provider documentation and your own account before enabling a service. Beebo product wording reviewed Sep 23, 2026, 11:54 PM Eastern.