The format
Glopzi license keys follow this pattern:
GLPZ-XXXXX-XXXXX-XXXXX-XXXXX
- Always starts with
GLPZ-. - Four groups of five characters, separated by hyphens.
- Total length: 24 characters plus four hyphens.
- Uppercase letters and digits, no special characters, no lowercase.
The format is designed to be readable, dictatable over a phone, and resistant to character-confusion mistakes (we avoid 0/O and 1/I).
Where to find your key
After purchase, your key arrives by email immediately. If you missed the email, sign in to the dashboard and look in the Licensestab. Each plan you’ve purchased shows up there with its key, status, and bound domains.
For the WordPress plugin, paste the key into the activation field at WordPress Admin → Glopzi Studio. For custom sites, the dashboard handles the binding automatically; you don’t paste the key anywhere.
What activation does
The first time a Glopzi runtime makes a request to our servers using your key, three things happen atomically:
- The site’s domain is bound to your license. From now on, that domain counts against your plan’s site limit.
- A unique site secret is generatedand stored encrypted on your server (WordPress) or tied to your dashboard record (custom sites). It’s used to sign requests so nobody can spoof your site.
- You’re free to start saving animations. The first save publishes to our CDN and your visitors see the result.
Note
Auto-binding on first use is convenient but it means typos count. If you accidentally activate the key on staging.example.com instead of example.com, that takes a seat. You can remove it from the dashboard’s domains panel; see Adding and managing domains.
Multiple sites on one key
Pro and Agency plans allow multiple sites under one key. To activate a second (or twentieth) site:
- On WordPress, paste the same key into the new site’s plugin. Glopzi recognizes the key, checks the site count is under your limit, and adds the new domain to your bound list.
- On custom sites, add the new domain from the dashboard before installing the snippet. Or let auto-bind handle it on first runtime request.
Plan site limits are visible in the dashboard. If you exceed your limit, additional activations are rejected with a clear message about which plan to upgrade to.
Regenerating a compromised key
If you’ve accidentally exposed your key (in a screenshot, in a public repo, in a screenshare), you can regenerate it from the dashboard. The old key stops working immediately; you’ll need to paste the new key into every site’s WordPress plugin.
Custom site keys are stored on our side, not yours, so they don’t need re-entry. If your custom site key is compromised, contact us and we’ll rotate it on our end.
Heads-up
License keys aren’t a substitute for proper secrets management. They’re a usage license, not a credential. Don’t commit them to public repos, but don’t panic if one slips: just regenerate.
Next steps
- Adding and managing domains: the domain side of activation.
- Plans, billing, and trial: tier limits and how upgrades work.
- WordPress integration: where the key goes on a WordPress site.