ApplicationsModernize
Automate the systems that have no API
A lot of enterprise work still lives in applications nothing can connect to — old ERPs, claims systems, supplier portals, government sites. Cenna agents use them the way a person does: through the screen. They run in browser sessions in your cloud, follow your rules, and record every step.
01The problem
Why nothing else could automate them
Every workflow builder and agent platform starts the same way: pick a connector. These systems don't have one — and never will.
No API to call
The system predates APIs, or the vendor never shipped one. There is nothing for an integration platform to connect to.
No connector, no MCP server
Nobody is building connectors for a 2004 claims system or your supplier's homegrown portal. The catalog approach ends here.
Too costly to replace
The system works, the data is in it, and a migration is a multi-year project. So people keep retyping between screens.
So people are the integration
Today the "integration" is a person copying values from one window into another, all day. That is the job the agent takes.
The agent needs none of it. If a person can use the screen, the agent can.
02How it works
How it works
The agent works the interface the way your team does — it just never gets tired, never mistypes, and records everything.
- 01
Show it the task once
Describe the job in plain language — "enter approved invoices from the queue into the supplier portal" — and walk it through once.
- 02
It signs in as itself
The agent gets its own scoped credential, granted and revocable by you. It never borrows a person's login.
- 03
It works the screen
Reads the page, fills the fields, clicks the buttons — checking each step landed before taking the next.
- 04
Every run is recorded
Each step is captured with a screenshot, so any run can be reviewed end to end. When the agent is unsure, it stops and asks.
One agent, real enterprise screens
Signs in — the fields it's acting on marked live
Reads the admin console and finds its way
Fills the form and completes the task
03Scale
Scales in your cloud. No machines.
Old-style automation meant a room of bot machines or a VDI farm — licensed per bot, patched by IT, idle most of the day. Cenna runs browser sessions in your own cloud: they start when there is work, run in parallel when there is a lot of it, and scale to zero when there is none.
No bot machines · No VDI farm · Parallel when busy, zero when idle
04Where it's used
Where enterprises use it
The systems everyone has agreed are impossible — until now.
- Order and invoice entry in an old ERP
- Claims lookups in a TPA or payer portal
- Supplier and vendor portals with no API
- Government and regulatory filings
- Bank and insurance back-office systems
- Provider credentialing portals
- Mainframe screens behind a web emulator
- Any internal tool the vendor stopped updating
05Control
Under control the whole time
Approval before it matters
Put a human sign-off in front of any step you choose — nothing submits to a government portal without a yes.
Its own scoped credential
The agent signs in as itself, with access you granted and can revoke in one click.
Recorded and priced
Every run is traced with screenshots and its cost, in your account — the same governance as every Cenna application.
06FAQ
Common questions
What happens when the screen changes?
The agent reads the screen the way a person does — it looks for "the Submit button," not pixel position 840,512. A moved button or a reworded label doesn't break it. If a page changes so much the task is genuinely unclear, it stops and asks instead of guessing.
How does it sign in? What about MFA?
With its own credential, scoped to what you granted, stored in your account. SSO and MFA flows are handled in the session, and you can revoke access at any time.
What if it makes a mistake?
Every step is checked before the next one, anything you flag needs approval before it submits, and each run is recorded with screenshots — so a mistake is visible, attributable, and stoppable, unlike a person's typo at 4:45pm on a Friday.
Is this allowed on third-party portals?
You use it with your own accounts under your own agreements, the same as an employee using the portal. You decide where it runs; approvals and scoped credentials keep it inside those lines.
How is this different from RPA?
RPA replays recorded clicks against fixed screen positions and breaks when anything moves — and it needs dedicated machines. Cenna agents understand the screen, adapt when it changes, and run in cloud sessions with no machines to maintain.
Bring us the system everyone says can't be automated.
Thirty minutes: pick your most stubborn no-API system, and we'll show an agent doing the work in it — signed in, step by step, recorded.
Get a DemoBuilt for speed. Engineered for control.