Skip to content

Three commands. That’s all it takes.

In the next 5 minutes, you’ll spawn a computer, run code on it, and share it with a URL. No installation. No configuration. No deployment step. Just HTTP.

Or skip all of this and just:

Terminal window
ssh hoody.com

That’s it. Full Hoody OS in your terminal. From any device, anywhere. But let’s start with the API approach first.


Sign up at hoody.icu and grab your API token from the dashboard. This token authenticates every request you make.

Terminal window
# Install the Hoody SDK (includes CLI)
npm install -g @hoody-ai/hoody-sdk
# Authenticate
hoody auth login

A project organizes your containers. A container is a full Linux computer — Debian 13, systemd, the works — already online the moment it’s created.

Terminal window
# Create a project
hoody projects create --alias "my-first-project"
# Spawn a container (a full Linux computer)
hoody containers create --project $PROJECT_ID --server-id $SERVER_ID --name "dev-box"

Your container has the full Hoody Kit HTTP service stack built in — terminal, files, exec, sqlite, cron, pipe, browser, code, displays, daemon, notifications, tunnel, workspaces, curl, ssh, proxy, plus dynamic http/https ports. Let’s use a few:

Terminal window
# Execute a shell command on your container
hoody terminal sessions exec --ephemeral --command "echo 'Hello from the cloud!'"
Terminal window
# Read a file from your container
hoody files get /etc/hostname
Terminal window
# Run a SQL query on the built-in SQLite
hoody db exec-transaction --db app --create-db-if-missing --transaction '[{"statement":"CREATE TABLE greetings (message TEXT)"},{"statement":"INSERT INTO greetings VALUES ('"'"'Hello, Hoody!'"'"')"},{"query":"SELECT * FROM greetings"}]'

You’ve been using the API directly. Now open the visual experience — Hoody OS.

Hoody OS is a full web-based operating system that lives inside each of your containers — every container you spin up gets its own OS, on a server you own. It’s served by the workspaces service:

  • Hoody Workspaces (https://{projectId}-{containerId}-workspaces-1.{server}.containers.hoody.icu) — A floating-window desktop where you arrange terminals, code editors, displays, files, and AI agents side by side. The Home dashboard and Console management views are apps inside this workspace, navigated to via in-app paths rather than separate service subdomains.

Every app is a URL. Open it in any browser. Embed it in an iframe. Share it with a teammate. Control it via AI agent. The URLs just work — HTTPS with HTTP/2 and HTTP/3, zero configuration, zero certificates to manage. Ever.

Screenshot Needed Hoody OS — Workspaces view showing floating windows: terminal, code editor, file browser, AI chat, and live display preview
Hoody OS: Your entire computing environment in a browser tab

The inception: Hoody OS itself runs on a Hoody container. The OS that manages your containers is running in a container. It’s embeddable, shareable, and multiplayer — just like everything else.

Open your Workspace URL in any browser. Phone, laptop, TV, tablet — same environment, same state.

Terminal window
ssh hoody.com

Full Hoody OS as a TUI (Terminal User Interface). We built an entire browser engine for the terminal (hoody-terminal-browser), so you get the same OS experience — floating windows, AI chat, file management — rendered in pure text. Access from literally anything that supports SSH: a Raspberry Pi, an ESP32 (we won’t judge), a server with no GUI, or your phone’s terminal app.

Screenshot Needed Hoody OS via ssh hoody.com — TUI interface showing the same floating windows rendered as terminal characters
ssh hoody.com — The exact same OS, but for your terminal

No per-machine SSH key upload required for this gateway — it opens a Hoody login screen (the same one you see in a browser) inside the TUI as soon as you connect. This is distinct from container SSH, which uses per-container public keys and the ssh.$serverName.containers.hoody.icu gateway — see Networking → SSH for container shell access.


You just:

  1. Spawned a full Linux computer — not a VM, not a Docker container, a real isolated system
  2. Ran commands on it via HTTP — no SSH, no keys, no client software
  3. Read files and queried a database — all through URLs
  4. Made it accessible from anywhere — it was already online from the moment it was created

This is the HTTP revolution. Every program, every file, every process is a URL.


Understand Containers

Learn what makes Hoody containers different from everything else. Containers →

Explore the Kit

Discover all 18 HTTP services built into every container. The Hoody Kit →

Build Something Real

Follow a guide to build a full-stack app, deploy AI agents, or vibe code. Guides →