AI browser automation

Some systems have no API. AI browser automation signs in anyway.

A supplier portal, or the carrier back end that nobody has got round to replacing. There is no integration to buy, so a person opens a browser and types the fields in again. Often they are copying them straight from a document that somebody has only just scanned.

  • Runs on accounts you hold
  • Every run leaves a log

What AI browser automation is

AI browser automation is software that drives a real browser the way one of your team would. It signs in to the account you already hold, works through the pages and fills the fields. What comes back is structured data your own systems read. The difference from a recorded macro is that this one copes when the page moves underneath it.

The work that never got a system

Every business keeps a few jobs that live inside somebody else's website and nowhere of its own. The vendor never shipped an API, or the plan that includes one costs more than the work is worth. So the job stays manual, and every new client adds another hour of it each week.

  • 01

    There is no API to call

    The system was built for people to click through, never for other software to call into. The only way in is the one your team already uses, which is a keyboard.

  • 02

    The subscription nearly fits

    A no code tool handles the simple pages and then stops at the login, or the file upload. You pay every month for the half that works.

  • 03

    It breaks on a Tuesday

    A recorded macro holds up until the vendor moves a button, and then it silently stops. Nobody notices for a week. Nothing announced itself as broken.

What the build actually does

  • 01

    Sessions that survive the login

    The first sign in is easy. The work is staying signed in through an expiry, or a code sent to a phone, without somebody watching. That is the part most tools hand back to you.

  • 02

    Forms filled from your own file

    A spreadsheet or a CSV goes in, and the rows come out the other side as submitted records. Nobody retypes a column that already exists somewhere.

  • 03

    An endpoint your software calls

    The automation sits behind an API of your own. Your application asks for a lookup and gets JSON back, so the browser underneath is somebody else's problem.

  • 04

    Volume handled in parallel

    Several browsers run at once against the same portal, at a rate that respects it. A backlog of four thousand rows stops being a fortnight of somebody's life, and becomes an overnight run.

  • 05

    Failures that reach a person

    A run that breaks retries, and a run that keeps breaking raises an alert with the page it died on. Silence is the one outcome nobody is allowed to have.

  • 06

    Systems you hold the account for

    We automate the systems you own, or the ones a contract entitles you to use. Where a portal's terms restrict automated access, that surfaces during scoping rather than after the build. Nothing in the build defeats a CAPTCHA, and nothing hides whose account is signed in.

How the first three weeks run

  1. Week 1

    01We sit with the person who does it now

    Two days watching the job happen on the real portal, at the speed it really goes. The exceptions they work around without thinking about them are the ones that decide the design.

  2. End of week 2

    02You get a costed plan

    The plan names the one workflow to automate first and the hours it gives back. It also names what stays manual. You decide whether it goes ahead.

  3. From week 3

    03One workflow goes live

    The first automation runs against your account, logged, with a person confirming anything it submits. The rest follow once a fortnight of real runs has held up, and not before.

A subscription against a build

Both drive a browser. What separates them is what happens the day the portal changes, and who owns the thing afterwards.

MeasureA subscription toolA build you own
Pages behind a loginUsually where the trial endsSessions held, expiry handled
When the page movesThe recording stops workingSelectors repaired as maintenance
Reaching your own systemsExport a file and import itAn endpoint your application calls
Cost as volume growsPer run, per seat, every monthBuilt once, then hosting
Who holds the credentialsA vendor you have not metYour own secrets manager

Three portals worth the build

Each of these arrives the same way. High volume, no API, and a person who has learned every quirk of a website they did not choose.

A carrier portal

Quotes pulled while the caller waits

An agent opens the same insurer site forty times a day for the same eight fields. The build signs in, runs the quote and hands the numbers back to the CRM. The agent reads them without leaving the record.

A filing deadline

Returns submitted from your own ledger

A quarterly filing takes a week of copying figures by hand into a government form. The build takes the ledger export and works through the submission, stopping before it files. A named person presses the last button.

After the OCR runs

Extracted fields typed into the system that needs them

The reading of an invoice is solved already, over on our document processing and OCR page. This page is about getting those fields into a supplier portal that has no import route. The two halves ship as a single pipeline.

Where the credentials live

This work needs a login to a system that matters, which makes storage the first question rather than a late one.

Your secrets manager, not our code
Credentials get read at run time, and nothing is ever written into a repository of ours.
Or inside your own network
The browsers run inside your own network, which is what some portals expect to see.
Every session recorded
What was opened, what was submitted, and when. An audit asks eventually.

What the automation is built from

We fit the automation around whichever portal you are stuck with, however old it is. Nothing on this list is a requirement, and the work goes ahead against whatever the vendor built.

What drives the browser
PlaywrightThe browser, driven properly
PuppeteerWhere a project already runs it
Managed browser infrastructureBrowsers at volume without a server farm
What decides the steps
ClaudeReading a page it has not seen
GPTTurning a screen into fields
PythonThe rules that must not guess
Where the output goes
PostgreSQLRuns, results and evidence
REST APIsThe endpoint your software calls
SentryThe alert when a run dies
What people say

Not our words.
Theirs.

Every quote here is a real Trustpilot review. We did choose which ones to show you. The score beside them is the part we do not control, and it counts all 29 reviews.

Trustpilot4.4out of 5Excellent29 reviews · checked 19 August 2026Read all of them

These reviews are for Appkodes, our software product division.

YouTube

A Joysale client on the product and the service

He runs a marketplace built on Joysale, our Letgo style product. The clip is his own account of working with us.

YouTube

A Fantacy client on the build

Fantacy is our Amazon style retail product. He goes through what was built and how the work ran.

YouTube

An Airfinch client, filmed after his written review

Airfinch is our Airbnb style rentals product. He had already left the same review on GoodFirms before recording this.

YouTube

A second Joysale client on the same product

Another marketplace running on Joysale. Worth watching beside the first, since the two bought the same thing.

Trustpilot
I've worked with Appkodes for 7 years on 4 different projects. We constantly require support or the implementation of new features, and we have the guarantee that the quality of their work remains the same throughout this time.
Juan VásquezCLJuan VásquezSep 2025
Trustpilot
Appkodes exceeded all of our expectations! From the very first contact, the team demonstrated a high level of professionalism, technical expertise, and commitment to quality.
Global SoftwinBRGlobal SoftwinMay 2025
Trustpilot
Appkodes team helped me to launch my healthcare application very quickly. Their software was very close to my requirements and adding some extra features made my project easy.
WassimFRWassimApr 2025
Trustpilot
I so much love your services and I will continue to patronize your company.
Kolawole Alaba JohnsonNGKolawole Alaba JohnsonApr 2025
Trustpilot
I worked with AppKodes for a website and mobile app development project, and overall, I'm very satisfied with the results. Their team was responsive and flexible throughout the process, and they delivered a product that met my expectations both in design and functionality.
Яша ФирузAUЯша ФирузApr 2025
Trustpilot
It was a good experience working with the team. They understood my ideas clearly and built everything as expected. The team was supportive, quick to respond, and helped me whenever I needed changes. Thank you for your hard work and support!
Prem SharmaCAPrem SharmaApr 2025
Trustpilot
I have got a mobile app project going on successfully with the team. Their Support is good. turn around time for any requirement is great. Every detail of my app is meticulously designed. THANK YOU APPKODES.
FFINFast Fiber NetworksApr 2025
Trustpilot
Appkodes is a leader in developing high-quality applications and websites. It was a pleasure working with them, and this certainly won’t be our last collaboration. My experience was exceptional, they developed an outstanding app and website, with smooth and refined interactions.
BSABaderApr 2025
Trustpilot
Overall very good experience. I have been availing services for past 3 years. They are available for discussions and resolving issues whenever we faced any. Mr. Saravana has been looking after our project and I'm very much happy with his timely response. I would definetely recommend.
Vannala RajuINVannala RajuApr 2025
Trustpilot
Initially, I was hesitant to deal with them, believing their customer service would be poor. However, I was surprised. They act with great responsibility and professional efficiency. My regards to them.
Ahmed NhariMAAhmed NhariApr 2024
Trustpilot
You have been supporting me very quickly in every matter, especially in the last 2 months, and this makes me very happy.
Deniz SeçerTRDeniz SeçerJan 2024
Trustpilot
Very professional. Our project was quite complex and they covered all the aspects. Appkodes did an amazing and professional job developing and creating our Apple and Android apps. I was positively impressed with the communication you can absolutely trust on what they say.
Anu JosephOMAnu JosephJul 2023
Trustpilot
Mani and Saravanan of the Appkodes team are amazing, they have done the best to create and support my project! I give them 10/10 stars for their efforts and work!
Joely CineasUSJoely CineasJul 2023
Trustpilot
It was really great, they are there for me whenever I had a problem or to fix something. Thank you so much Ameer
GomezCAGomezApr 2023
Trustpilot
I've been working with Appkodes for almost a year and i can recommend them to work with as they are so much friendly and professional and you can clearly see it once you start your project right away. They are intact and they are transparent with their communication.
JohnUSJohnFeb 2023
Trustpilot
I have to be honest, sometimes it's hard to find a company or someone abroad to do your project. Not only might you waste your time and money, there is this thing called trust. In business you must trust the person you are dealing with.
Zack GizawUSZack GizawDec 2022
16 of 29 reviews, plus 4 videos

Businesses we have built for

Bring the NoiseByChatChosenHandy FeetStuffillVRA Health

Frequently asked questions

Is this the same as RPA?

The job is the same and the shape is different. Classic RPA sells you a licence for each robot and a studio to draw the steps in. This is a build you own outright, running on your own hosting, with no seat count to renew.

What happens when the portal changes its pages?

A change breaks the step that touched it, the run stops and an alert names the page. Repair is maintenance work, usually hours rather than days. Recorded macros fail quietly for one reason. Somebody assumed the portal would hold still.

Can you automate a site that discourages bots?

We automate systems you own or are contractually entitled to use, on your own account. Where the terms restrict automated access, that comes up in scoping and it is your call to make with the vendor. We do not defeat CAPTCHAs, and we do not disguise whose account is signed in.

Where do our passwords and MFA codes live?

In your secrets manager, read at run time. They are never committed to a repository and never pasted into a third party builder. For MFA the usual route is a shared corporate method that your own team controls.

Would Zapier or a browser add-on do the job?

They do more than people expect, and they hold up right until a login appears. Those tools earn their money on the simple half. A build is worth it when the volume is high, the page is awkward, or the output has to land in a system of yours.

Browser automation

Bring us the portal
everyone avoids

A free automation audit. We watch the job once, say what a build costs and tell you plainly when a subscription would do instead.

Eighteen years of excellence