Mediar solutions, in plain language: five workflow categories, the legacy systems each one runs on, and the savings each one shipped.

Both, in a defined order. The first engagement is a $10,000 turn-key program that delivers your first one or two workflows running in production, typically inside three to four weeks. That fee converts to runtime credits with a bonus, so it is effectively prepaid usage. After the program, you are on $0.75 per minute of executor runtime with no per-seat licensing. The product itself is a Windows desktop application plus a no-code web app at app.mediar.ai/web for recording workflows, backed by the open-source Terminator SDK on github.com/mediar-ai/terminator for teams that want to extend it.

Whichever line owns the workflows your UiPath rollout is stuck on. The most common rip-and-replace patterns we see: SAP B1 order-to-cash at distributors and F&B chains, Oracle EBS procurement at manufacturers, banking core sync at community banks on Jack Henry or Fiserv, claims intake at mid-market insurance carriers, and patient intake at regional health systems. The technical decision underneath all five is the same: stop treating the UI as pixels and start treating it as the accessibility tree.

Because each of those legacy systems exposes a Windows accessibility tree (the same surface a screen reader uses) and the executor talks to that tree, not to image pixels. Selector-based RPA tools have to write a fresh selector for every UI version of every screen of every system. The accessibility-tree approach reads role, name, and bounds, which stay stable across most patches. The result is one engine, six legacy ecosystems, fewer moving parts to maintain.

Power Automate Desktop is excellent on Microsoft 365 surfaces and on simple Windows Forms apps. It tends to stall on the systems above for two reasons: SAP GUI and Oracle Forms render through Windows but use heavy custom controls that Power Automate's recorder reads inconsistently, and EHRs like Epic Hyperspace run inside Citrix sessions where the recorder loses fidelity. Mediar reads the underlying accessibility tree directly, which is why the same five solution lines hold up at production volume.

Three places, in priority order. First, if a stable API exists, an API-first integration is cheaper and more reliable than any desktop automation, including this one. Second, browser-only flows on modern SaaS (no thick client involved) are better served by browser automation tools. Third, free-form planning workflows (multi-day case investigation, fraud triage, novel exception handling) need an agentic system with the model at runtime, which is not the architecture this executor is built around.

A workflow that runs ten minutes a day for 250 working days uses 2,500 minutes of runtime, which is $1,875 a year on the $0.75 per minute meter. The same workflow on a UiPath attended Robot at the public list price of around $420 a month is about $5,040 a year before Studio seats and Orchestrator licensing. The cost gap widens on long-tail low-volume workflows because UiPath bills for the seat regardless of usage and Mediar bills for runtime.

The Mediar platform is SOC 2 Type II certified and HIPAA compliant, and it deploys on-prem or cloud depending on the buyer's security posture. The executor runs inside your existing Citrix or VDI session and writes audit rows for every step. Compliance is one of the reasons the model lives at authoring time and not at runtime: an auditor can read the deterministic workflow file in git rather than guessing what an LLM decided on a given run.