How can we help you?

PowerOps runs on Windows 10 or later, 64-bit. Each open profile is its own browser process, so memory scales with how many profiles you keep open at the same time. Plan disk space for the application, the browser it manages, and each profile's own browser directory.

Run the installer. It puts PowerOps in your own user folder, so it needs no administrator password, and the browser engine comes with it — there is nothing else to download and it works offline. Updates are one button inside the application. To remove it, use Add or remove programs; your profiles are kept.

Name the profile and let PowerOps generate its device identity. The identity is generated as a set, so its fields agree with each other from the first open. Assign a proxy from your library if the profile needs one, then open it. The browser it opens in is Orbit Browser, which comes with the application.

Opening a profile starts its own browser with its stored identity, and the row shows it as running. When you are done, close the browser window rather than killing the process. Close is when PowerOps writes the profile's state out, and it is the moment Cloud Sync captures cookies, Local Storage and IndexedDB if you use it.

A profile is its own browser directory, a stored device identity generated as a coherent set, and its own proxy assignment. Nothing is shared between profiles. Sites see the same device every time the profile opens.

Every profile has a number and a name, and the search bar matches either. Type a number to jump to the profile a script drives, or a name to find the one a person set up.

Group profiles by client, task or account set so the list shows one job at a time. Filtering by group also scopes bulk work, which keeps an action aimed at exactly the profiles it should touch.

Select several rows and act on them once. Assign a proxy across the selection, move the selection into a group, or open and close profiles together. Each action follows the same rules as acting on a single row, repeated per profile.

Each row shows whether its profile's browser is running right now. A running profile holds its browser directory open, so wait for the row to show it closed before you expect its state to be written out.

PowerOps generates a profile's identity fields together as one set, and the profile presents as Windows 11. Fields generated together agree with each other, which is what a real device looks like.

The identity is stored with the profile and applied on every open. A site that saw the profile yesterday sees the same device today. Nothing rotates unless you ask for a new fingerprint.

Edit a field and only that field changes. The rest of the stored set stays exactly as it was. That makes a small correction possible without disturbing an identity a site already knows.

Generating a new fingerprint replaces the whole set at once, and PowerOps says so before it does. Sites will see a different device on the next open. Use it when you want a fresh identity rather than a corrected one.

Add HTTP, HTTPS or SOCKS5 endpoints to the proxy library, with credentials where the provider requires them. The library is shared across profiles, so one endpoint can serve several profiles or exactly one.

Run a test on one endpoint or across the whole library. A test makes a real connection through the endpoint and reports the observed address, which is the address sites will see. An endpoint that fails the test will fail inside a profile too, so test before you assign.

Select the profiles and assign endpoints across the selection in one action. Each profile keeps its own assignment, so the bulk step is a convenience and changes nothing about how a single profile uses its proxy.

Set a profile's timezone and locale to match where its proxy exits. A profile whose address sits in one country while its clock sits in another is easy to notice. The identity fields are yours to edit, so align them when you assign the route.

PowerOps serves a local HTTP API on http://127.0.0.1:50326. It binds to loopback only, so nothing on your network can reach it and every request comes from the same machine PowerOps runs on. The Local API comes with the paid plans, and the trial opens it for 30 days without a card. The full route list and examples live on the Local API page.

Every route except status requires a bearer key in the Authorization header. The status route stays open so a script can check that PowerOps is up before it authenticates. Treat the key like any other secret and keep it out of committed code.

Ask the API to start a profile's browser. The response includes the CDP WebSocket endpoint for that browser. Connect Playwright or Puppeteer over that endpoint and the script drives the session with the profile's own identity and proxy in place. When the script is done, close the browser so state is written out.

Each open profile is its own browser process, so memory is the practical ceiling. Work through large jobs a few profiles at a time. Open a small batch, do the work, close it cleanly, then start the next. Closing between batches also gives Cloud Sync its capture point if you use it.

A workspace is the shared container for a team's profiles, and each member carries a role that sets what they can do inside it. Keep separate clients in separate workspaces so access follows the work. The free plan runs one workspace; the paid plans add more of them, along with roles and Cloud Sync.

Invite teammates to a workspace by email. The invitation ties the workspace to that person's account, and their role decides what they see once they join.

Encryption keys are created on your devices, and each device holds its own. Keys never come from the server. Credentials that PowerOps keeps for you live in the operating system's credential store.

Cloud Sync captures cookies, Local Storage and IndexedDB when a profile closes. The capture is encrypted on your machine before anything is uploaded, with keys that were created on your devices. The server stores what it cannot read.

One device holds a synced profile at a time. Opening the profile takes the lease, and the lease releases when the profile closes and its state is captured. The lease is what stops two machines from writing over the same session.

SmartScreen warns about programs it has not seen widely before. That reflects how far a file has spread, not what is in it. Choose More info, then Run anyway.

Check the endpoint first. Host, port and protocol have to match what the provider issued. Then check the credentials, since an expired password fails exactly like a dead endpoint. If both are right and the test still fails, the route itself is down and the provider is the next call.

A synced profile can be held by another device through the single-holder lease. Close the profile on the device that holds it, let the close capture its state, and this machine can take the lease. Profiles that are not synced are local and open without a lease.

PowerOps writes to the folder you extracted it into and to your profile data directory, and nowhere else. Each profile keeps its own browser directory inside that data directory. Removing PowerOps is deleting the folder, and profile data stays until you delete the data directory yourself.

Yes, through Cloud Sync, which the paid plans include. A profile's cookies, Local Storage and IndexedDB are captured when it closes, encrypted on your machine and uploaded. Another device with your keys opens the same profile and picks up where the session left off. The single-holder lease keeps one machine on it at a time.

PowerOps is Windows only today. If that changes, the download page is where it will show up first.

PowerOps verifies every update it downloads before anything runs, and nothing installs without you asking.