Public Beta roadmap
What works now.
What may come next.
This roadmap communicates direction, not deadlines. Priorities may change after security work, user feedback and infrastructure testing.
iA roadmap item is not a promise of delivery. Only features marked “Available” are part of the current product.
Available now
✓Files and templatesUpload, create, rename, delete and import a public repository.✓Browser VS CodeEdit the same account workspace through editor.datanode.host.✓Sandbox TerminalRun commands through the Bubblewrap-scoped environment.✓Web application publishingServe Static/PHP files or route a custom domain to a Node.js/Python worker.✓Telegram identityOne account, one verified Telegram binding and confirmation codes.✓Authenticator and localizationTOTP security plus complete English and Russian interfaces.✓Snapshots and restoreCreate, download and atomically restore workspace recovery points.✓Public APIScoped account, storage, files, execution, logs, workers and snapshot endpoints.✓SSH accessUse key-only access to the same Bubblewrap workspace with forwarding disabled.✓Always-on workersRun a persistent process with restart policies and isolated logs.✓Docker-compatible workflowsBuild Dockerfiles with rootless Podman without exposing a host daemon.✓Runtime observabilityWorker output, machine events, status and source filters in a dedicated Logs tab.
Planned next
→Scheduled snapshotsAutomatic recovery points with account-controlled retention.→Multiple workersMore than one independently managed process per workspace.→Incident timelinePublic component history and maintenance notices beyond per-sandbox logs.
Exploring, not committed
?GPU workloadsRequires a separate resource and isolation model.?Additional regionsDepends on demand, operations and data-location requirements.?GitHub OAuthMay complement Telegram without weakening the current account binding.
