Serve
Serve is the Compex workflow for governed deployment of models, APIs, or apps against protected data for approved users. It lets a service operate under policy-controlled execution rather than receiving unrestricted access to raw data.
What Serve can cover
- A model endpoint used by named internal users.
- A vendor API operating against client-owned data.
- A workflow app that returns scoped results.
- A decision-support service where outputs require evidence records.
How it works
Define the service boundary
The parties define who can use the service, what inputs are allowed, what data can be touched, and what outputs can be returned.
Approve the deployment
The model, app, or API is reviewed before being made available to approved users.
Serve under policy
Compex enforces the agreed scope and records service events, access decisions, and output context.
Monitor evidence
Reviewers inspect evidence records to understand usage, decisions, and boundary enforcement.
What this means
For business readers, Serve is the pattern for turning a successful pilot into a controlled user-facing workflow without handing over the underlying data by default.
Current status
Serve is pilot-ready when users, service scope, approval model, and output handling are clearly defined.
Limitations
Serve does not remove the need to validate the model or app itself. Model quality, output safety, and legal review remain separate responsibilities.
Plan a Serve pilot
Use the pilot process guide to define roles, service boundaries, and evaluation criteria.