| Ramain | Legacy RPA | |
|---|---|---|
| How a process is set up | Show it once while a digital worker watches | Map the process, then developers script each step |
| When a screen changes | Small changes handled on their own; bigger ones get a proposed fix for approval | The script breaks until someone rewrites it |
| Exceptions | Sent to a person with the run attached | Usually a failed job and a ticket |
| Systems it works in | Any screen your team uses, no APIs needed | Screens and APIs, through connectors and selectors |
| Pricing | $1,500/month with 150,000 credits; then $0.01 per additional credit | Bot licences, platform fees and build services |
Scripts and workers
Legacy RPA records a fixed path through an application: click this field, type that value, press this button. It is fast when nothing changes and brittle when anything does. A Ramain digital worker reads the screen the way a trained person would, so it knows what a field is for, not only where it sat last week.
That changes how work gets set up. There is no process-mapping workshop and no build sprint. Your team shares how the task is done today, a digital worker does it once while you watch, and that run becomes the workflow.
Where RPA costs pile up
Most RPA spend comes after go-live. Vendor portals ship new layouts, logins add one-time codes, a column moves. Each change stops a bot until a developer fixes the script, and a large estate keeps a team busy doing exactly that.
- 01Small layout changes are handled on their own, in the run.
- 02Bigger changes are recovered, and a proposed fix waits for your team's approval.
- 03Cases outside the rules stop and go to a person, with the run attached.
Paying for work, not bots
RPA is usually sold by the bot, on top of a platform and a services contract to build it. Ramain Platform costs $1,500 per month with 150,000 shared credits, 50 active workflows and five concurrent runs. Additional usage is $0.01 per credit, with no seat fees. Enterprise adds custom capacity and managed workflow services.
When RPA still fits
A high-volume, unchanging task on a single internal system is a good RPA job, and a working bot is worth keeping. Ramain earns its place where the screens change, the inputs vary and exceptions need judgement. Many teams run both and move the bots that break most often first.