Skip to content

Beta: these docs are still being updated. The next full update is on 18 November at 8 PM UTC. Docs in beta. Full update 18 Nov, 8 PM UTC.

Hoody.com

Lookup tables for Computers.

The label goes in the service position of a computer URL; N is the instance number. What each service does: The Hoody Kit.

ServiceURL label
Terminalterminal-N
Displaydisplay-N
Filesfiles-N
SQLitesqlite-N
Execexec-{execId} (a lowercase alphanumeric exec ID, such as exec-1 or exec-test)
Browserbrowser-N
Agentagent-N
Codecode-N
cURLcurl-N
Notificationsn-N
Daemonsdaemon-N
Croncron-N
Pipepipe-N
Notesnotes-N
Watchwatch-N
Runrun-N
Tunneltunnel-N
Proxy Logslogs-N
Egressegress-N (a bare egress means egress-1)
VMvm-N

Docker solved packaging; Hoody computers are full machines. Docker answers how to package and deploy an app. Hoody answers how to give someone a computer reachable from anywhere.

Docker containerHoody computer
What it isA process running from a filesystem imageA full Linux computer
Init systemNone (or an improvised PID 1)systemd
PersistenceEphemeral by default (volumes are add-ons)Persistent by default
NetworkShared bridge / host networkOwn network stack with own IP
ServicesOne process per Docker container (convention)The Kit services, plus anything you install
Accessdocker exec from the hostA URL, reachable from any network
StateDestroy and rebuildSnapshot, restore, branch
OSStripped-down layersFull Debian 13 with apt
PurposeShip softwareRun computers
Traditional VMHoody computer
AccessSSH, VNC, RDP (specialized clients)HTTPS (browser or curl)
Boot timeMinutesSeconds
OverheadFull OS + hypervisorLightweight
DensityLow (a full OS per VM)High
Idle resourcesHolds fixed resources whether you use it or not: a 2-core, 4GB VM costs the same idle as it does under loadComputers are not charged; they share their server’s capacity, and most Kit services start only on the first request to their URL
IsolationHardware-level (hypervisor)Computers are isolated from each other (details)
Built-in servicesNone; install everything yourselfThe Kit services, out of the box
EmbeddableNoYes; the Kit’s web pages embed as iframes (which ones)
AI-accessibleRequires SSH adapterNative; the interface is HTTP
SnapshotsDepends on the VM platform and storage; snapshots can share unchanged disk blocksFilesystem snapshots

Files written to disk persist through the normal lifecycle. Restoring a snapshot changes them, deleting the computer removes them, and a server reinstall (host_reinstalled) leaves them gone. /ramdisk is temporary: its contents are lost when the host server reboots. Every state, failed and copying included, is in lifecycle states.

StageWhat happensHow to
CreateOne POST to the API brings the computer up; its Kit URLs exist at once and answer once it is runningCreate, Edit, Delete
RunIt operates as a full Linux machine: install software, run servers, write code, train models. Files written to disk persist; /ramdisk is temporary
SnapshotCaptures files and configuration stored on disk, not RAM or running processes. Snapshots count toward your total storageSnapshots
StopThe computer halts and keeps its files, but running programs end (pause instead to keep them). Start it again, and your files are where you left themManaging Computers
PauseThe computer is suspended. Resume takes one to two seconds, and in-memory state survivesPause and resume
RestoreReverts the computer to any snapshot in one API callRestore a snapshot
CopyDuplicates the computer to another server or project. Cloning a development environment for a new team member is one API callCopy & Sync
DeleteDestroys the computer and its snapshots, and its service URLs no longer reach the computerDelete a computer