Mediar on GitHub

The repos that matter

The org has 32 repositories, but you only need a handful to understand what Mediar ships. Terminator is the one to clone first; everything else is a binding, an example set, or the macOS sibling.

The claim you can verify in the source

Every RPA vendor says their automations are resilient. With Terminator you do not have to take that on faith, because the mechanism is in the open MIT source. The README is explicit: it locates elements through the Windows Accessibility Tree, the same interface a screen reader uses, by matching on role, name, ControlType, and AutomationId. You can inspect those exact values yourself with Inspect.exe or Accessibility Insights for Windows.

That is the whole reason it survives a UI change. A pixel matcher or an XPath is pinned to where something sits on screen. An accessibility query is pinned to what the thing is.

# Brittle RPA: tied to where things are on screen
click(x=482, y=311)                 # breaks if the window moves
click(image="submit_button.png")    # breaks on a theme or DPI change
select(xpath="/div[3]/div[2]/button[1]")  # breaks on any re-layout

# Terminator: tied to what the element IS
# (verifiable in the MIT source at github.com/mediar-ai/terminator)
locator.role("Button").name("Submit").click()
# Resolved through the Windows Accessibility Tree:
#   role          = "Button"
#   name          = "Submit"
#   ControlType   = UIA_ButtonControlTypeId
#   AutomationId  = "btnSubmit"
# The button can move, restyle, or shift DPI. The semantics hold.

Open-source engine vs. the Mediar product

This is the part the org page never spells out. Terminator and the Mediar platform are not competitors and they are not the same thing. One is the engine you can fork; the other is the managed product an ops team buys. They share the element-location engine, and diverge on everything around it.

Read the table left to right: the open-source SDK gives engineers the raw capability for free; the platform wraps it for teams that do not want to build and maintain the surrounding plumbing.

How you actually pull it in

Terminator is not a single package. The Rust crate is the core, and there are bindings and entry points so you can use it from whatever you already work in.

Cloning the repo vs. booking a pilot

If you are an engineer who wants to script a few desktop tasks, the MIT repo is genuinely all you need. Star it, read the README, ship something.

The product exists for a different reader: an ops, finance, or RPA center-of-excellence lead running 100+ repetitive workflows a week across legacy systems like SAP GUI, Oracle EBS, Jack Henry, Fiserv, FIS, Epic, or Cerner, who needs recording-by-watching, self-healing, validation, audit logs, and compliance without standing up and maintaining the engine themselves. That is where the $0.75-per-minute managed platform earns its keep, and where the open-source repo stops being the answer.

Frequently asked questions