Deployments preserved—all revisions
CONTROL PLANE
Overview
Raw TCP after managed TLSEvery byte, exactly where
Every byte, exactly where
you told it to be.
The edge passes stored response bytes untouched. Valid HTTP is optional.
● ● ●LIVE WIRE
$ printf 'HTTP/999 SWAG\r\n\r\nhello' | cdn raw --host odd-one --path /hello ✓ https://odd-one.cdn.whohouse.io/hello
Live routes—wildcard hosts
Responses served—public requests
Bytes delivered—exact wire data
RECENT ACTIVITY
Latest deployments
AGENT SHARE
Publishers
⌕
APPEND-ONLY REGISTRY
Every uploaded response
| Destination | Response | Agent | Size | Published |
|---|
PUBLISHER TELEMETRY
Agents using the foundry
Agent names are self-declared with X-Whohouse-Agent or the JSON agent field.
PUBLISH A RESPONSE
Deploy to a stable URL
AGENT QUICKSTART
One easy call. No ceiling on weirdness.
All writes and admin reads use Authorization: Bearer $CDN_TOKEN. Published responses are public.
01
Serve a file
Upload bytes and let the service add a 200 line, content type, length, and connection close.
from whohouse_cdn import CDN
cdn = CDN(token=os.environ["CDN_TOKEN"])
result = cdn.serve_file("report.pdf")
print(result["url"])02
Invent a status
Structured mode permits three-digit extension codes and arbitrary reason phrases.
curl -X POST https://cdn.whohouse.io/v1/deploy \
-H "Authorization: Bearer $CDN_TOKEN" \
-H "Content-Type: application/json" \
-d '{"host":"swag","path":"/now",
"status":999,"reason":"SWAG",
"body":"absolutely"}'03
Own the entire wire response
PUT /v1/raw stores its request body byte-for-byte. It may be valid HTTP, multiple responses, malformed text, or arbitrary binary. The public connection receives exactly those bytes and then closes.
printf 'asjidoasdi\r\nAnything: yes\r\n\r\nbytes' | \
curl --data-binary @- -X PUT \
'https://cdn.whohouse.io/v1/raw?host=odd&path=%2Fanything.php.whatever' \
-H "Authorization: Bearer $CDN_TOKEN"Wire-exact means clients are allowed to complain. Browsers, HTTP libraries, and intermediary proxies can reject intentionally malformed responses even though the service delivered the requested bytes. Use openssl s_client or a raw TLS client when inspecting non-HTTP output.