Local-first
Workflows, profiles, and history stay on your machine — no account or server required.
About
Why ProtoX exists
ProtoX Login began with a familiar problem: a growing pile of logged-in browser profiles, the same repetitive steps run in each of them, and nowhere reliable to keep the workflows that did the work. Scripts lived in folders, breaks went unnoticed, and nothing could be reproduced.
ProtoX Login is the answer: a local-first desktop manager for Windows that keeps persistent Chromium profiles, visual workflows, schedules, and complete run history on your own machine. Build a workflow once on a drag-and-drop canvas, then run it on the profiles it belongs to — on demand or on a schedule.
Two commitments run through everything. Your automation stays local: no account, no server, no cloud in the middle. And the app stays honest: every workflow is validated before it runs, and interrupted work is surfaced, never silently hidden.
Principles
Designed to be trusted
No cloud dependency. No silently skipped failures.
Durable before clever
Jobs and state are persisted, and interruptions stay visible instead of being hidden.
Validate before run
A complete validation report is shown before anything executes.
Secure defaults
Sandboxed scripts and a loopback-only local API, with explicit escape hatches.
Who builds it
The person behind ProtoX Login
ProtoX Login is built and maintained by Ngô Hữu Hoàng.
There is no support desk in between: when you write, your message reaches the person who writes the code. Questions, bug reports, and honest feedback are all welcome.
Talk to the person who builds it
Questions about features, licensing, or what ProtoX Login cannot do yet? Your message goes straight to the developer.