Licensing
Editions, license keys for self-hosted installs, and what happens when a license runs out.
Gatehouse runs without a license as the Free edition, for up to 5 people. Paid plans unlock more people and features. On the hosted service your plan is managed for you. Self-hosted installs use a license key.
| Edition | People | Includes |
|---|---|---|
| Free | 5 | Gateway, policies, approvals, Slack approvals |
| Team | Licensed seats | Google and GitHub sign-in, access requests from chat |
| Business | Licensed seats | SSO (OIDC and SAML), SCIM, Active Directory, audit streaming, MFA enforcement, IP allow-list |
| Enterprise | Unlimited | Everything, plus priority support and an SLA |
Adding a license key
An owner pastes the key in Settings → General → License and clicks Apply. Or set it when you deploy:
GATEHOUSE_LICENSE=<key>, orGATEHOUSE_LICENSE_FILE=/run/secrets/gatehouse_license
A key saved in Settings takes precedence over the environment.
Keys are verified offline with a public key built into Gatehouse, so licensing works on air-gapped installs and never calls home. A key can't be edited: changing anything in it, such as the seat count, makes it invalid.
When a license runs out, or you're over your seats
Nothing stops working. Owners and admins see a notice in the console:
- Over seats: active people count toward seats; disabled people don't. Add seats or disable people who've left.
- Expiring: a reminder starts 30 days before the expiry date.
- Expired: the edition keeps working for a 30-day grace period, then shows as Free.
Agents, policies and the audit log are never interrupted by licensing.
To buy or renew, email sales@usegatehouse.com.