Authority before action
Recommendations do not become operational changes without explicit authorization and the required approvers.
Catalyst Trust Center
Know what is proven, protected, and ready for production.
Review the product boundary, data principles, pilot controls, and production exit evidence without separating trust from the decisions Catalyst is built to defend.
Assurance caseBoundary visible
Decision accountability
Proof travels with the work.
Trust is not a separate report. It is the evidence, authority, control, and outcome record behind each material decision.
1Signal
2Evidence
3Authority
4Action
5Outcome
Working productDemonstrable
Pilot controlsDefined
Production exitEvidence required
Buyer security summary
Start with the boundary you need to evaluate.
Move between the working product, pilot configuration, data handling, and production acceptance without reading the entire security review first.
Runs today
What the working product demonstrates
Catalyst demonstrates the complete accountability operating model with clearly labeled demonstration records.
Decision this supportsSee exactly which capabilities can be evaluated now.
The public experience does not connect to your production systems.
01
Audience command views and decision queues
02
AI governance, Agent Gate, and evidence review
03
Decision policy, delivery lineage, and outcome verification
04
Executive reporting and reproducible audit snapshots
Data and authority principlesReview four operating principles+
Traceable records
Source references, import times, evidence freshness, confidence, approvals, conditions, and measurement periods remain attached.
Minimum necessary data
Catalyst does not need prompts or responses merely to calculate AI cost, allocation, utilization, or value.
Tenant boundaries
Production architecture is designed around tenant-isolated data, permissions, connector scopes, and environment-specific policies.
Reporting and audit proofSee how a report claim opens to its source records+
Reproducible reporting proof
A report claim should open to the records behind it.
Catalyst retains the reporting period, creator, record count, integrity link, and exact source references behind a checkpoint. The demonstration shows the operating model; production immutability requires validated server-side storage and access controls.
Production path
A pilot must close foundational controls, not defer them.
Before production use, the deployment and its controls are agreed, tested, and evidenced. These are the ten decisions and exit tests Catalyst expects a pilot plan to contain.
Product views across this site use demonstration records. We do not publish real security data, ours or anyone else's.
Define the boundary
Agree deployment, region, tenancy, identity, and data handling.
Connect with least privilege
Approve each connector scope, secret owner, and action boundary.
Test the controls
Exercise isolation, authorization, recovery, logging, and rollback.
Make the production decision
Accept documented evidence against explicit go, extend, or stop criteria.
Architecture and dataDeployment, residency, encryption, and key custody.Open 3 controlsClose controls
Deployment model
Agree the hosted topology, network boundary, region, environments, and any private connectivity.
Required exit evidence
An approved architecture diagram, named service owners, and separate demonstration, pilot, and production boundaries.
Data residency
Inventory stored data, processing locations, subprocessors, and any cross-region transfer.
Required exit evidence
A signed data map stating what Catalyst stores, where it is processed, how long it remains, and how deletion is verified.
Encryption and key ownership
Confirm encryption in transit and at rest, key custody, rotation, and revocation responsibilities.
Required exit evidence
Documented cipher and key controls, a completed rotation test, and an explicit decision on provider-managed or customer-managed keys.
Identity and boundariesTenant isolation, SSO, roles, and least-privilege connectors.Open 3 controlsClose controls
Tenant isolation
Bind every request, record, connector, and policy evaluation to an organization and environment.
Required exit evidence
Negative cross-tenant tests, authorization tests, and an evidence package showing that one tenant cannot read or change another tenant's records.
Identity and SSO
Connect the organization identity provider and map groups to Catalyst roles and decision authority.
Required exit evidence
SSO, MFA and conditional-access behavior, joiner and leaver handling, privileged-role review, and a tested emergency-access procedure.
Connector permissions
Scope each connector to the minimum systems, records, operations, and environments needed for the scenario.
Required exit evidence
A reviewed permission manifest, read-only defaults, protected secrets, and separate written authorization for any action-capable connector.
Audit and resilienceRetention, integrity, backup, recovery, and operating ownership.Open 2 controlsClose controls
Audit retention
Set the retention period for evidence, decisions, policy versions, tickets, receipts, and verification records.
Required exit evidence
Searchable and exportable audit history, synchronized timestamps, access logging, and an immutability test for records designated as final.
Backup and recovery
Agree recovery-point and recovery-time objectives, backup ownership, and failure communications.
Required exit evidence
A successful restore test, documented dependencies, and a recovery runbook with named escalation owners.
Security and acceptanceSecurity testing, remediation, rollback, and the production decision.Open 2 controlsClose controls
Security testing
Threat-model the pilot architecture and test code, dependencies, secrets, access controls, and exposed interfaces.
Required exit evidence
Resolved critical findings, an accepted remediation plan for lower findings, and a production security review signed by both teams.
Pilot exit criteria
Define success before connecting production records, including accuracy, access, resilience, operating ownership, and measurable outcome.
Required exit evidence
Signed acceptance criteria, tested incident and rollback paths, approved data export and deletion, and an explicit go, extend, or stop decision.
The exact deployment choices depend on your environment. The evidence standard does not: the control must be documented, tested, owned, and accepted before production use.
Proof standardsReview how Catalyst qualifies product, value, and production claims+
Proof standards
How we handle proof.
No fabricated proof
Partner names, quotes, or outcomes are shared only with explicit approval.
No hidden production claims
The working demo and production prerequisites remain visibly distinct.
No value without evidence
Estimated opportunity and verified outcome remain separate throughout the evaluation.
Safe operating defaultsReview the actions Catalyst will not take without authority or evidence+
Safe operating defaults
Catalyst coordinates authority. It does not invent it.
No automatic model switching, subscription cancellation, or workload shutdown
No silent blending of demonstration data and live totals
No unqualified savings claims or invented zero values
No cross-currency totals without a documented conversion
No duplicate decision records when an opportunity moves to approval
No live-connector claim until your connection is configured and verified
Evaluate with a real scenario
Bring the controls, evidence, and outcome you need to defend.
We will show the boundary between the current working product and the production validation your environment requires.
Book a guided product demo