Security

Built for data that matters.

How Nextra Flow is designed to protect credentials, data and execution, described as architecture. We do not claim certifications, and we label controls that are still planned.

01 — Architecture

Where each control lives.

Select a control to highlight the layer it protects.

Client / APITLS ↓
01EdgeTLS termination
02Control planeauth · roles · audit
03Execution planeisolated runners
04Secrets vaultcredentials
05Data storesrun history · logs

Architecture overview. Highlighted layers show where the selected control applies.

Credentials live in a dedicated vault, separate from flow definitions. Once saved, a secret is write-only.

  • Secrets referenced by ID, never embedded in flows
  • Write-only after save, never displayed again
  • Scoped access: a run receives only the secrets its flow needs

Design intent for the Nextra Flow preview. Controls are verified before general availability, and no certifications are claimed.

02 — Credential protection

Secrets are written once and never read back.

A credential you enter is placed in a vault. Flows hold only a reference to it, so a flow definition can be shared or exported without exposing a secret.

  1. 01You enter a secretOver TLS, into a write-only field.
  2. 02The vault stores itEncrypted and separate from flow definitions.
  3. 03The flow holds a referencesec_4t9d, not the value.
  4. 04A run receives it at runtimeOnly the secrets that flow needs, only for that run.
03 — Data encryption

Encrypted in transit and at rest.

Every connection to Nextra Flow uses TLS. Stored run history, schemas and configuration are designed to be encrypted at rest.

Sensitive values can be masked in logs and run history, so a failed phone number appears as a pattern rather than as the number. Key management details and algorithms will be documented once they are verified for the production environment.

04 — Access control

Roles decide who can do what.

RoleScopeManage membersSecretsEdit flowsView runs
OwnerBilling, workspace settings and everything below✓✓✓✓
AdminMembers, connections and secrets✓✓✓✓
BuilderCreate and edit flows, mappings and rules—✓✓✓
ViewerRead run history and dashboards———✓

API keys are scoped separately and are split into test and live environments.

05 — Execution isolation

One workload cannot read another.

Each execution runs in an isolated worker with resource and time limits. Custom expressions are evaluated in a restricted sandbox.

Workspace A · run_8f3k2
Workspace B · run_a71c0
Workspace C · run_2d9ee

Illustrative. Separate lanes, separate secrets, separate limits.

06 — Audit logging

Who changed what, and when.

Changes to flows, mappings, members and secrets are designed to be recorded, alongside the full history of every run.

EventSubjectActor
mapping.updatedshopify_orders_to_erp v3 → v4builder
secret.rotatederp-prodadmin
flow.runrun_8f3k2api key nx_test_…
member.role_changedviewer → builderowner

Sample entries to show the shape of the audit trail.

07 — Monitoring

You hear about problems first.

Failed runs, elevated failure rates and unusual access can alert your team. Platform-level monitoring watches the services themselves.

Alerts can be sent by email or webhook. The observability views show every failure with its cause, and the status page, once the service is live, will report platform availability.

08 — Enterprise controls

For governed environments.

These controls are on the roadmap for larger organizations. We label them so you can plan accurately.

SSO (SAML / OIDC)

Planned

SCIM user provisioning

Planned

Audit log export

Planned

IP allow-listing

Planned

Custom data retention

Planned

Private networking

Planned
09 — AI and your data

Proposals, not unsupervised access.

The AI assistant is designed to work from field names and masked samples by default, and to propose changes that you approve. Before AI features are enabled for real workspaces, we will publish what is sent to a model, how it is retained and how to opt out. In this preview, the assistant is a local simulation and sends nothing anywhere.

Our position

No badges we have not earned.

Nextra Flow is in preview and has no independent certifications or audits to show. When that changes, we will list them here with the scope and the date. Until then, we would rather show you the design and answer your questions.

Stop building the same integration twice.

Connect your systems once.Translate your data reliably.Keep every workflow moving.