Licensing

Tests on your own computer need no account. A remote endpoint machine runs tests once it holds a license, and the controller gives it one from the plan of the account it is signed in to. Adding endpoints walks through the sign-in and the first activation; this page explains the plans, what a license does over time, what the endpoint card shows about it, and how a controller without internet is licensed.

Free and Team

A new account is on Free. Two remote endpoint machines can be licensed to it, and they belong to the account alone. One controller is signed in to a Free account at a time: a sign-in from another controller signs the earlier one out.

A Team has as many machine slots as it bought, and they are shared. A machine licensed by one member is usable by every member and by every CI run, and the slot is counted once however many people use the machine. Members are invited on the Team page of the account.

The Team trial lasts 30 days, asks for no card, and removes the limit on the number of endpoint machines. It is started on the account page or from the controller's Account tab. When the trial ends without a purchase, the account returns to Free, and the machines marked Keep in priority on the Activated endpoint machines page stay licensed first, up to what Free allows.

The pricing page has the prices, the billing periods and how machines are counted.

Activation and revocation

A machine is licensed from its card in the Endpoints panel: right-click the card and choose Activate License. The controller reserves one of the plan's slots and pushes the license to the endpoint. The controller never activates a machine on its own.

The license belongs to the machine, not to the controller that activated it. Any controller of the team that reaches the machine runs tests on it.

Revoke License in the same menu removes the license from the machine and hands the slot back. The team owner can also revoke any machine, and a member the machines it activated, on the Activated endpoint machines page. A machine revoked there while no controller reaches it keeps its license until the license runs out, and its slot stays taken until then; the controller's Account tab lists it as revoked with the time its slot frees.

Renewal

A license is valid for three days. A signed-in controller renews its own token and the licenses of the machines it manages once a day, so a machine stays licensed as long as a controller of the account signs in now and then.

When no controller of the account has signed in for three days, the licenses run out. The card's license row reads Ready for license and its status Locked: the endpoint answers, but a run cannot start there. Sign in and choose Activate License from the card's menu again.

The Account tab's machines table shows Licensed for every machine the account holds, and Renewal overdue when its last renewal is more than a day old.

License states on the card

Every remote endpoint card shows its license row at all times. The row reads one of these:

• Licensed: the machine holds a valid license.
• Ready for license: the machine holds no valid license, or its license ran out. Activate it from the menu.
• No license slot: every machine slot of the plan is in use. Revoke a machine you no longer need, or start the trial or buy Team, then activate this one.
• Activating… and Revoking…: the controller is reserving the slot and pushing the license, or removing the license and freeing its slot.
• Activation failed and Revoke failed: the action did not go through; hover the row for the reason and try again from the menu.
• Not licensed: the license state is read once the endpoint is reachable.

The localhost card needs no license. Its row reads Not signed in while the controller is signed out, once for the whole panel, and stays empty otherwise; tests on localhost run either way.

The card's status pill reads Locked whenever the endpoint answers but a run cannot start there, because the controller is not signed in or the machine holds no valid license. The Troubleshooting section of Adding endpoints tells the cases apart.

Bundle File for a controller without internet

A controller without internet cannot sign in, activate machines or renew their licenses. A Bundle File does it for that controller. It is downloaded by the team owner on the Offline lab page of the account, on the trial or on Team, and holds a fresh license for every machine the team has activated, valid for 30 days.

1. On the controller without internet, check that the machines you want appear in the Endpoints panel with the status Locked: they are reachable, but appear as Locked because this controller is not signed in.
2. In the controller's Account tab, click Export Request File…. The Request File names the controller and the machines it sees.
3. On a computer with internet, choose the Request File on the Offline lab page and download the Bundle File. The machines the Request File names are activated for the team, slots permitting, and the bundle carries a token for that controller. Without a Request File the bundle holds the licenses only, for a controller that already has its token.
4. Back on the controller, click Import Bundle File… in the Account tab. The controller signs in with the bundle's token and pushes the licenses to the machines. The tab says which bundle is in use and the date its licenses are valid through.
5. Repeat before the licenses run out. A controller signed in by a bundle does not renew on its own; the next bundle brings the next licenses and token.