For platform teams

Scoped keys per project, shared and per-member budgets, and an audit trail you can hand to security — the setup for a team running Relixr across multiple products.

Once more than one project, service, or team shares a Relixr workspace, the questions change: who can spend what, who can see what, and who did what — not just "how do I make a request."

Structure keys by project, not by person

Mint one management or inference key per project or service, scoped to only what that project needs (see API key scopes), rather than sharing a single workspace key across everything. This gets you two things for free: a leak in one project doesn't expose every other project's credential, and per-key usage in Activity already gives you a per-project cost breakdown without any extra tagging.

Budgets at every layer

• A workspace-level cap as the overall ceiling.
• Per-member limits for anyone whose individual usage should be bounded independent of their project's key caps.
• Per-key caps on each project's key, sized to that project's expected load.

See Setting spend controls for how these three layers interact — they're independent, not nested, so a project hitting its own cap doesn't require the workspace cap to have been sized around it in advance.

Roles and the audit trail

Workspace roles gate what a member can do in the dashboard, and — critically — what scopes they're allowed to put on a key they create: nobody can mint a key with a capability they don't personally hold (see API key scopes). Every guardrail policy change, member change, and key action is recorded, so a security review or an incident retro has a record to work from rather than relying on memory.

Rollout pattern

1. Create the workspace and set the overall spend cap first, before any project keys exist.
2. Provision one scoped key per project or service, sized and capped independently.
3. Turn on the guardrails you need workspace-wide — PII redaction and a model allowlist are the two worth enabling before anything else, since they protect you from code you don't directly control, including a future project you haven't onboarded yet.
4. Point each project at Usage analytics, filtered to its own key, as its cost dashboard.