Bubblewrap namespaces
Commands run through Bubblewrap with separate namespaces. System binaries and certificate directories are mounted read-only.
Security without mystery
Your account has a key.
Your account has a key.
Your project has a boundary.
Identity checks protect account changes while sandbox controls keep project commands scoped. Each layer has one clear job and a visible recovery path.
datanode / securityLIVE
Protected
TelegramIdentity bound✓
AuthenticatorCode verified✓
Implementation, not promises
What the sandbox actually does.
These statements describe the current Beta implementation. Limits are explicit, including the protections Datanode does not yet provide.
No host root
The terminal runs as the service account and does not grant root access to the host operating system.
Workspace and runtime only
Project files are writable in /workspace. Temporary files and tool caches use isolated runtime directories.
Outbound network is shared
The current sandbox keeps network access available. It is not a separate VM network boundary, so abuse controls and command limits still apply.
No persistent command history
Terminal commands and output exist only in the active browser view. Datanode does not persist them in local browser storage or an application command-history table.
Manual recovery points
Each account can create and restore up to five snapshots. They are not scheduled backups; dependencies, caches and secret environment files are excluded.
Clear removes active project data
Clearing storage removes non-protected project contents. Recovery is possible only from a snapshot created before the clear operation.
Constrained commands
Terminal commands have time and resource limits. One persistent worker per workspace is available with restart policies and isolated logs.
Current architecture
A short, inspectable path.
Telegram establishes identity. The panel authorizes the account. Commands enter a Bubblewrap sandbox, while project files stay in the account workspace.
Architecture and project details →
Telegramidentity→Gatewayrouting→Panelauthorization→SandboxBubblewrap→Storageworkspace
Security in detail
Four controls. No vague promises.
Inspect each layer to understand what it protects and what state confirms it is working.
Telegram binding
One Datanode account remains attached to one Telegram identity.
SelectedAuthenticator
Use time-based codes as the primary second confirmation method.
AvailableTelegram code
Request a six-digit code in the bot when you need another confirmation path.
AvailableSandbox isolation
Runtime commands and files remain inside the scope assigned to the account.
AvailableContinue exploring
See how the pieces connect.
The five product pages describe one system. Move to the next layer or open the real console.