Sessions and the License

A session is one active persona. Your plan sets how many sessions you can use at once, and a signed license token on each machine says how many personas may be active there, and until when.

Sessions and the capCopy Anchor Link

Your plan has a session cap: how many personas can be active at once. Plans lists each plan's cap. bauta status shows the plan, the sessions in use and across machines, and this install's id:

bauta status

plan       <plan>, <cap> sessions
sessions   <in use> in use of <cap>, on <machines> machines
install    <install id>

During a trial, the plan line also says how many days are left, and in the trial's last three days a line says when it ends. With no account, bauta status shows this machine's free session, and answers without asking our server:

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

Over the capCopy Anchor Link

The license token on a machine says how many personas may be active there. The gateway counts its active personas against it. A persona beyond it, or any new one while the license has expired, waits in a queue with its connection open, first come first served, until a browser closes or a new license arrives; a persona that is running is never stopped to make room. bauta stats shows the gateway's active and queued personas, against the license:

bauta stats

A persona that is running is never stopped.

The license tokenCopy Anchor Link

bauta setup, bauta activate and bauta login get this machine a signed license token from our server, and bauta keeps it in ~/.bauta/license. bauta activate prints how many active personas the token allows on this machine, and until when.

While it runs, bauta serve renews the token at most once a minute. It sends the license key, the install id, how many personas are active and the bauta version. What bauta sends lists everything bauta sends, and when.

If the server cannot be reached, the last token holds until it expires. A persona that is running is never stopped.

The browser checks the license once, at launch, and a license that expires while the browser runs does not stop it. If the license is missing, expired or not ours, the page sees the real machine, and the browser says why on stderr.

MachinesCopy Anchor Link

Each machine has an install id, random and made once. With an account, activate your license key once per machine. Your key is on your dashboard:

bauta activate <license key>

In Docker and CI, set BAUTA_LICENSE_KEY instead; it wins over a key activated on the machine. A container keeps its install id when its /data is on a volume.

A persona reads the same on all your machines, and its directory moves between them. See moving a persona between machines.

Signing in and outCopy Anchor Link

bauta login signs up or in with GitHub, in the terminal: it prints a code to enter on any device. bauta logout takes the machine back to its free session. bauta upgrade prints the URL of the pricing page.

A persona's noise comes from your license's secret, so signing in or out can give this machine's personas new fingerprints. When the machine has personas, bauta login and bauta logout ask first:

3 personas on this machine will get new fingerprints. Continue? [y/N]

From the free session, a new account keeps them.

While BAUTA_LICENSE_KEY is set, it wins over the key bauta login keeps, and bauta logout asks you to unset it first.

NextCopy Anchor Link

• Plans: each plan's sessions.
• License keys: your key, on each machine.
• The CDP gateway: where personas become active.