Why I got fed up with Selenium and built a local browser-as-a-service

Hey everyone! I wanted to share a quick update on why I’m building NTXM Browser Mini and the specific problem it solves.

If you’ve ever built a web scraper, an automated testing suite, or an AI agent that needs to look at the web, you know the absolute nightmare that is managing WebDrivers. You write a script, Chrome updates silently in the background, your driver breaks, and your entire pipeline crashes.

I built NTXM Browser Mini to completely decouple the browser runtime from language-specific drivers. By embedding a C++/CEF rendering engine with a built-in local REST server, it essentially treats the browser as a local microservice.

How it works:

• You run a single, lightweight executable locally.

• You send standard HTTP REST requests from any language (Python, Go, Node, Curl) to open tabs, wait for dynamic element states, and grab rendered HTML.

• Everything runs offline-first on your machine, so your data payloads never hit a third-party cloud.

I’m focusing hard on keeping it zero-config and lightweight. If you've run into similar automation headaches, I'd love to hear how you're solving them! Check out the documentation here on our NTXM Browser Mini Product Page.