Ironhelm Suite

API keys and sites

One key per site. How keys bind to sites, which development copies share a key, how to move or remove a key, and what happens when a site has no working key.

Every site that runs Ironhelm Suite connects with its own API key. Your plan sets how many keys can exist at once: Solo 1, Studio 10, Agency 50. You manage keys under Sites and API keys in your account.

How a key binds to a site

A new key is free until the first site connects with it. From then on it belongs to that site's address. The same key used on a different live site is refused with a message naming the site it belongs to.

Development copies share the key

The key also works, without using another slot, on development copies of its site:

  • localhost, 127.0.0.1 and private network addresses
  • addresses ending in .local, .test, .localhost, .ddev.site or .lndo.site
  • staging., stage., dev., test., uat. and qa. subdomains of the site, for example staging.example.com for example.com

So you can build on your laptop or a staging server and go live with the same key.

Moving a site

  • Same address, new server: nothing to do. The key follows the address.
  • New address: in Ironhelm on the old site, open Settings, API key and updates and choose Disconnect this site. Then connect the key on the new site.
  • Old site already gone: remove the key in your account and create a new one.

Removing a key

Choose Remove next to the key in your account. Within seconds our server asks the site to check in, and Ironhelm on that site pauses its features. A removed key can never be used again; its slot is free for a new key at once.

If the site cannot be reached (a private address, a strict firewall), it pauses at its next scheduled check, at most twelve hours later.

When a site has no working key

SituationWhat runs
Never connected, or disconnected on purposeOnly the Ironhelm screens, so you can connect a key
Key removed, subscription ended, key belongs to another site, or our server unreachable for 30 daysThe security protections that were on keep running with their current settings: firewall, login protection, two-step login, passkeys, hardening, security headers, spam shield, safe SVG. Everything else pauses.

Pausing never deletes settings or data. Connect a working key and everything resumes exactly as it was. While paused, settings cannot be changed; the API key screen always works.

At the plan's limit

When every key is in use, your account offers the next plan up. Remove a key you no longer need, or upgrade: you pay only the difference for the time left, and new keys are available at once.

Multisite

A multisite network uses one key for the whole network, connected from the network's main site.