Where it runs
Use Mariete managed cloud, your approved cloud and model provider, or a fully local and air-gapped deployment.
Your work stays inside the boundary you choose.
Decide where Mariete runs, which systems it can access, when a person must review, and how long context remains. Security follows the work from the first brief to the finished action.
Control starts before the first agent runs.
Deployment, access, review, and evidence are one operating boundary. Each can be narrowed to match the work and the obligations around it.
What it can reach
SSO, SCIM, role-based workspaces, and least-privilege access keep every agent inside the systems and context you approve.
When people review
Human approval can remain at the decisions and actions that matter. The boundary is part of the workflow, not an afterthought.
What the record keeps
Audit logs, source evidence, and workspace retention settings make the path from brief to action visible and reviewable.
Vendor review should not start from zero.
Security, compliance, and procurement teams can request the current evidence package under NDA and speak directly with a named security contact.
What the review receives
- SOC 2 Type II and ISO 27001 documentation
- GDPR and HIPAA materials
- Latest third-party penetration test
- Sub-processor list and data-flow details
- Named security contact for due-diligence calls
Documentation is shared under NDA. Response targets and availability are confirmed when the request is received.