Trust
Trust & governance
Zentro is built for teams that are accountable for operational changes. This page summarizes the control surfaces and commitments customers can rely on.
Control surfaces
Each block below maps to a signed-in route. Read the full narrative on the platform overview.
Audit trail
Operational events — API keys, billing webhooks, approvals, automation activity — are designed to land in one append-oriented log you can export and walk through with auditors.
Audit log →Approvals
High-impact automation waits for an explicit approval record before execution. The queue is a first-class route, not a side channel.
Approvals →Connectors
Optional HTTP backends for reasoning, robot-style automation, and health checks. Nothing runs against your stack until you configure endpoints and credentials.
Connectors →API access & keys
Scripts and integrations authenticate with scoped keys. Keys are created and rotated from Settings; usage flows through the same-origin API surface documented in the reference.
API keys →
Operational execution posture
The product is designed for review-first operations: dry-run and approval workflows for high-impact actions, with auditable records of approved execution paths.
Availability and abuse resistance
Public and sensitive routes are protected with authentication boundaries and request controls designed to reduce abuse and preserve service availability.
Customers can expect
- Explicit authentication for user APIs and alert ingest
- Audit-focused operational records for key platform actions
- Clear separation between evaluation mode and production-backed workspaces
Security communication
For security disclosures, data handling questions, and procurement review requests, contact support via zentro.run channels. Customer-specific architecture and implementation details are shared through authenticated support and enterprise review workflows.