Your License Key

Your license key ties bauta on your machines to your account and its plan. You activate it once per machine; after that, bauta serve keeps the license current.

Where to find itCopy Anchor Link

Your key is on your dashboard, under License key. It stays masked until you choose Show, and Copy puts it on your clipboard. A key is 64 hexadecimal characters.

If you made your account with bauta login, or when bauta setup offered one, that machine already keeps the key and is activated.

Activate a machineCopy Anchor Link

bauta activate <license key>

Run it once on each machine. It keeps the key on the machine, fetches the machine's first license token, and prints how many personas may be active on this machine, and until when.

Sign in with GitHubCopy Anchor Link

bauta login

bauta login signs you up or in with GitHub, in the terminal. It prints an address and a code to enter there, on any device, your phone too. It then keeps your account's key and activates this machine. Signing up accepts the Terms.

When this machine already has personas, bauta login asks before it goes on. A persona's fingerprint is derived from its name and the license's secret, so another license gives the personas new fingerprints. A new account made from this machine's free session keeps them.

bauta login needs a terminal. In a script, set BAUTA_LICENSE_KEY instead.

Log outCopy Anchor Link

bauta logout

bauta logout takes this machine back to its free session: 1 session, no account. It forgets the key and the license token. When the machine has personas, it asks first, since they would get new fingerprints. While BAUTA_LICENSE_KEY is set, unset it to log out.

Check your licenseCopy Anchor Link

bauta status

bauta status prints the plan, the sessions in use across your machines, and this machine's install id:

plan       trial, 10 sessions, 3 days left (until Nov 15)
sessions   2 in use of 10, on 2 machines
install    <install id>

In the last three days of a trial, it adds a line with the date the trial ends and the pricing page's address. On a machine with no account, it prints the machine's free session:

plan       free, no account: 1 session on this machine
install    <install id>
Run "bauta setup" for 3, or 10 for 30 days.

bauta status sends only the license key to our server.

Docker and CICopy Anchor Link

Set BAUTA_LICENSE_KEY to your key. When it is set, it wins over a key kept on the machine.

export BAUTA_LICENSE_KEY=<license key>
bauta serve

docker run --init --cap-add=SYS_ADMIN -p 127.0.0.1:9222:9222 \
  -e BAUTA_LICENSE_KEY=<license key> ghcr.io/bautabrowser/bauta

Without a key, a container runs the free plan, with 1 session. See Docker.

The license tokenCopy Anchor Link

Our server answers an activation with a signed license token, which bauta keeps in ~/.bauta/license. The browser checks the license once, when it launches.

While bauta serve runs, it renews the license at most once a minute, sending the license key, the install id, how many personas are active and the bauta version. If the server cannot be reached, the last token holds until it expires, and a persona that is running is never stopped. A license that expires while the browser runs does not stop it either.

MachinesCopy Anchor Link

A key works on any number of your machines, and your plan's sessions count across all of them at once. Each machine has an install id, random and made once. bauta status shows how many sessions are in use and on how many machines. The dashboard lists each machine running bauta with your key, with its bauta version, its sessions and when it was last seen.

What a persona's profile keeps (cookies, passwords) is encrypted with your license's key, not the machine's. Copy ~/.bauta/personas/<name> to another of your machines, on any OS, and it opens there with its cookies and passwords. A browser under another license cannot open it.

Keep it secretCopy Anchor Link

Keep your key confidential. You are responsible for all activity under it, and sharing or publishing it is against the Terms.

NextCopy Anchor Link

• Plans and sessions: what each plan allows.
• Environment variables: BAUTA_LICENSE_KEY and the others.
• Docker: run the gateway in a container.