How licensing works
Without a key, Gadka supports up to 10 active accounts. On each server, the seat limit is the sum of the seats on its valid licenses.
Running Free without a key
To try Gadka, run the server without a key. The Free edition supports up to 10 active accounts. Gadka has no separate trial edition or test licenses.
How a key is tied to a server
Each Standard or Enterprise key is issued for one installation. At startup, the server uses machine characteristics to calculate its Server ID in the format GDK-XXXX-XXXX-XXXX-XXXX and a shortened hardware fingerprint. Together they form the installation code you enter when you buy a license.
- The key works only on the server with that Server ID.
- Minor changes, such as replacing a disk or RAM or updating the kernel, do not invalidate the key.
- The Server ID changes when you move Gadka to a new physical or virtual machine.
- If you copy the database to another server, that installation runs as Free.
The key works offline. The server verifies it without contacting the vendor.
Account limit
Your key specifies the number of seats. Each active account uses one seat. You can have a base license and additional licenses for extra seats. On any given day, the limit is the total number of seats covered by valid licenses.
Conversations continue when all seats are in use. To add someone or reactivate an account, free up a seat or buy another one.
What happens when a license expires
| Stage | What you see | What you can use |
|---|---|---|
| License is valid | Valid until … on the license page | All features |
| Grace period after expiration | The license expired on … The grace period lasts until … banner | All features |
| After the grace period, up to 10 active accounts | A notice that the installation has returned to Free | All Free features, within the Free limits |
| After the grace period, more than 10 active accounts | Everyone sees a banner explaining that they can only read | Reading, searching and downloading files |
The key sets the length of the grace period, usually 30 days. When the server returns to Free, federation and workflows pause. Their settings are saved and take effect again when you install a valid key.
When the account count exceeds the limit
If there are more active accounts than the license allows, everyone can still read the conversation history, but posting and most changes are blocked.
| Still available | Paused |
|---|---|
| Signing in and out | Sending, editing or deleting messages and adding reactions |
| Reading channels, threads and conversations | Creating channels and adding people |
| Searching and downloading files | Uploading files |
| Changing passwords and 2FA settings | Updating statuses and profiles |
| Deactivating accounts and installing a key as the owner | Sending invitations and changing roles |
The server allows changes again as soon as the account count is within the limit. No restart is needed. If your team still cannot post, check why posting is blocked.