Cloud & Deployment Shapes
What workflow data crosses network boundaries in Catalyst deployments?
Only explicitly configured workflow data crosses network boundaries in Catalyst deployments. Catalyst leverages Dapr’s secure service-to-service networking to keep most internal workflow, agent state, and service traffic contained within your private cloud or on-prem cluster by default, restricting external transfers solely to manually approved third-party tool, model, or API integrations. Unintended external calls from custom workflow code may potentially expose data beyond your configured private network perimeter.
Was this article helpful?
Your feedback helps improve Diagrid's FAQ experience.
Keep reading
More Diagrid FAQ articles
- Cloud & Deployment Shapes
Can I run Catalyst within my private VPC or on-prem network?
Overview of deployment options for Diagrid Catalyst agent workflows within private, customer-controlled cloud network environments.
- Cloud & Deployment Shapes
How do I deploy Catalyst for hybrid cloud agent workflows?
IT teams practical guidance for deploying Diagrid Catalyst agent workflows via CNCF Dapr using secure tunnels for state synchronization across hybrid cloud
- Cloud & Deployment Shapes
How do managed and self-hosted Catalyst deployments differ?
Detailed comparison of operational overhead and infrastructure control tradeoffs for engineering teams evaluating managed