n0-computer · okdistribute · Mar 5, 2026 · Mar 5, 2026 · Mar 5, 2026
diff --git a/concepts/relays.mdx b/concepts/relays.mdx
@@ -2,74 +2,77 @@
 title: "Relays"
 ---
 
-Relays are servers that temporarily route encrypted traffic until a direct, P2P connection is
-feasible. Once this direct path is set up, the relay server steps back, and the
-data flows directly between devices. This approach allows Iroh to maintain a
-secure, low-latency connection, even in challenging network situations.
+Relays are servers that temporarily route encrypted traffic until a direct, P2P connection is feasible. Once this direct path is set up, the relay server steps back, and the data flows directly between devices. This approach allows Iroh to maintain a secure, low-latency connection, even in challenging network situations.
+There are situations where a direct connection can’t be established, and in those cases traffic falls back to running through the relay. Relay servers do not have access to the data being transmitted, as it’s encrypted end-to-end.
 
-There are situations where a direct connection _can't_ be established, and in
-those cases traffic falls back to running through the relay. Relay servers **do
-not** have access to the data being transmitted, as it's encrypted end-to-end.
+Relays serve two roles in iroh:
 
-We're working on formally collecting the direct connection rate from production
-iroh networks. Anecdotal evidence points to roughly 9 out of 10 networking conditions we see in practice allowing a direct connection to be established. Our holepunching implementation is deterministic - if it works between two devices once, it should continue to work as long as their networking setup remains stable.
+1. **Holepunching assistance.**  When two endpoints first connect, they exchange network information through the relay to attempt a direct P2P connection.
+2. **Encrypted traffic fallback.** If a direct connection can't be established (due to strict NATs, firewalls, or other network conditions), traffic flows through the relay instead.
 
-## Public relays
+Once a direct path is established, the relay steps back and data flows peer-to-peer. Relay servers **cannot read** any of the traffic they handle — it's encrypted end-to-end.
 
-iroh is configured with a set of public relays provided by [n0.computer](https://n0.computer) that are free to use. The public relays rate-limit
-traffic that flows through the relay. This is to prevent abuse, and ensure the
-relays are available to everyone. There are no guarantees around uptime or
-performance when using the public relays.
+In practice, roughly 9 out of 10 networking conditions allow a direct connection. iroh's holepunching implementation is deterministic: if it works between two devices once, it will continue to work as long as their networking setup stays stable.
 
-We recommend using the public relays for development and testing, as they are
-free to use and require no setup. However, for production systems, we recommend
-using dedicated relays instead.
+## Deploy your own relay
+
+<Card
+  title="Deploy a dedicated relay"
+  icon="server"
+  href="https://services.iroh.computer?utm_source=docs&utm_content=concepts-relays"
+>
+  Sign up for Iroh Services and spin up a managed relay for your project in minutes.
+</Card>
 
-## Dedicated relays
 
-For production use, we recommend using dedicated relays. Dedicated relays are relay
-servers that are either self-hosted or provided as a managed service. Dedicated
-relays provide better performance, security, and uptime guarantees compared to
-the public relays. 
+## Why relays are better
 
-## Why this architecture is powerful
+Unlike traditional servers, relay servers are **stateless**. They don't store your application data — they just facilitate connections. 
 
-This approach makes uptime management significantly easier compared to
-traditional client-server architectures:
+- **No database synchronization.** Nothing to replicate across relay instances.
+- **No state migration.** When a relay goes down, clients reconnect to another with no data loss.
+- **Simple scaling.** Spin relay instances up or down like any lightweight service.
+- **Automatic failover.** Iroh can attempt to connect to multiple relays automatically; as long as one is reachable, your peers find each other.
 
-**Stateless servers, stateful clients**  
-Unlike traditional servers that store your application's data and state, relay
-servers are just connection facilitators. All your business logic and data lives
-in your clients. This means:
+This inverts the traditional model: relays are disposable connection facilitators, while your clients own all the application state and logic.
 
-- **No database synchronization** - You don't need to worry about keeping multiple server databases in sync or handling data replication
-- **No state migration** - When a relay goes down, clients simply reconnect to another relay without any data loss or state transfer
-- **Simple server management** - Relay servers are lightweight and easy to spin up or down. No complex deployment procedures or data migration steps
+## Public relays
 
-**Automatic failover**  
-iroh clients automatically try multiple relays when connecting. If one relay is unavailable, clients seamlessly fall back to another relay in your list without application-level retry logic. Your peers will find each other as long as at least one relay is reachable.
+Iroh hardcodes a set of public relays provided by
+[n0.computer](https://n0.computer), free to use. 
 
-**Multi-cloud resilience**  
-For even better guarantees, you can distribute relays across multiple cloud providers. If one provider experiences an outage, your application keeps running on relays hosted elsewhere. Since relays don't store state, you can freely mix providers without worrying about cross-cloud data consistency.
+Public relays:
 
-**Cost-effective scaling**  
-Adding capacity means spinning up more lightweight relay instances, not provisioning databases or managing complex stateful server infrastructure. You can easily scale up for peak usage and scale down during quiet periods.
+- Rate-limit traffic to prevent abuse
+- Carry no uptime or performance guarantees
+- Are shared across all iroh developers worldwide
 
-This architecture inverts the traditional model: instead of treating servers as precious stateful resources and clients as disposable, relay-based architectures treat relays as disposable connection facilitators while clients own the application state and logic.
+**Public relays are suitable for development and testing.** For production, use dedicated relays.
 
-## Connection Changes
+## Dedicated relays
 
-During the lifespan of a connection, networking conditions can change, for
-example when a user switched from 5G to WiFi, plugs in an ethernet cable, or a
-sysadmin modifies router configurations. The connection may change from direct
-to relayed, or even a mixed combination of the two. Iroh will automatically
-switch between direct and relayed connections as needed, without any action
-required from the application.
+Dedicated relays are relay servers provisioned exclusively for your project — either managed through Iroh Services or self-hosted. 
 
-## Read more
+They offer:
+
+- **Isolation** — no noisy neighbors; your traffic is yours alone
+- **Uptime guarantees** — SLAs available via [Iroh Services](/iroh-services/relays)
+- **Version locking** — stay on a specific iroh version or run blue/green deployments
+- **Multi-region & multi-cloud** — deploy relays across regions and providers for resilience
+
+## Deploy your own relay
+
+<Card
+  title="Deploy a dedicated relay"
+  icon="server"
+  href="https://services.iroh.computer?utm_source=docs&utm_content=concepts-relays"
+>
+  Sign up for Iroh Services and spin up a managed relay for your project in minutes.
+</Card>
+
+Or self-host using the open-source relay binary:
 
-- [Dedicated infrastructure guide](/deployment/dedicated-infrastructure)
 - [Relay source code](https://github.com/n0-computer/iroh/tree/main/iroh-relay)
 - [Relay binary releases](https://github.com/n0-computer/iroh/releases)
-- [Managed relay service](/iroh-services/relays)
+- [Dedicated infrastructure guide](/deployment/dedicated-infrastructure)
 
diff --git a/deployment/dedicated-infrastructure.mdx b/deployment/dedicated-infrastructure.mdx
@@ -2,6 +2,8 @@
 title: "Dedicated Infrastructure"
 ---
 
+import RelayEndpointConfig from '/snippets/relay-endpoint-config.mdx';
+
 By default, iroh will use public shared infrastructure to facilitate connections over
 DNS and end-to-end encryption over relays. This infrastructure comprises:
 
@@ -17,14 +19,30 @@ We recommend using the public relays for development and testing, as they are
 free to use and require no setup. However, for production systems, we recommend
 using dedicated relays instead.
 
+<Card
+  title="Deploy a dedicated relay"
+  icon="server"
+  href="https://services.iroh.computer?utm_source=docs&utm_content=concepts-relays"
+>
+  Sign up for Iroh Services and spin up a managed relay for your project in minutes.
+</Card>
+
+
+<Card
+  title="Self-host a relay"
+  icon="wrench"
+  href="https://github.com/n0-computer/iroh/tree/main/iroh-relay"
+>
+  Learn how to self-host a relay for your project.
+</Card>
+
 ## Using dedicated relays
 
-To use dedicated relays with your iroh endpoint, you need to configure the
-endpoint to use your relay's URL.
+To use dedicated relays with your iroh endpoint, configure it with your relay URLs:
+
+<RelayEndpointConfig />
 
-For detailed information on configuring custom relays, including code examples
-and API documentation, see the [iroh relay configuration
-guide](/iroh-services/relays/managed).
+For full deployment steps, see the [managed relay guide](/iroh-services/relays/managed).
 
 ## Why use dedicated relays in production?
 
@@ -33,21 +51,13 @@ enhanced security, better uptime guarantees, and greater control over your netwo
 using your own servers, you can optimize connection speeds and reduce
 latency for your specific use case. 
 
-If you require more control over your relay infrastructure, you can choose to
-[self-host your own
-relay](https://github.com/n0-computer/iroh/tree/main/iroh-relay) or [upgrade to
-a managed relay service](/iroh-services/relays). This managed relay
-service is monitored by [n0.computer](https://n0.computer) who maintain the iroh project, and
-offers SLAs around uptime and performance.
-
-[Sign up for a free account](https://n0des.iroh.computer?utm_source=docs&utm_content=dedicated-infrastructure) to get started.
 
 ## Recommended setup
 
 We recommend setting up at least two relays for redundancy in different regions.
 For example, you could set up one relay in North America and another in Europe.
 
-### Why this architecture is powerful
+## Why this architecture is powerful
 
 This approach makes uptime management significantly easier compared to
 traditional client-server architectures:

diff --git a/docs.json b/docs.json
@@ -140,7 +140,7 @@
     "primary": {
       "type": "button",
       "label": "Login",
-      "href": "https://n0des.iroh.computer?utm_source=docs&utm_content=nav-login"
+      "href": "https://services.iroh.computer?utm_source=docs&utm_content=nav-login"
     }
   },
   "contextual": {

diff --git a/images/add-relay.png b/images/add-relay.png
diff --git a/images/create-project.png b/images/create-project.png
diff --git a/images/region-relay.png b/images/region-relay.png
diff --git a/iroh-services/access.mdx b/iroh-services/access.mdx
@@ -36,7 +36,7 @@ To authorize endpoints to push metrics to your project, Iroh Services uses API K
 
 ```rust
 use iroh::Endpoint;
-use iroh_n0des::Client;
+use iroh_services::Client;
 
 #[tokio::main]
 async fn main() -> anyhow::Result<()> {

diff --git a/iroh-services/billing/faq.mdx b/iroh-services/billing/faq.mdx
@@ -39,7 +39,7 @@ details.
 ## Where can I see my invoices?
 
 Invoices are available in the **Settings** > **Billing** section of your
-[project dashboard](https://n0des.iroh.computer).
+[project dashboard](https://services.iroh.computer).
 
 ## Are taxes included in the prices?
 

diff --git a/iroh-services/billing/index.mdx b/iroh-services/billing/index.mdx
@@ -14,7 +14,7 @@ Iroh Services offers plans to fit your needs, from free tiers for experimentatio
 | **Net Diagnostics** | Community support | Priority support tickets | Guaranteed SLA response times |
 | **Support** | Discord | Email & Discord | Dedicated support & professional services |
 
-For full plan details and pricing, visit the [pricing page](https://n0des.iroh.computer/pricing).
+For full plan details and pricing, visit the [pricing page](https://services.iroh.computer/pricing).
 
 ## How billing works
 
@@ -23,7 +23,7 @@ Iroh Services billing is usage-based, calculated monthly. Your bill is determine
 - **Your plan tier** — each plan includes a base set of features and resource allocations.
 - **Resource usage** — additional charges may apply for usage beyond what's included in your plan, such as metrics volume or relay bandwidth.
 
-Billing is managed through the [Iroh Services dashboard](https://n0des.iroh.computer). You can view your current plan, usage, and invoices at any time.
+Billing is managed through the [Iroh Services dashboard](https://services.iroh.computer). You can view your current plan, usage, and invoices at any time.
 
 ## Next steps
 

diff --git a/iroh-services/billing/manage-subscription.mdx b/iroh-services/billing/manage-subscription.mdx
@@ -3,7 +3,7 @@ title: "Manage Your Subscription"
 description: "Upgrade, downgrade, or cancel your Iroh Services subscription"
 ---
 
-Manage your subscription from the [Iroh Services dashboard](https://n0des.iroh.computer).
+Manage your subscription from the [Iroh Services dashboard](https://services.iroh.computer).
 
 ## Upgrade your plan
 

diff --git a/iroh-services/metrics/custom.mdx b/iroh-services/metrics/custom.mdx
@@ -37,7 +37,7 @@ For a complete example, see the [iroh-ping example on GitHub](https://github.com
 
 ```rust
 use iroh::Endpoint;
-use iroh_n0des::Client;
+use iroh_services::Client;
 
 #[tokio::main]
 async fn main() -> anyhow::Result<()> {

diff --git a/iroh-services/metrics/endpoint.mdx b/iroh-services/metrics/endpoint.mdx
@@ -29,7 +29,7 @@ extended retention and lookback for endpoint-level metrics. This allows you to
 analyze historical data and identify trends over time, which can be crucial for
 long-term performance optimization and troubleshooting.
 
-Please refer to the [pricing page](https://n0des.iroh.computer/pricing?utm_source=docs&utm_content=endpoint-metrics) for more details on plan features
+Please refer to the [pricing page](https://services.iroh.computer/pricing?utm_source=docs&utm_content=endpoint-metrics) for more details on plan features
 and benefits. 
 
 [Contact us](mailto:support@iroh.computer) if you have any questions about upgrading your plan.

diff --git a/iroh-services/metrics/how-it-works.mdx b/iroh-services/metrics/how-it-works.mdx
@@ -11,15 +11,15 @@ Iroh Services dashboard. Metrics will be automatically collected and reported on
 1. The endpoint is built using the API Secret Key
 2. The endpoint sends metrics data to a Cloud endpoint hosted in the Iroh Services platform.
 3. The Iroh Services platform aggregates the data and makes it available in the project dashboard.
-4. Iroh services deletes data on a rolling bases outside the retention window, based on your [plan](https://n0des.iroh.computer/pricing). 
+4. Iroh services deletes data on a rolling bases outside the retention window, based on your [plan](https://services.iroh.computer/pricing). 
 
 
 ## How it works 
 
 Once an iroh endpoint is integrated in rust program, you can add an 
-`iroh_n0des::Client` to begin sending metrics to the Iroh Services platform. 
+`iroh_services::Client` to begin sending metrics to the Iroh Services platform. 
 
-1. The `iroh_n0des::Client` will automatically detect any running iroh instance in your
+1. The `iroh_services::Client` will automatically detect any running iroh instance in your
 endpoint and begin sending metrics as long as the secret and the ssh
 key match what has been set up in your project on the Iroh Services platform.
 2. Call `endpoint.online().await` before creating the Client. The endpoint must be online before the client is instantiated in order to
@@ -30,7 +30,7 @@ authenticate to the platform.
 ## Metrics Retention
 
 Project-level metrics are retained based on your events plan. Please refer to the
-[pricing page for more details on plan features and benefits](https://n0des.iroh.computer/pricing).
+[pricing page for more details on plan features and benefits](https://services.iroh.computer/pricing).
 
 Endpoint level metrics are only available on Enterprise plans. For projects on
 these plans, the amount of endpoint-level raw data retained is calculated on

diff --git a/iroh-services/metrics/index.mdx b/iroh-services/metrics/index.mdx
@@ -56,4 +56,4 @@ No personally identifiable information (PII) is collected or stored. The
 focus is on overall network performance rather than individual user behavior.
 
 If you have concerns about data collection, please refer to the
-[privacy policy](https://n0des.iroh.computer/legal/privacy).
+[privacy policy](https://services.iroh.computer/legal/privacy).
diff --git a/iroh-services/net-diagnostics/usage.mdx b/iroh-services/net-diagnostics/usage.mdx
@@ -13,19 +13,19 @@ display.
 
 To add net diagnostics support to your own iroh application, you need to:
 
-1. Connect to the n0des platform with an `iroh_n0des::Client`
+1. Connect to the n0des platform with an `iroh_services::Client`
 2. Grant the `NetDiagnosticsCap::GetAny` capability to n0des so it can request diagnostics from your endpoint
 3. Run a `ClientHost` so n0des can dial back into your endpoint
 
-[See the `net_diagnostics` example in the `iroh-n0des` repository for a complete working example of this integration.](https://github.com/n0-computer/iroh-n0des/tree/main/examples/net_diagnostics.rs)
+[See the `net_diagnostics` example in the `iroh-services` repository for a complete working example of this integration.](https://github.com/n0-computer/iroh-services/tree/main/examples/net_diagnostics.rs)
 
 
 ### 1. Update Cargo.toml
 Add the following to your `Cargo.toml`:
 
 ```toml
 [dependencies]
-iroh-n0des = { version = "...", features = ["net_diagnostics", "client_host"] }
+iroh-services = { version = "...", features = ["net_diagnostics", "client_host"] }
 ```
 
 ### 2. Get Your API Secret
@@ -45,7 +45,7 @@ Here's a minimal integration:
 ```rust
 use anyhow::Result;
 use iroh::{Endpoint, protocol::Router};
-use iroh_n0des::{
+use iroh_services::{
     ApiSecret, Client, ClientHost, CLIENT_HOST_ALPN, API_SECRET_ENV_VAR_NAME,
     caps::NetDiagnosticsCap,
 };

diff --git a/iroh-services/quickstart.mdx b/iroh-services/quickstart.mdx
@@ -7,7 +7,7 @@ This guide will walk you through hooking up your first endpoint to Iroh Services
 
 ## Prerequisites
 
-- [An Iroh Services Account](https://n0des.iroh.computer?utm_source=docs&utm_content=quickstart)
+- [An Iroh Services Account](https://services.iroh.computer?utm_source=docs&utm_content=quickstart)
 - [Rust Language](https://rust-lang.org/tools/install/) 
 
 *While iroh is currently only available in Rust, it can be deployed in many other languages and environments.
@@ -16,11 +16,11 @@ Languages](deployment/other-languages) guide for more information.*
 
 ## Step 1: Create a Project
 
-After signing in, [create a new project](https://n0des.iroh.computer/projects/projects/new?utm_source=docs&utm_content=quickstart). This will be your
+After signing in, [create a new project](https://services.iroh.computer/projects/projects/new?utm_source=docs&utm_content=quickstart). This will be your
 sandbox for all endpoints. This is the control center where you can manage and
 monitor your infrastructure, including relays, metrics, and networks.
 
-[![Create Project](/images/new-project.png)](https://n0des.iroh.computer/projects/projects/new?utm_source=docs&utm_content=quickstart)
+[![Create Project](/images/new-project.png)](https://services.iroh.computer/projects/projects/new?utm_source=docs&utm_content=quickstart)
 
 
 ## Step 2: Get Your API Key
@@ -34,10 +34,10 @@ this to authenticate your endpoints.
 
 ## Step 3: Add the Iroh Services Client
 
-Add the `iroh-n0des` crate to your `Cargo.toml`:
+Add the `iroh-services` crate to your `Cargo.toml`:
 
 ```
-cargo add iroh-n0des
+cargo add iroh-services
 ```
 
 
@@ -47,7 +47,7 @@ Then, in your code, create a client and connect your endpoint to Iroh Services.
 
 ```rust
 use iroh::Endpoint;
-use iroh_n0des::Client;
+use iroh_services::Client;
 
 #[tokio::main]
 async fn main() -> anyhow::Result<()> {