Sam Morris

Demonstrate by Notte - Browser workflows to deployed automation in minutes

by
Record any browser task once and get production-ready code instantly with Demonstrate Mode. Edit further your code in our Automation Studio with live browsers, deploy automation code as a serverless function, and schedule it to run autonomously. Managed sessions, proxies, identities, and vaults handle everything behind the scenes. The fastest path from prototype to production in one unified platform.

Add a comment

Replies

Best
Hannah Krause

I wasted an embarrassing amount of time just trying to get a basic browser automation to run. One tool to record another to fix things then something else to actually execute it. Half the time it just dumb.

Tried Demonstrate Mode out of curiosity. Showing the flow once and getting code right away is the first time this hasn’t felt overengineered. Still early but not having to bounce between tools already makes it worth paying attention to. 
Best of luck team with the launch.

Leonhard

After trying a few recordings what really matters for me is what happens after the first run. The fact that the recorded flow becomes code you can open, change and run again right away matters a lot. Small tweaks usually force a full redo with other tools so keeping that loop tight inside Demonstrate saves time and avoids redoing work.

Selina

Most browser automation tools talk a lot about what they can do but its not always clear how that becomes something usable day to day. Reading this the focus seems to be on building workflows that don’t need constant fixing once they’re set up. That direction comes across as more practical for teams that want automations to keep running longterm instead of becoming another thing to maintain

Yulia Kuznetsova

There a big difference between tools that show results and tools that show how those results were reached. A lot of agent based systems hide too much so when something goes wrong you’re left guessing. The way Notte and Demonstrate keep the steps visible and editable suggests more control over time which matters when automations stop being experiments and start being depended on.

Brandon Ellis
Seen both sides of browser automation break in different ways. Agents can deal with surprises but lose reliability fast while scripts usually work fine until a site changes even slightly. Interesting here is not choosing one over the other, but mixing them. Keeping the repeatable steps fixed and using reasoning only where it is actually needed looks closer to how real automation works once things run at scale.
Natalie Brooks
When a recorded workflow depends on things like dynamic selectors, loading states or small layout shifts what parts stay locked as code and what parts stay flexible for the agent to handle at runtime?
yama

The hybrid approach with AgentFallback is really thoughtful. When the agent fallback handles a UI change dynamically, does it automatically update the underlying script selectors, or does it require manual review to commit those fixes permanently?

Mykyta Semenov 🇺🇦🇳🇱

Congratulations on the launch! We develop corporate platforms for large corporations a lot — it used to be our main specialization. We’ll definitely check out your project!

divyaprakash D
The 'AgentFallback' concept is a game changer for browser automation. Brittle selectors are the biggest pain point in Playwright/Puppeteer. Does the agent use visual/OCR cues to recover when a selector breaks, or is it strictly DOM-based reasoning?
华 张

I’m blown away by how quickly I can turn a quick browser recording into production-ready automation—this has cut our development time in half! Quick question: how does the platform handle proxy rotation and IP blocking for long-running, high-scale tasks?