Per-customer sandboxes at fleet scale, without the per-customer bill

Your SaaS has 800 customers. The honest architecture gives each one their own database, their own filesystem, their own scheduled jobs. The honest architecture is also the one your CFO won't sign off on, because Fargate-per-tenant or Kubernetes-namespace-per-tenant is 800 line items.

So you compromise. You shove everyone into shared multi-tenancy. You find the bug six months later where customer A reads customer B's invoices.

On Hoody, 800 containers fit on a small fleet of bare metal boxes. Each tenant gets a real isolated container: separate kernel namespace, separate disk, separate URL. Most are idle most of the time, drawing nothing. The economics make per-customer isolation actually affordable, not a luxury you talk yourself out of.