NodeFox
Security

Know where your data goes
and who holds the keys.

Runs execute in your browser or on your own machine. Model requests go straight to the provider you choose, with your keys. NodeFox handles sign-in and authorizes each run.

Data path

Four places your data can go.

A run touches your systems, your model provider and the machine it runs on, and relies on NodeFox services for your account and its authorization.

Your systems

A workflow reads and writes only through the APIs, files and folders you grant it.

Your model provider

Model requests go directly to the provider you configure, with your keys.

Where runs execute

In the browser of the person running it, or on your own machine with the headless runner.

NodeFox services

Sign-in, plan and run authorization, and optional publishing and audit features.

Credentials

Know where each key is held.

Provider keys are held where the run happens and go only to their provider. Access to your own systems is whatever you grant the workflow.

In the browser

Provider keys

Held in your browser’s workspace settings; review what an export contains before sharing it.

Connected services

OAuth connections are authorized through your NodeFox account.

Headless

Provider keys

In a keys file on the runner, readable only by its user (0600) and scrubbed from logs.

Organization keys

Enterprise admins can issue a setup code that places assigned keys on a runner.

Run authorization

Each run is authorized with a short-lived run key fetched from NodeFox.
Approvals and records

Gate the writes. Keep the record.

The workflow is an explicit graph, so what can change a system, and when, is visible in the visual graph before anything runs.

Writes wait for a condition

A consequential write fires only after the check or sign-off you wire in front of it.

People decide at set points

A run stops at the step you choose and waits for a person’s answer.

Code steps are JavaScript

Headless runs them in V8 isolates, with an OS sandbox on macOS and none on Linux.

Every run leaves a record

Headless runs keep their log, transcript and result on the machine, under retention you set.

Compliance

Where we stand today.

Review the controls that apply to your workflow: data destinations, credential access, approvals and execution records.

Certifications
None held today, including SOC 2 and ISO 27001.
Security review
We answer questionnaires and join your security review.
Single sign-on
Not available today.
Audit stream
Optional on Enterprise: run records streamed, encrypted, to your organization.

Bring your security questions.

We’ll walk through the data path for your workflow and answer your questionnaire.