Security
Last updated: February 1, 2026
Syla Flow was built for teams whose data cannot leave their own walls. This page summarizes how the platform is deployed, isolated and governed.
1. Deployment model
Syla Flow installs on-premises or inside your own private cloud account. There is no default path for workflow data, prompts or outputs to reach SYLA infrastructure — the platform runs entirely inside your perimeter.
2. Tenant and team isolation
Each department or team operates in its own isolated workspace. Workflows, data connections and tool credentials do not cross workspace boundaries unless an admin explicitly shares them.
3. Access control
Single sign-on, role-based permissions and least-privilege defaults govern who can view, edit or publish an agent. Admins manage access from one command centre with full visibility across workspaces.
4. Audit and traceability
Every workflow run, edit and permission change is logged. Live traces show each step and variable an agent produced, so a decision can be reconstructed after the fact.
5. Encryption
Data is encrypted in transit between platform components and at rest, using your environment key management where available.
6. Vulnerability disclosure
If you believe you have found a security issue in Syla Flow, report it to security@syla.one. We acknowledge reports within one business day and do not pursue legal action against good-faith research.
7. Request the full security brief
For architecture diagrams, deployment options and answers to a formal risk review, contact contact@syla.one or book a call.