Security Model
On-Premise Data Isolation
All data remains within the organization's network. No data is transmitted to external servers during normal operation. The only external communication occurs during initial license activation.
Authentication
Web users authenticate via email and password; the session token is stored in an HTTP-only secure cookie and expires after a documented lifetime. Runners authenticate via machine credentials (Machine Key + Machine Secret) and receive short-lived session tokens with automatic refresh.
Role-Based Access Control
| Role | Capabilities |
|---|---|
| ADMIN | Full system control: users, runners, licenses, all resources |
| DEVELOPER | Create/publish workflows, manage triggers |
| OPERATOR | Execute workflows and view results |
Encryption
Passwords and machine secrets are stored as one-way cryptographic hashes; the cleartext values are never written to disk. License data is encrypted at rest with a per-installation key. Transport: TLS with organization-provided certificates. Session tokens are signed with a per-installation secret.
Audit Logging
All administrative actions (user creation, runner registration, workflow publishing, license activation) are recorded with user ID, action, resource, IP address, and timestamp.
Was this page helpful?
A quick signal helps us prioritise improvements.