01
Your data, your region
Choose where your data lives at onboarding — EU, UK, US, UAE, APAC. Single-tenant deployments isolate each customer's data plane. Enterprise customers can deploy on-premise or to a sovereign-cloud region with no outbound dependency.
02
Credentials never co-mingled
Connections in flow code are logical names; the actual URL and credentials are bound per environment and resolved at runtime. Secrets live in your secret manager of choice — HashiCorp Vault, AWS Secrets Manager, Oracle Vault, or our managed equivalent — never in our application database, never in flow code, never in logs.
03
Append-only audit trail
Every flow change, deployment, approval, and execution is recorded to an immutable audit log. Append-only at the database layer. Step-level payload capture for debugging is opt-in per flow with field-level redaction rules.
04
Approval workflows
Per-environment approval policies: auto, single-approver, two-approver, Slack-approval, signed-PR-merge. SOX-style separation-of-duties is enforced at the platform layer, not bolted on as process. Designated approvers see the full diff before signing off.
05
Encryption everywhere
TLS 1.2+ in transit. AES-256 at rest. Per-tenant key isolation on Enterprise plans. Customer-managed encryption keys (BYOK) on request.
06
AI assistant boundaries
Customer data is never used to train models. The AI assistant runs on your isolated workspace; payloads passed to it for debugging are governed by the same redaction rules as audit-log capture. On Enterprise, the AI tier can be disabled entirely.