Configure your endpoint
Once you have one or more relay URLs, configure your endpoint to use them: By default, your endpoint authenticates to Shared and Dedicated relays. The iroh-services preset uses your project API key locally to mint a token bound to the endpoint’s Endpoint ID and scoped to relay use. The token expires after 30 days by default; the project API key is not sent to the relay. See API Keys for details.RelayMode::Custom; see Dedicated Infrastructure.
Why use your own relay?
Running dedicated relays gives you:- Isolation: your traffic isn’t mixed with other applications
- Performance: relays close to your users reduce latency and improve NAT traversal success
- Capacity: the shared public infrastructure is rate-limited
- Redundancy: distribute relays across regions or cloud providers for failover
- Compliance: keep relayed traffic inside your own network or jurisdiction
Get a relay
Choose Shared Relays for the standard Pro production setup. Choose dedicated infrastructure when you need isolation, version locking, or blue/green deployments. Iroh Services can manage it for you, or you can self-host.Use Shared Relays
Use authenticated, multi-tenant production relays included with the Pro plan.
Deploy a dedicated relay
Add single-tenant capacity, custom regions, and version locking through Iroh Services.
Self-host a relay
Run the
iroh-relay binary or image on a server with a public IP and DNS name. Automatic TLS via ACME is built in.