What is Datanode?
A managed Linux workspace with Files, Terminal, browser VS Code and optional static or PHP domain publishing.
Explore the workspace →
Independent project · Public Beta
An isolated Linux workspace with files, Terminal and browser VS Code. Request access through Telegram in about 30 seconds — without administering a VPS.
Bubblewrap sandbox
No host root
By @factorialovich
Datanode
Sandbox online
DN
Workspace
RunningGood evening.
Storage
264 MB
of assigned workspace quota
Quick launch
EnvironmentPHP Site
public/index.php
domain connected
Everything needed to move from a blank workspace to a live site
File manager
Sandbox shell
Browser editor
Domain publishing
Understand it in 30 seconds
Not a VPS.
A focused workspace.
Datanode gives one account a persistent project space, browser tools and a constrained command environment. Infrastructure administration stays outside the user workflow.
Compared with a VPS
You do not administer an operating system or receive host root. Datanode is narrower: one project scope with ready browser tools.
Compared with Codespaces
Datanode is not repository-first. Access is Telegram-bound and the workspace can start blank, from a template or from an imported repository.
Compared with Replit
The focus is a small isolated sandbox and transparent files, commands and publishing — not a broad collaborative application platform.
Who is it for?
Developers and learners building scripts, prototypes, Telegram bots, static pages and PHP sites who want browser access without managing a server.
One workspace · four surfaces
Less switching.
More building.
Every tool works against the same private file scope, so a change in the editor is immediately available to the terminal, file manager and published site.
Files
Your project, clearly organised.
Navigate folders, upload files up to 50 MB, rename, move and edit without leaving the browser.
public
index.php2 KB
assets
app.js8 KB
README.md1 KB
Click a row or expand a folder
Terminal
A real shell, kept inside the sandbox.
Run commands in a scoped session, pop it out full-screen and use mobile-friendly terminal controls.
Open terminal →Editor
VS Code in the browser.
Open the same workspace at editor.datanode.host with familiar editing, search and project navigation.
Open browser editor →Domain
Publish where your audience already looks.
Connect a hostname, verify DNS and serve a static or PHP project directly from your workspace.
Manage domain →A short path to useful
Request. Create.
Ship.
Datanode keeps account delivery, workspace setup and publishing understandable from the first Telegram message to the first live request.
Bind your account
Request access through the Telegram bot. One Datanode account stays linked to one Telegram identity.
Open Telegram bot →Choose a workspace
Start blank or pick a focused template. Your files and quota stay visible from the console.
Open workspace →Connect and publish
Point your domain, verify the connection and publish supported web projects from the same workspace.
Open Domain →A workspace that recognises you
One identity.
One luminous access key.
Your Telegram-bound account becomes the single key to the console, editor, terminal and published domain.
Start with the right shape
Templates that give you a useful first file.
Choose a starting point without locking the workspace down. Each template creates a practical structure you can inspect, change or replace.
Explore the consoleBlank workspace
A clean file scope for your own structure.
Node.js app
Package scripts, a public entry and API example.
Python app
A lightweight project structure ready for the terminal.
PHP Site
A publishable public directory and index file.
Security without mystery
Your workspace and your account both have boundaries.
Telegram binding controls identity delivery. Authenticator or a six-digit Telegram code adds a second confirmation path, while runtime commands remain scoped to the assigned sandbox.
One Telegram identity per accountOptional Authenticator protectionAccount-change notifications in Telegram
Your workspace is one message away
Build in your own space.
Put it on your own domain.
Request access in Telegram, then manage the whole workflow from one focused console.