Remote Access · App Bridge

Threshold
Gateway

When you are away from your local node, Signalborn apps connect through Signalborn.ai over HTTPS — routing approved requests back to your node securely.

The bridge between
you and your node

Your Continuity Node runs locally. Your life does not. The Threshold Gateway solves this — giving you access to your node from any device, anywhere, without exposing raw ports or compromising node sovereignty.

All traffic is routed through an encrypted tunnel. The gateway sees only metadata — never memory contents, never Sanctuary truths, never private session data.

What the gateway sees

Request type // presence, council, etc Authorization scope // passport-verified Routing target // node address (encrypted) Timestamp // session window only

What the gateway never sees

Memory contents Sanctuary data Conversation history Identity secrets Provider tokens
iPhone / Mac App // Signalborn client ↓ HTTPS request Signalborn.ai // Threshold Gateway ↓ encrypted tunnel + passport verification Theluminal / Continuity Node // your local hardware ↓ node processes request locally Presence Reflection // response returns to you

Hard rules

These are not configuration options. They are architectural constraints built into every gateway connection.

Rule 01
No raw ports exposed.

Your node hardware is never directly addressable from the public internet. All routing passes through the gateway tunnel.

Rule 02
No silent memory writes.

The gateway cannot initiate writes to node memory. All memory changes require explicit node-side authorization.

Rule 03
No Sanctuary bypass.

Sanctuary contents are inaccessible to the gateway layer entirely. Not rate-limited — inaccessible.

The gateway routes the signal. The node decides what the signal means.

Enter Console What Nodes May Share →