Airgap policy
Block tools that need internet access in an air-gapped environment.
Security and deployment
Keep workflow runs, work data, and software connections inside your environment by default.
Keep workflow data, logs, AI models, and software setup local. Use approved workstations or your own servers without relying on an outside cloud service.
Data location
Approved local folders
Public internet
Blocked
Controlled actions
Approval required
Credentials
Stored locally
Run records
Audit logging on
Backup policy
Customer managed
Before a run starts
3 / 3 checkedControls
Choose which tools, folders, users, and internal services each workflow can access. Keep passwords and keys in the local service instead of showing them in the interface.
Block tools that need internet access in an air-gapped environment.
Limit workflows to approved folders and local paths.
Keep connection passwords and keys in local settings.
Use signed-in sessions and roles to control access.
Record important security, workflow, software, file, and review events.
Use your own rules for backup, retention, recovery, and removal.
Deployment shapes
Start on one workstation, then use the same setup across managed lab computers or your own servers.
Administrators can control software versions, access, settings, data location, retention, backups, and reviews while keeping workflows close to lab software and data.
Run workflows and keep work data on one controlled workstation.
Send approved settings and software setup to managed lab workstations.
Connect approved internal storage and services under your company rules.
Workflow mapping
Review workstation rules, local servers, air-gapped use, encryption, access, and offline packages.