Policy
A policy enforcement point for AI requests
PEP sits between your people and the model. An existing chat client keeps working. You change its address to PEP. From then on, every request can be identified, checked against your rules, and recorded before a model sees it.
The boundary in front of the model. Corporate policy is the floor. A person can make that boundary tighter. They cannot make it looser unless the organisation has said so.
Where it runs
People sign in to the console. The console talks only to the control plane. The PEP instance that handles the AI request can run beside that control plane, in the client’s public cloud, or in the client’s own environment.
People
Sign in with single sign-on
An administrator manages the organisation. A person may hold a profile that makes policy stricter. The organisation’s identity provider signs them in. PEP does not keep a separate password for them.
Applications
Call a PEP instance
A coding tool or another application sends the AI request straight to the PEP instance. It does not sign in to the console to do that.
People reach the console. Applications do not.
User interface
PEP Console
HTTPS. The signed-in session stays between the browser, the console, and the control plane.
Control plane
Management
The console calls this service. It does not open the database, and an AI request does not pass through it. Before anything changes, the control plane checks the person, the action, and the organisation.
- Organisations and membership
- Organisation policy
- User profiles, which can only narrow that policy
- Which organisations an instance serves
- The configuration an instance should run
- Enrollment of a new instance
- An audit of each administrative change
The instance calls out. The control plane does not call in. Outbound HTTPS, with a key that belongs to that instance.
RiskRate environment
SaaS
The console, the control plane, and the PEP instance run in our cloud. The AI request is handled there.
PEP instance
Handles the AI request with the policy it already holds.
The request then goes to one of these.
- Router beside the PEP
- Central Router
- A model, directly
Client public cloud
Dedicated
A dedicated PEP instance runs in the client’s public-cloud account. It calls the control plane. The control plane does not open a path into that account.
PEP instance
Handles the AI request with the policy it already holds.
The request then goes to one of these.
- Router beside the PEP
- Central Router
- A model, directly
Client environment
On-premises
The PEP instance runs in the client’s own environment. It calls the control plane over an outbound connection. No inbound management path is required.
PEP instance
Handles the AI request with the policy it already holds.
The request then goes to one of these.
- Router beside the PEP
- Central Router
- A model, directly
If the control plane cannot be reached, the instance keeps the last policy and configuration it accepted. It does not loosen that policy because management is unavailable.
What you get
Sensitive information stays out of the model
A secret, a password, or other data your policy marks as sensitive is stopped or cleaned before a model receives it. The model works on the request the policy allows.
Evidence for a compliance review
Decisions are recorded against the policy version that made them. The record keeps who asked, what PEP decided, and which route produced the answer. Raw prompts stay out of that record unless policy explicitly allows them.
See the risk without slowing the answer
In shadow mode the person receives the model’s answer at the speed of a direct call. Beside that answer, PEP records the risk it saw and the decision it would have made.
Hold a plan before the work continues
In gated mode the model writes a plan first. PEP compares that plan with what the person asked. An acceptable plan is followed by the answer. A plan that drifts is repaired inside a fixed budget, or stopped.
A hard stop on denied actions
When PEP can see a tool or a retrieval step, it can stop an agent from deleting or exposing protected material. A tool or destination the policy denies is not repaired into a different action.
Runs where the organisation needs it
The same service runs in European managed hosting, inside the customer network, or air-gapped with a local database and the organisation’s own models. There is no required US cloud.
This page describes PEP. It is not available to order.
The other products
- Router — Policy decides which routes are allowed. Router decides which of those routes is the right one: sufficient capability, at the lowest expected cost.
- Search — Each subject keeps its own index: the sites, feeds and pages that belong to that subject, refreshed on a schedule and retrieved when a model is allowed to look.