What domain binding does
A license can have one or more bound domains. The runtime checks the visiting page’s domain against the bound list before fetching your compiled bundle.
- Domain in the bound list: animations run normally.
- Domain not in the bound list: runtime refuses to load the bundle. The page is unaffected (no animations, but also no errors).
The point: someone copying your script tag to their site can’t piggyback on your subscription. The runtime simply won’t respond.
Auto-binding on first use
The first time a runtime request comes from a domain your license hasn’t seen, Glopzi auto-binds the domain (if you’re under your plan’s site limit). No manual action required for the common case.
Auto-bind is the right default because most users add Glopzi to a site, save animations, and want it to just work. Manual binding before installation would add a step that almost everyone does anyway, but later than they should.
Note
If you’re at your plan’s site limit, auto-bind fails with a clear error. The runtime tells the dashboard which domain was rejected so you can decide whether to remove an old binding or upgrade your plan.
Adding a domain manually
For staging environments, custom subdomains, or domains you want to register before installing, add them from the dashboard:
- Sign in to the dashboard.
- Open the Sites tab on your license.
- Click Add domain and enter the hostname (with or without
www; apex and www are treated as one). - Save.
The new domain counts against your plan’s limit immediately, even if you haven’t installed Glopzi on it yet.
Removing a domain
When you stop using Glopzi on a site, remove the domain to free up the seat:
- Open the Sites tab.
- Click the trash icon next to the domain you want to remove.
- Type the domain to confirm. This is intentional: removing a bound domain immediately stops Glopzi from running on that site.
Heads-up
Removing a domain doesn’t delete the animations you saved for it. They’re still on our servers. Re-adding the domain restores them. But while removed, your visitors see no Glopzi animations on that site.
Apex vs www, http vs https
Glopzi normalizes domain names so common variations all count as one binding:
- Apex and www: binding
example.comalso coverswww.example.com, and vice versa. - HTTP and HTTPS: ignored. Same binding regardless of protocol.
- Trailing slashes: ignored.
- Different subdomains are different domains.
example.comandshop.example.comcount as two bindings. - Ports are ignored (
example.comcoversexample.com:8443). Useful for staging environments.
Next steps
- License keys: the key side of activation.
- Plans, billing, and trial: how site limits map to plans.
- Integrations: install on each domain you add.