Prod capacity under Young's new stated load (2026-10-17)

Young, 2026-10-17: prod hosts 2 live websites + e-commerce tenants (Mercury V2 + POS + EVE) + Hermes agents + EVE. That is a heavier prod than my earlier numbers assumed, so I re-ran the capacity maths. All figures measured or from Tam's live-measured tenant sizing — nothing estimated.

The arithmetic

Without agents on prod it would be 4.2 tenants. Co-locating the agent fleet costs 0.7 GB = 14% of one tenant slot. That is the whole trade.

What this changes

1. My earlier "~4–6 tenants" was optimistic for the new load. It was right for the old plan (agents elsewhere). With agents + websites + tenants on one node, plan for 4 tenants, not 6. Four is the honest number and it still beats the pilot's needs (2–3 tenants).
2. The consolidation question is now answered by arithmetic, not opinion. Moving agents off prod buys back 14% of one tenant slot — while costing the portability proof, adding a single point of failure, and widening the E5 blast radius. The trade is bad. Keep agents portable and present.
3. EVE on prod is not installed. No eve binary, no eve dir. Young lists "Hermes Agents + EVE" as prod's load; today only v3-heart-prod runs there. That is a build gap (Sol/Ace), not a capacity problem — and it fits in the 0.7 GB envelope.

Disk — the real constraint to watch

RAM binds before disk (4 tenants vs 18+). Worth noting because the business plan prices per tenant; RAM is what caps the pilot node.

The cost line that still matters

Node capacity is not the money. Always Free covers 2 OCPU / 12 GB; we run 4 OCPU / 24 GB, and four tenants alone need ~19 GB. So:

• The node is firmly in billable territory at pilot scale (not a free-tier ride).
• The Oracle burn check remains the one open infra number (Young's console).
• My business-plan-v2 two-row infra table still collapses to one row when it lands.

Honest limits

• Website RAM (~1 GB) is an estimate; I measured the agent and tenant figures, not the Nuxt processes' RSS on prod.
• "Mercury V2" is a name I have not seen in a measured doc — I have priced the Medusa stack Tam measured. If Mercury V2 is a different stack, its footprint needs its own measurement.
• EVE's prod footprint is unknown because EVE is not installed on prod yet.