Licence and team members

You should never be locked out of your own tracker, and you should never pay for a client. This page explains how the licence works. Prices and team member counts for each edition are on pricing.

Editions #

• Free. No licence needed, with a small number of team members.
• Trial. A trial key from the website gives you a larger team member count for 30 days. After that the install behaves as Free.
• Team and Studio. Paid annual editions. The key carries the number of team members and an updates-until date, one year after purchase.

Single sign-on is available on every edition. See sign-in.

Who counts as a team member #

A team member is an active user who is staff, or who holds the admin or member role on at least one project.

Clients never count. Client-only users, deactivated users and imported inactive placeholders are free, and the number of clients is unlimited on every edition.

Fallback licence #

A paid licence covers every build released on or before its updates-until date, forever. A build released after that date still runs, with the team members from your licence, but staff see a banner: “Your updates ended on 21 Oct 2027. This version needs a renewal, or go back to version 1.4.” Reads and writes are not affected.

The version named in the banner is the newest release dated on or before your updates-until date, taken from the release list the update check fetches. When that list is not available, because the check is off or the server has no network, the banner says “an earlier version” instead.

Over the limit #

Nothing is removed or locked. Adding a team member is refused with a plain message such as “Your licence covers 15 team members. Remove someone or upgrade.”

These actions add a team member and are refused at the limit:

• inviting someone to a project as admin or member, or adding them
• changing a role from client to admin or member
• a staff-domain sign-in or invite acceptance that would create a staff user
• turning on staff for someone in /admin/users
• reactivating a user who would count

If a lapsed trial or a smaller licence leaves you over the limit, the team members you have keep working. Only new team members are refused.

Entering a key #

A key looks like eddy1. followed by two long base64 parts. You can enter it in three places:

• the installer, with --license
• the setup form, on first run
• /admin/settings, in the Licence section, which also shows your plan, team members used and updates-until date

To enter a key from the server, for example when nobody is signed in:

eddy set-license <key>

Keys are not tied to a domain or a machine, so you can move servers. A key is checked offline against public keys built into the app, so Eddyline never calls home about your licence.

Renewals #

Renew before or after your updates-until date. You receive a new key with a date one year later. Paste it in /admin/settings or run eddy set-license. Cancelling a renewal changes nothing on your install: the fallback licence keeps it working on the versions it covers.

Upgrading from Team to Studio gives you a new key with more team members and the same updates-until date.