Wayfinder Router
Wayfinder Router is a lightweight proxy service that provides a single trusted endpoint for accessing Arweave data through the decentralized ar.io gateway network. It fetches content from multiple gateways, verifies integrity via cryptographic hash checking, and serves verified data to your users.
Your Users
|
v
+------------------+
| Wayfinder Router |
|------------------|
| - Verification |
| - Caching |
| - Telemetry |
+------------------+
|
+--------------+--------------+
| | |
v v v
+------+ +------+ +------+
| GW1 | | GW2 | | GW3 |
+------+ +------+ +------+
\___________+___________/
|
ar.io Gateway NetworkWhy Use Wayfinder Router?
Content Verification
Cryptographically verify all content against trusted gateways before serving
Single Endpoint
Give your users one reliable URL instead of managing gateway failover in client code
Built-in Caching
LRU cache with optional disk persistence for fast repeat access
Admin Dashboard
Web UI for configuration, monitoring, and content moderation
Two Operating Modes
| Mode | Behavior | Use Case |
|---|---|---|
| Proxy | Fetch, verify, and serve content through the router | Full verification, caching, single domain |
| Route | Redirect clients directly to a gateway URL | Lower latency, client-side verification |
When to Use Wayfinder Router
Use Wayfinder Router when you need:
- A single trusted endpoint for your application
- Server-side content verification
- Centralized caching and rate limiting
- Content moderation capabilities
- Monitoring and telemetry
Use the SDKs directly when you need:
- Client-side verification in browsers
- Custom routing logic in your application
- Integration with existing infrastructure
Architecture Overview
The router separates routing (where to fetch data) from verification (who to trust):
- Routing Gateways - Where content is fetched from (all ar.io gateways, trusted peers, or static list)
- Verification Gateways - Who to trust for hash verification (top-staked gateways or static list)
This means even if a routing gateway is compromised, tampered content is detected and rejected. When verification fails, the router returns an error to the client rather than serving potentially malicious content.
Get Started
Quick Start
Get running in 30 seconds with a standalone binary or Docker
Configuration
Environment variables for routing, verification, caching, and more
Admin UI
Web dashboard for monitoring, configuration, and moderation
Operations
Monitoring, troubleshooting, and production deployment
How is this guide?