Tenant connector account
Each connection belongs to the tenant and references an authorized provider account rather than a shared global credential.
Connector catalog · Public preview
Explore the business-system categories in Zurvina's connector architecture. Tenant binding, credential references, scopes, read/write separation, approval, verification, metering and audit are separate controls.
Current public catalog categories are previews. Write access is not enabled here and no provider is represented as production-certified without evidence.
Connection governance
The architecture defines a tenant-bound connector gateway. The accepted forensic baseline still treats connectors as mock by default with limited verification on branches, so target controls below are not availability claims.
Each connection belongs to the tenant and references an authorized provider account rather than a shared global credential.
The target connector contract stores a secret-manager reference only; raw credentials must not be exposed to public clients, prompts or ordinary records.
Requested and granted scopes are reviewed against the minimum required capability. Excessive or mismatched scope is intended to fail closed.
Read and write are explicit capabilities. Write operations are disabled by default until policy, approval and connector certification permit them.
Mock, implemented, read-verified, write-verified, production-certified and suspended are distinct lifecycle states. The public catalog currently claims Preview / not certified.
Potentially effectful writes become governed action proposals and follow entitlement, policy, risk and human-approval requirements before execution.
Effectful connector operations use stable operation identity so retries are intended not to create duplicate provider side effects.
A request is not proof of success. Provider identifiers and outcomes must be verified before completion is recorded.
Connector activity is designed to meter calls, effectful executions and applicable provider/API cost by tenant and operation.
Connection, scope, approval, execution, verification and outcome context remain attributable without exposing protected credential material.
Catalog by business function
Provider-specific availability will only be published when tenant binding, scopes, read/write behavior, verification and certification evidence support the label.
6 connector categories shown
Infrastructure
No production certification evidence is published for this preview category.
Review control documentationAccess
No production certification evidence is published for this preview category.
Review control documentationWorkplace
No production certification evidence is published for this preview category.
Review control documentationRevenue
No production certification evidence is published for this preview category.
Review control documentationService
No production certification evidence is published for this preview category.
Review control documentationIntelligence
No production certification evidence is published for this preview category.
Review control documentationEarly access
Explore an approval-governed operating model with the Zurvina team. Demo access remains controlled and no purchase occurs from this page.