Security
Security, identity
and architecture.
Your agents run in your environment. Verlet controls access to the evidence you choose to bring in.
01Architecture
Two environments.
A deliberate handoff.
The hosted application inspects recorded runs. It does not start your agent or replay its commands.
Your environment
Your agent and harness
Your model provider, tools and runtime.
Capture beside the work
SDK, supported proxy, MCP or OTLP.
Review and export
A local run bundle you choose to upload.
Local files remain under your access and retention controls.
Verlet hosted application
Stage and validate
Encrypted job staging, then role and policy checks.
Record the evidence
Organization-scoped sources and history.
Review and decide
Named reviewers, approvers and decision records.
Evidence is recorded after validation. Uploaded bytes enter staging first.
Inside the hosted architecture
- Web hosting
- Application entry and routing.
- Application hosting
- Python API and background worker.
- Managed identity and database
- Authentication and PostgreSQL evidence storage.
- Private queue
- Job-ID signals. Job bodies stay encrypted in PostgreSQL.
The public website is a separate static deployment. It does not connect to the application database or require an application session.
02Identity
Sign in.
Then check access.
An authenticated account also needs an enabled membership in the organization.
The hosted sign-in flow uses invited email codes or passwords through a managed identity service. The server checks account identity, organization membership and role on requests, and checks membership again before queued work runs.
| Role | Access |
|---|---|
| Viewer | Read authorized workspace records and safe run metadata. |
| Reviewer | Add and inspect permitted evidence, review captured content and prepare proposals. |
| Administrator | Manage organization settings, content intake and provider connections. |
Decision approval also checks the named approver's identity. An administrator role alone does not grant that approval.
Session and organization boundaries
Session cookies use Secure, HttpOnly and SameSite protections. Browser changes are subject to origin checks. Evidence and source tables enforce PostgreSQL row-level security; the application refuses a database role that can bypass it.
03Evidence
Choose what
crosses the boundary.
Metadata is the starting point. Capturing content is an explicit choice.
Permitted content
Content-bearing run uploads require an administrator's admission policy and permission and retention references. Telemetry attributes can also contain content. Check local files before upload. Export does not automatically redact secrets or personal data.
Specific encryption boundaries
Hosted source files, session payloads and job payloads use AES-GCM encryption. This is separate from the database's access controls. Local capture ledgers and exported bundles are plaintext; protect those copies with your own storage encryption and access controls.
Read-only cost connections
Supported billing connections read OpenAI API or Anthropic Console costs within an agreed provider scope. Connection credentials are encrypted and are not returned by the connection API. Revoking a connection stops future imports; it does not remove evidence already recorded.
04Decisions
Keep the record
behind the decision.
Reviewers can trace a decision to the evidence available when it was made.
History and approval
Evidence events are append-only, source files have content hashes, and earlier decisions retain their evidence snapshots. Approval checks the named approver and the configured policy for separating proposal from approval.
A file hash detects changed bytes. It does not prove who executed a run or establish a business outcome.
Retention and removal
Administrators can record retention policies and legal holds. Hosted organization erasure is a separate privileged maintenance operation with a preview and checks against the current evidence record.
Backups, downloaded records, identity-provider records and local capture files need separate retention and removal procedures.
Before you connect
Talk through your requirements.
Review identity, source permissions, retention and hosting requirements with us before onboarding.
Discuss securityThis page describes implemented application controls and the documented hosted architecture. Deployment settings and operational assurance need to be confirmed for your environment; it is not an independent security certification.
To report a security concern, contact hello@getverlet.com. Start with a description and leave credentials and customer data out of the message.