use-cases / forty-client-sites-one-rent / hero

CONTAINERS · WORKSPACES · AGENCY FLEET

Forty client sites. One rent. One dashboard.

Every client site is its own isolated container — files, processes, ports, hostname. They all live on one bare-metal server you rent once. You open one Hoody Workspace and see the whole roster as tiles. Click a tile, you're inside.

Read the containers guide

agency.containers.hoody.com · clients

https://agency.containers.hoody.com/clientslive · 40/40 up

clients40

server1

you payflat-rate

saved / mo$1.5k–2.3k

.net

bayside-dental2d

.com

north-loop-pizza5d

.com

gallagher-law8d

.com

verde-yoga11d

.com

lakeside-realty14d

.net

harborview-cpa17d

.com

ridgepoint-vet20d

.org

millcreek-bakery2d

.com

stonepark-school5d

.com

ironhill-press8d

.net

auburn-roofing11d

.com

cedar-coffee14d

.com

westside-physio17d

.com

blue-fox-design20d

.org

pinegrove-hotel2d

.net

sunset-marina5d

.com

fairmont-clinic8d

.com

rosewood-spa11d

.com

halecorp-hr14d

.com

delaney-electric17d

.net

northstar-credit20d

.org

mariposa-cafe2d

.com

elm-street-flowers5d

.com

valley-brew8d

.com

kingfield-academy11d

.net

summit-orthodontics14d

.com

windsor-tailors17d

.com

anchor-supply20d

.org

porter-and-sons2d

.com

hilltop-church5d

.net

mainline-tax8d

.com

broadway-cleaners11d

.com

winterhaven-inn14d

.com

saltbox-studio17d

.com

rivermark-bank20d

.net

oakridge-pharmacy2d

.com

quincy-foods5d

.com

harvest-moon-co8d

.com

ember-fitness11d

.com

midtown-music14d

ROSEWOOD-SPA · IN FOCUSclick any tile to enter the container

host halecorp-hr.comip 10.10.0.118cid 507f1f77bcf86cd

WORKSPACE ISOLATION · 4 OF 40 SHOWNhost: bare-metal-01

WORKSPACEbayside-dental

WORKSPACEnorth-loop-pizza

WORKSPACEgallagher-law

WORKSPACEverde-yoga

each client gets its own files, processes, ports, hostname — kernel namespaces, not a WHERE clause

one workspace · forty containers · one host · one bill

use-cases / forty-client-sites-one-rent / mechanism

How forty fits in one

Three things have to be true at once for this to actually work — not just on a slide deck. Containers give you the isolation. The host gives you the density. Workspaces give you the single pane of glass.

ONE CONTAINER PER CLIENT

Isolation by namespace

Each client site is a Hoody container with its own filesystem, process tree, network namespace, and DNS hostname. A POST request to /api/v1/projects/[id]/containers spawns it from a base image; a DELETE removes it cleanly when the contract ends. Nothing leaks between clients.

ONE SERVER UNDERNEATH

Density on shared metal

All forty containers sit on one bare-metal box. The kernel deduplicates shared memory pages and the filesystem stores deltas, not copies, so the thirty clients sitting idle most of the day cost almost nothing on top of the server you already rent.

ONE WORKSPACE ON TOP

All clients in one tab

Open app.hoody.com, log in, and the whole roster shows up as tiles in a single Workspace. Click a client and you're inside that container — terminal, files, code editor, browser preview — without juggling forty Vercel projects or forty SSH keys.

Containers do the isolation. The host does the density. The Workspace does the management. The agency principal sees one screen, not forty dashboards in forty browser tabs.

use-cases / forty-client-sites-one-rent / economics

The math finally works

Per-site hosting is linear in dollars. Per-server hosting is bounded. The shape change shows up most clearly when you stop paying for clients who haven't deployed in three weeks.

WHAT YOU PAY FORBEFORE · PER SITENOW · PER SERVER

hosting bill40 × $40–60/site1 × flat-rate server

idle clientsstill billedno extra cost

deploy targets40 dashboards1 workspace

vendor accounts40 invoices1 invoice

Per-site numbers reflect public list pricing on Vercel Pro, Netlify Pro, and similar tiers; actual agency bills vary by traffic and add-ons. Hoody bare-metal entry pricing starts at $29/month for an entry box; mid-range fleet hosts cost more (final price varies by spec, region, and rental duration). Density depends on workload — forty static-leaning client sites pack comfortably; a fleet of database-heavy SaaS apps wants more headroom.

use-cases / forty-client-sites-one-rent / isolation

Why this isn't "shared hosting"

The shape looks like classic cPanel — many sites, one box. The mechanism is nothing like it. Containers give every client a real Linux instance, not a virtualhost line.

BLAST RADIUS

A hacked client can't breathe on the next one

Each container has its own root filesystem, its own process namespace, its own user accounts. A compromised WordPress site can't read another client's wp-config.php, can't see another client's processes, can't exhaust another client's CPU quota. The kernel enforces it.

BILLING SHAPE

Charge per client, pay per box

You keep billing your clients per site — that's what they understand. Underneath, you pay one server bill. The margin used to disappear into hosting line items; now it stays in the agency. Onboard the forty-first client and the box doesn't notice.

OFFBOARDING

Delete a client cleanly

When a contract ends, one DELETE /api/v1/containers/[id] removes the filesystem, processes, scheduled jobs, environment variables, and SSH keys. No leftover droplet rotting in DigitalOcean. No half-uninstalled WP Engine site. The client's footprint is gone.

use-cases / forty-client-sites-one-rent / punchline

Forty clients used to be forty invoices. Now it's one server and a folder.

before · the per-site shapeafter · the per-server shape

FORTY INVOICES

one bill per client, every month, in forty different vendor portals

ONE SERVER · ONE FOLDER

1 × bare-metal host1 × workspace · 40 tiles

the rent is paid once · the roster lives in one tab

Read the workspace docs

use-cases / forty-client-sites-one-rent / replaces

What this replaces

The standard agency stack is a tower of per-site billing — one vendor for static sites, another for WordPress, another for the droplet that runs the legacy PHP nobody touches. Forty clients used to mean forty rent bills. The container model collapses them:

Vercel client tier (per-project)Pricing scales with project count and team seats
Netlify per-site billingOne bill per site, even when the client is asleep
DigitalOcean droplet-per-client$6–24/mo each, idle or not, plus a snapshot bill
WP Engine per-install plansFlat per-install fee on top of the agency seat
Cloudways (per-application)Per-app surcharges stack on top of the server
Custom shared-hosting setupsReal isolation costs an afternoon every time it breaks

use-cases / forty-client-sites-one-rent / cta

Stop paying forty rents to host forty clients. Pay one rent and host the agency.

Read the containers guide

use-cases / forty-client-sites-one-rent / related

Read the others

Sixty containers on one server

One bare-metal box runs dozens to hundreds of Hoody containers. KSM and BTRFS dedup make the marginal cost near zero.

Containers·Snapshots

Onboard a developer with one link

A new engineer joins on Monday. You send one URL. They open it on whatever laptop they have and they're in a fresh container cloned from your developer-baseline snapshot — code, deps, env, seed data, VSCode-in-browser. Writing code in five minutes, not setting up.

Snapshots·Containers·Terminal·Files

API endpoints that materialize on demand

A wildcard exec script catches the call, asks an LLM to write the handler, runs it in a V8 sandbox, and saves the route. The next call is native.

Exec·Agent·Code·Files

Branch computers like Git

Snapshot a running container — files, processes, memory. Restore in seconds. Fork via /copy. Branching, but for the entire machine.

Snapshots·Containers

Real VS Code on your phone

The Code Orchestrator spawns a VS Code instance on the container and serves the editor over a normal HTTPS URL. Any device with a browser can open it. The work lives in the container, not on the device.

Display·Terminal·Files·Containers+1

AI agents that spawn other AI agents

A research agent posts to /api/v1/projects/$PID/containers to start a child container, then calls the child's agent URL like any other HTTP service. Sub-agents spawn their own sub-agents the same way. No orchestrator framework, just URLs.

Agent·Exec·Containers

One sandbox per customer, automatically

An exec script catches your signup webhook, copies a fresh-customer container, and hands the new tenant their own URL. Isolation is the operating system, not a tenant_id column.

Containers·Snapshots·Exec·Files

Wake up to a finished prototype

Hand the agent a paragraph at midnight. It spawns its own containers, snapshots before risky steps, and posts to your notification webhook at sunrise.

Agent·Snapshots·Containers·Browser+2

Emergency production fix from your phone

PagerDuty wakes you. Open the terminal URL on your phone. PATCH the snapshot from before the bad deploy. Production is back. No bastion, no VPN, no laptop.

Terminal·Snapshots·Network

Tail production logs to a URL anyone can curl

One pipe URL. Up to 256 readers. Three engineers tail the same incident at once with no bastion, no Datadog seat, no log forwarder.

Pipe

Push one build to thirty CI workers at once

The build container streams the tarball to a pipe path with ?n=30. All thirty test workers curl the same URL. Bytes go through once, fanned out.

Pipe

Watch your agent think from the coffee shop

Your agent runs at home. You're at a café. Pipe each event of the loop through Hoody Pipe and curl the same path from your phone — the trace lands character by character. No SSH, no dashboard, no upload.

Pipe·Agent

Move 200GB between clouds with two curls

pg_dump | gzip | curl from Frankfurt. curl | gunzip | psql in Singapore. Bytes flow through the pipe with zero disk in the middle.

Pipe

Send a teammate a database state in one line

pg_dump streams straight into their psql. No file uploaded, no link shared, no download. The pipe routes the bytes through.

Pipe

Stream LLM tokens to anything that reads HTTP

Step 3 streams tokens with curl -T -. Step 4 curls the same path. Tokens move generator to consumer at line speed. No SSE plumbing, no broker.

Pipe·Agent

A progress bar your boss can spectate without joining

Append ?progress to the pipe URL. Anyone who opens it gets a live HTML dashboard — bytes, speed, ETA, state. Up to fifty spectators, none consuming a receiver slot, none touching the stream.

Pipe

The webhook fan-out you didn't have to build

Stripe POSTs to a pipe path with ?n=12. Twelve subscribers curl the receiver URL with ?n=12. The pipe holds the event until everyone is connected.

Pipe·Exec

A CI cache that's just two curl commands

tar | zstd | curl puts node_modules into a pipe. Twenty downstream jobs curl | zstd -d | tar x. No S3 bucket, no cache action, no egress bill.

Pipe·Containers

Drag-drop uploads into your script

hoody-pipe serves a web upload form at every path. Drag a file onto the page, your script reads the bytes from stdin. Zero upload code, no S3 bucket, no presigned URLs.

Pipe·Exec

Broadcast a workshop to 200 viewers from your laptop

ffmpeg streams your screen to a pipe path with ?n=200. Each attendee curls the URL into a browser tab. No platform, no logins, no upload.

Pipe

Inter-container IPC without the message broker

Container A writes to a pipe path. Container B reads from the same path. Backpressure is the connection. No Redis, no queue, no broker.

Pipe·Containers

Tail your agent on the train, get pinged when it lands

The agent streams its trace to a pipe path you can curl from your phone. When it finishes, its last act hits hoody-notifications and your phone buzzes. Two URLs and a buzz — no SDK, no client app, no dashboard.

Pipe·Agent·Notifications

A microphone over HTTP, in two terminals

ffmpeg captures the mic, pipes to a URL. The other end curls and plays the audio. No Zoom, no SDK, no signaling server.

Pipe

Five agents, five pipes, one verdict

A panel of five models reviews the same input. Each runs in its own container and streams its verdict to its own pipe path. A judge process curls all five in parallel and tallies the result.

Pipe·Agent·Containers

Replay this morning's incident to the whole team

Snapshot the incident-time logs in hoody-files. Replay them through a Hoody Pipe URL with ?n=8. Eight engineers curl the same path and watch the cascade fire in lockstep — the post-mortem is a synchronized stream, not a Confluence doc.

Pipe·Files

The fastest 'send me that file' you've ever typed

A teammate pings for a 4 GB dump. Slack rejects it, Drive needs a share request. You type curl -T file …; they type curl … > file. The bytes move directly between disks — no upload bar, no link to share.

Pipe

Run a local LLM, serve it to your whole fleet

One GPU runs llama.cpp. Its tokens stream into a pipe path with ?n=50. Fifty containers curl the same URL and split the stream.

Pipe·Daemon

A live metrics dashboard with no metrics backend

Each container's monitoring loop curls a metric to a pipe URL. The dashboard curls the same URL with ?progress and renders the SSE stream.

Pipe

The cron job that deletes itself when you're done

POST a managed cron entry with expires_at set 48 hours out. The job runs on schedule, then removes itself — no reminder, no cleanup PR, no stale entry.

Cron

Snapshot the container right before the nightly migration

A hoody-cron entry that fires at 02:55 UTC, curls the snapshots URL, and names the artifact pre-migration-2026-05-04. Five minutes later the migration runs. If it succeeds, the snapshot sits idle and costs nothing. If it fails, you restore in 30 seconds with a single PATCH.

Cron·Snapshots

A separate crontab for every customer, automatically

Each tenant gets their own container and their own hoody-cron service. Customer A's 9am digest fires on time even when customer B's job hangs for 40 minutes, because they aren't on the same crontab.

Cron·Containers

Wake an agent at 3am, retire it at 4

A nightly cron POSTs a spawn request, the agent does its hour of work, then a second cron tears the container down. The agent exists only when there is work for it to do.

Cron·Agent·Containers

Daily rollups without an orchestrator

Raw events pile up in a sqlite URL. Every night a cron entry curls an exec endpoint, the script runs the rollup SQL, writes the daily table back. No DAG, no Airflow Postgres, no scheduler dashboard.

Cron·SQLite·Exec

A crontab per branch, deployed with the code

Your repo checks in `.hoody/crontab`. The deploy script PUTs that file to the new container's Cron API. Each branch gets its container, its filesystem, its schedule.

Cron·Containers

On-call escalation that ages out with the shift

POST a cron entry with expires_at = shift end. When the shift ends, the entry deletes itself. The next on-call posts their own.

Cron·Notifications

Hourly scrape, daily digest, weekly archive — one container

Three lines in one crontab: hourly browser scrape into SQLite, daily exec digest, weekly archive to files. Flat-rate server, three rhythms, no scheduler service.

Cron·Browser·SQLite·Files

Let your customers BYO their own cron schedule

Customers POST their own 5-field expressions; their crontab lives in their container, isolated. You don't validate against a global queue.

Cron·Containers

Schedule the agent, not the script

A 5-field cron entry curls hoody-agent with a prompt instead of running a fixed script. Today is the last day of the month — the agent figures it out. The data shape changed — the agent figures it out.

Cron·Agent

A heartbeat for the silent jobs

Each cron run POSTs a heartbeat to a notifications endpoint. A second cron checks last-heartbeat and pages on silence. Silence is the alert.

Cron·Notifications

Keep the last 24 hours as 24 snapshots

An hourly cron POSTs a snapshot named with the hour. After 24 hours each new snapshot overwrites yesterday's at the same hour. The 24-floor time machine.

Cron·Snapshots

Replay this morning's webhooks at the same time tomorrow

You captured 30 minutes of real Stripe traffic into a hoody-files folder. One cron entry replays it against staging at 9am every weekday — same volume, same payloads, same time-of-day pressure.

Cron·Files·Exec

Edit your crontab from a phone, in the airport

Open the cron URL on your phone in the gate area. Tap a row, change a single field of the cron expression, hit Save. PATCH lands. The job fires tonight on the new schedule. No SSH session, no jump box, no laptop.

Cron·Terminal

A scheduled digest that fans out to 200 inboxes

Cron at 9am POSTs to an exec script that builds the digest and curls a pipe URL with ?n=200. Two hundred recipients hit the same URL once.

Cron·Exec·Pipe

Mute the flaky job without losing it

PATCH /entries/[id] [ enabled: false ]. The job stays in your crontab waiting to be fixed. No deletion, no rewrite, no lost context.

Cron

An agent that grades yesterday's agents

A nightly cron POSTs to the supervisor agent with yesterday's agent traces from SQLite. The supervisor scores each one. Cron is the supervisor.

Cron·Agent·SQLite

Cleanup jobs that schedule their own retirement

The cleanup script checks if there's anything left to clean. When the directory is empty, it DELETEs its own cron entry. Job's done, job's gone.

Cron·Files

Roll your TLS certificates without an SSH session

Cron weekly: POST to an exec script that runs certbot, posts the new cert to the proxy via PATCH. No shell session, no key, no jump host.

Cron·Exec

A weekly canary that tries to break production

Sunday 7am cron wakes a Hoody Agent in a fresh container against a snapshot of prod. It runs the OWASP top twenty, fuzzes the API, and writes a findings report to a URL by 9am. Container retires.

Cron·Agent·Browser·Snapshots

The hobby-project graveyard you can afford to keep alive

Eleven half-finished side projects on Heroku is eleven dynos at $5–7 each. On Hoody it's eleven containers on one $29 bare-metal box. Idle costs zero, the URL wakes the container in milliseconds, and the chess engine nobody uses still runs.

Containers

A preview environment per pull request, all month

Each open PR gets its own clone of a snapshot. The container wakes when reviewers click the link; idle PRs cost nothing.

Containers·Snapshots

Run a 12-product portfolio from one bare-metal box

Twelve isolated containers, each its own SaaS, share one $49 bare-metal server — a step above the $29 entry tier, chosen here for the RAM headroom fifty containers want. Per-product margins go from negative to nice.

Containers

Kill the staging-server tax

Stop paying for a duplicate of production. Snapshot the prod container, branch staging from it on demand, freeze it back to disk when nobody's testing. Three environments, one machine, one bill.

Containers·Snapshots

Replace the E2B bill with the bare metal you already rent

Your agents stop renting compute by the second from E2B/Modal/Daytona. They use containers on the box you already have.

Containers·Agent·Exec

Idle staging costs nothing, so staging stops getting deleted

Staging used to die because it was expensive to keep around. When idle is free, staging gets to live — even the one a teammate touched 90 days ago.

Containers·Snapshots

Per-customer sandboxes at fleet scale

Eight hundred isolated customers on three bare-metal servers — one flat-rate monthly bill, no per-tenant meter. Each tenant gets a real container with its own kernel namespace, filesystem, and URL. Idle containers cost nothing on top of the server you already pay for.

Containers·Snapshots·Exec

The CI cache that's not an S3 line item

Cache files live in /files on the box you already rent. Workers PUT and GET tarballs over HTTP. No S3 bucket, no egress, no third vendor — the bytes never leave the box.

Files·Containers

Fifty demo environments for fifty sales calls

Each prospect gets a real, isolated copy of your product seeded with their data. Cloned from a snapshot. Theirs to keep for a week.

Containers·Snapshots

Forty client sites. One rent. One dashboard.

How forty fits in one

Isolation by namespace

Density on shared metal

All clients in one tab

The math finally works

Why this isn't "shared hosting"

A hacked client can't breathe on the next one

Charge per client, pay per box

Delete a client cleanly

What this replaces

Read the others

Sixty containers on one server

Onboard a developer with one link

API endpoints that materialize on demand

Branch computers like Git

Real VS Code on your phone

AI agents that spawn other AI agents

One sandbox per customer, automatically

Wake up to a finished prototype

Emergency production fix from your phone

Tail production logs to a URL anyone can curl

Push one build to thirty CI workers at once

Watch your agent think from the coffee shop

Share your screen with a URL, not a meeting invite

Move 200GB between clouds with two curls

Send a teammate a database state in one line

Stream LLM tokens to anything that reads HTTP

A progress bar your boss can spectate without joining

The webhook fan-out you didn't have to build

A CI cache that's just two curl commands

Drag-drop uploads into your script

Broadcast a workshop to 200 viewers from your laptop

Inter-container IPC without the message broker

Tail your agent on the train, get pinged when it lands

A microphone over HTTP, in two terminals

Five agents, five pipes, one verdict

Replay this morning's incident to the whole team

The fastest 'send me that file' you've ever typed

Run a local LLM, serve it to your whole fleet

A live metrics dashboard with no metrics backend

The cron job that deletes itself when you're done

Snapshot the container right before the nightly migration

A separate crontab for every customer, automatically

Wake an agent at 3am, retire it at 4

Daily rollups without an orchestrator

A crontab per branch, deployed with the code

On-call escalation that ages out with the shift

Hourly scrape, daily digest, weekly archive — one container

Let your customers BYO their own cron schedule

Schedule the agent, not the script

A heartbeat for the silent jobs

Keep the last 24 hours as 24 snapshots

Replay this morning's webhooks at the same time tomorrow

Edit your crontab from a phone, in the airport

A scheduled digest that fans out to 200 inboxes

Mute the flaky job without losing it

An agent that grades yesterday's agents

Cleanup jobs that schedule their own retirement

Roll your TLS certificates without an SSH session

A weekly canary that tries to break production

The hobby-project graveyard you can afford to keep alive

A preview environment per pull request, all month

Run a 12-product portfolio from one bare-metal box

Kill the staging-server tax

Replace the E2B bill with the bare metal you already rent

Idle staging costs nothing, so staging stops getting deleted

Per-customer sandboxes at fleet scale

The CI cache that's not an S3 line item

Fifty demo environments for fifty sales calls