Architecture
How devices, cloud coordination and agents work together.
System overview
ReignHub separates the interface, connection coordination and agent execution. Send instructions from any device while your agents work on your own computer.
Native applications
NSGo renders native desktop and mobile views. Go handles devices, pairing, networking, session caches and providers in the same application process. Native views deliver a small package and low memory usage without bundling a browser runtime. See measured performance.
The desktop app is both a controller and a host: connect to other computers or share local agents with authorized devices. Mobile apps act as controllers.
Web and connection service
Next.js and React power the website, documentation and browser console, deployed to Cloudflare Workers through OpenNext. The service handles discovery, pairing signals and encrypted relay.
- Durable Objects manage device rooms, online connections and WebSocket signaling.
- D1 stores device identities, pairing relationships and service metadata.
- End-to-end encryption keeps session and attachment decryption on devices; relays forward ciphertext.
Direct connections first
Clients gather LAN, IPv6 and STUN candidates. Native apps explore UDP and TCP paths; browsers use WebRTC. Once connected directly, application data flows between devices. When direct access is unavailable, an encrypted relay can carry traffic according to service access.
An optional Go probe provides TCP/UDP discovery on one public port. Its endpoints are published by the connection service. Connection strategy.
Agent integration
Providers map native agent interfaces to shared session, message, model and attachment capabilities. Codex App and CLI have dedicated providers, with sessions grouped by project in one interface. Connect your agents.
Deployment options
Use the official service to manage accounts and devices, or deploy your own Worker with the same clients, connection protocol and encryption. Self-host ReignHub.