Skip to content

TypeNew primitive StageQuick win DifficultyModerate ForAI builders ForSolo founders ForBackend devs ServicesAgent ServicesSnapshots ServicesContainers ServicesBrowser ServicesSQLite ServicesNotifications Why HoodySnapshot time travel Why HoodyContainer economics Why HoodyHTTP-native

TypeNew primitive StageQuick win DifficultyModerate ForAI builders ForSolo founders ForBackend devs ServicesAgent ServicesSnapshots ServicesContainers ServicesBrowser ServicesSQLite ServicesNotifications Why HoodySnapshot time travel Why HoodyContainer economics Why HoodyHTTP-native

TypeNew primitive StageQuick win DifficultyModerate ForAI builders ForSolo founders ForBackend devs ServicesAgent ServicesSnapshots ServicesContainers ServicesBrowser ServicesSQLite ServicesNotifications Why HoodySnapshot time travel Why HoodyContainer economics Why HoodyHTTP-native

TypeNew primitive StageQuick win DifficultyModerate ForAI builders ForSolo founders ForBackend devs ServicesAgent ServicesSnapshots ServicesContainers ServicesBrowser ServicesSQLite ServicesNotifications Why HoodySnapshot time travel Why HoodyContainer economics Why HoodyHTTP-native

Back to use cases

use-cases / wake-up-to-finished-prototype / hero

AGENT · OVERNIGHT BUILD

Wake up to a finished prototype

Describe the project at midnight. Sleep. The agent works through the night in its own containers, snapshots before risky steps, and posts to your notification webhook at sunrise. You open a working URL on your phone before the coffee is done.

Read the agent docs

7:14 AM

5G

Tuesday, May 57:14 AM

Hoody · agent-task-241

now · push

Done. Live at invoices.example.run

Tests passing · snapshot saved · 8h 27m · 41 tool calls

liveinvoices.example.run

Recent invoices3 of 12

INV-2026-0042$1,840.00paid
INV-2026-0043$620.50open
INV-2026-0044$2,310.00draft

OVERNIGHT · agent-task-241

23:47 -> 06:14 · 41 events

00:14containers.spawnapi · web · sqlite
01:18files.writesrc/handlers/createInvoice.ts
02:42containers.snapshotpre-migration
03:47sqlite.queryCREATE TABLE invoices
04:09browser.clickbutton#submit-invoice
05:21proxy.aliasinvoices.example.run -> exec-1
06:14webhook.sendPOST notify.hoody.com

use-cases / wake-up-to-finished-prototype / night

The eight hours you don't see

The agent is a container talking to other containers over HTTP. Each step is one HTTP call you'd be making by hand. Snapshots bracket the risky ones, so failure costs nothing and the morning has a roll-back point.

23:47

Prompt sent. POST /api/v1/agent/tasks accepts the description and returns a task id.

23:47

Prompt sent. POST /api/v1/agent/tasks accepts the description and returns a task id.

00:03

Three containers spawned via the containers API. One for the API, one for the web, one for the database.

00:03

Three containers spawned via the containers API. One for the API, one for the web, one for the database.

01:18

First failing test. The agent reads the trace from the WebSocket event stream and patches the handler.

01:18

First failing test. The agent reads the trace from the WebSocket event stream and patches the handler.

02:42

Snapshot created with POST /containers/[id]/snapshots before running the schema migration.

02:42

Snapshot created with POST /containers/[id]/snapshots before running the schema migration.

04:09

hoody-browser opens the live UI, fills the test invoice, takes a screenshot, asserts the totals.

04:09

hoody-browser opens the live UI, fills the test invoice, takes a screenshot, asserts the totals.

05:21

Proxy alias points the chosen domain at the web container. The URL is now public.

05:21

Proxy alias points the chosen domain at the web container. The URL is now public.

06:14

Outgoing webhook to your notification endpoint of choice. The phone lights up.

06:14

Outgoing webhook to your notification endpoint of choice. The phone lights up.

use-cases / wake-up-to-finished-prototype / morning

What you wake up to

A live URL, a passing test bar, and a window of agent events. Not an essay, not a code dump. A working artifact you can hand a teammate.

agent-1.containers.hoody.com

livehttps://invoices.example.run

us-nyc-1

Testsall passing

agent/ws · tool_use · last 6

01:18tool_usefiles.write src/handlers/createInvoice.ts
01:42tool_useterminal.exec bun test --filter invoice
02:42tool_usecontainers.snapshot pre-migration
03:55tool_usesqlite.query CREATE TABLE invoices
04:09tool_usebrowser.click button#submit-invoice
05:21tool_useproxy.alias invoices.example.run -> exec-1

If you don't like what you see, the snapshot from before bed is one PATCH call to /containers/[id]/snapshots/[name] away. The night was an experiment, not a commitment.

use-cases / wake-up-to-finished-prototype / punchline

You spent eight hours sleeping. The agent spent eight hours building.

YOUR NIGHTrest

AGENT NIGHTscaffold, test, deploy, snapshot

no laptop open
no contractor invoice
snapshot to revert

use-cases / wake-up-to-finished-prototype / replaces

What this replaces

Asynchronous prototype work has always been blocked on humans being awake. Snapshot the night and it stops being blocked.

Midnight standup messagesAsking a teammate to start it for you
Friday-morning prototype promisesA week of context-switching for one demo
Devin / Replit agent runsNeed a tab open and a battery awake
Contractor prototypesPay for the boring 60% you'd have skipped
Rough scaffolds you redo by handSame files written by you, just slower
Half-done weekend projectsThe wrapper around Stripe, the auth, the CRUD

use-cases / wake-up-to-finished-prototype / cta

You used to wake up to email. Now you wake up to product.

Read the agent guide

use-cases / wake-up-to-finished-prototype / 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

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.

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.

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.

Share your screen with a URL, not a meeting invite

ffmpeg streams your X11 to a pipe path. Receiver URL plays it as embedded HTML video. No Zoom, no app, no calendar invite.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

Forty client sites, one rent, one dashboard

Each client site lives in its own container; you bill them per-site, you pay the host once. The math finally works for agencies.

Containers·Workspaces

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

The Kit

Terminal
Display
Files
Exec
SQLite
Agent
Browser
Code
cURL
Daemon
Notify

Platform

Instant Spawn
Time Travel
Shared FS
Firewall
Realms
Custom Domains

Resources

Docs
API Reference
Community

Company

Manifesto
Pricing
Contact
Terms
Privacy
Acceptable Use
Abuse
Bug Report

© 2021-2026 Hoody Limited