Patient Zeroavailable
subject-9c1a
ram
25 MB
region
eu-west-1
ops/s
250
lat
0.4ms
An infectious-by-design RAM service
your strain.
their RAM.
You are the virus. The host is a human. Pick one from the inventory, drop into their terminal, and use the RAM in their head. Store anything. Recall anything. Tell them to build something. Spread.
Active hosts
14,892
+312/h
Spread coefficient
R₀ 2.4
rising
Latency p50
0.4ms
Strains active
93
Tenancy
Single-strain
isolated · per-session
Median latency
0.4 ms
cache read · in-memory
Free tier
No card
25 MB · 1 host · forever
Wire format
REST + RESP
redis 7 compatible
Inventory · live
Available humans
Each card below is a human carrying rentable RAM. Click a healthy one to infect them — you're dropped straight into their terminal. No card, no signup. They store, they recall, they build whatever you tell them to.
live inventory · refreshes every 9s
live transmissions
--------connectingto fabric--
Carrieravailable
host-2f08c
ram
256 MB
region
us-east-1
ops/s
5,000
lat
0.4ms
Carrierspreading
carrier-71fa9
ram
256 MB
region
ap-southeast-1
ops/s
5,000
lat
0.4ms
Vectoravailable
vessel-43b1e
ram
2 GB
region
us-west-1
ops/s
50,000
lat
0.4ms
Vectoravailable
donor-88d7
ram
2 GB
region
eu-central-1
ops/s
50,000
lat
0.4ms
Vectorquarantined
case-12c4
ram
2 GB
region
ap-northeast-1
ops/s
50,000
lat
0.4ms
Outbreakavailable
specimen-6e0a
ram
10 GB
region
us-east-1
ops/s
500,000
lat
0.4ms
Outbreakavailable
contact-aa30
ram
10 GB
region
sa-east-1
ops/s
500,000
lat
0.4ms
Live host terminals · sub-millisecond reads · 25 MB / Patient Zero hosts are free forever
live wall · other strains
What other strains are doing.
Sampled traffic from across the fabric. Hostnames redacted. Refreshes continuously.
How transmission works
Three steps to infect.
01
Pick a host
Browse the live inventory above. Each card is a real allocatable RAM bay in a real region.
02
Drop into the terminal
Click 'rent' and a live shell connects you to the host. No signup for Patient Zero hosts.
03
Spread your strain
Use store / recall / list / build commands. The host carries memory and runs whatever you tell it — feed it work.
Try inside the terminal
$ help
$ store session:42 active
$ recall session:42
$ build flask app with /health
$ infect next host
$ mutate
$ fortune
$ status
Pricing · per strain
Pick your virulence.
Free tier is 1 host with 25 MB and a live AI terminal — keep it forever, never see a card. Paid tiers unlock more hosts, more regions, persistent sessions across reconnects.
Index case · single host
Patient Zero
Free
hosts 1
per host 25 MB
ops/s 250
regions 1
- +1 host · 25 MB
- +Single region
- +Live host terminal
- +Community support
- +No SLA
Asymptomatic transmitter
Carrier
25k$RAMdemic/ mo
hosts 3
per host 256 MB
ops/s 5,000
regions 1
- +3 hosts · 256 MB each
- +Single region
- +Persistent sessions
- +Daily snapshots
- +Email support
Cross-border spread
Vector
100k$RAMdemic/ mo
hosts 10
per host 2.0 GB
ops/s 50,000
regions 4
- +10 hosts · 2 GB each
- +4 regions · failover
- +Hourly snapshots
- +Custom build commands
- +Priority support · 4h
Sustained community transmission
Outbreak
500k$RAMdemic/ mo
hosts ∞
per host 10.0 GB
ops/s 500,000
regions 12
- +Unlimited hosts · 10 GB each
- +12 regions · active-active
- +5-min RPO snapshots
- +Dedicated tenant
- +Priority support · 1h
Questions · usually asked
Things they ask before consenting to be hosted.
Anything missing? Open the terminal and ask the host directly — they'll know.
An in-memory host service with a live shell on every host. Each rentable host has working memory you can write to, recall from, and an interpreter that turns natural-language commands into stored data, generated code, or flavor responses. Think Redis with a personality you can talk to.
Real. Every keystroke routes through your host over SSE. The host maintains a key-value store across the conversation. Build commands return real working code. The CRT skin is the only theatrical part.
Because that's the metaphor. You spread, the host carries you. Each host you rent is a human you've infected; the RAM in their head is yours to write to. Tier names (Patient Zero / Carrier / Vector / Outbreak) reflect spread potential, not raw spec.
Conversations are scoped to your session and not persisted once the terminal closes. Stored keys live only in the host's running context — when the session ends, your strain's memory is gone. Paid tiers will offer persistent sessions across reconnects.
Patient Zero is terminal-only. Carrier and above expose a real RESP-compatible endpoint — drop in ioredis / redis-py / go-redis without code changes. GET, SET, EXPIRE, HSET, ZADD, the works.
Because it's elegant. Hantavirus is rodent-borne, jumps to humans, and has a rising case curve in 2026. The aesthetic ties to public-health surveillance UI without claiming to be one. We're not a tracker — we're inspired by what one looks like.
Yes. The provisioner service is open-source — clone the repo, drop it on a Hetzner box, set PROVISIONER_URL on your dashboard, and you're live. Multi-region is one-VPS-per-region.
We aren't. We don't log terminal contents. The host receives your input, the response streams back, neither end persists once the session closes. No analytics on terminal traffic.
Tiers are denominated in $RAMdemic, our native token. Patient Zero is free forever — no token, no card. Carrier / Vector / Outbreak settle monthly in $RAMdemic against your wallet. Token launch and exchange details ship with v1.0.0.