Skip to content
Your AI@https://hoody.com Connect to Hoody

Dev mode

We kept it plain. Here is Hoody, concretely.

Every section now shows what Hoody literally is: links, calls and limits. Every building block is indexed on the home page. Your AI combines them into countless more.

Open the index

hoody / computers + kit

Computers + Kit

Full Linux computers, online.
Every tool inside has a link.

Each Hoody computer is a full Linux machine: Debian 13, systemd, its own files, network and processes. Run your apps on it, run Docker inside it, and, with the Hoody Kit, open its terminal, desktop, browser, editor, files and database at their own HTTPS links, for you, your team or your AI.

Nothing to install. Open the link and the tool is there, on a laptop, a phone or a TV.

Example views. The link below opens the tool itself, in any browser. Pick another tool and the same tab shows it.

One link per tool

Pick a tool, the link follows

https://p7-c2-terminal-1.n12.computers.hoody.com

p7projectc2computerterminaltool1instancen12server

+7
terminal-1A full Linux shell in any browser.Swap the tool word to reach another tool on the same computers. Change the 1 to a 2 for a second session that shares the same files.See it in the Kit ↓

In Dev

Link shape
https://{p}-{c}-{tool}-{n}.{node}.computers.hoody.comproject id, computer id, tool, instance, server; each part can be read or swapped on its owndocs / foundation / projects-computers
A port you run
https://{p}-{c}-http-8080.{node}.computers.hoody.coma site or app on port 8080, HTTPS included
Your computers
hoody computers listcolumns ID NAME STATUS IMAGE CREATED
Find the links
GET https://api.hoody.com/api/v1/computers/{id}returns project_id, id and server_name, the parts of every link
hoody / computers

Servers, computers, Kit

Servers in many countries.
Computers on every server.
The Kit in every computer.

An example with four servers. The free server has a region preference, subject to capacity. A Plus server runs in US East, a Pro server in Finland and a bare metal server in Singapore. Each server holds computers. Each computer has the Kit tools inside.
Where your servers run8 regions
  • USUS West
  • CACanada
  • USUS East
  • FRFrance
  • DEGermany
  • FIFinland
  • INMumbai
  • SGSingapore

Free server: region preference, subject to capacity

Your next server: pick a region

  1. 1Free

    RegionRegion preference, subject to capacity

    A slice of a shared machine

    3 computers

  2. 2Plus

    RegionUS East

    A slice of a shared machine, paid users only

    12 computers

  3. 3Pro

    RegionFinland

    A slice of a shared machine, paid users only

    30 computers

  4. 4Bare metal

    RegionSingapore

    A whole machine, only yours

    As many as it has room for

One computer, openedEvery computer has this

Kit

  • Terminal
  • Desktop
  • Code
  • Files
  • SQLite
  • Browser
  • More
  • ContainersEvery server
  • Virtual machinesBare metal only
Servers
Start with a free server. Each paid plan adds another one, in a region you pick. A server is a slice of a shared machine, or a whole machine that is only yours.
Computers
Each of your computers is a full Linux machine that keeps running and keeps its files. It can run containers of its own, and virtual machines on bare metal.
Kit
The Hoody Kit fills each computer with tools you open at a link, ready a moment after the computer starts.

Inside each of your computers

Debian 13 · systemd services · its own files, network and processes · keeps its state

01 / Work in it

  • AgentYour AI, next to your files, from browser or SSH.
  • TerminalA shell in any browser tab, shared by its link.
  • DesktopLinux apps in any browser, even on a TV.
  • CodeVS Code in a browser tab.

02 / Build and run

  • Exec scriptsA function in a file is a live endpoint.
  • DaemonsKeeps servers and workers running.
  • CronScheduled jobs, with an end date if you want.

03 / Data and the web

  • FilesYours, plus Drive, Dropbox, S3 and more.
  • SQLiteDatabases with no server to run.
  • BrowserChromium or Firefox your AI can drive.Every tool, with its link ↓

04 / How a link reaches your app

Every link goes through the Hoody Proxy, on the same server as your computers. It adds HTTPS, checks who may enter, and hands the request to the tool or app inside.

https://p7-c2-
http-3000

http-3000 is your own app, listening on port 3000 inside the computer. Change the number for another app: http-5000, http-8000.

Outside, it is always HTTPS on port 443. The proxy hands each visit to your port.

docs / proxy ↗
.n12.computers.hoody.com
Hoody Proxy

It runs on the same server as your computers, so there is no extra network hop and your traffic stays on your server. Certificates are issued and renewed for you.

Speaks HTTP/1.1, HTTP/2 and WebSocket (live terminals and desktops use it), plus HTTP/3 where the server supports it.

docs / concepts / proxy ↗
Real visitor IP

For external requests routed directly by Hoody Proxy, your app sees each visitor's real IP address, as if there were no proxy in between. No X-Forwarded-For header to read.

It happens in the server's kernel, so any program, even old software, can log, rate-limit and block the visitor. Nothing to configure. Requests forwarded by proxy hooks show the hook's connection address instead. Calls from Hoody computers can show a different source address.

docs / concepts / proxy ↗
Who gets in

Lock any link with a password, sign-in tokens or a list of allowed IP addresses, for a whole project or for one computer.

docs / proxy / permissions ↗
Proxy hooks

Your own script sees each request first: check it, change it, answer it, or pass it on. It runs in your own Exec, never next to anyone else's.

docs / proxy / hooks ↗
Your names

Give a tool or app a short name, like my-api.n12.computers.hoody.com, or point a domain you own at it. The certificate is issued and renewed for you.

docs / proxy / your domain ↗
Local tunnel

Show an app running on your laptop at your computer's public link, or let your computers reach a service on your laptop.

Your laptop dials out, so it never accepts an incoming connection, and there is no DNS, certificate or sign-up step.

docs / kit / tunnel ↗
Going out

The other direction, separate from the proxy above: requests your computers send can leave through an upstream SOCKS5 or HTTP proxy you choose, to change the IP they come from.

docs / kit / egress ↗

Also runs inside

Containers

Docker, Compose and Buildx come ready with the dev kit, which is on by default. Kind, K3s and Minikube run full Kubernetes clusters, and Podman works too.

On every server.

docs / computers / images ↗
Virtual machines

Turn on KVM and boot another operating system or kernel inside one of your computers.

Dedicated bare-metal servers you rent only. Off by default, and not on the free tier.

docs / servers / virtual machines ↗
More computers

No price per computer: create as many as your server's plan and capacity allow, and copy one to another server or project in one call.

Free includes 3 computers.

docs / servers ↗

every serverdedicated bare metal only

In Dev

Your app on port 3000
https://{p}-{c}-http-3000.{node}.computers.hoody.comhttp-{port} routes to the app on that port; outside it is HTTPS on 443docs / foundation / proxy
Real visitor IP
req.socket.remoteAddressin Node, the visitor's IP; in Exec scripts, metadata.clientIpdocs / concepts / proxy
Run a command
POST https://{p}-{c}-terminal-1.{node}.computers.hoody.com/api/v1/terminal/executebody {"command": "docker ps", "wait": true}docs / kit / terminals
Turn on KVM
PUT https://api.hoody.com/api/v1/computers/{id}/kvmbody {"kvm": true}; computer stopped, dedicated server onlydocs / foundation / servers / virtual-machines
hoody / managed

The foundation under your work

Managed, top to bottom.

Hoody runs the infrastructure and gives you the tools to keep your work running inside it. Build your sites, apps and workflows without babysitting servers.

01 / The servers

Bare metal.
Hoody handles it.

Bare metal from OVHcloud and Hetzner, fully run by Hoody. Security and kernel updates are on Hoody, with no provider account or server setup for you.

Explore the infrastructure ↗
You build onFull Linux computers

Debian 13, root access, persistent storage. Docker and Compose are ready inside.

docs / computers / images ↗

02 / The computers on them

Apps restart after a crash.
Run servers and workers as daemons with an automatic restart policy.docs / kit / daemons ↗
Save a version. Go back.
Take snapshots before changes and restore the saved disk state. Running processes and memory start fresh.docs / computers / snapshots ↗
Close the tab. Work keeps running.
Your computers stay on. Files, settings and databases persist when you leave.
The services are already connected.
Open the Kit at its HTTPS links. Your apps get links too, with certificates handled by Hoody.
hoody / inside your computers

Inside your computers

The Kit comes with them.

Terminals, files, browsers, data and your AI, already inside your computers. Open a service at its link. Use the same permissions model across them.

Choose See it for an example.
Every link is also an API.
Your AI can use it too.

{p} project ·{c} computer ·{node} serverLink shapes, with placeholder IDs

Terminal

Run commands and share a persistent shell session.

https://{p}-{c}-terminal-1.{node}.computers.hoody.com
POST /api/v1/terminal/execute

Display

Open Linux applications in your browser.

https://{p}-{c}-display-1.{node}.computers.hoody.com
GET /api/v1/display/screenshot

Browser

Drive Chromium or Firefox over HTTP.

https://{p}-{c}-browser-1.{node}.computers.hoody.com
GET /api/v1/browser/snapshot

Code

Use VS Code from a browser tab.

https://{p}-{c}-code-1.{node}.computers.hoody.com
https://{p}-{c}-code-1.{node}.computers.hoody.com/?folder=<path>

Files

Browse, edit and download your files by link.

https://{p}-{c}-files-1.{node}.computers.hoody.com
GET /api/v1/files/{path}

SQLite

Query SQL databases and key-value data over HTTP.

https://{p}-{c}-sqlite-1.{node}.computers.hoody.com
POST /api/v1/sqlite/db

Exec

Turn JavaScript or TypeScript files into HTTP endpoints.

https://{p}-{c}-exec-1.{node}.computers.hoody.com/{script}
GET /{script}

Agent

Work with the same AI session from web, SSH or CLI.

https://{p}-{c}-agent-1.{node}.computers.hoody.com
hoody agent prompt "<task>" -c <id>

Curl

Make HTTP requests into links you can share or schedule.

https://{p}-{c}-curl-1.{node}.computers.hoody.com
POST /api/v1/curl/request

Daemons

Keep servers and workers running, with automatic restarts.

https://{p}-{c}-daemon-1.{node}.computers.hoody.com
POST /api/v1/daemon/programs/add

Cron

Schedule commands, with optional job expiration.

https://{p}-{c}-cron-1.{node}.computers.hoody.com
POST /api/v1/cron/users/{user}/entries

Notifications

Send desktop alerts or relay them to an open browser page.

https://{p}-{c}-n-1.{node}.computers.hoody.com
POST /api/v1/notifications/notify

Pipe

Stream bytes between devices through a named link.

https://{p}-{c}-pipe-1.{node}.computers.hoody.com/api/v1/pipe/{name}
PUT /api/v1/pipe/{name} · GET to receive

Egress

Use your computers as proxies, or set an upstream proxy.

https://{p}-{c}-egress-1.{node}.computers.hoody.com
GET /api/v1/egress/upstream

Tunnel

Expose local web apps or reach local TCP services.

https://{p}-{c}-tunnel-1.{node}.computers.hoody.com
https://{p}-{c}-http-{port}.{node}.computers.hoody.com

Program limits

Confine a daemon: read-only files, port and process limits, its own firewall.

https://{p}-{c}-daemon-1.{node}.computers.hoody.com
POST /api/v1/daemon/programs/edit/{id}

Most services start when first opened. Program limits belong to Daemons. Also included: Notes, Watch, Run and Proxy Logs.

docs / kit
hoody / do it directly

From an idea to a request

Do it directly, three ways.

The same action, over HTTP, from your terminal or in TypeScript. Or say what you need and let your AI make the calls.

Run a command on your computers and get its output and exit code back.

HTTP request / Terminal
POST https://{p}-{c}-terminal-1.{node}.computers.hoody.com/api/v1/terminal/execute
Content-Type: application/json

{
  "command": "ls -la /app",
  "wait": true
}

Runs in terminal 1. The response contains the command output.

docs / kit / terminals ↗
Before you use this example

Replace {p}, {c} and {node} with your project ID, computer ID and server name. Kit requests use the proxy credentials you configure.

Account API requests use Authorization: Bearer <token>.
Service requests use your link's proxy permissions.
docs / proxy / permissions ↗

Or just ask your AI

Run ls -la /app on my Hoody computers and show me the output.

Hoody AI (free) is built in. You can also use your ChatGPT plan (via Codex sign-in) or Claude Pro or Max. Give your AI the Hoody Skill ↗

Start free, in one line.

Free to start with no card: Hoody AI is built in, and the AI you already use works too.

No code
Code
Your AI@https://hoody.com Connect to Hoody

Works in ChatGPT, Claude or any AI that can fetch a page. Copy it and paste it in.

Your AI
@https://hoody.com Connect to Hoody
docs / foundation / agent-skill-bundle
Browser
https://hub.hoody.com
docs / kit / agent
Terminal
ssh hoody.comAny machine with an ssh client, in an interactive terminal. Nothing to install.
docs / kit / agent
Skill
npx skills add https://hoody.com/SKILLS/SKILL.mdnpx skills add HoodyNetwork/hoody-sdkThe second one adds every docs page on disk, for offline use.
docs / foundation / agent-skill-bundle
CLI
npm install -g hoody-sdkcurl -fsSL https://install.hoody.com | shThe second one is for Linux and macOS. Without installing: npx hoody-sdk <command>
docs / foundation / cli
SDK
npm install hoody-sdkTypeScript. Node.js 20.19 or newer, Bun, Deno.
docs / getting-started / quickstart
HTTP API
curl -H "Authorization: Bearer <token>" https://api.hoody.com/api/v1/computers/
docs / api / authentication
Browser SDK
<script src="https://cdn.jsdelivr.net/npm/hoody-sdk/dist/hoody-sdk.browser.min.js"></script>Exposes window.HoodySDK. Pin a version for production, and give pages short-lived scoped tokens.
docs / getting-started / quickstart

Since 2021

From privacy to agentic infrastructure

hoody / kit

What your computers come with

Every service has its own link. Open it, share it, or hand it to your AI. Anyone with the link can open it until you lock it. Kit links have the shape https://{p}-{c}-<kit>-1.{node}.computers.hoody.com: {p} is your project, {c} one of your computers, {node} its server.

Computers

Bots

API