The Clout guide
This is the documentation a person who has paid for Clout reads. It describes what the product does today, in the order a new customer meets it.
Where something does not work yet, this guide says so in the same sentence it would have described the feature. That is deliberate: a guide that documents an intention teaches people a product that does not exist, and they find out at the worst moment.
Read these in order
| 1. Getting started | Create an account, sign in, get the app onto a computer |
| 2. The two engines | Which browser runs your profile, where it comes from, and why it depends on where the profile came from |
| 3. Bringing your profiles across | AdsPower, Kameleo, Multilogin, Dolphin and GoLogin, and what each one needs from you |
| 4. Profiles | What a profile is, creating one, the fingerprint, proxies, editing, and the trash bin |
| 5. Machines | Signing in on a second computer, what syncs, and retiring a machine |
| 6. Teams | Ranks, access, and which permissions the server actually enforces |
| 7. Your subscription | What a plan grants, what a period ending does, cancelling, refunds and deletion |
Alongside them: How your data is held, which is where your credentials live, what protects them, what leaves your machine, and who can read what. Read it before you import an account you cannot afford to lose.
What works today
Measured 6 September 2026. Chapters 1 to 3 were written by driving the running app and portal; chapters 4 to 7 and this table were written by reading the product itself, screen by screen and route by route, and quote its own words where they appear.
| State | |
|---|---|
| Sign in to the portal | Works. Google, on app.cloutlabs.co. Telegram is built and the sign-in page says whether it is switched on |
| Download the app | Works. macOS, Windows and Linux, one row each under Downloads |
| macOS build | Signed and notarized. It opens without an argument |
| Windows build | Not signed. SmartScreen warns on first run until a certificate is bought |
| Sign in inside the app | Works. Through your system browser, and the app is unusable until you do |
| A computer under Devices | Works, and it happens on sign-in. Nothing to pair |
| Removing a computer | Works, and it is permanent for that machine. Signing in again is refused |
| Connecting a computer to sync | Works. Account, This computer, Connect |
| Sync | Pulls. A connected computer receives the account's fleet. Nothing uploads a new profile yet |
| Import from AdsPower, Kameleo, Multilogin, Dolphin, GoLogin | All five work from the app. Dolphin needs a token, GoLogin needs a token or a sign-in |
| Create a profile | Works, with no AdsPower installed and no network call |
| The browser engine | Installed by the app from our servers. Kameleo profiles still need Kameleo |
| Engine coverage | Versions 143, 144, 145, 146, 147 and 151 are published for macOS, Windows and Linux. Profiles use their exact pinned version |
| Proxy per profile | Works, on the profile or from the saved proxy book |
| Saved proxy book, checks, rotation | Work |
| Trash bin, favourites, folders, tags, templates, extensions | Work |
| Team: invite, ranks, folder access, per-member permissions | Work |
| Permission groups | Stored on the account. Group names, membership and permissions follow the team across computers |
| Five permissions in the catalogue | Nothing enforces them yet, and the screen greys them out and says so |
| Bandwidth and usage meters | Work |
| Payment, invoices, self-serve checkout | Do not exist. Plans are arranged by conversation and granted by hand |
| Proxy pools | In the store and on the local API, not on any screen |
Words this guide uses
Profile. One browser identity: its fingerprint, its cookies, its proxy, its name. A profile is what you launch.
Fleet. All the profiles on your account. There is one fleet per account, and a team shares it.
Engine. The actual browser binary that runs a profile. There are two, and which one runs a given profile is decided by where that profile came from. See The two engines.
Version, or kernel. One installed build of an engine. "Chrome 151" is one. A profile can pin a version or take the newest installed one.
Device, or computer. A machine that has signed in to your account with the app on it. The portal calls these Devices.
Read only. What your account becomes if the subscription lapses. Everything opens; nothing saves. See Your subscription.