Appearance
Console
The console at console.burrowee.com is your account dashboard: every gateway you own, every session, every domain, in one place, from anywhere.
It is worth knowing what the console is not. It never carries your traffic, and it does not own your gateways' data. Your gateway keeps its own targets and sessions locally; the console mirrors that state (the gateway syncs it up through the relay) and remote-controls it (a dashboard action travels down to the gateway, changes the gateway's local store, and syncs back). That is why some actions need the gateway to be online — and why a few things are greyed out with a "Gateway is offline" note when it isn't.
Signing up
- Open
https://console.burrowee.comand click Sign in with GitHub. That is the entire signup — your GitHub identity is your account. - Burrowee is in preview, so new accounts land on a waiting list page. Access is granted manually.
- Check back later. Once approved, the same address takes you straight to the dashboard — no re-login needed (the page re-checks your status whenever you return to it).
From the dashboard, the quickstart takes you to your first open session.
The areas
| Area | What it does |
|---|---|
| Gateways | Create and set up gateways; manage each one's targets, domains, relays, and sessions remotely. |
| Sessions | Sessions you own and sessions shared with you; mint, share, extend, revoke. |
| Edge relays | Register and approve relays you run on your own servers. |
| Custom domains | Verify domains, issue certificates, and attach hostnames to targets. |
| Team | Members, roles, and invites for sharing gateways with others. |
| Account | Your profile, plan, billing, and bandwidth usage. |
The dashboard home shows your name, tenant, and plan, plus shortcut cards into Gateways, Edge relays, and Custom domains — and how much of this month's bandwidth allowance you have used.
Console vs the gateway's local console
Every gateway also serves a local console on its own machine at http://127.0.0.1:16518. The two show the same gateway. The local console talks to the gateway's store directly, so it works even when the cloud is unreachable; the cloud console works from anywhere but needs the gateway online for live operations. Use whichever is closer.