Enterprise

Automation with controls your security team can review

Multi-department workspaces, granular roles, approval gates on high-impact actions, complete audit trails and a documented security posture that does not overclaim.

Enterprise posture

  • Dedicated workspaces per department, isolated by tenant scoping
  • Owner / admin / member / viewer roles enforced server-side
  • Approval checkpoints with named approvers and timestamps
  • Security event feed and audit log export
  • Custom integration work against documented APIs
  • Signed service agreements and DPA templates
Controls

What enterprise buyers actually ask for

Each item below is implemented in the product today unless explicitly marked otherwise.

Tenant isolation

Implemented

Every tenant row carries a workspace id. Cross-tenant reads are refused, return nothing, and are logged as critical events with the requester recorded.

Role-based access

Implemented

Four roles with explicit permissions, enforced in the data layer rather than the UI. A hidden button is not a permission.

Approval gates

Implemented

High-impact workflow and agent steps pause for a named human decision. Rejection cancels the run and preserves the record.

Audit trail

Implemented

Authentication, permission changes, billing events, workflow changes, agent tool calls and approval decisions are recorded.

Data export & deletion

Implemented

Self-service JSON export of workspace data, and owner-only deletion that removes workflows, runs and credentials.

SSO / SAML

Roadmap

Not enabled in this deployment. Enterprise agreements can specify SSO as a scoped implementation item.

Dedicated infrastructure

Custom

Single-tenant deployment options are quoted per contract and require a separate architecture review.

Compliance attestations

Not claimed

No SOC 2, ISO 27001 or HIPAA certification is claimed. Independent audits would be required before any such claim.

Engagement

How an enterprise rollout runs

  1. Discovery and controls review. Two to three sessions with operations and security. Output: process inventory and a control matrix.
  2. Pilot. One department, two workflows, measured for four weeks. Success criteria agreed in advance.
  3. Expansion. Additional departments with role and approval design per team.
  4. Managed operation. Monitoring, monthly review and quarterly roadmap under a service agreement.

Enterprise agreement outline

  • Scope: departments, workflows, integrations
  • Volume: runs, tokens, seats, workspaces
  • Security schedule: roles, approvals, retention
  • Data processing addendum (template, reviewed by counsel)
  • Support targets and escalation path
  • Exit: export, deletion, credential destruction

Contract templates are commercial starting points, not legal advice. Both parties should have counsel review the final agreement.

Start a conversation

Bring your security questionnaire

We answer with evidence from the implementation, and we will say plainly when something is not done yet.

Enterprise solutions · Sonai