What if selectors just worked?
You know the drill. Chrome updates, your idx_aaname breaks. Someone touches the DOM, your anchor element vanishes. We got tired of it too.
Updated
TL;DR
- Mediar uses AI to find UI elements instead of brittle selectors
- No Orchestrator to maintain - runs locally or in our cloud
- Document extraction works without training ML models
- Pay per execution instead of per-bot licensing
The stuff that eats your week
Selector whack-a-mole
Fix the aaname on the SAP login. Now the Salesforce button broke. Classic.
Exception handling that's 80% of your code
Try-catch, retry scope, log message, send email. For every. Single. Activity.
Document Understanding "training"
Label 200 invoices. Retrain. Confidence too low. Label more. Ship it and hope.
Orchestrator maintenance windows
Saturday 2am. The upgrade failed. Monday is going to be fun.
Teaching junior devs why strict selectors matter
Then watching them use idx anyway because it's faster to build.
The ceremony around simple automations
Git branch, PR review, DEV/TEST/PROD, change request ticket. For moving data between two spreadsheets.
Same task, different approach
| UiPath | Mediar | |
|---|---|---|
| Building a workflow | Drag activities, configure each | Record it once, done |
| When Chrome updates | Rebuild the selector | Figures it out |
| When it fails at 3am | Check logs, reproduce, fix | Auto-retries with context |
| Reading invoices | Train DU model first | Just reads them |
| Running bots | Orchestrator + Robot license | Click run |
| Monthly cost for 3 bots | ~$1,260 | Usage-based |
SAP invoice reconciliation. No selectors.
11 invoices in under a minute. The part you'd normally spend on selector debugging? Gone.
Want to see it on your workflows?
15 minutes. Bring a workflow you're tired of maintaining. We'll show you how it runs without the selector headaches.