# iroh

> iroh.computer | Egress and tunnels, Storage; 7 records: free tier, limits, identity cost and evidence.

HTML https://fshy.ajam.dev/p/iroh/ | JSON https://fshy.ajam.dev/api/v1/entity/iroh.json | how to read a record: https://fshy.ajam.dev/llms-full.txt

## iroh public relays

- `egress/iroh-public-relay` | qualifies-with-caveat | evidence documented | binding per-ip-shaping | category relay (hosted, unmetered by claim)
- needs card no, phone no, ID no, institution no | verified 2026-10-22T03:20:00.000Z (live) | stale on 2026-11-22
- url https://docs.iroh.computer/relays/rate-limiting
- free tier: four public relay regions, no authentication, rate-limited per connection | unit: unlimited | metered on: downloaded-bytes | read on: 2026-10-22 | source: [1]
- per-object cap: not applicable: a stream
- retention: not applicable | source: [1]
- egress: no byte quota; a per-connection rate limit that is retuned | metered: no | source: [1]
- identity: anonymous | detail: no authentication on the public relays
- interface: unknown
- limits:
  - per-ip-shaping (binding): per connection, value not published and retuned as needed [1]
- interface detail: the n0 public relay preset, spoken over QUIC
- tooling: iroh
- composes with: a zero-cost relay for the connections that fail to hole-punch, which makes it a redundancy layer rather than a capacity layer.
- reliability: the documentation says not to rely on the public relays for production
- notes: A relay that transits bytes is metered by definition, and this one meters rate rather than volume. No number, so no capacity claim.
- extras:
  - stale_after_days: 180
  - bytes_transit: yes
  - transit_note: a relay that transits bytes when hole-punching fails, at a per-connection rate it does not publish
- evidence:
  - [1] 2026-10-22: 'The exact rate limits aren't published today, as they get tuned as needed', plus the warning that public relays are not for production workloads
- sources:
  - [1] https://docs.iroh.computer/relays/rate-limiting

## iroh public relays (n0.computer)

- `storage/iroh-public-relays` | qualifies-with-caveat | evidence reported | binding per-ip-shaping | category relay/P2P — SIGNALLING with encrypted fallback transport
- needs card no, phone no, ID no, institution no | verified 2026-10-21 (inherited) | stale on 2026-11-05
- url https://docs.iroh.computer/iroh-services/relays/public
- free tier: No storage. Free, no account, no card. Public relays are rate-limited per connection but the rate limits are deliberately unpublished. The paid Shared tier is the only one with published figures: 100 GB relayed egress/month then $0.09/GB, 5 MB/s, 10,000 concurrent connections. | unit: GB | metered on: stored-bytes | read on: 2026-10-21 | source: [1]
- per-object cap: not stated | source: [1] | note: not stated
- retention: not stated | source: [1] | note: not stated
- egress: Free public relays, rate-limited. Self-hosting a relay is free and unlimited (open licence) — the cost moves to your own bandwidth. | metered: no
- identity: anonymous | detail: anonymous
- interface: unknown
- limits:
  - per-ip-shaping (binding): 5 MB/s [1]
  - per-ip-shaping (binding): 10,000 concurrent connections [1]
- limits note: Not a storage provider. Only relayed bytes hit the operator, hence the per-connection rate limit rather than a byte quota.
- interface detail: QUIC over TLS 1.3; Rust crate `iroh`, bindings for other languages
- tooling: `iroh` crate; relay is a library, not a service with an upload endpoint
- composes with: This is SIGNALLING, not relaying, in the normal case: 'roughly 9 out of 10 connections go direct; the relay is only a fallback'. The relay carries bytes only when hole punching fails, which is what makes the free tier viable at all.
- reliability: 'The exact rate limits aren't published today, as they get tuned as needed' and 'Do not rely on it for production workloads' — the free tier is explicitly capacity-unstable by design.
- notes: the same as the free tier
- evidence:
  - [2] 2026-10-21: 'In practice, roughly 9 out of 10 connections go direct; the relay is only a fallback'; relays are stateless and cannot read traffic (QUIC/TLS 1.3)
  - [3] 2026-10-21: 'The exact rate limits aren't published today, as they get tuned as needed ... applied per connection'; 'Do not rely on it for production workloads'
  - [1] 2026-10-21: Free: 'Rate limited' / 'Variable'; Pro $19/mo: 10,000 connections, shared relays, 5 MB/s; Dedicated $199/mo/region: unlimited
  - [4] 2026-10-21: '100 GB of relay egress per month, then $0.09/GB'; 'A 5 MB/s rate limit'
  - [5] 2026-10-21: worked example: 2,000 users x 10 GB/mo; 'if 98% of the traffic could travel directly ... only the remaining 2% (400 GB) would pass through'
- sources:
  - [1] https://www.iroh.computer/pricing
  - [2] https://docs.iroh.computer/about/faq
  - [3] https://docs.iroh.computer/relays/rate-limiting
  - [4] https://docs.iroh.computer/iroh-services/relays/shared
  - [5] https://www.iroh.computer/blog/shared-relays

## iroh n0 public relays

- `storage/iroh-n0-public-relays` | fails-egress | evidence documented | binding none | category rejected-provider
- identity a placeholder: card and phone unknown | verified 2026-11-04T01:24:26.450Z (live) | stale on 2026-12-05
- url https://docs.iroh.computer/relays/rate-limiting
- free tier: Community plan, $0 per month: public relays in US, EU and Singapore, rate-limited traffic, no uptime guarantees, no auth; the rate limit is not published | unit: none | metered on: none | read on: 2026-10-21 | source: [1]
- per-object cap: not recorded | source: [1] | note: not recorded
- retention: not recorded | source: [1]
- egress: Public relays are rate-limited per connection with no published limit; the pricing page lists egress and rate limit as 'Variable'. Paid routes: Pro $19/month has a 5 MB/s rate limit and 100 GB egress then $0.09/GB; Dedicated adds $199/month per region with no rate limits and 250 GB egress then $0.09/GB. | metered: no
- identity: email
- interface: unknown
- tooling: not recorded
- composes with: the same as tooling
- reliability: Free public relays: rate-limited traffic with an unpublished limit, no uptime guarantees, development and hobby use only; no published limit supports 1 TiB a day. The paid Dedicated route has no rate limit and bills $0.09/GB beyond 250 GB.
- notes: the same as reliability
- evidence note: documented from vendor pages read on 2026-11-03: the plan rates and egress (https://www.iroh.computer/pricing), and the rate limiting and hobby-use statements (https://docs.iroh.computer/iroh-services/relays/public and https://docs.iroh.computer/relays/rate-limiting). Identity, retention and per-object cap were not read.
- extras:
  - dead_end.failure_class: egress
  - dead_end.why: Free tier is 'rate-limited traffic' with 'No uptime guarantees' and the exact limits are deliberately unpublished ('The exact rate limits aren't published today, as they get tuned as needed'
  - dead_end.first_recorded: 2026-10-21
- evidence:
  - [1] 2026-10-21: Free tier is 'rate-limited traffic' with 'No uptime guarantees' and the exact limits are deliberately unpublished 'The exact rate limits aren't published today, as they get tuned as needed'
  - [2] 2026-10-21: cited as the basis of the rejection: Free tier is 'rate-limited traffic' with 'No uptime guarantees' and the exact limits are deliberately unpublished 'The exact rate limits aren't published today, as they get tuned as needed'
  - [3] 2026-10-21: cited as the basis of the rejection: Free tier is 'rate-limited traffic' with 'No uptime guarantees' and the exact limits are deliberately unpublished 'The exact rate limits aren't published today, as they get tuned as needed'
  - [2] 2026-11-03: rate limit per plan: Variable on Community, 5 MB/s on Pro, Unlimited on Dedicated | capture: sha256:677a58c510e73c87a15e93ac568bdfb3937e2fa45690b989fa9ad94c9260551a | quote: | Rate limit | Variable | 5 MB/s | Unlimited | Custom |
  - [2] 2026-11-03: egress per plan: Variable on Community, 100 GB then $0.09/GB on Pro, 250 GB then $0.09/GB on Dedicated | capture: sha256:677a58c510e73c87a15e93ac568bdfb3937e2fa45690b989fa9ad94c9260551a | quote: | Egress | Variable | 100 GBthen $0.09/GB | 250 GBthen $0.09/GB | Custom |
  - [3] 2026-11-03: public relay traffic is rate-limited | capture: sha256:268dee5a141ea15ee40a7018f29bc473de3fb70f56c3c3a8a44fb1a9d0b8ecee | quote: Traffic is rate-limited to prevent abuse
  - [3] 2026-11-03: public relays are for development and hobby use only | capture: sha256:268dee5a141ea15ee40a7018f29bc473de3fb70f56c3c3a8a44fb1a9d0b8ecee | quote: Public relays are suitable for development and hobby use only.
  - [1] 2026-11-03: dedicated relays have no rate limits | capture: sha256:962e4513e4dc6427b10423f4f41cdcb15196dba2bc4246ec17cd668e64d660cd | quote: dedicated relays remove rate limits entirely
  - [1] 2026-11-03: the public relays' rate limit has no published number | capture: sha256:962e4513e4dc6427b10423f4f41cdcb15196dba2bc4246ec17cd668e64d660cd | quote: The exact rate limits aren't published today, as they get tuned as needed.
  - [2] 2026-11-03: the Community plan lists rate-limited traffic | capture: sha256:677a58c510e73c87a15e93ac568bdfb3937e2fa45690b989fa9ad94c9260551a | quote: Rate-limited traffic
  - [2] 2026-11-03: the Community plan row of the public relays carries no egress price and no volume quota; the $0.09/GB figures are on Pro and Dedicated | capture: sha256:677a58c510e73c87a15e93ac568bdfb3937e2fa45690b989fa9ad94c9260551a | quote: | Egress | Variable | 100 GBthen $0.09/GB | 250 GBthen $0.09/GB | Custom |
  - [1] 2026-11-03: the public relays' limit is a per-connection throttle, not a volume quota or a price | capture: sha256:962e4513e4dc6427b10423f4f41cdcb15196dba2bc4246ec17cd668e64d660cd | quote: Rate limiting is a property of a single relay connection, not a global switch.
  - [3] 2026-11-03: the public relays have no price | capture: sha256:268dee5a141ea15ee40a7018f29bc473de3fb70f56c3c3a8a44fb1a9d0b8ecee | quote: available to all iroh users at no cost
  - [2] 2026-11-04: rate limit per plan: Variable on Community, 5 MB/s on Pro, Unlimited on Dedicated | capture: sha256:677a58c510e73c87a15e93ac568bdfb3937e2fa45690b989fa9ad94c9260551a | quote: | Rate limit | Variable | 5 MB/s | Unlimited | Custom |
  - [1] 2026-11-04: the public relays' rate limit has no published number | capture: sha256:962e4513e4dc6427b10423f4f41cdcb15196dba2bc4246ec17cd668e64d660cd | quote: The exact rate limits aren't published today, as they get tuned as needed.
  - [3] 2026-11-04: public relays are for development and hobby use only | capture: sha256:268dee5a141ea15ee40a7018f29bc473de3fb70f56c3c3a8a44fb1a9d0b8ecee | quote: Public relays are suitable for development and hobby use only.
- sources:
  - [1] https://docs.iroh.computer/relays/rate-limiting
  - [2] https://www.iroh.computer/pricing
  - [3] https://docs.iroh.computer/iroh-services/relays/public

## iroh Services — Community (free tier)

- `storage/iroh-services-community` | fails-egress | evidence reported | binding none | category Hosted coordination service (relays + metrics + diagnostics) — NOT storage
- needs card no, phone no, ID no, institution no | verified 2026-10-21 (inherited) | stale on 2026-11-05
- url https://www.iroh.computer/pricing
- free tier: 0 bytes of storage. Free plan = public relays in US/EU/Singapore, 7-day metrics retention, no auth, rate-limited traffic, no uptime guarantee. | unit: mixed | metered on: stored-bytes | read on: 2026-10-21 | source: [1]
- per-object cap: not stated | source: [1] | note: not stated
- retention: Free plan = public relays in US/EU/Singapore, 7-day metrics retention, no auth, rate-limited traffic, no uptime guarantee | days: 7 | source: [1] | note: not stated
- egress: Variable / unpublished (inherits public relay limits). | metered: no
- identity: email | detail: email
- interface: unknown
- limits note: Relay only. There is no pinning service, no blob hosting, no object storage SKU anywhere in n0's product line — the entire product is coordination plus egress.
- interface detail: Dashboard at services.iroh.computer + `iroh-services` crate; account is username + email + password.
- tooling: `iroh_services::Client` pushes endpoint metrics on an interval; net-diagnostics can dial back into your endpoint (requires granting `Caps::net_diagnostics_get_any()`).
- composes with: Free tier covers signalling and discovery for an unlimited number of endpoints — which is exactly the part a self-hosted origin needs. It contributes nothing to bytes at rest or bytes served.
- reliability: Free tier requires an account only to see metrics; the relays themselves need no account at all.
- notes: the same as the free tier
- extras:
  - dead_end.failure_class: retention
  - dead_end.why: 0 bytes of storage. Free plan = public relays in US/EU/Singapore, 7-day metrics retention, no auth, rate-limited traffic, no uptime guarantee.
  - dead_end.first_recorded: 2026-10-21
- evidence:
  - [1] 2026-10-21: plan table: Free/Pro $19/Dedicated $199 per region/Enterprise; rows are Connections, Relays, Rate limit, Egress, Auth, Custom DNS, Metrics, Support. No storage row exists.
  - [2] 2026-10-21: Public free / Cloud $19+ / Open Source self-host. 'Hosting' here means relays and discovery.
  - [3] 2026-10-21: signup form is username + email + password (no card, no institution)
- sources:
  - [1] https://www.iroh.computer/pricing
  - [2] https://www.iroh.computer/services/hosting
  - [3] https://services.iroh.computer/

## ipfs / shipyard

- `storage/ipfs-shipyard` | fails-quota | evidence reported | binding none | category rejected-provider
- identity a placeholder: card and phone unknown | verified 2026-10-21 (inherited) | stale on 2026-11-05
- url https://www.iroh.computer/blog/iroh-global-content-discovery
- free tier: The IPFS pinning lane is closing, not opening — and free IPFS pinning was already excluded at <=6 GB in earlier waves. iroh's own blog frames Mainline+blake3.net as the successor, which is… | unit: none | metered on: none | read on: 2026-10-21 | source: [1]
- per-object cap: not recorded | source: [1] | note: not recorded
- retention: not recorded | source: [1]
- egress: not recorded | metered: no
- identity: email
- interface: unknown
- tooling: not recorded
- composes with: the same as tooling
- reliability: the same as the free tier
- notes: the same as the free tier
- extras:
  - dead_end.failure_class: quota
  - dead_end.why: The IPFS pinning lane is closing, not opening — and free IPFS pinning was already excluded at <=6 GB in earlier waves. iroh's own blog frames Mainline+blake3.net as the successor, which is…
  - dead_end.first_recorded: 2026-10-21
- evidence:
  - [1] 2026-10-21: The IPFS pinning lane is closing, not opening — and free IPFS pinning was already excluded at <=6 GB in earlier waves. iroh's own blog frames Mainline+blake3.net as the successor, which is…
  - [1] 2026-10-21: the iroh post the record cites is the source of the name; the provider name keeps the service and drops a personal note
- sources:
  - [1] https://www.iroh.computer/blog/iroh-global-content-discovery

## iroh Shared relay

- `egress/iroh-shared-relay` | fails-quota | evidence documented | binding volume-quota | category relay (metered, QUIC)
- needs card no, phone no, ID no, institution no | verified 2026-10-22T03:20:00.000Z (live) | stale on 2026-11-22
- url https://docs.iroh.computer/iroh-services/relays/shared
- free tier: 100 GB relay egress per month, 10,000 concurrent connections, 5 MB/s rate | unit: GB | metered on: downloaded-bytes | read on: 2026-10-22 | source: [1]
- per-object cap: not applicable: a monthly allowance
- retention: not applicable | source: [1]
- egress: metered at 100 GB/month, which is 3.3 GB/day | metered: yes | free allowance: 100 GB/month | price per TB: USD 0.09/GB | source: [1]
- identity: email | detail: an n0 account and an API key
- interface: unknown
- limits:
  - per-ip-shaping: 5 MB/s per connection [1]
- limits note: the allowance is a byte volume over a period, which none of the six kinds names; the number is in egress.free_allowance and binding names per-ip-shaping as the nearest kind
- binding note: the monthly byte allowance in egress.free_allowance is what runs out, and no kind in the six-value vocabulary names a byte volume over a period counted per account. per-ip-shaping is the closest, because it is the only kind that bounds a volume, and its subject here is the account rather than the caller's address
- interface detail: an iroh relay URL attached to a project, spoken over QUIC
- tooling: part of interface detail
- composes with: the paid fallback for the 7-10% of iroh connections that fail to hole-punch; it composes with the transport and not with a free budget.
- reliability: the allowance is a 30-day trial rather than a persistent free tier
- notes: The free public relays are a separate product with deliberately unpublished limits.
- extras:
  - stale_after_days: 180
  - bytes_transit: yes
  - transit_note: the paid relay transits bytes, which is why it meters them at 100 GB per month
- evidence:
  - [1] 2026-10-22: up to 10,000 concurrent connections, 100 GB relay egress per month then USD 0.09/GB, a 5 MB/s rate limit, and a 30-day trial on Pro
- sources:
  - [1] https://docs.iroh.computer/iroh-services/relays/shared

## n0 hosted blob pinning / storage service

- `storage/n0-hosted-blob-pinning-storage-service` | fails-quota | evidence reported | binding none | category rejected-provider
- identity a placeholder: card and phone unknown | verified 2026-10-21 (inherited) | stale on 2026-11-05
- url https://www.iroh.computer/pricing
- free tier: Does not exist. n0 sells coordination (relays, metrics, diagnostics) and never bytes at rest. Checked the pricing table, the hosting page, the services dashboard, the org's 100-repo… | unit: none | metered on: none | read on: 2026-10-21 | source: [1]
- per-object cap: not recorded | source: [1] | note: not recorded
- retention: not recorded | source: [1]
- egress: not recorded | metered: no
- identity: email
- interface: unknown
- tooling: not recorded
- composes with: the same as tooling
- reliability: the same as the free tier
- notes: the same as the free tier
- extras:
  - dead_end.failure_class: quota
  - dead_end.why: Does not exist. n0 sells coordination (relays, metrics, diagnostics) and never bytes at rest. Checked the pricing table, the hosting page, the services dashboard, the org's 100-repo…
  - dead_end.first_recorded: 2026-10-21
- evidence:
  - [1] 2026-10-21: Does not exist. n0 sells coordination (relays, metrics, diagnostics) and never bytes at rest. Checked the pricing table, the hosting page, the services dashboard, the org's 100-repo listing
  - [2] 2026-10-21: cited as the basis of the rejection: Does not exist. n0 sells coordination (relays, metrics, diagnostics) and never bytes at rest. Checked the pricing table, the hosting page, the services dashboard, the org's 100-repo listing
  - [3] 2026-10-21: cited as the basis of the rejection: Does not exist. n0 sells coordination (relays, metrics, diagnostics) and never bytes at rest. Checked the pricing table, the hosting page, the services dashboard, the org's 100-repo listing
- sources:
  - [1] https://www.iroh.computer/pricing
  - [2] https://www.iroh.computer/services/hosting
  - [3] https://docs.iroh.computer/iroh-services/relays/shared