Swfte Studio
A visual builder for agents and workflows on the same platform as the Connect model gateway and Nexus policy layer.
Best for: Teams that want AI agents and business workflows built, tested and governed in one place, with published prices and managed hosting in AWS Ireland, and who can live with a smaller connector catalogue.
Connectors and integrations: 100+ tool integrations, plus an API for custom systems. That is far fewer than the largest catalogues in this guide.[1]
AI-native capability: Builds agents and workflows in one canvas. The Pro tier lists multi-agent orchestration. Agents can connect to external MCP servers (a Pro feature). Swfte does not expose your own agents as an MCP server today.[1][2][3]
Governance and approvals: Role and tenant controls, and human-approval steps in workflows. A workflow step can pause until a named person approves. Policy applied while an agent runs is handled by Nexus. SAML SSO and SCIM are in development.[1][2][3]
Deployment and data control: Managed service, with customer data at rest in AWS Ireland. Dedicated or private deployment is designed for and scoped with Swfte as an engagement. There is 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. Pro lists 25 agents and 25,000 executions a month; Team lists unlimited agents and 100,000 executions.[1]
Extensibility: An API for custom systems is listed on the Team tier. Model access goes through the Connect gateway, which takes your own provider keys.[1][2]
Built and designed, kept apart:
| Capability | State | Note |
|---|---|---|
| One canvas for agents and workflows, with an agent usable as a workflow step | Built | Two models under one editor: an agent is not the same object as a workflow graph. |
| Human approval step that pauses a workflow until a person decides | Built | The decision is recorded. A denial stops the run unless the graph has a deny branch. |
| Approval gate on agent tool calls at run time | In progress | Off by default, and limited to worker runs today. |
| Runtime policy and a hash-chained record of agent actions (Nexus) | Built | Applies to runs enrolled in a policy. |
| Connect to external MCP servers | Built | A Pro feature in Studio. |
| MCP gateway with API-key scope and call logging | Built | Logs the call, not its arguments or caller. No per-tool allow or deny rule on the gateway yet. |
| Expose your own agents or workflows as an MCP server | Not offered | Not available today. |
| 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, as the pricing and trust pages say. |
| Dedicated or private deployment | Designed for | Scoped with Swfte. Not self-serve. |
Watch-outs:
- The connector catalogue is a small fraction of the largest in this guide. Check your own systems against the list first.
- SAML SSO and SCIM are in development, not generally available.
- No self-serve self-hosting. Private deployment is an engagement with Swfte.
- Swfte does not publish an uptime SLA figure and does not claim to be “GDPR compliant” or “EU AI Act compliant”.
- Studio drives tools and APIs. It does not operate a desktop screen the way RPA does.
Sources: Swfte Studio page, Swfte pricing, Swfte trust page (read 2026-10-06).