Everything you need to run Interconnect.
Getting started
Install, enroll your first device, and connect a resource in five minutes.
How ForgeLink works
Our P2P protocol end to end — ICE/STUN/TURN traversal and AES-256 tunnels.
Core concepts
Zero trust, identity, device posture and how ACLs evaluate.
Guides
Task-based walkthroughs for the most common setups.
API reference
Fully typed REST and gRPC endpoints with examples.
CLI
Every command and flag for the fastforge binary.
Terraform
Manage policies, routes and devices as version-controlled code.
Self-hosting
Run the coordination server in your own VPC or on-prem.
Security
Hardening guidance, compliance mappings and disclosures.
Popular articles
The pages teams open most in their first week.
How ForgeLink works
ForgeLink is our own peer-to-peer protocol — devices connect straight to each other, so there's no concentrator to backhaul through and nothing in the middle decrypting your traffic.
- 01
Authenticate & enroll
A device signs in against your identity provider — SSO and MFA included — and the coordination server returns a signed list of the peers it's allowed to reach.
- 02
Gather candidates
Each peer discovers how it can be reached: its local addresses, its public address via STUN, and a relay address via TURN held in reserve.
- 03
Forge a direct path
ICE races those candidates and picks the lowest-latency route that actually works, hole-punching through NAT so the two devices talk peer-to-peer.
- 04
Relay only when needed
When a symmetric NAT or strict firewall blocks every direct path, traffic falls back to the nearest TURN edge — relayed, never decrypted.
- 05
Encrypt end to end
Every session is wrapped in AES-256 from the moment it opens. Keys rotate continuously and the coordination server only ever knows who may connect — never the traffic itself.