Swfte Studio
A visual builder for agents and workflows, with the Connect gateway for model choice and Nexus for policy applied while agents run.
Best for: Teams that want governed agents and the workflows around them in one place, with approvals, traces and published prices, and managed hosting in AWS Ireland.
Build surface: A visual canvas for agents and workflows. The Team tier lists API access. Agents and workflows are two models under one editor.[1][2]
Tools, integrations and MCP: 100+ tool integrations, plus an API for custom systems. Agents can connect to external MCP servers (a Pro feature). Swfte does not expose your own agents as an MCP server today.[1][2]
Multi-agent, workflows and evaluation: The Pro tier lists multi-agent orchestration, and workflows are the core of the builder. Evaluation suites with an automated judge exist in the platform service. The Studio page also describes golden sets and regression runs; their status is listed as to confirm below.[1][2]
Governance and approvals: Role and tenant controls, human-approval steps in workflows, and a workflow step that pauses until a named person approves. Nexus applies policy while agents run. SAML SSO and SCIM are in development.[1][2]
Deployment and data control: Managed service with customer data at rest in AWS Ireland. Dedicated or private deployment is designed for and scoped as an engagement. No self-serve self-hosting.[1][2]
Pricing transparency: Free (10 workflows, 5 agents, 2,000 executions per month); Pro $39; Team $99 (3 users included); Enterprise custom. Studio meters executions.[1]
Built and designed, kept apart:
| Capability | State | Note |
|---|---|---|
| Visual canvas for agents and workflows; an agent can run as a workflow step | Built | Two models under one editor. |
| Human approval step in workflows | Built | Pauses until a named person decides; the decision is recorded. |
| Approval gate on agent tool calls at run time | In progress | Off by default, limited to worker runs today. |
| Connect to external MCP servers | Built | A Pro feature. |
| Expose your own agents as an MCP server | Not offered | Not available today. |
| Per-tool allow and deny rules on the MCP gateway | Designed for | The gateway checks an API key scope and logs each call. Per-tool rules are not built. |
| Evaluation suites with an automated judge | Built | In the platform service. |
| Golden sets, regression runs, release channels and gradual rollout | In progress | Not available today. Studio has A/B experiments between chatflow versions and version rollback; golden sets, regression runs against a baseline, release channels and gradual rollout are in development. |
| SAML SSO and SCIM | In progress | In development. |
Watch-outs:
- SAML SSO and SCIM are in development, not generally available.
- No self-serve self-hosting. Private deployment is an engagement with Swfte.
- The tool catalogue is 100+ integrations, a fraction of the largest in this guide.
- Agents and workflows share an editor but are not one graph model.
- Swfte does not publish an uptime SLA figure.
Sources: Swfte Studio page, Swfte pricing, Swfte trust page (read 2026-10-06).