Security and data

Your workflows, not your data.

Nokto was designed by a former network and security engineer. The principle: collect the bare minimum, and never expose what should not be exposed.

Metadata only

Nokto reads the status, date and duration of executions. It neither reads nor stores the content flowing through your workflows.

Keys encrypted, never sent back

Your instance API keys are encrypted at rest and never returned to the browser. Create a key dedicated to Nokto, revocable at any time.

Hosted in Europe

Application and database on a dedicated server in Europe, with no US subprocessor for storage.

Strict isolation

Each organisation is isolated at database level. A client report link gives read-only access to that report alone.

Strong sign-in

Single-use sign-in link or strong password, attempt limits.

No AI in detection

Alerts rely on rules. No data is sent to an AI model to decide on an incident.

AI diagnosis is opt-in

Assisted diagnosis is off by default and enabled instance by instance. The context is redacted before analysis.

Everything is logged

Sensitive actions are written to an audit log: who, what, on which workflow, with what result.

In plain terms

What Nokto reads, and what it never reads.

What Nokto reads

  • The name and status of your workflows
  • The status, date and duration of executions
  • The number of executions per day
  • The error message of a failed execution

What Nokto does not read

  • The content processed by your workflows
  • Your credentials for third-party services
  • Your own customers' data
  • The content exchanged with an AI model

Frequently asked questions

Does Nokto read the data flowing through my workflows?

No. Nokto reads and keeps execution metadata: status, dates, duration, workflow name. The content processed by your workflows is neither read nor stored.

Where is the data hosted?

On a dedicated server in Europe, operated by Owepo. The API keys of your instances are encrypted at rest and never sent back to the browser.

Which permissions should the API key have?

Read access to workflows and executions is enough for monitoring. The retry and reactivate actions need write access: grant it only if you want to use those actions.

How do I delete my data?

Delete the instance in Nokto and revoke the key in n8n or Make. When a subscription ends, data is deleted within 90 days.

Your first monitored workflow in ten minutes.

Connect an n8n instance or a Make team: Nokto discovers your workflows, learns their rhythm and warns you at the first anomaly.

14 days free · no credit card · cancel anytime