There are two ways to run agents for an enterprise. Run them on your own multi-tenant platform and connect to the client's systems from outside. Or install the platform inside the client's environment and run it there.
The first is cheaper for the vendor. The second is what we do.
What single-tenant means in practice
Conduit installs in your cloud subscription or on your premises. All platform state, including agents, runs, approvals, audit log, knowledge, and learned memory, lives in your database. Sign-in is through your identity provider. Secrets live in your vault. There is no shared control plane and no path by which your data leaves your boundary.
Our operational access is just-in-time and unilaterally revocable by you. The platform keeps running if you revoke it.
Why it matters more for agents than for software
A SaaS reporting tool that sees your data is a privacy question. An agent that acts inside your systems is a control question. When something can post a journal entry, the people accountable for the ledger need to be able to say where the thing that posted it lives, who can reach it, and how to turn it off. "In our cloud, under our access model, with a switch we hold" is an answer a risk committee accepts.
What it costs us, and why we pay it
Single-tenant is harder to operate. Every client is an installation. Upgrades ship as signed platform releases and re-validate against each client's golden sets rather than rolling out once to everyone.
We pay that cost because it keeps lock-in low. Your connectors, your knowledge, your evaluation sets, and your trained agents accumulate in your installation and belong to you. The vendor relationship is never holding your assets hostage.
When the walls need to be physical
For some organizations, the data posture, the regulator, or the risk committee rules out any inference outside the building. Zeus brings the whole stack, including in-boundary inference, on premises, for select clients, by conversation.
Your infrastructure. Your boundary. Your call.