Skip to content

Security and trust

Trust the workflow because you can see and control it.

Zelvara keeps identity boundaries, application access, human decisions, releases, and operating history connected to the work they govern.

We do not display unverified certifications or compliance claims.

Control is a product behavior, not a badge wall.

Each control appears in the interface where an administrator or reviewer needs to make a decision.

Identity and Domain boundaries

Authorization is applied before resources, totals, activity, or traces are returned. Hidden resources use a consistent non-enumerating response.

Application and action permissions

Platform administrators publish and install reviewed application packages. Domain administrators configure only assigned accounts.

Human approvals

Sensitive work can pause with a readable impact summary before a person approves, edits, or denies it.

Versioned release and rollback

Draft, staging when enabled, and production point to immutable configuration revisions with audited release decisions.

Audit and operational visibility

Runs, decisions, releases, connection health, and recovery state remain inspectable without logging secrets.

A run can stop safely and still explain why.

Blocked work, denied actions, paused Domains, and revoked revisions are represented as explicit states with recovery context.

Action review

Approval required

Proposed change

Update 12 customer onboarding records

  • Within policy

  • Person decides

  • Audit retained

Sample data. This is an example of the review screen, not a customer record.

Architecture detail

Technical evidence stays available to evaluators.

Storage and release commits
PostgreSQL is the durable control-plane store. Redis is used for bounded cache and notification acceleration, not as the correctness dependency. Release pointer changes, audit records, and outbox events commit together.
Secrets and logging
Connection access tokens, refresh tokens, client secrets, registration credentials, and PKCE verifiers are encrypted. Structured logs redact tokens, secrets, free-text prompts, and raw audit payloads.
Revisions and rollback
Runtime conversations resolve and retain their starting production revision. New conversations use the current production pointer. Revoked revisions can advance affected sessions under an audited rollback policy.

Review the controls against your requirements.

Bring your identity, application, approval, release, retention, and audit questions to a focused product review.