The CI cache that's not an S3 line item

Most CI pipelines burn money on cache traffic. Push artifacts to S3, pull them on the next job, pay for storage, pay for egress, pay again when builds run from the runner's region. The line item starts at $40 a month and ends wherever the runners decided to stop being polite.

On Hoody the CI cache is a hoody-files URL on the same bare metal that runs your build containers. Push a tarball with a curl. Pull it with a curl. No bucket lifecycle, no IAM policy, no egress charge: the bytes never leave the box. Compress 10GB of node_modules, write to /cache/sha256-abc, the next build downloads it at NVMe speed.

When the cache fills up, a cron job prunes by atime. Done.

Your CI cache stops being a separate vendor. It's a folder on the box you already rent.