Per-tenant prompts, per-tenant data isolation, per-tenant rate limits. The architecture that lets one codebase serve 200 customers without leaking.
Multi-tenant agent platforms have three hard problems: prompt isolation, data isolation, and per-tenant rate limits. Get any one of them wrong and you have a leak that ends the company. Below: the architecture we shipped for a platform serving 200 customers. The 72-hour deploy plan We ship most projects in this category on a 72-hour clock. Interview the two people who do this job today.
Interview the two people who do this job today. Pull 50 sample inputs (calls, chats, tickets). Identify the three top customer intents. Stand up the eval harness with 25 cases drawn from the sample inputs. The eval harness has to exist before the first prompt does.
Per-tenant prompts, per-tenant data isolation, per-tenant rate limits. The architecture that lets one codebase serve 200 customers without leaking. It is filed under AI Infrastructure because that is where operators looking for this problem actually start, and it is written from production work rather than from a content calendar.