Credentials stay in the vault
Provider keys are injected on the server. They never reach your agent, your prompts or your logs.
Security
Credentials live server-side. Access is granted explicitly. Spend has a ceiling. The code is open, so you can check all of it.
Provider keys are injected on the server. They never reach your agent, your prompts or your logs.
Browsing the catalog grants nothing. Each key gets the connections and resources you name, and write or spend actions need approval bound to that action.
Set a daily or monthly cap per connection. Requests are refused at a zero balance, and concurrent calls cannot overspend it.
Answers from your own provider keys never enter the shared cache. They are cached for your organization only.
Every execution is recorded with who, what, which provider and what it cost.
Per-provider limits are enforced in the database, so a burst cannot exhaust a supplier quota across workers.
Solo to enterprise
You get the same protections without setting anything up. Your provider credentials never reach your code, and a spending limit keeps a runaway script from emptying your balance. Turn on the rest when you need it.
Scoped keys per team or automation, limits per key, an append-only audit trail and code your reviewers can read. Self-host it in your own cloud if the data has to stay there.
Answers obtained with your own provider keys never enter the shared cache. They are cached for your organization only.
Connect is not a model and does not train on what you send. Each provider sets its own terms, and the catalog shows who answers each operation.
There is no SOC 2 report today and we will not imply one. The controls are built to be audited: append-only logs, scoped access and open code.
Regional hosting on AWS (North America, Europe, Asia and Latin America) is being rolled out, and choosing where your data stays is not available yet. The public MCP adapter is built but switched off until its authorization model is settled. We would rather say so than imply otherwise.
Start on Konnect in a few minutes, or clone the repo and run Connect yourself.