How it all works

Your profile's device sits inside the browser itself, rather than being written into the page on top of an answer already given. A fallback, the Built-in engine, ships too, and the Engine screen always names the one running for you right now.

The app opens with no account at all: two profiles, no card, everything on this machine.

You sign up on the site, and the app opens that page itself. What you get back is a one-time code that lives minutes and works once.

1. 1

   You sign up on the site

   The app opens the page itself.

2. 2

   You are issued a one-time code

   For this account, valid for minutes and valid once.

3. 3

   The link takes you back to the app

   The system routes it into the copy already open, not a second one.

4. 4

   The code becomes your pass

   From there it works the same as a password you typed.

5. 5

   This machine takes a device seat

   By hardware id, against the seats your plan carries.

A profile is a machine of its own, built on one of five templates.

Everything else is drawn from pools of what real machines report, and what moves together on them moves together for you. The finished fingerprint is stored nowhere and is put together again at every launch, so the same profile always shows a site the same machine.

• macOS, Chrome

• Windows, Chrome

  Platform Win32, an x86 architecture hint, pixel ratios of 1, 1.25 and 1.5.

• Linux, Chrome

  Platform Linux x86_64 with an empty platform version, because Chrome on Linux reports none.

• Android, Chrome (phone)

  Five touch points, no system chrome, and the whole handset taken from one list.

• Android, Chrome (tablet)

  The same platform but not mobile: a tablet reports a desktop-shaped user agent.

A profile does not open in one move, and almost any step along the way can refuse. A window that looks ordinary and is not is worse than a window that never opened.

The order is chosen so that a refusal reaches you before the window rather than after it. Your cookies and logins are in place before the browser makes its first request.

1. 1

   Room for the window

   How many profiles run at once is capped by the memory in this machine.

2. 2

   The proxy check

   A half-configured proxy gives you no launch.

3. 3

   The generation check

   A profile from a newer build stops here.

4. 4

   The lock on the profile

   The profile is marked busy before any window appears.

5. 5

   Your session

   Cookies and logins arrive before the browser starts.

6. 6

   The address change

   Only if the profile asks for a fresh IP.

7. 7

   The exit country

   Four providers name it over TLS, not one.

8. 8

   Extensions

   The ones you enabled reach the profile, and a refusal is told to you.

9. 9

   Protection

   Tracker blocking, link cleaning and the rest of the substitutions.

10. 10

    The window

    The start page first, your destination second.

You can give an address in four kinds of connection, and a batch copied from a seller exactly as it stands goes in with one paste. You enter the same address in the library once, and profiles point at it.

The exit country then sets the timezone and the language stack, because a clock that disagrees with the address is one of the first things checked. Your proxy password never reaches the command line.

• HTTP and HTTPS

  The common case, with a login and password too.

• SOCKS5

  With a login and password as well, if the seller issued them.

• SSH

  Your own server as an exit, with no third-party proxy to buy.

• Proxy providers

  Eight providers with type, regions and a price hint, and nothing is bought through us.

A profile with a window opens our start page, and it lives on your own computer. A start page fetched from someone else's server would announce every launch of yours to its owner.

It shows the exit address with country and network, the profile, the engine actually running, and the readings the profile presents. It goes out once, and only through this profile's own proxy.

You pick a scenario when you create a profile, and between them the five name 20 platforms. The scenario decides which platforms a profile knows, what it blocks, and how many actions a day it treats as normal.

A new account gets a ramp rather than the full ceiling at once: 20, 35, 50, 65, 80, 90 and then 100 per cent over seven days. Nobody blocks you from anything, the hint simply sits next to the profile.

You will not have to rename the headings in your file: the app recognises them by meaning rather than by an exact string, and in several languages at once. A column it could not recognise is named to you outright instead of guessed at.

Profiles past the limit queue up and wait for a seat instead of failing. The limit itself depends on the memory in your machine.

On the Flows screen you build a flow out of 19 kinds of step without writing a line of code, and three of them take other steps inside. Before a run you choose the profiles and how many of them work at once.

• Go to URL

  Open an address in the profile's tab.

• Wait

  Pause for a time or for a selector.

• Click

  Click what a selector matches.

• Input text

  Fill a field and fire its input event.

• Scroll

  Scroll by an amount or to an element.

• Extract text

  Read text into a variable.

• Take screenshot

  Capture the page, kept with the run.

• Press key

  Send one key, such as Enter.

• Random delay

  Pause a random time between two bounds.

• Repeat

  Run the steps inside a set number of times.

• If / else

  Two branches and one of them taken.

• For each element

  Run the body once per matched element.

• Tab control

  Open, switch or close a tab.

• Cookies

  Read, set, delete or clear cookies.

• Run JavaScript

  Run JavaScript in the page.

• Wait for request

  Wait for a request matching a pattern.

• Type like a person

  Type the text letter by letter with real key presses, with pauses and, if you set a share, typos that are erased at once.

You set a schedule for every day, for days of the week or by the hour in your own city's time, and a missed slot is not caught up later. It runs only while the app is open, because we install nothing into your system as a service.

If no group is ticked for a member, they see every group, and the window says so: «Nothing picked: this person sees every group». It is an explicit lifting rather than an accident.

Every machine takes a device seat by hardware id. A profile open on one machine will not open on another: you get a plain refusal naming whoever is holding it right now.