Paid activation
AIGIS-hosted
Request an AIGIS-hosted activation; runtime work starts only after paid approval.
- Paid commercial activation first
- BYO production model keys
- Runtime provisioned after approval
AI governance & assurance
Your teams want AI everywhere. Your board wants proof it's safe. Governed enforces the access controls you already trust before any model sees your data, and turns every AI decision into board-ready evidence.
Natural-language question from a sales VP.
Resolved to her Salesforce identity; only her permissions apply.
Object, record, and field checks. Live, never cached.
Amount and SSN removed before the prompt was built.
Written to an append-only ledger. Replayable on demand.
Platform
Permissions enforced before the model, every action on the record, across the systems you already run.
replayable from the ledger
Strip, don't mask
Restricted data is removed before the prompt exists. Not hidden. Gone.
Enforced before the model
Object, record, and field permissions. Live, never cached.
Deploy anywhere
Model-agnostic
Trusted, and honest about it
Salesforce · in productionSOC 2 Type I · in progress3 provisional patentsGAR · open specServiceNow & SAP in design-partner co-development.
The defensible moat
Masking hides the value of a restricted field. Stripping removes the field entirely. The difference matters because a model that can see a field name can still reason about it, reference it, and surface it in a response.
Industry default
What the LLM sees:
The model still knows SSN__c and AnnualRevenue exist. It can reference those field names, draw inferences from their presence, and include them in its response.
AIGIS approach
What the LLM sees:
The model has no way to know SSN__c exists. The field is removed before the prompt is built, so there is nothing to reference, infer, or accidentally surface in a response.
For the technically curious: Salesforce Agentforce honors object and field-level security at query time. AIGIS adds a second layer that removes fields from the prompt context before the LLM ever sees them, so model output cannot leak structural metadata. Both approaches enforce permissions. Only one enforces them on the model itself.
How it works
Every request runs the same governed path before anything is read, written, or sent to a model. Here's what one looks like.
Live governed request
Enforced before the model
Setup paths
AIGIS is isolated by design. Teams can choose a paid managed launch, move the data-touching runtime into their own cloud, or run the governed data plane fully inside their boundary.
Paid activation
Request an AIGIS-hosted activation; runtime work starts only after paid approval.
Paid hybrid activation
Request a hybrid activation; Governed operates the experience while your sensitive data plane runs in your cloud.
Paid private activation
Request a customer-hosted activation; your team runs the full governed data plane in your environment.
For your engineers
A few lines to govern any AI call. Object, record, and field permissions enforced, restricted fields stripped, and an evidence record emitted, automatically.
from governed import Governed
gv = Governed(api_key="gv_live_…")
answer = gv.query(
"which renewals are at risk this quarter",
as_user="j.smith@acme", # enforced as this user
)
# → permissions enforced · 2 fields stripped · evidence record emittedTrust
No invented logos, no overstated certifications. Here is exactly where we stand, and where to verify it.
SOC 2 Type I · in progress
Audit initiated. Not yet complete.
Salesforce · in production
Real 3-tier enforcement: object, field, and record level.
ServiceNow & SAP · design-partner co-development
Active co-development. Enforcement asymmetry is disclosed on every pitch.
Model-agnostic · bring your own key
Claude, GPT, Gemini, open-source, or self-hosted. No lock-in.
3 provisional patents
Filed on permission-provenance enforcement mechanisms.
GAR · open-spec candidate
Governed Audit Record v1 — an auditor-grade provenance format for enterprise AI.
We disclose our enforcement asymmetry on every page: Salesforce enforcement is production-grade today; ServiceNow and SAP are active design-partner co-development. You will always know exactly what is enforced where.
Next step
Use a Salesforce-first governance review to inspect the permission path, the provenance ledger, and the current ServiceNow and SAP design-partner boundaries.