A privileged position, treated as one.

These are properties of the system today.

Least privilege

Provider credentials are held by Verundo, never by the agent. An agent sees tools, not tokens, and only the tools it is granted.

Controlled execution

No action reaches a provider except through a protected action under policy. There is no bypass path for the agent.

Explicit approvals

Held actions execute only after a named person decides, and that decision is on the record with its reason.

Audit trail

Every run, action, approval, containment, recovery and observed external change is recorded, attributed to an agent identity and a model.

External verification

Recovery is confirmed by re-reading the external system, not by trusting an API response.

Data minimisation

Credential-looking values are masked before they are stored or shown. Verundo records what an action changed, not entire objects.

Idempotent execution

Every provider write carries an idempotency key, so retries and uncertain outcomes never duplicate a mutation.

Signed webhooks

Every inbound provider notification is signature-verified; the payload never decides state, only which object to re-read.

Tenant isolation

Each customer is its own organisation. Every record carries its organisation, the application checks it on every read and write, and PostgreSQL row-level security enforces it again in the database for all customer traffic.

Encrypted credentials

Each organisation's provider credentials are encrypted with AES-256-GCM before they are stored, under a key kept outside the database, and are never shown again. Agent keys are stored only as a fingerprint.

Hosted in the EU

The database and the application run in Stockholm. Error reports go to an EU-hosted tracker with personal data removed first.

Marked plainly: what is not built yet.

Managed key vault

KMS-backed keys per organisation with scheduled rotation. Today one application key, held outside the database, encrypts all stored credentials.

Configurable retention

Per-organisation retention windows for run records and before-states. Today records are kept for the length of the agreement and deleted when it ends.

SSO and approval rights

SAML/OIDC sign-in, and approval rights per role. Today accounts sign in with email and password, and organisations have owner, admin and member roles.

Certifications

Verundo holds no SOC 2, ISO 27001 or similar certification yet. We will not claim one until an auditor has issued it.