Everything you need to know about the VeroTX execution layer, the WorkStream Playbook Engine, and how enterprises run agentic AI WorkStreams across Finance, Operations, People Ops, IT, Sales, and Support.
Type a keyword to filter questions and answers across all topics.
Short, direct answers to the questions we hear most. Each one links to the page it comes from.
VeroTX is the System of Action for enterprise work: a platform that runs structured, end-to-end WorkStreams across your existing systems.
It coordinates AI agents, human approvals, and system calls inside one governed runtime. Every action is recorded in the Execution Ledger.
PlatformA WorkStream is a named, versioned enterprise process that VeroTX runs end to end, such as vendor onboarding, invoice exceptions, employee onboarding, or access provisioning.
Teams compose WorkStreams in the studios. VeroTX runs them, escalates to humans when needed, and produces the artifacts the business needs.
WorkStream PlaybooksA Playbook is the definition of a WorkStream: the steps, policies, approvals, and system calls that the WorkStream Playbook Engine executes.
The engine sequences agent actions, human approvals, and system calls, enforces governance rules, and handles exceptions. The same runtime executes Procurement, Finance, People Ops, and Engineering Ops Playbooks.
WorkStream PlaybooksVeroCortex is the reasoning engine behind VeroTX. It reads the user's intent, works out the next action, picks the agent that owns that action, and holds the action to the rules configured at design time.
It does not choose models on cost or latency at runtime. Each agent is configured in Agent Studio with its own model, parameters, guardrails, and dos and don'ts, then tested and released.
VeroCortexIn Agent Studio the developer describes the business outcome the agent must deliver, and the evaluation engine scores the agent against that description in three layers.
An agent cannot be deployed until it passes the evaluation criteria, which is how VeroTX keeps agent behavior predictable in production.
VeroCortexVeroli is the conversational face of VeroTX, where people ask for an outcome in plain language and follow the work as it runs.
Business users start WorkStreams, check status, and review what an agent did without opening a console.
VeroliAn App is a packaged set of WorkStreams for a business function, such as Procurement or People Ops.
Apps ship on the same platform, engine, and governance. Teams extend them or compose new ones in the studios.
PlatformAn Agent Action is a unit of agent work that produces a business outcome inside a WorkStream, such as a budget analysis, a contract review, a three-way match, or an inventory reconciliation.
Agent Action Credits meter that work, and the credits consumed reflect the volume and complexity involved. Usage is captured at that level of detail and published on your AAC usage page.
PlansYes. Flows run on a schedule and WorkStreams respond to inbound events, so agents keep working while nobody is at a screen.
A scheduled Flow can check commodity prices and signal a buy, or place the order when pre-authorized. A WorkStream awaiting RFQ replies reads each quote as it arrives and prepares the comparison.
Long-running processesWorkflow and RPA tools move data between steps, while VeroTX runs the work itself, including the decisions, exceptions, and approvals in between.
Rule-based bots break when a case falls outside the script. The full comparison is on the AI agents versus workflow automation explainer.
AI agents vs workflow automationNo. VeroTX runs on top of the systems you already have and writes back to them.
Connectors read context from and write results to ERP, CRM, ITSM, HRIS, and category applications. Your systems of record stay the systems of record.
PlatformThe first WorkStream goes live in production in 4 to 8 weeks.
The deployment path starts with one WorkStream covering intake, approval, execution, and exception handling, then expands to adjacent processes on the same platform.
Deployment pathVeroTX has 259 pre-built connectors across 23 categories, plus REST APIs, webhooks, MCP, and event streams.
Core systems include SAP S/4HANA, SAP Ariba, Oracle Fusion Cloud ERP, NetSuite, Microsoft Dynamics 365, Salesforce, Workday, ServiceNow, DocuSign, Arena PLM, SharePoint, and Box. Any system with a REST API can be added in the connectors studio.
Which systems does VeroTX connect to?VeroTX is built for enterprise business teams that own a process, with IT keeping governance and security control.
Finance, procurement, People Ops, and engineering operations teams compose and change WorkStreams in the studios without writing code.
PlatformA prototype agent is quick to build; the connectors, scoped credentials, approval interfaces, audit record, long-running state, and versioned rules around it are not.
Most enterprises buy the execution layer, which is common to every process, and build only what is genuinely proprietary, which a WorkStream stage can call.
Build vs buyChoose VeroTX when you need to run a governed business outcome, not only move data between applications.
WorkStreams can wait for days or weeks, assign agent work, stop at human approval tollgates, preserve the Playbook version used by each run, and record every action in one Execution Ledger. VeroTX can also run above an existing Workato investment.
System of Action vs iPaaSAn integration platform moves data between applications; VeroTX owns the business outcome that crosses them, including the waiting, the judgment, and the approvals.
Its unit of work is a recipe that runs and finishes. A WorkStream has stages, tollgates, versioned rules, and an Execution Ledger, and it survives a wait of weeks.
System of Action vs iPaaSRobotic process automation drives an application's screens, which breaks when a layout changes. VeroTX reaches systems through APIs, file exchanges, and data syncs.
The larger difference is governance: agent judgment runs inside deterministic rails, policy is applied at a tollgate before anything commits, and the runtime writes the record.
System of Action vs iPaaSYes. VeroTX sits above your systems of record and above the pipes and bots that connect them, and a WorkStream stage can call either one.
Those tools keep the jobs they are good at. What changes is that the end-to-end outcome gets one Playbook, one set of tollgates, and one ledger.
System of Action vs iPaaSOnly where you allow it. Every WorkStream defines which steps an agent may complete on its own and which require a human approval.
Role-based controls, approval rules, and escalations are part of every WorkStream. Configuration changes also require human approval before they ship, so nothing changes in production silently.
PlatformThe action is traceable and reversible through the Execution Ledger, which records every step with who acted, under which policy, and when.
Exceptions escalate to a person instead of proceeding silently, and overrides are captured with role and policy context. Teams can review the run and change the Playbook before the next execution.
Execution LedgerYour data lives wherever your residency policy requires, because VeroTX is Kubernetes-native and cloud-agnostic.
The platform runs on AWS, Google Cloud, Microsoft Azure, and Oracle Cloud, plus private cloud, on-premise, and hybrid. With Bring Your Own Cloud, data, encryption keys, and network controls stay inside your own account.
PlatformThe Execution Ledger is the audit trail of every WorkStream action, held in one queryable surface.
It records what ran, who approved it, which policy applied, and which artifacts were produced, for auditors, finance, and security.
Execution LedgerVeroTX is SOC 2 Ready and aligns with ISO 27001 and GDPR practices, with a Type I audit underway.
The platform includes end-to-end encryption, role-based access control, immutable audit trails through the Execution Ledger, and data residency controls.
FAQEvery customer runs on a fully single-tenant stack, on VeroTX-managed infrastructure or inside your own cloud account.
Nothing is shared with another customer at the application or data layer. Self-hosting keeps data residency and network policy under your control.
Where data is storedVeroTX ships Apps for Procurement, Finance Ops, People Ops, and Engineering Ops today.
Each App is a set of WorkStreams on the same platform, engine, and governance. Other structured processes are composed in the studios.
PlatformVeroTX serves Financial Services, Healthcare, High-Tech, Manufacturing, Food and Beverage, Professional Services, and Retail.
The platform adapts to sector requirements while supporting regulations such as SOX, HIPAA, and GDPR.
SolutionsNo. The studios are no-code surfaces where business teams create and change WorkStreams, forms, connectors, and agents.
IT keeps governance and security policy. Changes still pass human approval before they reach production.
PlatformStart by scoping one WorkStream with the VeroTX team, then run it in production before expanding.
Pricing runs on two meters, WorkStream Playbooks and Agent Action Credits, so scope and usage stay visible from the first deployment.
PlansVeroTX is a System of Action built for governed, multi-day enterprise WorkStreams, which makes it the alternative to evaluate when the work goes beyond moving data between applications.
It pairs 259 pre-built connectors with Playbook stages, human approval tollgates, agents released only after evaluation, and one Execution Ledger for every run.
System of Action vs iPaaSKeep Workato for the reliable data integrations it already runs, and add VeroTX when a business outcome needs owners, approvals, waiting, and an audit record.
A WorkStream stage can call an existing recipe, so the pipe keeps its job while the end-to-end process gets one Playbook and one ledger.
System of Action vs iPaaSVeroTX ships 259 pre-built connectors across 23 categories covering 1,086 governed actions, and does not need an integration platform to reach systems of record.
Coverage spans ERP, HRIS, CRM, procurement, contract, treasury and service systems, and each call runs under scoped credentials.
System of Action vs iPaaSA VeroTX WorkStream is designed to wait days or weeks for a supplier reply or an approval, then resume where it stopped.
In-flight state lives in Tables and the run finishes on the Playbook version it started on, instead of being split into separate recipes with state parked in between.
System of Action vs iPaaSVeroCortex reads intent, determines the next action, selects the agent that owns it, and holds that action to the rules configured at design time.
Each agent is configured with its model, parameters and guardrails, and is tested in three evaluation layers before release.
System of Action vs iPaaSIn VeroTX, policy is enforced by the Playbook rather than left to a model, and every action runs under scoped credentials on a fully single-tenant stack.
Agent judgment runs inside deterministic rails, and an action commits only after the rules and tollgates in the Playbook are satisfied.
System of Action vs iPaaSHuman approval tollgates are part of the VeroTX process definition, so a spend above the configured threshold stops until the named approver clears it.
The approver sees the evidence gathered by the run, and the decision is recorded in the Execution Ledger.
System of Action vs iPaaSThe VeroTX Execution Ledger is written by the runtime as work happens and binds each action to the Playbook version in force at the time.
It records agent actions, system calls, approvals and waits for the whole business outcome, not only individual job runs.
System of Action vs iPaaSVeroTX reaches older systems through their APIs, file exchanges and database syncs into Tables, rather than driving their screens with a bot.
Where an existing bot or integration already reaches a system, a WorkStream stage can call it.
System of Action vs iPaaSVeroTX ships pre-built Playbooks for procurement, finance operations, people operations and engineering operations, and the first WorkStream goes live in 4 to 8 weeks.
Teams adapt a Playbook through configuration instead of assembling the process from individual recipes.
System of Action vs iPaaSBusiness teams compose in the VeroTX studios for apps, flows, agents, tables, forms, connectors and analytics, and proprietary logic is called from a stage.
You can run on a single-tenant stack hosted by VeroTX or in your own AWS, Azure, Google Cloud or Oracle Cloud account.
System of Action vs iPaaSVeroTX meters Agent Action Credits against completed business outcomes, such as a budget analysis, a contract review or a three-way match.
Usage is broken down at that level on your AAC usage page, and human users are not priced per seat.
System of Action vs iPaaSOur team can help you scope your first WorkStream, plan the deployment path, and connect you with support that fits your rollout.
Request Demo