Freelance

Your own Upwork profile, a seller account on Fiverr, a Freelancer account: one per platform. Each one carries its own reviews, its own history and its own money.

Open two of them in one browser and the platform behind them sees one person: the same screen, the same fonts, the same graphics string, the same clock.

An account that loses its rating loses the years behind it. That is the thing being protected here, not the browser.

Most people keep accounts apart with what is already on the machine, and each of those answers stops halfway.

The half they leave open is the device. Every window reports the same computer as the window beside it, and that is what ties two accounts together.

Cookies and site storage live in a directory that belongs to that profile alone, and the proxy is a property of the profile rather than of the machine.

The device readings are derived from the profile id, so the same profile answers the same way at every launch.

On ARMANOS Browser the engine itself hands those answers to the page, before any script on it runs.

• Cookies and site storage

  A directory per profile, and nothing reads across the boundary.

• The exit address

  A proxy that is set and cannot be applied stops the launch instead of letting the profile out from your home connection.

• Clock and language

  Both follow the exit country: 114 countries carry a matching time zone and a matching language list.

• Device readings

  Screen, cores, memory, graphics strings and the font set come from one of five templates and one seed.

• Extensions

  Each profile has its own enabled set, chosen from a catalog of 11 inside the app.

• Passwords and one-time codes

  The account password is sealed by the system on Windows only, and the code generator follows RFC 6238.

The Freelance scenario carries six daily ceilings: the pace it treats as a safe day for a freelance account. They sit on the profile card, in the Safe daily ceiling section, next to today's count.

A profile created today starts lower. The ramp is 20, 35, 50, 65, 80 and 90 percent of the ceiling over the first six days, and the whole ceiling from day seven onward.

What the app counts is narrow: a top-level page opened in that profile's windows. The bar turns amber at 80 percent of the day's ceiling and red at the ceiling, and it stops nothing.

The scenario names Upwork, Fiverr and Freelancer, and naming is not automating. What you get is an ordinary browser window with an identity of its own.

The exit country is resolved over TLS from four providers rather than one, because a single free endpoint starts refusing during a bulk launch.

That answer decides the clock and the language list, so an account working from a German address does not sit in your own time zone.

Cookies do not live on our server. The session, the thing that keeps thirty accounts signed in, sits in the profile directory on the machine where you worked.

So you point ARMANOS at a folder your own cloud already syncs, on the Engine screen under Sessions on two computers, through a folder. Each profile leaves as a single encrypted file: scrypt to stretch the passphrase, then AES-256-GCM.

The passphrase for the sync files stays on this machine and never goes into the folder, and the system seals it on Windows only. Someone reading that folder sees a file named by the profile id and a label holding a time, a size, the machine name you typed and the app version.

1. 1

   You close the profile

   Four seconds later the app checks that it is still closed, packs the session without the caches and writes it. The packed file has a 400 MB ceiling.

2. 2

   The write is atomic

   A neighbouring temporary file first, then a rename, so the cloud never picks up half a session.

3. 3

   The other machine notices

   Once a minute it reads the folder's own timestamp, and only a change there makes it read the labels.

4. 4

   You open the profile there

   The fresh session is put in place before the window exists, and a notice names the machine it came from.

When both machines changed one session, nothing is overwritten and nothing is merged. A notice names the other machine, the choice waits for you in the profile menu, and sending yours keeps a dated copy of what it replaced, up to three such copies.

Two live sessions of one account from two addresses is the pattern that costs people accounts. The app refuses to produce it.

When you open a profile you claim it on the server: the app renews that claim every minute and releases it the moment you close the last window. If a machine loses power, the profile does not stay claimed forever: the claim lapses after three minutes.

From the second machine you get a refusal that names the holder and when they started, not silence. A takeover is deliberate, and the previous holder sees why their windows closed.