Private transport
The tunnel is an access layer, not conversation storage.
Twoody Private Tunnel
A private path between your apps and your Twoody Server.
The tunnel connects a remote app to your private server without turning Twoody into the intermediary receiving your messages. On LAN, apps can talk directly to the server; remotely, the tunnel keeps private access.
Remote mobile
An employee can ask an authorized folder from a phone if server and connector are reachable.
No magic access
The tunnel must not bypass auth, permissions or server rules.
Cómo funciona
01
App picks server
Local, private host or managed.
02
Network decides
LAN if available, private tunnel if remote.
03
Server authorizes
Auth, sessions and permissions stay on Twoody Server.
04
Answer returns
The stream returns to the app without creating a Twoody copy in self-hosted mode.
Detalles importantes
Simple explanation
- E2EE encrypts transport; self-hosted also removes Twoody from the application path.
- LAN remains the most direct path when on site.
- The tunnel makes remote access usable without bluntly exposing the server.
Keep it honest
- External cloud services called by a tool receive what the user chooses to send.
- Managed mode must be described separately from self-hosted.
- The promise depends on actual server, model and connector configuration.
FAQ
Why not do everything only on LAN?
Because users also want access from outside. LAN is ideal on site; the tunnel serves remote use.
Is the tunnel temporary access?
The better product message is: a permanent, controlled private path between apps and server, with auth and permissions.