Rindler automates the repetitive web work your team still does by hand. Say what you need in plain English, and Rindler goes to the real site, signs in when needed, completes the task, and returns clean structured data. Put it on a schedule and it keeps running. Instead of making a browser agent guess every time, Rindler maps each site ahead of time and repairs workflows when pages change, so recurring tasks stay reliable
Rindler is a map of a website that an agent calls instead of reading the page. The map knows what screens the site has and what you can do on each one, and it knows what comes back when you do it. So your agent gets the same fields back every run, in the same shape. We've mapped more than 1000 sites so far.
How a run works
We build the map ourselves, once, before anyone runs against it.
Our ingest picks up the site and works out what it's looking at.
The mapper drives the site click by click and drafts the map.
A fleet of agents goes through and fixes what the draft got wrong, and the map has to pass a check against the live site before it serves anyone.
Every run after that just draws on the map. There's no model sitting there working the page out again, so the run is fast and you get the same fields back in the same shape every time. Most browser agents redo all of that work on every single visit. That's why the field names come back different each run, and it's why every run takes as long and costs as much as the first one.
Inside a run we pick the transport step by step. For one action we drive a real browser, and for the next we call the site's own endpoint. If you bet everything on those endpoints you end up thin at the hard flows. Drive a browser for every click and it's slow.
What happens when a site changes
Every map runs against the real site once a day, checking a list of things that site still has to be able to do. Most of the time that means we catch a break before it shows up in your run. Fixing it is on us, so it doesn't end up as a ticket in your backlog. And if a step does fail mid run, a model works that one step out again while the run is going, and the request finishes.
What it costs
Starter is $100 a month for 100 sessions, with a 7 day free trial and one site you pick that we map for you. Teams is $1,000 for 1,000 sessions and scheduled automations. A session costs a dollar at every tier, and you don't pay for a run that fails.
https://chat.rindler.ai/ is a playground with a few sites open so you can poke at one without signing up. If the site your team is stuck on isn't in there, name it and tell me what you need done. I'll be here all day!
This made me stop scrolling. Instead of building another AI app, you're improving the way AI interacts with the web itself. That's a much bigger opportunity than it might seem at first glance. Looking forward to seeing real-world use cases.
Automation that feels reliable is hard to build. Excited to see what the team has created here. Best wishes for the launch!
A clean approach to browser automation always gets my attention. Looking forward to seeing how developers use this in real workflows.
The login and bot protection part caught my attention. How do you handle sites that frequently change their security flow?
Congrats on the launch! Love the idea of turning websites into reusable maps instead of making agents rediscover everything on every run. Curious how Rindler handles frequent UI changes or A/B tests—does the map update automatically? Wishing you an amazing launch day!
About Rindler on Product Hunt
“Automate the web work your team does by hand”
Rindler launched on Product Hunt on August 7th, 2026 and earned 229 upvotes and 19 comments, placing #4 on the daily leaderboard. Rindler automates the repetitive web work your team still does by hand. Say what you need in plain English, and Rindler goes to the real site, signs in when needed, completes the task, and returns clean structured data. Put it on a schedule and it keeps running. Instead of making a browser agent guess every time, Rindler maps each site ahead of time and repairs workflows when pages change, so recurring tasks stay reliable
Rindler was featured in Productivity (657.9k followers), Developer Tools (517.2k followers) and Artificial Intelligence (475.5k followers) on Product Hunt. Together, these topics include over 342.5k products, making this a competitive space to launch in.
Who hunted Rindler?
Rindler was hunted by Garry Tan. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Rindler stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Garry Tan
Rindler is a map of a website that an agent calls instead of reading the page. The map knows what screens the site has and what you can do on each one, and it knows what comes back when you do it. So your agent gets the same fields back every run, in the same shape. We've mapped more than 1000 sites so far.
How a run works
We build the map ourselves, once, before anyone runs against it.
Our ingest picks up the site and works out what it's looking at.
The mapper drives the site click by click and drafts the map.
A fleet of agents goes through and fixes what the draft got wrong, and the map has to pass a check against the live site before it serves anyone.
Every run after that just draws on the map. There's no model sitting there working the page out again, so the run is fast and you get the same fields back in the same shape every time. Most browser agents redo all of that work on every single visit. That's why the field names come back different each run, and it's why every run takes as long and costs as much as the first one.
Inside a run we pick the transport step by step. For one action we drive a real browser, and for the next we call the site's own endpoint. If you bet everything on those endpoints you end up thin at the hard flows. Drive a browser for every click and it's slow.
What happens when a site changes
Every map runs against the real site once a day, checking a list of things that site still has to be able to do. Most of the time that means we catch a break before it shows up in your run. Fixing it is on us, so it doesn't end up as a ticket in your backlog. And if a step does fail mid run, a model works that one step out again while the run is going, and the request finishes.
What it costs
Starter is $100 a month for 100 sessions, with a 7 day free trial and one site you pick that we map for you. Teams is $1,000 for 1,000 sessions and scheduled automations. A session costs a dollar at every tier, and you don't pay for a run that fails.
https://chat.rindler.ai/ is a playground with a few sites open so you can poke at one without signing up. If the site your team is stuck on isn't in there, name it and tell me what you need done. I'll be here all day!
Michael