Every installation of Eido Build is licensed by Eido, and runs while it stays in touch with Eido’s licensing service at license.eido.io.
Checking in#
Every four hours, Eido Build checks in. It sends:
- its install id
- the version it is running
- how many users it has
- how many projects, work items and agents it has
Those are counts only. It sends none of their content: no titles, no descriptions, no code, no customers, no conversations.
In reply it is told what it is licensed as. That is shown in the panel at the top of Admin, along with when it last checked in.
Check-ins are signed with a key that your installation made for itself. There is no licence key to enter or keep safe.
What your licence is based on#
Your licence is based on the number of users in your Eido Build. See Users and permissions.
When Eido Build locks#
Eido Build locks itself when:
| Reason | What the lock screen offers |
|---|---|
| A trial has ended | A link to subscribe on the Azure Marketplace, or to email sales. |
| The Azure Marketplace payment has failed, and stayed unpaid for seven days | Who to contact. |
| The installation has been blocked by Eido | The reason, and support’s address. |
| It has not checked in for 14 days | Support’s address. |
| It was never registered, or its registration has been lost | Support’s address. |
What locked means#
Everybody sees one screen and nothing else, admins included. The screen shows your install id.
While Eido Build is locked:
- nobody can use it
- no new stage, agent run or conversation with Odie starts
- it will not update itself
Nothing is deleted. Work that was waiting carries on once the lock is lifted.
Getting back in#
Only Eido’s licensing service lifts a lock. Restarting Eido Build does not.
Once the cause is put right, for example the subscription is paid or the trial is extended, Eido Build unlocks by itself. It checks every hour while it is locked, and the lock screen checks every three minutes while somebody has it open. The lock screen also has a button to check now.
If it cannot check in#
A check-in can fail for ordinary reasons, such as a network change or an outage at our end. Eido Build allows for that.
| Time without a successful check-in | What happens |
|---|---|
| Up to 3 days | Nothing. |
| 3 days | Admin shows a warning. |
| 14 days | Eido Build locks. |
If you see the warning, check that Eido Build can make outbound HTTPS calls to license.eido.io. A new firewall rule or a change to outbound filtering is the usual cause.
Reinstalling or moving#
An installation that has been rebuilt needs its registration reset before its check-ins are accepted again. Contact support with your install id before you rebuild or move an installation.