Spelling check

“mejar ai”: you are almost certainly looking for Mediar AI

Mediar (pronounced “mee-dee-ar”) gets typed a lot of ways: mejar, mejar ai, medair, mediar ai. Same product. This page sorts out the spelling, separates it from the other similar-sounding AI companies, and explains the one thing Mediar does that the look-alikes do not.

Matthew Diakonov, Written with AI

Published June 15, 20266 min read

Direct answer (verified 2026-06-15)

“Mejar ai” is a misspelling of Mediar AI. Mediar is a Windows desktop automation tool that replaces enterprise RPA (UiPath, Power Automate, Automation Anywhere). It learns a repetitive workflow by watching you do it once, then runs it on its own through the operating system’s accessibility APIs, the same interfaces a screen reader uses. That is why it works on legacy apps that have no API: SAP GUI, Oracle EBS, mainframe terminals, and banking core systems. The product lives at mediar.ai.

Sorting out the look-alike names

Search engines scatter this query across a few unrelated companies because the names rhyme. Here is who is who, so you land on the right one.

What you typed / saw	Who it is	Likely your match?
mejar ai / mediar ai	Mediar, Windows desktop automation that replaces RPA	Yes, if you want desktop automation
mojar ai	A separate enterprise AI-agent platform (different company)	Only if you wanted that specific vendor
memar	A separate 3D-focused AI product (different company)	No, unrelated to automation

The rest of this page is about Mediar. If you wanted one of the others, you are in the wrong place, and that is fine.

The one thing Mediar does that the look-alikes do not

Most automation tools, old RPA and new browser agents alike, look at a screen the way a camera does: pixels and coordinates, or fragile selectors that assume the layout never moves. Mediar reads the screen the way a screen reader does. Windows exposes a structured accessibility tree of every control, with a role and a label, and Mediar acts on that tree directly.

Here is what that tree looks like for an SAP invoice header. Mediar targets the element labeled Vendor, not a pixel position. That is the whole reason it self-heals: when a vendor reorders fields or applies a new theme, the pixels move but the label does not.

accessibility-tree.txt

You do not write any of that by hand. You record the workflow once, Mediar resolves each step to a label, and then it replays it across as many documents as you have.

record once, run many

You can read the engine yourself

The part that drives Windows through the accessibility tree is open source. It is called Terminator, it is written mostly in Rust, it is MIT-licensed, and its own tagline is “playwright for windows computer use.” If you want to verify how the label-targeting actually works, or extend it, that repository is the place to start. A typo-spelling page from a content farm cannot show you that, because they do not have the source.

70% lower cost vs UiPath

“An LG-customer F&B chain moved off UiPath to Mediar; their CFO told the board they are now saving on costs at this level.”

Mediar deployment, reported on mediar.ai

Why a misspelling is worth a whole page

Mediar is a young name, and it does not map cleanly to English spelling, so people who heard it on a call or saw it for a second type it however it sounded. The intent behind “mejar ai” is almost always the same: someone is evaluating a way to automate repetitive work on Windows desktop apps, usually because an existing RPA project stalled or because a six-figure implementation quote landed on their desk.

If that is you, the honest summary is short. Mediar is good at exactly one hard thing: driving legacy desktop software that has no API, reliably, without a team of certified developers maintaining brittle scripts. Browser-based AI agents are great for new SaaS, but if your data lives in SAP GUI or a green-screen terminal, they will not help you. That gap is the entire reason the accessibility-API approach exists.

Pick one stuck workflow, see it run in a week

Book a working session with the founders. Bring a legacy desktop process and we will scope a pilot on it.

Questions people actually ask

Frequently asked questions

Is "mejar ai" the same as Mediar AI?

In almost every case, yes. "Mejar ai" is a phonetic misspelling of Mediar (pronounced "mee-dee-ar"). If you searched for desktop automation, an RPA replacement, or a tool that does data entry into SAP, Oracle, or banking systems, the product you are looking for is Mediar at mediar.ai.

Are there other AI companies with names that sound like this?

Yes, and that is part of the confusion. There is a separate enterprise AI-agent platform spelled Mojar AI, and a separate 3D-focused product spelled Memar. Those are different companies. If you came here for Windows desktop automation that replaces UiPath or Power Automate, that is Mediar.

What does Mediar actually do?

It learns a repetitive desktop workflow by watching you do it once, then runs that workflow on its own through the operating system's accessibility APIs. Because it reads the same interface a screen reader reads, it works on legacy Windows apps that have no API at all: SAP GUI, Oracle EBS, mainframe terminals, Jack Henry, Fiserv, FIS, Epic, and Cerner.

How is that different from UiPath or Power Automate?

Traditional RPA tools lean on brittle selectors or pixel matching that break when a screen moves or a label changes. Mediar targets elements by their accessibility label, so it self-heals when the interface shifts. Mediar customers report saving roughly 70% versus UiPath, and Mediar reaches production in about a week instead of months.

Can I see how it works under the hood?

Yes. The automation engine is open source as Terminator at github.com/mediar-ai/terminator. It is written mostly in Rust, MIT-licensed, and described as "playwright for windows computer use." Teams that want to extend Mediar or build custom workflows start there.

What does Mediar cost?

Pricing is $0.75 per minute of runtime, with no per-seat licensing. There is a $10,000 turn-key program fee that converts into usage credits, so it functions as prepaid runtime rather than a sunk setup cost.

How do I try it?

You can record a workflow in the no-code web app at app.mediar.ai/web, or book a working session with the founders to scope a pilot on one of your own legacy workflows.