Opportunities › Browser automation maintenance and healing › Proposed app
%22%2F%3E%3C%2Fsvg%3E)
Mendrun
Run browser scripts that repair themselves when websites change
- Score
- 34
- confidence 61
- Evidence
- 7
- items on the page
- Rivals
- 2
- named in sources
- First version
- 45 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2020
- Established market · AI estimate
ScreensConcept
Desktop app: Engineers monitor automation health, review code diffs, and manage deployment rules—dense technical work requiring extended focus and keyboard interaction. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Automations
2 need attention24 of 26
About this appAI proposal
Mendrun hosts your browser automation code and watches every run. When a site changes and a step fails, it uses the captured page state, steps and error to find the cause and write a fix as a code change you can review.
It is for engineers whose products depend on scraping, pulling reports or submitting forms on sites with no API. You keep ordinary scripts you can read, test and version, with the cost and predictability of code, not an agent improvising on every run.
Failures are hard to reproduce, so Mendrun keeps the evidence from each failed run: screenshot, DOM snapshot, network log and step trace. You choose whether fixes wait for approval or deploy once they pass your checks.
- Tagline
- Automations that mend themselves, in code you can read.
- Voice
- PlainCalmPrecise
- Why this name
- Mend plus run: it keeps scheduled runs going by repairing what breaks. Two plain syllables, easy to say.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Managed browser runtime
Upload Playwright-style scripts and run them on a schedule, by API or by webhook. No browsers or queues to maintain.
No member yet
Failure capture
Every failed run stores a DOM snapshot, screenshot, network log and step trace so you can see what the site looked like.
No member yet
Root-cause diagnosis
An AI agent compares the failed run with the last good one and says what changed: a moved selector, a new step or a renamed field.
No member yet
Proposed fixes as diffs
Fixes arrive as a readable code diff with the evidence behind it. Approve, edit or reject in one screen.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#0F4C4ADeep Teal · primary#F6F3ECPaper · surface#1B2422Ink · text#E8A33DAmber · accent#4C8C5AMoss · data: healthy#B5482FBrick · data: failed
Typography
Aa
Mendrun
PricingAI proposal
The material gives no competitor prices. These tiers are a starting point to test; the opportunity suggests pricing per run, runtime use or agent-assisted fix, or tiers by automation count.
Trial
Free
- 3 automations
- 500 runs a month
- Failure capture
- Manual fix suggestions
Team
$99 a month
- 25 automations
- 20,000 runs a month
- Verified fixes
- Auto-deploy rules
- Email and webhook alerts
Scale
$399 a month
- 150 automations
- 150,000 runs a month
- Longer evidence retention
- Priority runtime
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- No loop in the product. Mendrun reaches customers through developer content, example repair write-ups and direct sales. Runs happen behind the scenes and are not seen by third parties.
- Do they become customers?
- Test whether engineers who read a public repair write-up sign up and connect a real script. Teammates who see alerts are already users, so there is no outside viewer to convert.
- First customers
- Engineers at small software companies of 5 to 50 people whose product pulls data or submits forms on sites without APIs, such as for billing or logistics.
- Where to reach them
- Hacker News and Show HN: Post a demo of a real site change repaired live, since the topic drew interest there.
- Playwright community forums: Answer broken-selector questions and link to a free diagnosis of a failing script.
- Direct outreach: Contact founders and engineers of data-extraction products and offer a managed pilot.
- First milestone
- Five teams each run at least three real automations for a month, and two pay for the Team tier.
Why people already pay for this
- VerifiedHacker News post received 117 points and 58 comments
- Public claimWebsites change, selectors break, and failures can be painful to reproduce and fix, making maintenance the hard problem in browser automation.
- Public claimTeams ask whether RPA tools can fill API gaps by automating websites without APIs.
- Public claimCommon use cases for browser automation include scraping data, pulling reports, and submitting forms.
- Public claim
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Browser runtimeContainerised headless browsers with a job queueScheduled runs need isolated browsers that scale up and down and capture traces.
- This app · Evidence storageObject storage for snapshots and tracesScreenshots, DOM snapshots and network logs are too large for Postgres.
RisksAI inference
- AIA generated fix may pass the checks yet change behaviour, such as submitting a wrong value in a form. Assertions and approval defaults must be strong.
- TechnicalBot detection, captchas and logins on target sites can make runs fail for reasons a code fix cannot solve.
- RegulatoryCustomers may automate sites whose terms forbid it, and storing page snapshots may capture personal data. Terms and retention controls are needed.
- CommercialTeams may keep Playwright in their own CI and add an AI coding tool, so the hosted runtime must be clearly worth paying for.
- DataStored credentials and captured pages are sensitive; a breach would end trust in the product.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.