Step 3 — Go live

Once a gateway is connected, the console stops showing samples and starts showing your agents, connections, grants, approvals, and audit trail.

Demo mode → your data

Demo mode is an explicit choice you make once per workspace. While it's on, every page carries a "Demo data" note and a "Connect a gateway to go live" prompt. It's a safe sandbox: every action works, but nothing is written and nothing is real.

When your gateway registers, the demo banner disappears and the same pages re-render from your gateway's real state — a clean, empty console you fill with your own connections and grants. Nothing about the layout changes; what you explored in the demo is exactly what you'll operate live.

How the console talks to your gateway

It depends on where the gateway runs — which lines up with where your gateway runs:

• A remote or hosted gateway is reached through a same-origin server-side proxy (/api/gw). Your browser sends requests to Permaura; the server injects the decrypted bearer token and forwards them. The token never touches the browser.
• A local gateway on 127.0.0.1 can't be reached by a cloud server, so the browser talks to it directly. This works because the gateway ships permissive CORS with Private Network Access enabled, and browsers allow https:// pages to reach http://localhost. The status may read "unverified" — Permaura's servers can't ping your loopback to confirm it — even though it's genuinely live in your browser.

"Unverified" is fine for a local gateway

For a gateway on your own machine, unverified just means the cloud couldn't independently reach it — not that anything is wrong. Your console is reading live data directly from the gateway.

You're live

That's the core loop: create an account → connect a gateway → go live. From here you'll add a connection, connect an agent, and grant it access. The Console tour walks through every page.

➡️ Continue to Step 4 — Add a connection.