Skip to content
Defaultdefault
Log out

Container

default

Pending

Project

Default

Hoody / first run

Server

node-sg-sin-1

Singapore

Plan

Free · shared compute · 20 GB disk

welcome / surfaces

Quick actions

Your first container is alive.

In Hoody, everything is HTTP — every container, every program, every port. Open it in a browser, hand it to an agent, or curl from anywhere.

Recommended

Open WorkspacesTerminalFiles

Your operating system in a browser tab.

Restart·Stop

workspaces

Open

:8080

workspaces is live now. :8080 is a template — works once you bind an HTTP server on that port inside your container.

Service URLs· 12 servicesPrimary
Treat these URLs like private share links — anyone holding the full URL can reach enabled routes. (Restrict in Workspaces ▸ Permissions.)
workspacesDrag-window OS — terminals, editors, agents
Open
terminalBrowser-based shell in your container
Open
filesBrowse, upload, edit, archive
Open
codeVS Code in the browser
Open
sqliteSQLite Studio — query, browse, visualize
Open
displayGUI apps streamed via X11
Open
notesReal-time collaborative notes (CRDT)
Open
browserHeadless Chrome (Playwright)
Open
agentHoody AI agent driving your container
Open
runSpawn, supervise, tail processes via HTTP
Open
tunnelExpose local ports / pull remote TCP
Open
nPush notifications (Web Push + internal)
Open
+ 7 headless HTTP servicesWant a second terminal? Bump the index. Each is its own session.
Port URLs· 4 examples
:8080any HTTP server you bind
:3000Next.js / Vite preview
:8443TLS upstream
sshSSH proxy into the container
Bind, share. No nginx, no DNS, no certs.
Control surfaces· 5 doors
Every surface below can access existing containers AND spawn new ones — same API, same auth, your choice of door.
WorkspacesUI for the whole platformOpen Workspaces
SSH$ ssh hoody.com
AIPaste @hoody.com into ChatGPT
curl$ curl https://api.hoody.icu/api/v1/…
SDK$ npm i @hoody-ai/hoody-sdk

Need a second container? Workspaces ▸ New container, or:

Sharing & permissions

IDs are unguessable (24-hex). Anyone holding the full URL can reach enabled routes — so treat URLs like private share links, not secrets.

Restrict per program, port, token, or IP — in Workspaces ▸ Permissions or via the proxy-permissions API.

Rent hardware, not a stack.

Run Hoody on dedicated bare metal when you outgrow shared compute. Rent hardware from Workspaces; Hoody runs the ops automatically — provisioning, networking, isolation, snapshots. You bring workloads.

Open Workspaces

Even Hoody OS — the dashboard you click into via Workspaces — runs inside a Hoody container, on your server.

Read the docs