Built to pass your customer's security review.

Every change is proposed, reviewed and approved by a named person before it is applied. Agents never hold credentials. Your customer can see every step.

Audit ledgerHarbor Mutual · illustrative
Example audit ledger entries
TimeByEntryResult
09:12SurveyorRequested read access to CRM: Account, ContactWaiting
09:40Customer ITApproved read access to CRMApproved
10:05BuilderProposed 12 field mappings, with sample rowsWaiting
11:18Vendor engineerApproved 11 mappings, edited 1Approved
13:30Dossier writerDrafted questionnaire answers, each citing the specDraft
14:02Customer ITRejected write scope on TicketingRejected
Every proposal, approval, rejection, change and rollback, with who, when and why. Exportable to your customer's security tools.

Know where every record goes.

Three parties, three territories. Choose where Pilotage runs and the chart redraws the route your customer's data takes.

Pilotage runs in
Your customerPilotageYour companyCustomer systemsCRMTicketingERPConnectorholds the credentialsDeployment specin your git repositorydecisions, mappings, settingsmetadata and masked samplesmetadata and masked samples,straight to your accountonly the spec crossesthe boundaryPilotage agentsscan, map, rehearse
  • Agents run in Pilotage's cloud and reach customer systems only through the connector.
  • They read metadata and sampled, masked records. Raw records are kept only as long as a test needs them.
  • What comes back to you is the deployment spec: decisions, mappings and settings.

The questions your reviewer will ask, answered.

Ten controls that apply to every deployment, whoever the customer is. The last three are specific to software run by AI agents.

Who can change a production system?Customer-approved changes
Production changes wait for the customer's named owner, not just the vendor. Every agent action has an autonomy level the vendor sets and the customer can only make stricter.
What can each connection reach?Least privilege
Every connection gets only the scopes the deployment spec lists, and the customer sees that list before granting access.
Who holds the credentials?No credentials in agents' hands
Agents never see raw credentials. They act through the connector layer, which holds and uses the secrets on their behalf.
What happens in an emergency?Break-glass access
Emergency access to a customer system is time-boxed, needs a stated reason, and is logged and shown to the customer.
Can we see what happened?A complete audit ledger
Every proposal, approval, rejection, change and rollback is recorded with who, when and why, and can be exported to the customer's security tools.
What if a record contains instructions?Protection against hidden instructions
Content read from customer systems is treated as data, never as commands to an agent, and is screened for instructions planted in records or documents.
How much data is kept?Data minimization
Rehearsal uses sampled, masked data by default. Raw records are not stored beyond what a test needs, and retention is set per customer.
Is our data used to train AI models?No training on customer data
Never, by Pilotage or a model provider. Providers are used under zero-data-retention terms, and the Pattern Library learns from stored approvals, not from training.
Could an agent act on something nobody approved?Every action bound to an approval
Each message and change carries an approval tied to its exact content. If one character changes after approval, it is refused.
How do you test the AI against attacks?Injection testing on every release
A suite of planted-instruction attacks runs before every release. Any success blocks the release.

Asked by security reviewers.

Does Pilotage change anything in production on its own?

No. Every change to a customer system is approved by a named person first, and production changes wait for the customer's own owner.

Who can see our customers' data?

Agents read through the connector layer and never see raw credentials. Rehearsal uses sampled, masked data by default, and retention is set per customer.

Can it run in our cloud, or our customer's?

Yes. Pilotage runs in its own cloud by default. With Pilotage in your cloud, it runs inside your cloud account or your customer's when policy requires it.

What happens when an agent is wrong?

Every proposal shows its evidence and sample rows before anyone approves it. Rejections are recorded, so agents stop proposing what reviewers turn down.

Do our customers need an account?

No. They join by email link, free, and can approve inside your own product.

Is our data used to help other vendors?

Your patterns stay in your own library. The shared network library is opt-in and holds only system-level knowledge with no customer or vendor content.

Everything a reviewer asks for, in one request.

Ask once and we send the documents your customer's security team needs.

Request the security pack
  • Security packArchitecture, data flows, controls and the answers most questionnaires ask for.
  • Data processing agreementReady to sign, with the processing terms for customer data.
  • Subprocessor listEvery third party that touches data, what it does and where it runs.
  • Per-deployment trust pageData flows, access scopes and the audit log for one customer, shared by link.

Bring us your next enterprise customer.

See your product deployed into a real customer setup, gate by gate.

A readiness diagnostic runs the Survey stage during the sales cycle, so you and your prospect see the gaps before signature.