# Computers reference **Page:** concepts/computers/reference [Download Raw Markdown](./concepts/computers/reference.md) --- # Computers reference Lookup tables for [Computers](/concepts/computers/). ## Kit service URL labels The label goes in the service position of a computer URL; `N` is the instance number. What each service does: [The Hoody Kit](/kit/). | Service | URL label | | :--- | :--- | | [Terminal](/kit/terminals/) | `terminal-N` | | [Display](/kit/displays/) | `display-N` | | [Files](/kit/files/) | `files-N` | | [SQLite](/kit/sqlite/) | `sqlite-N` | | [Exec](/kit/exec/) | `exec-{execId}` (a lowercase alphanumeric exec ID, such as `exec-1` or `exec-test`) | | [Browser](/kit/browser/) | `browser-N` | | [Agent](/kit/agent/) | `agent-N` | | [Code](/kit/code/) | `code-N` | | [cURL](/kit/curl/) | `curl-N` | | [Notifications](/kit/notifications/) | `n-N` | | [Daemons](/kit/daemons/) | `daemon-N` | | [Cron](/kit/cron/) | `cron-N` | | [Pipe](/kit/pipe/) | `pipe-N` | | [Notes](/api/notes/) | `notes-N` | | [Watch](/api/watch/) | `watch-N` | | [Run](/api/run/) | `run-N` | | [Tunnel](/kit/tunnel/) | `tunnel-N` | | [Proxy Logs](/api/proxy-logs/) | `logs-N` | | [Egress](/kit/egress/) | `egress-N` (a bare `egress` means `egress-1`) | | [VM](/kit/vm/) | `vm-N` | ## Computer or Docker container 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 container | Hoody computer | | :--- | :--- | :--- | | **What it is** | A process running from a filesystem image | A full Linux computer | | **Init system** | None (or an improvised PID 1) | systemd | | **Persistence** | Ephemeral by default (volumes are add-ons) | Persistent by default | | **Network** | Shared bridge / host network | Own network stack with own IP | | **Services** | One process per Docker container (convention) | The [Kit services](/kit/), plus anything you install | | **Access** | `docker exec` from the host | A URL, reachable from any network | | **State** | Destroy and rebuild | Snapshot, restore, branch | | **OS** | Stripped-down layers | Full Debian 13 with apt | | **Purpose** | Ship software | Run computers | ## Computer or VM | | Traditional VM | Hoody computer | | :--- | :--- | :--- | | **Access** | SSH, VNC, RDP (specialized clients) | HTTPS (browser or curl) | | **Boot time** | Minutes | Seconds | | **Overhead** | Full OS + hypervisor | Lightweight | | **Density** | Low (a full OS per VM) | High | | **Idle resources** | Holds fixed resources whether you use it or not: a 2-core, 4GB VM costs the same idle as it does under load | Computers are not charged; they share their server's capacity, and most Kit services start only on the first request to their URL | | **Isolation** | Hardware-level (hypervisor) | Computers are isolated from each other ([details](/concepts/security/reference/#computer-isolation)) | | **Built-in services** | None; install everything yourself | The Kit services, out of the box | | **Embeddable** | No | Yes; the Kit's web pages embed as iframes ([which ones](/kit/reference/#embedding)) | | **AI-accessible** | Requires SSH adapter | Native; the interface is HTTP | | **Snapshots** | Depends on the VM platform and storage; snapshots can share unchanged disk blocks | Filesystem snapshots | ## Lifecycle stages 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`](/foundation/storage/ramdisk/) is temporary: its contents are lost when the host server reboots. Every state, `failed` and `copying` included, is in [lifecycle states](/foundation/computers/create-edit-delete/reference/#lifecycle-states). | Stage | What happens | How to | | :--- | :--- | :--- | | **Create** | One POST to the API brings the computer up; its Kit URLs exist at once and answer once it is `running` | [Create, Edit, Delete](/foundation/computers/create-edit-delete/) | | **Run** | It operates as a full Linux machine: install software, run servers, write code, train models. Files written to disk persist; `/ramdisk` is temporary | | | **Snapshot** | Captures files and configuration stored on disk, not RAM or running processes. Snapshots count toward your total storage | [Snapshots](/foundation/computers/snapshots/) | | **Stop** | The 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 them | [Managing Computers](/foundation/computers/managing/) | | **Pause** | The computer is suspended. Resume takes one to two seconds, and in-memory state survives | [Pause and resume](/foundation/computers/managing/#pause-and-resume) | | **Restore** | Reverts the computer to any snapshot in one API call | [Restore a snapshot](/foundation/computers/snapshots/#restore-a-snapshot) | | **Copy** | Duplicates the computer to another server or project. Cloning a development environment for a new team member is one API call | [Copy & Sync](/foundation/computers/copy-sync/) | | **Delete** | Destroys the computer and its snapshots, and its service URLs no longer reach the computer | [Delete a computer](/foundation/computers/create-edit-delete/#delete-a-computer) |