Security & Privacy
Learn how the platform ensures total data sovereignty and execution safety through a local-first, privacy-centric architecture.
Zero Data Leakage
Sensitive data never leaves your infrastructure. All processing happens on your own hardware.
Isolated Execution
Workflows run in isolated environments to prevent cross-contamination or unauthorized access.
Secret Management
Credentials are stored exclusively in environment variables or a local encrypted vault.
Privacy Philosophy
Traditional automation tools (Zapier, n8n Cloud) require you to send your data to their servers. We believe that for many use cases—especially involving proprietary data or sensitive customer information—this is an unacceptable risk. Our platform is built on three core pillars:
Complete Data Ownership
You own the database, the logs, and the code. We have zero access to your data or usage patterns.
Local Execution
Workflow logic, AI reasoning, and tool executions occur strictly on your local machine or private cloud.
No Hidden Telemetry
The open-source core contains no tracking pixels, analytics, or phone-home mechanisms.
Execution Guardrails
Runtime Safety
- • Timeout limits for every step execution
- • Memory usage constraints for worker processes
- • Restricted filesystem access for tool executors
Audit & Transparency
- • Full execution logs for every workflow run
- • Input/Output sanitization for all tool calls
- • Open-source codebase for community security auditing
Security Best Practices
To maintain a secure environment, we recommend following these guidelines:
- 1. Never commit
.envfiles to git - 2. Use strong, unique API keys for LLM providers
- 3. Restrict MongoDB access to localhost or your VPC
- 4. Regularly audit workflow logs for unusual activity