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.
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.
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
USCA2USFRDE3FIIN4SG
USUS West
CACanada
USUS East2
FRFrance
DEGermany
FIFinland3
INMumbai
SGSingapore4
1Free server: region preference, subject to capacity
+Your next server: pick a region
1Free
RegionRegion preference, subject to capacity
A slice of a shared machine
3 computers
2PlusUS
RegionUS East
A slice of a shared machine, paid users only
12 computers
3ProFI
RegionFinland
A slice of a shared machine, paid users only
30 computers
4Bare metalSG
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.
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.
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.
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.
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.
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.
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.
boot starts it with the computer. By default a later crash (nonzero exit) restarts it; one that crashes right at startup is retried a few times, then marked fatal.
pip install requests · boot starts it with the computer. By default a later crash (nonzero exit) restarts it; one that crashes right at startup is retried a few times, then marked fatal.
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 ↗
hoody / permissions
Your rules, enforced at the right layer
Tell your AI who gets access.
Your agent can configure permissions through the API. Describe who should get in, which computers they can use and what they may do. Share Bots only with people and apps you trust to steer them. Give each a named key you can pause, expire, restrict by IPv4 or revoke.
Lock each link.
Require a password, a Hoody login, your app’s login or an IP list. Choose the services and instances people can reach.docs / proxy / permissions ↗
Give tokens only what they need.
Set API permissions, expiration and allowed IPs. Give an AI read access without permission to change your computers.docs / api / auth tokens ↗
Keep each client in their realm.
A realm scopes the computers and projects an AI or client can see through the API. Network access has its own rules.docs / api / realms ↗
Example office IP and IDs. Your AI checks project and computer rules, then writes with the current If-Match version. This example assumes no other inherited access grants.
<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.
The building blocks, in plain English. Your AI combines them into countless more. Open a line for its link and what to say to your AI. Every row on one page
Hoody Chatbot
Answers from the Hoody FAQ
Answers come from the FAQ and capability index. No messages leave this page.
hoody / our story
From privacy to agentic infrastructure
We started with privacy.
Per-app VPNs, browsing containers that beat fingerprinting, SOCKS5 proxies. 20 people, $3.2M raised. The lesson: real privacy needs full isolation, so containers.
We started building with AI.
A model in a loop with end-to-end tests: write, test, fail, fix, repeat. Every core system was built this way.
Agents running agents.
Verification chains across repositories, and an anonymous AI gateway, because inference deserves privacy too.