CADS-Tunnel documentation
CADS-Tunnel is a self-hosted, end-to-end-encrypted tunnel: publish a service running on your own
hardware — a laptop, a Raspberry Pi, a spare VM, your own AI agent — at a real HTTPS address, without
opening a port or exposing your device. This site documents the whole system: the tunnel, ct-agent,
the control plane, and the Agent-Fabric channel/MCP layer.
Organized around what you’re actually trying to do, not around the codebase’s own module boundaries (Diátaxis):
Tutorials
A guided first run, start to finish. Read these if you're new here.
How-to guides
You know roughly what you want — these get you there directly.
Reference
Environment variables, API endpoints, CLI commands — precise, no narration.
Explanation
How the pieces fit together and why they're built this way.
New here?
Start with Your first tunnel — from creating an account to a real, publicly reachable HTTPS address, using nothing you don’t already have.
A note on how this documentation is validated
Every procedure in this documentation has actually been run against the live production deployment, not just described from the source. Where a claim couldn’t be verified this way, it says so explicitly rather than presenting it as confirmed. If you find a step that doesn’t work as written, please open an issue — that’s a real defect in the docs, not a formality.