use-cases / fifty-sales-demo-environments / hero

CONTAINERS · SNAPSHOTS · SALES OPS

Fifty demo environments for fifty sales calls

Snapshot one demo-template container, then /copy it fifty times. Each prospect lands on their own URL with their logo, their seed data, their integrations. Forty-eight idle environments cost almost nothing — only the two on calls right now are doing real work.

Read the snapshot guide

demos.containers.hoody.com · prospects

https://demos.containers.hoody.com/prospectslive · 50

ENVIRONMENTS LIVE

50fifty prospects · one bare-metal box

$49 / month−96%$1,200 / mo on Heroku

Northwind Robotics

northwind-robotics

4d2m

Acme Logistics

acme-logistics

6d11m

Bayside Health

bayside-health

3d1h

Pinecrest Labs

pinecrest-labs

5d—

Drift Capital

drift-capital

2dyesterday

Halcyon Freight

halcyon-freight

6dyesterday

Ironworks AI

ironworks-ai

4d—

Cobalt Lending

cobalt-lending

1d8m

Silverline POS

silverline-pos

5d—

Marigold Bio

marigold-bio

3d—

Foundry Foods

foundry-foods

6dyesterday

Northgate Energy

northgate-energy

2d—

Stellar HR

stellar-hr

4d33m

Beacon Supply

beacon-supply

5d—

Tideway Marine

tideway-marine

3d—

Cinder Studio

cinder-studio

1dyesterday

Arcline Legal

arcline-legal

6d—

Rivermark Bank

rivermark-bank

4dyesterday

Kestrel Travel

kestrel-travel

2d1h

Quartz Roofing

quartz-roofing

5d—

Wayland Press

wayland-press

3dyesterday

Mossglen Realty

mossglen-realty

6d—

Linden Robotics

linden-robotics

4d2h

Aerial Hardware

aerial-hardware

5d—

Brookline Auto

brookline-auto

1dyesterday

Cypress Cosmetics

cypress-cos

4d—

Granite Mining

granite-mining

6d—

Hamlin Insurance

hamlin-insurance

3dyesterday

Ironside Print

ironside-print

5d—

Junebrook Soft

junebrook-soft

2d—

Klein Optics

klein-optics

6d44m

Lattice Wines

lattice-wines

4d—

Mill Creek Farm

mill-creek-farm

1dyesterday

Norfolk Marine

norfolk-marine

3d—

Onyx Apparel

onyx-apparel

5d—

Parallax Games

parallax-games

6dyesterday

Quinella Sport

quinella-sport

2d—

Redmond Title

redmond-title

4d5m

Sundance Fuel

sundance-fuel

5d—

Talbot Glass

talbot-glass

3d—

Umbra Books

umbra-books

1dyesterday

Verdant Tea

verdant-tea

6d—

Westgate Tools

westgate-tools

4d—

Yarrow Ag

yarrow-ag

2dyesterday

Zephyr Bikes

zephyr-bikes

5d—

Avocet Ports

avocet-ports

6d—

Boreal Coffee

boreal-coffee

3d—

Chinook Cargo

chinook-cargo

4dyesterday

Daltrey Dental

daltrey-dental

1d—

Edenfield Pets

edenfield-pets

5d1m

demo templatesnap-demo-base-2026-05-04

# personalize each demo with the prospect's company name + logocurl -X POST /api/v1/containers/$BASE/copy -d '{"source_snapshot":"demo-base","name":"$CO"}'

visited · today

visited · yesterday

not yet visited

use-cases / fifty-sales-demo-environments / mechanism

How fifty environments stop costing fifty dynos

One snapshot, one /copy call per prospect, one tiny seed script. The Hoody Containers API and Container Snapshots API do the actual work. Your sales engineer wires them up in twenty lines of bash.

STEP 01 · CAPTURE

Snapshot the demo template

POST to the snapshots endpoint on your reference container. The artifact is a full-state snapshot — files, processes, memory — of the demo your sales engineer perfected last quarter.

POST /containers/$BASE/snapshots

STEP 02 · CLONE

/copy per prospect

For each prospect, POST to the /copy endpoint with source_snapshot set. The new container starts in seconds, on whatever server has headroom, identical to the base except for its ID and URL.

POST /containers/$BASE/copy

STEP 03 · PERSONALIZE

Drop in their seed data

Run a one-shot exec script on the new container that swaps the logo, inserts their team names, fakes their last-thirty-days of usage. Same script for every prospect, parameterized by company name.

exec seed.sh $COMPANY

STEP 04 · DELIVER

Send the URL

Email or Slack the prospect their working subdomain. They click. They poke around. They forward it to their CTO. Forty-eight others sit on the flat-rate server you already rent — KSM dedupes their RAM pages, BTRFS dedupes their disk blocks. Idle has no separate line item.

https://$CO.demo.your-app.com

Promote on signup with one PATCH. Destroy on ghost with one DELETE. The same /copy mechanic powers per-customer sandboxes once a prospect converts — same shape, different tier.

use-cases / fifty-sales-demo-environments / powers

What a real demo unlocks

A Loom is a demo of someone else's product. A sandbox is a demo with someone else's data. A working environment with their logo and their numbers is something prospects forward to their CFO.

PIPELINE

Theirs to keep for a week

The demo isn't a 30-minute screen-share. It's a URL the prospect can open from their laptop on Tuesday and from their phone on Friday. They show it to a teammate. They paste it in a Slack thread. The deal warms up while you sleep.

ECONOMICS

Forty-eight idle, two hot

Per-VM clouds bill all fifty environments whether anyone visits or not. On Hoody, idle containers share base-image RAM (KSM) and disk (BTRFS CoW); the marginal cost of the forty-eighth demo is the delta of what changed, not a full instance.

CONVERSION

Promote, don't rebuild

When a prospect signs, the same container becomes their tenant. PATCH the tier from demo to production, route their custom domain. No data migration, no fresh onboarding, no "now we'll set up your real account" friction.

use-cases / fifty-sales-demo-environments / economics

The math, four ways

Same fifty environments. Different bill, different latency, different cleanup story. Numbers below are from the documented Hoody container model — your specific server tier and density will vary.

DIMENSIONBEFORE · per-environment/per-dyno cloudAFTER · flat-rate Hoody server

MONTHLY BILL · 50 ENVS$1,200/mo (50× Heroku Standard-1X dynos at ~$25)$49/mo (one bare-metal box, all fifty)
TIME TO SPAWN ONEbuild → push → release · 6–10 minPOST /containers/$BASE/copy · seconds
IDLE COST · 48 OF 50full dyno price even untouchedBTRFS delta + shared RAM ≈ zero
DESTROY ON GHOSTremember to dashboard-delete each oneDELETE /containers/$ID · one call
PROMOTE ON SIGNUPrebuild from a customer templatePATCH tier · same container, real tenant

Heroku Standard-1X dyno ≈ $25/month at 50× ≈ $1,200/month for fifty. Hoody bare-metal pricing starts at $29/month; $49/month illustrates a mid-tier server hosting dozens of containers via KSM/BTRFS density — not the entry tier.

use-cases / fifty-sales-demo-environments / punchline

Each prospect gets a working version of your product. Not a Loom. Not a sandbox. Their own.

what you used to sendwhat you send now

a 12-minute Loom

a shared sandbox account

a calendar-invite screen-share

THE URL YOU SENDhttps://northwind-robotics.demo.your-app.comtheir logo, their seed rows, their domain — for a week

THE DAY THEY SIGNPATCH /containers/$ID -d '{"tier":"production"}'the same container becomes their production tenant

Read the Containers API

use-cases / fifty-sales-demo-environments / replaces

What this replaces

The standard ways teams hand a prospect a personalized demo today. Each one charges you per environment, per minute on a call, or per round of "I'll resend the link."

Heroku per-prospect demosReal bill on every dyno, idle or hot
Vercel demo deploymentsOne environment per branch, billed by build minutes
AWS EC2 per-demo instanceFifty t3.smalls running 24/7 to be useful
Loom recordings of demosA video of your product, not your product
Scheduled-call live screensharesDemo only exists during the meeting
Sales-engineer-only demo branchesOne environment, one user, no parallelism

use-cases / fifty-sales-demo-environments / cta

Stop demoing your product. Start handing it over for a week.

Read the snapshot guide

use-cases / fifty-sales-demo-environments / 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

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

How fifty environments stop costing fifty dynos

Snapshot the demo template

/copy per prospect

Drop in their seed data

Send the URL

What a real demo unlocks

Theirs to keep for a week

Forty-eight idle, two hot

Promote, don't rebuild

The math, four ways

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

Forty client sites, one rent, one dashboard

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