Trust Center
Give security an accurate data-flow answer.
In BYOC, Calliope AI Workbench and your workloads run in your account. Calliope Labs Inc does not receive or proxy your prompts, code, model responses, or provider credentials. Model requests go directly to the endpoints you approve, including local endpoints when zero egress is required.
The trust model
Your workload boundary stays yours. Model egress is explicit.
Private AI is not one universal topology. The right design depends on data classification, model choice, customer contracts, and who operates each part of the system. We document those boundaries instead of collapsing them into a slogan.
For BYOC, the Workbench and workload data plane run inside your cloud account, network, and region. Your IAM, storage, network policy, and logging remain part of the control environment. Calliope Labs Inc does not sit in the path of workload or model traffic.
If you choose a hosted model provider, prompts and context travel directly from your environment to that provider under your agreement with them. If the workload requires zero egress, use a local model or an endpoint inside the approved boundary.
- Customer-owned data plane · Workbench sessions, workload compute, and storage run in the environment selected for the deployment.
- No Calliope AI prompt proxy in BYOC · Workload payloads do not pass through Calliope Labs Inc systems.
- Explicit model destinations · Your organization approves the endpoints allowed to receive model requests.
- Customer-held credentials · Provider keys remain in the deployment environment and are not exposed to Calliope Labs Inc.
- Zero-egress option · Keep inference local or inside the approved network boundary when external model traffic is not permitted.
Compliance status
Deployment topology is not certification.
Running Calliope AI inside an environment you already control can reduce the number of new data flows you must review. It does not transfer certifications or remove your obligations. The table below separates current Calliope AI status from the controls available in a customer deployment.
| Framework | Status | What it means for you |
|---|---|---|
| SOC 2 Type II | In progress | Formal attestation is not complete. Request the current security packet and available evidence for your review. |
| HIPAA | BAA on request | BYOC can keep Workbench and workload data inside your HIPAA-scoped environment. Model destinations still need to match your PHI policy and agreements. |
| GDPR | Controls aligned | A DPA and subprocessor list are available. Select region, deployment topology, and model endpoints to meet your own residency and transfer requirements. |
| EU AI Act and NIST AI RMF | Control mappings available | Zentinelle AI evidence can be mapped to AI-specific logging, attribution, policy, and oversight requirements. A mapping is not a certification. |
| ISO 27001 | Roadmap | Not currently certified. Security documentation can be reviewed against your supplier requirements. |
| PCI DSS | Not certified | A customer may scope BYOC inside its own PCI environment, subject to its architecture, assessor, and operating controls. |
| FedRAMP | Evaluating | No FedRAMP authorization is claimed. Public-sector and isolated deployment requirements are scoped with the customer. |
Data protection
Controls follow the topology you choose.
Storage in the chosen account
For BYOC, workload storage remains in customer-owned resources with customer retention and deletion controls.
Data protection →Customer network controls
Use customer IAM, network policy, private connectivity, and logging around the Workbench and workloads.
Architecture →Workbench administration
Base Workbench capabilities include identity, role-based access, and workspace access records.
Workbench →Agent-level policy when needed
Add Zentinelle AI to observe connected AI traffic, evaluate policy, enforce decisions, and retain evidence.
Zentinelle AI →Topology matched to risk
Choose BYOC, managed, on-premises, or isolated deployment based on the boundary your workload requires.
Deployment →Customer-held model keys
Bring approved provider credentials or run local models. In BYOC, Calliope Labs Inc does not receive those keys.
Secrets →Document packet
Give reviewers the documents behind the claims.
Public documents are linked below. Request the full packet for the latest security questionnaire responses, compliance progress, architecture material, BAA availability, and other evidence relevant to your topology.
Data Processing Agreement
How personal data is handled and processed.
Subprocessors
The third parties used by Calliope Labs Inc.
Privacy Policy
What Calliope Labs Inc collects and why.
Security Architecture
Deployment, isolation, identity, and network controls.
Compliance Status
Current status by framework, without implied certification.
Acceptable Use Policy
Permitted and prohibited uses.
Terms of Service
The commercial terms.
EULA
End-user license terms.
Open-Source Notices
Licenses for open-source components and the Astrolift AI and Zentinelle AI cores.
Bring the real architecture into the review.
Send the questionnaire and the proposed topology. An engineer can walk your reviewers through the workload boundary, model destinations, operator access, available evidence, and any controls that remain your responsibility.
