One control plane for every team’s AI.

Through one organization with projects and environments under it. Invite members with roles (owner, admin, developer, analyst), give each member and project its own spend ceiling, restrict which models each project may call, and read the audit log for who changed what. Each team gets its own keys, budget and model policy, so a runaway workload in one project cannot spend another team's allowance — while the organization keeps a single view across all of them. From the Business plan, people sign in through your own identity provider over SAML or OIDC, and your directory can create and deactivate their INFRO membership over SCIM.

That is the design. You connect the provider accounts you already hold, so your negotiated rates, committed spend, discounts, quotas and enterprise agreements keep applying exactly as they do today — your provider bills you, at your prices, and INFRO takes none of it. If you have negotiated rates below the published ones, the Team plan and above let you enter them in the console, and every cost figure INFRO shows you is then computed from yours rather than from a list price. Leaving is the same two lines as arriving: change the base URL and the key back, and your provider accounts are untouched because they were always yours.

We become one more dependency — that is the honest cost of the trade, and you should price it in. Three things make it survivable. The status page runs on a separate, far simpler deployment than the gateway and checks the gateway from your own browser. Text speaks the OpenAI shape, so keeping a direct provider key and a base-URL switch in your config is a two-line contingency we actively recommend. And there is no published uptime SLA, because a service with no operating history cannot honestly offer one; an enterprise agreement can carry a contractual one.

Yes, and the migration back is the same two lines that brought you in. Retrieve request and usage history through the public APIs, or download it as CSV from the request log and Analytics, and keep it in your own systems before it leaves your plan's queryable history window. There are no scheduled or emailed exports.

We never train on your prompts, inputs, or outputs, and we never sell them. Usage metadata supports platform metering, cost estimates and governance. Optional prompt and response logging is off by default and limited by your plan. Job records and generated media needed for delivery are separate. Your AI providers' data-use and retention settings remain governed by your agreements with them.

Not yet, and we will not claim otherwise. Regional processing requires infrastructure entitlements we have not purchased, and a hostname that merely looks European is a compliance claim a customer can falsify in one request. When it is genuinely enforced we will say so; until then, assume requests are processed wherever capacity is, and treat that as a reason to talk to us before signing anything that depends on residency.

No, and we will not imply otherwise on a slide. What exists instead is published rather than promised, at /trust: a SOC 2 roadmap with an audit firm engaged and the observation window not yet scheduled, ISO 27001 marked under evaluation with no date committed, the controls that are enforced today alongside the ones that are not, and our answers to a standard security questionnaire as a document you can download without talking to us. The DPA with Standard Contractual Clauses, the subprocessor list and the acceptable use policy are published in full too. Send your own questionnaire anyway — we answer every question including the ones where the answer is not yet. If a certificate is a hard gate on your side, tell us at the start and we will say plainly that we cannot clear it today.

Infrastructure vendors are named at /subprocessors, with the notice periods and emergency exception explained there. You choose and contract directly with the AI providers you connect. Request traces identify the connections attempted; provider data use and retention follow your own agreements and account settings.

Yes, on an enterprise agreement: the subscription is invoiced quarterly or annually on your terms rather than charged to a card. That is an invoice for the software only. Model usage is invoiced to you by your own providers on whatever terms you already have with them, and no arrangement with INFRO changes that or puts it on an INFRO invoice.