Every customer SFTPs into their own container

Your enterprise customers deliver files the way enterprises do: nightly SFTP drops. Each one's security team opens with the same question: do we get a VPN, or do you allowlist us?

Neither. Each customer gets a keypair, and their public key goes on their container. Every SSH connection to Hoody also serves SFTP, and the proxy routes each connection by the public key in the handshake: the bank's nightly drop lands in the bank's container because the key says so. One key maps to exactly one container, and the API refuses to assign a key twice: a drop cannot land in another tenant's box.

No VPN per customer, no allowlist churn, no shared landing zone to sort through afterward.

The key is the routing, and the routing is the tenancy.