Model constraints
Allow or block families, specific models, and premium tiers by organization, sub-org, or employee.
Claude / GPT / GLM / DeepSeek / KimiEnterprise controls / P0
Put a model and spend boundary around every employee.
One identity-aware policy layer for model access, token consumption, and cost across providers, sub-orgs, teams, and individual employees.
Employee policy ledger
5 model families
IdentityModelsTokensCostState
Maya C.Platform3 / 512M$500Active
Jonah R.Product2 / 58M$32074%
Priya S.Security2 / 56M$240Active
Organization policyApplied before every upstream request
ScopeOrg → sub-org → employee
ControlsModel + tokens + cost
CoverageCross-provider model catalog
EnforcementBefore upstream spend
Why a separate control plane
Your model estate is cross-provider. Your policies should be too.
Provider-native consoles are useful inside their own boundary. Rispn adds the missing enterprise boundary across the models and coding tools an employee actually uses.
Enterprise identity
Maya Chen
Engineering / Platform
Unified policy
$500 + 12M tokens
Monthly employee envelope
ClaudeAllow
GPTLimit
GLMAllow
DeepSeekBlock
KimiAllow
Policy inheritance
Set the default once. Override only where the work requires it.
Policies flow from the enterprise to sub-orgs and employees. A more specific rule can narrow access, lower a limit, or grant an explicit exception with a visible audit trail.
OrganizationGlobal AI policyApproved families + enterprise ceiling
Sub-orgEngineeringClaude, GPT, GLM, Kimi
Sub-orgFinanceClaude, GPT
EmployeeMaya$500 / 12M
EmployeeJonah$320 / 8M
EmployeePriya$240 / 6M
What administrators control
Three boundaries, resolved as one policy.
Token limits
Set monthly or periodic token envelopes and define what happens as an employee approaches the boundary.
Alert / restrict / blockCost limits
Cap provider-reported spend, aggregate it across approved providers, and stop spend before the next request leaves Rispn.
Observed cost stays distinct from estimatesEnforcement path
The decision happens before the bill.
01Resolve identitySSO, user, sub-org, key
02Compile policyinherit + explicit override
03Check requestmodel, tokens, remaining cost
04Allow or stopauditable decision
Identity, privacy, audit
Govern people without collecting their work.
Enterprise SSO maps requests to policy. Normal hosted traffic retains structured operational metadata without storing exact prompt text or snippets by default. Administrative changes and request decisions remain auditable.
IdentitySSO + org mapping
CredentialsBring your own provider keys
Prompt dataNo normal text retention by default
AuditPolicy and route decision trail