Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.streampixel.io/llms.txt

Use this file to discover all available pages before exploring further.

Streampixel runs workers, signalling, TURN, and build distribution in three independent regions. Each project is bound to one region at creation time. Pick the region closest to most of your end users — region choice directly impacts the input latency they feel while interacting with your stream.

​
Available regions

RegionCodeBest for
US-East-1us-east-1North America
EuropeeuropeEMEA
Asia Pacificasia-pacificAPAC
Region is set when you create a project and cannot be changed in place. To move a project to a different region, create a new project in the target region and re-upload your build.

​
Choosing a region

The single most important factor is geographic distance between the worker and the end user. WebRTC round-trip time (RTT) directly translates to perceived input lag — the time between a user clicking and seeing the result on screen.
User locationRecommended regionTypical RTT
US / Canada / Mexicous-east-120–80 ms
UK / EU / Africa / Middle Easteurope20–80 ms
India / SE Asia / Japan / Australiaasia-pacific30–120 ms
Global mixed audiencePick the region closest to your largest user segmentvaries
For globally distributed audiences, the simplest pattern today is to run one project per region and route users to the right share URL based on their location.

​
What’s region-specific

Resources tied to a region live entirely within that region. None of the following are shared across regions.
  • Worker pool — the GPU machines that run your Unreal binary.
  • Signalling endpoints — the WebSocket servers that broker the WebRTC handshake.
  • TURN servers — the relay servers used when peer-to-peer is blocked.
  • Build distribution — your packaged build is replicated to workers in the region.
  • SFU instances — the fan-out path for one-to-many streaming.

​
What’s global

These services are global — you use the same endpoints and credentials regardless of which region your project lives in.
  • Dashboard — manage every project from streampixel.io.
  • Account and authentication — Google OAuth via Auth0; one identity across regions.
  • REST API — https://api.streampixel.io/pixelStripeApi serves all regions.
  • Billing — usage from every region rolls up to one account.
  • Webhooks — fire from the region the project runs in but are configured globally per project.

​
Cross-region failover

There is no automatic cross-region failover today. If the worker pool in your project’s region is exhausted, sessions are queued in that region — they are not migrated to a different region. Plan for region-specific capacity if availability matters to you.
A regional outage will take down all sessions for projects in that region. If you need redundancy across regions, run parallel projects and implement client-side region selection.

​
Changing regions

The dashboard does not expose an in-place region change. To move a project:
1

Create a new project

In the dashboard, create a new project and select the target region.
2

Re-upload your build

Submit the same .zip to the new project — via dashboard or Upload File API.
3

Update embed URLs

Switch your iframe src or Web SDK appId to point at the new project.
4

Decommission the old project

Once traffic is fully cut over, delete the old project from the dashboard.
If you need help moving a production project — including preserving share URLs — contact support.

​
Next steps

Configuring your project

Set worker counts, codecs, and timeouts within a region.

How Streampixel works

Where regions sit in the overall architecture.

Streaming basics

Latency comes from more than just region — see the full breakdown.

Session lifecycle

What happens when a region’s worker pool is exhausted.