Almost anything you can do in a web browser: navigating sites, clicking, typing, uploading and downloading files, calling remote APIs, capturing screenshots and video, and stitching it all into complex flows.

Because Uindow interacts like a real person, it keeps working on sites that block ordinary automation.

You can run those flows yourself, on a schedule, or hand them to an AI agent.

Not at all. The fastest way to build an automation is to record one: press record, use the browser normally, and Uindow turns your actions into a working module.

You can also install ready-made modules from the repository, enter any details they need, and run them.

And if you prefer plain language, connect an AI agent over MCP and simply describe what you want done.

Yes. Uindow includes a real built-in code editor, with autocomplete, linting, and formatting, where you write modules in plain JavaScript.

Beginner-level JavaScript is enough to build powerful, tailored workflows, and the recorder can write most of the code for you to start from.

Avoiding that is exactly what Uindow is built for. Every click, keystroke, and scroll is a trusted, OS-level event, with natural mouse movement and realistic typing, so sites see a real person rather than a script.

And because Uindow runs on your own computer and your own IP, there's no shared datacenter address to flag.

There are no stealth plugins to install or maintain, it's simply how the engine works.

Those are excellent developer libraries for controlling a browser from code, mostly aimed at testing.

Uindow is a complete desktop app focused on interaction that looks human and runs from your own machine and IP, with a recorder, a visual editor, scheduling, a module library, and built-in AI-agent connectivity.

In short: they're great for writing browser tests, while Uindow is built for automations and agents that need to behave like a person and not get blocked.

Everything runs locally, on your own computer. We never host a browser for you and never route your traffic through a shared cloud.

That keeps your runs fast and private, and ties them to your own IP address, the most human fingerprint there is.

Never. Uindow uses the internet connection of the machine it runs on, so your automations go out through your own IP.

If you want runs to come from a different location, simply run Uindow on another machine or server you control.

Uindow speaks MCP (the Model Context Protocol), so agents like Claude, Cursor, or Copilot can drive it directly.

Run it locally over stdio for zero-latency, fully offline control. Your agent gets a browser that behaves like a human and isn't easily blocked.

Uindow can pause mid-run and ask you to step in, to log in, solve a captcha, or enter a one-time code, then continue exactly where it left off.

Your automations wait for you instead of failing at the first wall.

Yes. Each Uindow instance can run up to nine agents at once.

Each agent works in its own isolated, secure browser session with its own profile, so they run independently and can never see each other's data.

Yes. Automations can run at specific dates and times or repeat on a recurring schedule, and individual steps can be deferred to the future.

For always-on jobs, run Uindow on a machine that stays on, such as a small server or VPS you control.

Yes. The @uindow/cli package lets you drive automations from any terminal or CI/CD pipeline, so browser steps live right alongside the code you ship.

You can also stream live, colorized logs from the command line, much like tail -f.

A lot more than pass or fail. Every run can produce screenshots, full video recordings, downloaded files, structured tables, and detailed logs.

Results are searchable, filterable, exportable, and saved as real files on your computer.

Recording even continues through page loads, reloads, and failures, so nothing is missed.

Yes, all modules are private by default.

If you choose to publish a module to the Uindow Repository, it must first undergo a manual review and receive approval from our team before it becomes publicly accessible.

Uindow accepts no liability for user-generated modules, including any we approve for listing in the repository; modules reported to violate a third party's terms of service will be removed promptly upon notice at ugc@uindow.com, and we reserve the right to suspend the offending user's account without refund.

Yes, your credentials are securely protected.

Uindow is built on top of the Chromium web browser, and all sensitive data, such as cookies and passwords, is stored locally on your computer.

Modules do not have access to your private information by design!

This means you must manually authenticate before running any automation on websites that require login.

Yes, data privacy is a core principle of Uindow.

All files and data are stored exclusively on your computer, and no user activity is tracked.

Additionally, you have full control over your automation modules, which can remain private by exporting them as .js.yaml files.

Yes. A module's inputs are kept separate from its source code, so you can hand someone the exported .js.yaml file and nothing sensitive comes with it.

The app also can't reach into your files on its own, you decide exactly which files each run is allowed to use.

Mostly, yes. Building and running modules happens entirely on your machine, so the core works without an internet connection, beyond whatever the sites you automate require.

You'll only need to be online for things like signing in, or installing modules from the repository.

Uindow is deterministic at its core: your logic runs as plain, predictable JavaScript, not AI guesswork.

For the few tasks where that isn't enough, like summarizing text or judging sentiment, a small language model runs locally on your machine.

And when you want full autonomy, any MCP-compatible AI agent can drive Uindow itself.

The application's source code is published on GitHub, so you can read and audit exactly what runs on your computer.

Uindow is released under our own license rather than a standard open-source one, but the module format is open and portable, and our CSS selector engine is fully open-source.

Uindow is a desktop application you install on your own computer.

Please see the install page for the current list of supported operating systems and the latest download links.

No, Uindow does not have a free tier. However, you can enjoy a free trial with no commitment and, more importantly, no dumb restrictions.

Uindow gives you powerful capabilities, and how you use them is up to you.

Please respect the terms of service of the sites you automate and the laws that apply to you.

Uindow is designed for legitimate automation, testing, and agent workflows.

We're using Firebase for authentication so you can log in with either your Google account or any valid email address.

Make sure to add noreply@uindow.com to your contacts list and never follow authentication links that don't point to our domain, auth.uindow.com.