Launching today
Rindler
Automate the web work your team does by hand
383 followers
Automate the web work your team does by hand
383 followers
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
Free Options
Launch Team / Built With
Rindler
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
@michael_serrano Congrats for shipping🙌 qq Is there a local SDK or TypeScript client available to trigger Rindler sessions directly from our own backend application code?
Rindler
@michael_serrano @priya_kushwaha1 Yes, and if you have use-cases specific to your business, we'd be happy to have you on a call!
Rindler
@priya_kushwaha1 thanks for the support!! We also have an MCP server over HTTP, so from a Node backend you point the official MCP TypeScript client at https://mcp.rindler.ai/mcp with a bearer token and you're good to go.
To run an automation, you just need to specify the site and the task :)
Blockem Profiles
@michael_serrano I'm always excited by products that make the entire AI ecosystem stronger rather than competing with every existing tool. Nicely done
EverTutor AI
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!
Rindler
@suryansh_tiwari2 Great question Suryansh! We operate with self-healing infrastructure that ensures our mapped sites remain mapped, maximizing up-time/reliability and minimizing costs, and our infrastructure takes A/B tests into account when creating site mappings. Thank you for the best wishes!
Rindler
@suryansh_tiwari2 a lot of our time goes into making the maps robust up front, so they hold up on their own, and the self-healing Arthur described sits on top of that too. Long term we think mapping is what will make browser work efficient. Thanks for the support too!!
The login and bot protection part caught my attention. How do you handle sites that frequently change their security flow?
Congrats @michael_serrano & team!
Rindler
@hamza_afzal_butt The same mapping and maintenance infrastructure works for the log-in pages as well, so updating log-ins don't break the system. We try to adapt as best we can to the latest security measures as well.
Rindler
@hamza_afzal_butt thanks! Happy to chat more about our login process and how we keep it efficient but secure. Appreciate the support!
A clean approach to browser automation always gets my attention. Looking forward to seeing how developers use this in real workflows.
Rindler
@1mirul thank you, and let us know what you think!
Automation that feels reliable is hard to build. Excited to see what the team has created here. Best wishes for the launch!
Rindler
@monir_ thank you! Our goal is to get agents on web workflows being something that you can really trust and lean on. Let us know any thoughts/critiques you have on trying it out :)