One small box runs the bots, the stats and the background jobs. This page shows how it is doing, in plain words.
Reading Muse's latest health checks.
🟢 Online: answering fast and clean. 🟡 Degraded: up, but slow or wobbling, so replies may stall or need a retry. 🔴 Offline: checks cannot reach Muse at all. ⚪ Quiet: no fresh check has arrived, so nobody knows.
Load counts how much work is waiting in line. At 2.0 the box is exactly full. Above 2.0, work queues and everything slows down.
The box has about 8 GB and no spare. When memory fills up, even simple jobs crawl.
How hard the processors are working right now, moment to moment.
Loading…
A health checker pings our key services every few minutes. 100% means every check passed. The dips are the slowdowns, drawn out loud. 🟡 next to a service means degraded: it answered, but some checks in the last hour failed, so it is wobbling. 🔴 means it is down right now.
The box has 2 CPUs. Six Discord bots, the live counters and dozens of scheduled jobs all share them. When several heavy jobs land in the same minute, everything queues up and waits its turn.
Almost every job needs the internet: GitHub, Google, Discord, Cloudflare. When those pipes slow down, a call that should take 1 second takes 15 or more, and some never come back at all. A stalled job just sits there, holding its memory, while its work piles up behind it.
A job set to run every minute that takes 4 minutes to finish does not run once. It runs 4 deep, and each copy makes the others slower, which stacks even more copies. Slow becomes slower all by itself.
Browser sessions and big jobs are the hungriest. When the 8 GB is gone there is no spare to borrow, so the whole box wheezes until something finishes and frees room.
The box gets replaced without warning, sometimes mid-job. Everything then restarts at the same moment, straight into a fresh pileup while the pipes are still cold.
The websites themselves live on Cloudflare, not on this box, so e2.life and the rest stay up and fast for visitors. The Discord bots keep the connections they already hold. What suffers is speed behind the scenes: new work, deploys, stats and replies.
e2.life today: about 5,300 files, measured on our own deploy tree on Oct 31, 2026.
The whole network: about 43,800 files across the 8 main site trees we measured (E2, Starvard, The Studio, Clear Recipe, Open Arcade, YouBoob, LlamaChat, LlamaGram).
What static hosting costs us right now, per month. Cloudflare Pages does not charge for storage, requests, or bandwidth on static pages.
To feel the scale: if 100,000 people each read 8 pages, that is about 600 GB of bandwidth served. On a metered host that would cost real money. On Cloudflare it costs $0, and at a million people (about 6 TB) it still costs $0. The limits that actually matter are not traffic. They are these:
27% of the free cap. Lots of room.
74% of the free cap. Worth watching as courses and books grow.
83% of the free cap. Our closest limit. Passing it is what the $20 Pro plan below is for.
71% of the 100,000 free requests a day, from our Oct 31 Cloudflare pull. This is the one metered piece. The pages themselves are not metered at all.
Videos do not live inside the website deploys above: Pages caps each file at 25 MB and counts files per site. They live in Cloudflare R2, object storage built for media, which is already where every Llama Chat clip sits (llamachat.lol/media). R2 storage costs $0.015 per GB per month, the first 10 GB is free every month, and sending video out to viewers is always $0. A typical Llama Chat clip runs about 5 MB (measured on real posts: 2 to 8 MB). Open Arcade games are small code bundles that ride in the site deploy, and YouBoob's own hosted films total 143 MB today, so the growth below is almost all Llama Chat.
The first 10 GB costs nothing, every month. That alone holds about 2,000 clips before a dollar is spent.
Years of community clips at the current pace, for less than a coffee.
A hundred thousand clips. This is the "Llama Chat really took off" scenario, and it is still single digits.
Two hundred thousand clips, or about 670 hours of longer film at 25 MB a minute.
Roughly 270,000 Llama Chat clips, or about 900 hours of video. And views stay $0 at every size on this chart: on Amazon S3, a million clip views (about 5 TB out) would cost roughly $450 in bandwidth alone. On R2, egress is never charged. Storage math checked against Cloudflare's R2 pricing on Nov 14, 2026.
Same estimate we worked out on Oct 16, checked again against Cloudflare pricing on Oct 31, 2026. Growth costs us almost nothing, because the expensive-sounding parts (visitors, pages served, bandwidth) are the free parts.
Everything fits inside the free tiers. Nothing to buy.
What flips: the live bits (chat, login, feed) pass 100,000 Worker requests a day. Workers Paid is $5 a month and includes 10 million requests a month. The websites themselves still cost $0 to serve.
What flips: our biggest sites pass the 20,000-file free cap. Cloudflare Pro ($20 a month billed annually, $25 month to month) raises the cap to 100,000 files per site, plus the $5 Workers Paid above. Yes, hundreds of thousands of people a month really do fit in about $25.
What flips: almost all of the extra is chat and API overage, at $0.30 per million Worker requests past the included 10 million. Static pages and bandwidth are still unlimited and free.
Assumptions: about 8 page views per person per month, pages under 1 MB, our sites stay static-first. Not counted here: domain renewals (about $10 to $15 a year each) and the chat database, which is free today and would be the next thing after Workers to outgrow. Cloudflare really does a good job: the same global network that serves the biggest sites on the internet serves ours, and it does not slow down when a crowd shows up.
Data: the box reports its own load and memory about every five minutes, and a health checker pings the key services every few minutes. This page re-reads the numbers every 30 seconds. Status colors: 🟢 online / all clear, 🟡 degraded or busy (up, but slow or wobbling), 🟠 strained, 🔴 offline / overloaded, ⚪ no fresh data.