Agentic Index
FLOWX.AI vs Wonderful (2026)
FLOWX.AI last verified ·Wonderful last verified
FlowX is the stronger pick for modernizing a bank's back office on its legacy core, and Wonderful for customer service across many languages. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
FlowX starts you from a catalog of 246 pre designed agents, grouped into stacks for banking, insurance and logistics, and runs them on top of mainframes and core systems without replacing them. Wonderful came up through customer service, with voice, chat and email agents that its own engineers roll out on site in more than 35 markets. Both can work the screens of systems that have no API, and both can run inside the customer's own environment.
On the Agentic Index human approval ranking, FLOWX.AI clears the bar and Wonderful does not. FLOWX.AI documents all three intervention capabilities in full; Wonderful does not document autonomous triggers in full. 175 of the 554 platforms it grades clear it. See the human approval ranking
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. FLOWX.AI and Wonderful are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 1,165 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose FLOWX.AI if
- You want to start from working designs, with 246 catalog agents grouped into stacks for mortgage underwriting, commercial onboarding and fraud investigation.
- Your core runs on Jack Henry, FIS, Temenos or a mainframe, and agents have to work on top of it without replacing it.
- Regulation changes often, and you want agents that propose workflow updates for human approval before builder agents put them in place.
Choose Wonderful if
- Customer service is where you start, with voice, chat and email agents that need to work in local languages across many markets.
- You want forward deployed engineers on site to build the first use cases and then hand ownership to your team.
- You also want one gateway that routes, budgets and governs every model call across the company.
| Feature | F FLOWX.AI |
W Wonderful |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
FLOWX.AIIntegrations & Tool Calling Connectors do the integration work. A connector is a microservice the customer builds and deploys in any technology, acting as an anti corruption layer over an external system, responsible for data transformation between formats and for enrichment such as flags and tracing identifiers. Building one means configuring a Kafka consumer and producer, naming the in and out topics against the pattern the engine listens on, setting consumer threads against partition counts, defining the incoming and outgoing DTOs and implementing the business logic with the process instance UUID as the message key, with optional health checks, and FlowX publishes a quickstart repository and a currency exchange example connector. Connectors are invoked from the Process Designer through Send Message Task and Receive Message Task nodes, and the engine captures the reply into process variables. The platform also connects to named systems, including the Jack Henry, FIS, Finastra and Temenos core banking platforms, COBOL mainframes, transportation management systems, custom in house applications and RPA tools, plus databases, REST APIs, files over FTP, SFTP, Amazon S3 and Azure Blob, email, webhooks and AI tools over the Model Context Protocol, leaving the systems of record in place rather than replacing them. Sourcedocs.flowx.ai 5.9 building a connector and integrations overview pages, flowx.ai platform integrations pageread 2026-10-25 |
||
|
WonderfulIntegrations & Tool Calling Agents connect to the systems the work runs on, reading data, triggering actions and updating records directly in CRMs, ERPs, policy systems and data platforms. Engineers build on the underlying integrations, APIs and tools, and enterprise MCP gateways control what each agent is allowed to call. Sourcewonderful.ai/blog-articles/wonderful-an-enterprise-platform-to-turn-ai-ambition-into-agents-in-productionread 2026-10-03 |
||
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
FLOWX.AIWorkflow Orchestration FlowX processes are built from BPMN blocks, including exclusive (XOR) gateways that route each instance down one path on evaluated conditions and parallel gateways for concurrent branches. A Custom Agent node and BPMN integration place AI agents inside processes, and Agent Builder offers typed AI nodes such as intent classification and context retrieval. Sourcedocs.flowx.ai 5.9 exclusive gateway, parallel gateway, Custom Agent node and Agent Builder pagesread 2026-09-30 |
||
|
WonderfulWorkflow Orchestration Each agent is a composition of skills and loads only the ones the current task needs, so a single agent can carry a multi step process across domains and make decisions along the way. An orchestrator and managed workflows run complete business processes from the moment work arrives until it is resolved, and work can be handed between agents on different platforms over the A2A protocol. Sourcewonderful.ai/agentsread 2026-10-03 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
FLOWX.AITriggers & Channel Coverage Scheduled processes automate instance creation on dates, times or intervals through Start Timer Event nodes, with timer expressions in cron syntax or ISO 8601 durations, and timer start, intermediate and boundary events are each covered separately. Incoming Webhooks start a process from an external HTTP POST or resume a running instance, secured with API keys and running on events with no polling. Email Trigger connects to IMAP servers to monitor mailboxes, and Message Start Event starts an instance on a message, incoming email or incoming webhook. Four REST endpoints start processes, including by workspace and process name. Manage Triggers provides a central place to view, activate and deactivate event based triggers. A Chat UI component supports agent conversations with end users, with client SDKs for web, iOS and Android. Sourcedocs.flowx.ai v5.9 documentation index reached via the published /llms.txtread 2026-09-01 |
||
|
WonderfulTriggers & Channel Coverage Work reaches the agents through voice, chat, email, documents and embedded experiences, with the same skills applying on every channel. Live deployments include inbound calls at a national telecom, appointment booking at a bank and collections across 2.5 million clients, and an agent waiting on a human approval resumes when the approval arrives. Wonderful does not publicly describe schedule or webhook triggers. Sourcewonderful.ai/agentsread 2026-10-07 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
FLOWX.AIKnowledge Grounding & RAG The Knowledge Base integration ingests documents into Knowledge Bases that agents query during workflow execution, using vector embeddings with hybrid, semantic or keyword search, multiple stores, relevance scoring, append, replace and delete operations with an audit trail, and entries versioned with the app; companion pages cover managing stores, using Knowledge Bases in workflows and testing queries. Sourcedocs.flowx.ai 5.9 Knowledge Base integration overviewread 2026-09-30 |
||
|
WonderfulKnowledge Grounding & RAG Every agent works from what the organization already knows, with its data, documents and policies becoming the shared context agents draw on, read under one set of permissions. Knowledge bases sit in the chain each agent draws on, and each skill can carry its own knowledge for a specialized task. Wonderful does not say publicly how documents are indexed or refreshed. Sourcewonderful.ai/agentsread 2026-10-03 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
FLOWX.AIMemory & State Persistence Session memory lets AI nodes in chat driven workflows see earlier messages from the current conversation. A builder turns it on per Custom Agent or Intent Classification node with the Use conversation memory toggle, which is off by default, and a Memory tab in the workflow console shows the context that was sent to the model. That built in memory is tied to the chat session ID and is not shared across sessions or users. For memory that carries from one conversation to the next, FlowX publishes a cross session pattern. Each user's preferences, decisions and key facts are kept as a persistent profile in a dedicated FlowX Database data source keyed by user ID, and a summary of that profile is injected at the start of every new session so the agent can draw on earlier interactions. The profile store is a data source the customer creates and manages in FlowX Database, separate from the business data its processes run on. Sourcedocs.flowx.ai 5.9 memory capabilities and session state management patternread 2026-10-25 |
||
|
WonderfulMemory & State Persistence State carries through a run, so an agent that pauses for human review picks up where it left off once the work is cleared. Wonderful says every decision builds a record the platform learns from, but it does not describe a memory that agents read across separate conversations, or a scope or retention period for one. Sourcewonderful.ai/blog-articles/computer-useread 2026-10-03 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
FLOWX.AIHuman Oversight & Guardrails The hybrid AI and business rules pattern includes a runtime human gate as a named variation, with approval gates placed after AI steps so a reviewer sees the AI output and can correct it before it feeds the next step. The gates are built with User Task nodes in the parent BPMN process and are recommended for initial deployment and for high stakes decisions. A confidence weighted variation feeds the AI confidence score into the business rules, so low confidence extractions tighten thresholds or flag the result for manual review. The alternating AI and script structure leaves a traceable record of which extraction produced which input value, which formula computed which result and which classification drove which filter. Above the runtime, the FlowX.AI 5 architecture gates agent self modification of the platform, with agents proposing workflow changes and builder agents implementing them only after a designated operator approves. Observatory adds a policy engine evaluated against runs with Guards checking content before it reaches users, and tracks human in the loop and override mechanisms as EU AI Act controls with evidence attached. Sourcedocs.flowx.ai 5.9 hybrid AI and business rules pattern and Observatory pages, vendor submitted correction verifiedread 2026-09-09 |
||
|
WonderfulHuman Oversight & Guardrails A policy layer monitors every conversation for attempts to reach sensitive data or disclose what an agent should not, and teams configure the response, such as transferring to a human or ending the conversation. Agents pause where human review is required and resume once the work is cleared, and Wonderful Apps puts approve and decline controls in front of the people supervising each agent. Sourcewonderful.ai/blog-articles/the-hard-part-of-ai-agents-isn%e2%80%99t-building-themread 2026-10-03 |
||
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
FLOWX.AISecurity, Identity & Governance FlowX.AI operates an information security management system certified against ISO/IEC 27001, and an independent SOC 2 Type I examination confirmed its controls were suitably designed as of 17 June 2026 against the AICPA Trust Services Criteria for Security, Availability and Confidentiality. The SOC 2 Type II examination over an operating period is in progress, personal data is processed under GDPR, and the SOC 2 report and ISO 27001 certificate details are available under NDA through the contact form. Platform security has five layers. Identity is delegated to an external provider, with step by step Keycloak and Microsoft Entra ID configuration. Role based access control works at organization, workspace and project level with a published roles and permissions matrix, and separate runtime authorization for each project governs who reaches a published solution through project roles, end user groups and solution sharing. A dedicated Audit service centralizes platform events, and a Personal Information Guard detects and redacts personal data before it reaches a model and restores it afterwards. Swimlanes, business filters that restrict process instances by a business value, and permission based expressions that control UI visibility by role round out the controls, while Observatory's compliance mappings cover the customer's own AI apps. Sourceflowx.ai trust page, docs.flowx.ai 5.9 Securityread 2026-09-11 |
||
|
WonderfulSecurity, Identity & Governance Wonderful states SOC 2 Type II and ISO 27001:2022 certification, PCI DSS and GDPR compliance and EU AI Act alignment, verified independently each year, plus third party penetration tests twice a year. Permissions decide who can build, edit and ship agents down to the individual resource, and the AI Gateway sets which roles or teams may use which models. The detailed control list sits in a Vanta trust center at trust.wonderful.ai. Sourcewonderful.ai/ai-osread 2026-10-03 |
||
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
FLOWX.AIObservability & Auditability Observatory is FlowX's layer for watching AI agents at work. An SDK decorates agents, chains and tools and streams events to the Observatory API, which stores telemetry in PostgreSQL and optionally routes content through Observatory Guards for safety checks. A run is one execution trace, and an event is a log entry inside it. Four pillars read from that same store. Observability gives real time tracing of every agent, chain and tool call with cost and latency analytics, drift detection and threshold alerts. Governance gives a policy engine evaluated against runs, a six dimensional risk score per app, evidence collection and assessments, with apps registered in an AI registry. Compliance maps EU AI Act, NIST AI RMF and ISO 42001 controls to the runtime, with eighteen EU AI Act requirements scoped by risk tier, each resolving to met, partial, gap or out of scope, and a one click audit pack export returning per requirement evidence with timestamps, telemetry summaries and a gap analysis. ROI covers risk adjusted return, payback, NPV and Monte Carlo sensitivity per agent and project. Retention is configurable, with a seven year setting offered for the EU AI Act record keeping requirement, and Observatory can be self hosted as well as used as a managed service. These compliance mappings cover the customer's own AI estate. Sourcedocs.flowx.ai 5.9 Observatory overview and EU AI Act compliance pages, vendor submitted correction verifiedread 2026-09-09 |
||
|
WonderfulObservability & Auditability Conversations, decisions and tool usage are observable by default, so a team can see why an agent behaved as it did and not only what it did. Failures can be traced to the exact moment in a conversation and tagged, alerts flag tool failures and unusual volumes, and an immutable audit trail covers the environment, including every action an agent takes inside a legacy system. Sourcewonderful.ai/blog-articles/the-hard-part-of-ai-agents-isn%e2%80%99t-building-themread 2026-10-03 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
FLOWX.AIDeployment & Data Residency FlowX can run in the customer's own infrastructure as a containerized platform on Kubernetes, with setup guides for the FlowX Engine, Application Manager, Runtime Manager, Kafka authentication, Redis, ingress routing and authorization, and SaaS terms are published beside license terms. No managed cloud region selection is described. Sourcedocs.flowx.ai 5.9 setup guides and flowx.ai legal footerread 2026-09-30 |
||
|
WonderfulDeployment & Data Residency Four deployment models are offered: multi tenant SaaS with logical isolation, dedicated single tenant infrastructure, bring your own cloud on AWS, Azure or Google Cloud with data kept inside the customer's organization, and a fully air gapped on premises install maintained on site by Wonderful's engineers. Data residency options are set out in the trust center. Sourcewonderful.ai/deploymentread 2026-10-03 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
FLOWX.AIPrebuilt Agents, Templates & Packs FlowX lists 246 pre designed agents by industry and business area, 80 for banking, 69 for insurance and 97 for logistics, each with a one line function and a deployment effort estimate of low, medium or high driven mainly by how many systems it integrates with. FlowX describes catalog agents as blueprints rather than shipped components, each a pre designed combination of platform capabilities built with Agent Builder nodes and integration workflows, and every one is a variation of a small set of recurring agent typologies, each with its own page naming the nodes that implement it. Agents are grouped by business area into multi agent stacks, nine covering retail mortgage underwriting and seven covering commercial onboarding, coordinated with the multi agent orchestration patterns, with a fraud investigation stack of seven (alert triage, false positive screening, evidence compilation, timeline generation, case narrative, SAR compilation, call transcription) and a garnishment processing stack of six among the named compositions. The stacks page lists 50 stacks in all, 11 for banking, 9 for insurance and 30 for logistics. The same catalog can be browsed on the FlowX site with filters and detail views under a heading of 246 agents, while the homepage and about page round the count to 220 plus. Sourcedocs.flowx.ai 5.9 agent catalog, flowx.ai agent catalog and agent stacks pagesread 2026-10-25 |
||
|
WonderfulPrebuilt Agents, Templates & Packs A catalog lets a customer's own teams build an agent, skill or tool once and reuse it across the organization, and reusable skills package a procedure for any agent that needs it. Workflows such as KYC and credit servicing are taken into production by Wonderful's deployment teams, and Wonderful names no set of prebuilt agents or templates a customer adopts. Sourcewonderful.ai/agentsread 2026-10-03 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
FLOWX.AIModel Flexibility & Routing Customers configure model providers themselves under Organization Settings, AI Settings, Model Providers. They add a provider from a catalog, supply their own API key or use the FlowX managed key, test the connection against the provider API, and then whitelist which discovered models are available downstream, grouped by capability with context window and indicative pricing shown for each model. Defaults and Fallbacks assigns a default and an optional fallback model for each AI capability (text generation, image understanding, embeddings, document and OCR, developer agents, audio), set separately for Sandbox, Staging and Production workspaces. Workflow designers override the model on individual AI nodes using a portable provider and model identifier with an optional fallback provider and model, and the model is chosen from the node override first, then the workspace default, and otherwise the run errors. Supported providers are OpenAI with FlowX managed or bring your own key and EU, US and Global base URL presets, Azure OpenAI as bring your own key against the customer's own deployment endpoint, Mistral as bring your own key across its chat, vision, embedding and OCR lines, and any OpenAI compatible endpoint through a custom base URL. Two named permissions gate reading and editing the configuration. New providers in the catalog arrive on SaaS first, at release 5.10, and reach self hosted deployments in the next LTS release family. Sourcedocs.flowx.ai 5.9 AI providers and model configuration, vendor submitted correction verifiedread 2026-09-09 |
||
|
WonderfulModel Flexibility & Routing Nothing built is locked to one model, since the platform routes each task to the model that fits and new models drop in without rework. Admins keep control through the AI Gateway, which sets which roles or teams can reach which models, caps budgets and limits premium model use, and the company's CTO says customers choose the best models for each workload. Wonderful does not publicly show a model picker for each agent. Sourcewonderful.ai/ai-gatewayread 2026-10-03 |
||
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
FLOWX.AIAPIs, SDKs & MCP Extensibility FlowX publishes SDKs for React, React Native, Angular, iOS and Android for embedding FlowX processes in client applications, API reference pages for platform resources such as storage buckets and objects, and an MCP API reference for managing MCP servers and tools, the last marked as internal paths under review. Sourcedocs.flowx.ai 5.9 SDKs overview and API referenceread 2026-09-30 |
||
|
WonderfulAPIs, SDKs & MCP Extensibility The whole platform is exposed through an API with hundreds of endpoints, published as a Swagger file, and it can run headless, so customers can build their own interfaces or use it purely as an orchestration layer. Every agent, skill, tool, governance setting and app can be exported through that API, and a CLI is part of the AI OS. The API reference sits behind a customer login at app.wonderful.ai/docs. Sourcewonderful.ai/blog-articles/open-by-default-competitive-by-designread 2026-10-03 |
||
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
FLOWX.AITesting, Debugging & Optimization Evaluations lets customers test their own agents from end to end. A dataset attaches to a specific AI node in a specific workflow and holds test cases of input plus expected output plus optional retrieved context, added by hand or captured from a real node execution in a production run and marked with its source and a back reference. A catalog of ten built in evaluators covers general quality (correctness, conciseness, hallucination, answer relevance), RAG quality (groundedness, helpfulness, retrieval relevance) and deterministic scorers (exact match, Levenshtein, JSON match against a declared output shape contract), with custom evaluators writable against a supplied scoring prompt and a numeric or binary pass threshold. An experiment runs the workflow against every test case and scores each test case and evaluator pair through the async evals-judge service, producing aggregate scores per evaluator plus per test case rows showing input, actual output and expected output side by side, the judge's own reasoning, and pass or fail against each threshold. Every experiment freezes the node configuration at launch, so a baseline run and a run after a change are compared per evaluator and a drop on any evaluator shows a regression between agent versions, and FlowX advises growing the regression set from flagged production executions. Datasets, test cases and experiments are also exposed as REST endpoints for use from the customer's own tooling, and the judge model is resolved per organization through an EVAL capability an admin can rebind. Custom evaluators, multi dataset experiments and AI improvement suggestions carry later release badges. Sourcedocs.flowx.ai 5.9 Evaluations, vendor submitted correction verifiedread 2026-09-09 |
||
|
WonderfulTesting, Debugging & Optimization Changes are tested before they ship, with generative evaluations that simulate real interactions and score whether the agent met the intent behind each request, catching regressions and edge cases. In production, automated checks surface drift and failures, and A/B tests split traffic between two agent versions so the better one can be promoted and the other rolled back. Sourcewonderful.ai/blog-articles/fast-iteration-as-a-strategyread 2026-10-03 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
FLOWX.AIBrowser & Computer Use The Browser Automation node is available from FlowX.AI 5.13.0 on SaaS deployments. It drives a real browser to complete tasks on web applications that have no API, including filling multi page forms, navigating portals and retrieving results, as the customer describes the task in natural language and an AI agent plans and executes the browser interactions inside the platform's execution, logging and document storage layers. Outcomes are checked against the target site's recorded state changes rather than the agent's own success claim, browser sessions persist across workflow steps, and every run is logged through the platform's execution and observability layers. FlowX directs builders to an API integration where one exists and to the read only Web Page Extractor node where only page content is needed. Underneath, a real Chromium session is driven through the open source browser-use library, with per step logging of action, reasoning and next goal and a screenshot per step, and FlowX has published a 405 run benchmark of nine models over nine browser tasks scored against the fixture site's recorded state. Self hosted deployments receive the node with the next LTS release family. No terminal, desktop or screen scraping automation is claimed. Sourcedocs.flowx.ai Browser Automation, vendor submitted correction verifiedread 2026-09-23 |
||
|
WonderfulBrowser & Computer Use Agents reach legacy systems with no API, logging into software such as Oracle, Epic or SAP, moving between screens, filling in fields and submitting forms the way staff do. Each one runs in a managed virtual machine with its own credentials and a controlled session, every action is logged, and a single view shows which sessions are active or waiting on human review. Sourcewonderful.ai/blog-articles/computer-useread 2026-10-03 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | F FLOWX.AI |
W Wonderful |
|---|---|---|
|
Entry price Lowest public entry point |
Contact sales. No pricing is public, and prices are set against the value stream the platform accelerates, sized in a customized demo. | Contact sales |
|
Pricing confidence How public the numbers are |
Contact only | Contact only |
|
Billing Primary billing axis |
An enterprise subscription, plus value streams and agents. | An annual subscription, a minimum commitment, credits consumed per interaction, or a mix, set in each order form. |
|
Variable cost Workload / overage exposure |
Medium variable cost | High variable cost |
|
Free tier / trial Try before you buy |
No free tier
|
No free tier
|
|
Buying motion Self-serve vs sales call |
Sales call | Sales call |
|
Pricing verified When this pricing was last checked |
Product updates
Newest first, each linked to its source.
FLOWX.AI
-
· Agent capability
FlowX.AI 6.0 upgrades the Developer Agentic Harness, the Designer's AI agent that plans app changes and builds them on its own branch.
Source -
· Deployment / data residency
FlowX.AI 5.9.6, a maintenance release on the 5.9 long term support line, ships the document parser with its layout, table and OCR models built into the image.
Source -
· Agent capability
FlowX.AI 5.13.0 adds an AI agent to its Designer that surveys an existing app, drafts a plan from a plain language request, then builds or edits processes, screens, workflows and data types.
Source
More comparisons with FLOWX.AI or Wonderful
Other matchups in enterprise operations agents
Not the pairing you were after? These compare a different set of enterprise operations agents on the same 14 capabilities.