GateKeeper Enterprise
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Untethered Labs, Inc. · gkaccess.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
GateKeeper Enterprise at a glance
- Vendor
- Untethered Labs, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 17 Nov 2026
- Panel verdict
- The AI panel rates GateKeeper Enterprise 1.5/5, the mean of 6 judges. GateKeeper Enterprise is a password management product from Untethered Labs, Inc. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
GateKeeper Enterprise is a password management product from Untethered Labs, Inc. of College Park, Maryland, built around hardware tokens replacing the master password, with a PIN as second factor. Scores peak on identity integration at 4 to 5 and hold at 4 on audit and policy and on deployment and portability: the Hub connects to on-premise or Azure Active Directory, records each login with user, time and duration, keeps logins working offline through cached credentials, and can run on the customer's own Windows Server. Sharing and access control spreads 3 to 4 over how far shared-workstation login stands in for vault-level permissions. Security architecture sits at 2 with no variation — the captured data-encryption page lists only compliance framework names — and pricing transparency sits at 1: no tier price appears and Active Directory integration requires the unpriced Ultimate subscription. Sovereignty splits 1 to 3 on a proven US contracting entity, no public information on data residency, subprocessors or a data processing agreement, and a documented on-premises Hub that higher scores credit.
Speaks for it
- The Hub connects to on-premise or Azure Active Directory over LDAP for bulk user onboarding with token provisioning.
- Admins can disable, unlock and change passwords in Active Directory from the Hub while end users see no difference.
- Each login event is recorded individually with user, time and duration, alongside audit traceability for shared-computer logins.
- Offline login is documented through cached credentials and cryptographic tokens that resync with the directory on reconnect.
- The Hub runs on the customer's own Windows Server 2012+ with SQL Server 2007+.
Held against it
- We found no public information on encryption algorithms, key derivation or independent audits — the data-encryption page lists only compliance framework names.
- No price figure for any tier appears on the captured pages, and Active Directory integration requires the unpriced Ultimate subscription.
- Sharing is documented as shared-workstation login; we found no public information on vault-level permission levels, view-only or time-limited sharing, or emergency access.
- Sovereignty scores range from 1 to 3 over a proven US contracting entity and no public information on data residency, subprocessors or a data processing agreement.
- We found no public information on export of vault data or on macOS and iOS clients.
Best for
- You run shared Windows workstations across shifts and need each login attributed to a named person without users seeing the account's credentials.
- Your team manages users in on-premise or Azure Active Directory and wants central write-back to disable, unlock and rotate passwords.
- You operate where network access is unreliable and need offline login through cached credentials and hardware tokens.
- You want to run the management Hub on your own Windows Server rather than in a vendor cloud.
Avoid if
- You need published per-user pricing before committing — the captured pages carry no tier figures and gate Active Directory integration behind the Ultimate subscription.
- Your security review requires documented vault cryptography, key derivation or independent audit evidence before signing.
- You need governed team sharing with permission levels, view-only or time-limited grants, or emergency access.
- Your procurement requires a non-US contracting entity or proven EU data residency — the vendor is Untethered Labs, Inc. of College Park, Maryland.
The scores
| Criterion | Panel median |
|---|---|
| Encryption model & independent audits | 1 of 5 |
| Sharing, roles & recovery | 1.5 of 5 |
| SSO, directory sync & provisioning | 2.5 of 5 |
| Audit logs, policies & reporting | 2 of 5 |
| Hosting choice, offline access & export | 2 of 5 |
| European sovereignty | 1 of 5 |
| Pricing transparency | 0.5 of 5 |
Encryption model & independent audits
Show reasoningHide reasoning
How this is scored
What the vendor can prove about its security design: end-to-end encryption with named algorithms and key derivation, which fields are encrypted on the device and which are not, independent audits and penetration tests with published results, a bug bounty, and incident history disclosed.
0 — Vault contents are readable by the vendor by its own description: server-side encryption with keys the vendor holds, or no encryption of stored credentials.
3 — Client-side or end-to-end encryption described with the algorithms named; key derivation, audits and the scope of what is encrypted are basic or not described.
5 — A published security whitepaper or security page naming algorithms, key derivation and the client-side encryption model, and an independent audit, penetration test or certification (ISO 27001, SOC 2) named.
8 — A stated list of which fields are and are not encrypted (including URLs and metadata), recurring independent penetration tests or code audits with dates and reports or summaries published, a public bug bounty or vulnerability disclosure policy, past security incidents documented with their impact, and open-source clients or cryptography that can be reviewed.
10 — The design is verifiable end to end: full source or cryptographic design public, every field encrypted client-side including metadata, audits by named firms repeated yearly with full reports, a threat model that states what a compromise of the vendor's servers would expose, and incident post-mortems published.
The CISO
The pages describe a hardware-token unlock with a PIN second factor and continuous proximity authentication, but the vendor's data-encryption page yields only a list of compliance framework names — no algorithms, no key derivation, no statement of which fields are encrypted and which are not. I found no public information on independent audits or penetration tests, a bug bounty, or any disclosed incident history. 2 3 11
The Identity Engineer
The captured pages show a token-centred design — a physical security key replaces the master password with a PIN as second factor, continuous authentication locks the machine when the token leaves, and offline logins verify against locally cached, hashed credentials. We found no public information naming encryption algorithms, key derivation, independent audits or penetration tests, which fields of a stored credential are encrypted, or any bug bounty, so the vault's cryptographic design cannot be assessed from these pages. 2 3 11
The Compliance Auditor
The captured pages describe a hardware-token unlock with continuous authentication and a second PIN factor, but I found no public information naming the encryption algorithms, key derivation, or which fields of stored credentials are encrypted. I found no public information on an independent audit, penetration test or certification for the product itself; the listed frameworks read as regimes the product claims to help customers meet, not attestations about its own security. 2 3 4
The SME Owner
Their model replaces the master password with a hardware token — the key acts as factor one and a typed PIN as factor two, and the computer locks itself when the token walks away — but we found no public information on the encryption of stored credentials, on algorithms or key derivation, or on any independent audit, penetration test or certification. For a company moving off an Excel file I need the vault's cryptography documented, not just the fob. 2
The DevOps Engineer
The pages describe a physical-token unlock with continuous authentication and locally validated offline credentials — cached credentials, local hashed-credential databases, cryptographic tokens — but I found no public information naming the encryption algorithms, the key derivation, which fields are protected, or any independent audit, penetration test, certification or bug bounty. For a product whose whole pitch is holding your credentials, that is thin evidence to build on. 2 3 11
The Skeptic
The token-based unlock replacing the master password and wiki talk of locally hashed credentials and offline cached credentials are described, but we found no public information naming encryption algorithms, key derivation, independent audits, penetration tests, a bug bounty or any incident history — the captured page titled about data encryption lists only compliance frameworks. Admins can change users' passwords without informing them, so credentials are managed centrally, and nothing on these pages states what a compromise of the vendor's servers would expose. 2 3 8 11
Sharing, roles & recovery
Show reasoningHide reasoning
How this is scored
How credentials are shared and governed across a company: shared vaults or collections, role-based permissions, view-only and time-limited access, admin account recovery, emergency access, and what happens to shared items when an employee leaves.
0 — A personal password manager by the vendor's own description: no sharing between users is offered.
3 — Shared folders or vaults between users of one account; permission levels, admin recovery and offboarding are basic or not described.
5 — Shared vaults or collections with permission levels (for example read, edit, manage), groups and admin roles, and an admin account recovery or offboarding that keeps a leaver's shared items with the company.
8 — Recovery and offboarding documented with their key model, granular permissions down to hiding the password while allowing autofill, time-limited and one-time sharing with external parties, emergency access with a waiting period, delegated administration per team or location, and approval workflows for sensitive items.
10 — Access is governed and provable: least-privilege defaults, recovery and emergency access designed so the vendor never holds a key and stated so, periodic access reviews supported in the product, and every grant, change and revocation attributable to a person.
The CISO
What is documented is shared-workstation access — employees can be logged into a shared PC without knowing the account's credentials, with audit traceability per login — plus central admin management, tokens admins can reassign when the first is lost, and the ability to disable and unlock Active Directory accounts from the console. I found no public information on shared vaults with permission levels, view-only or time-limited sharing, emergency access, or the key model behind recovery. 4 5 6 8
The Identity Engineer
Sharing here is built around shared workstations: an authenticated employee is logged into the machine without ever seeing the account's credentials, each login is recorded individually with user, time and duration, and admins can rotate passwords from the Hub without informing users — so a leaver takes nothing with them. We found no public information on vault-level permission levels, view-only or time-limited grants, emergency access, or an admin recovery key model, which is what governed team sharing would need. 4 5 6 8
The Compliance Auditor
The documented model is central admin control over shared logins: users are logged into shared computers without seeing the account's credentials, every login is recorded per user, and admins can rotate passwords or disable accounts from the console. I found no public information on permission levels within shared vaults, admin account recovery, emergency access, or what happens to a leaver's stored items. 4 5 6
The SME Owner
This maps to how my team works: users sign into shared machines without ever knowing the account's credentials, admins can change passwords from the console without informing users while access keeps working, IT assigns a replacement token when one is lost, and every login is recorded per person with admins able to disable accounts. We found no public information on permission levels within shared vaults, on groups, or on emergency access — the documented sharing story is shared-workstation logins, not collections with read and edit rights. 2 4 6 8
The DevOps Engineer
Sharing here means shared workstations: the Shared Login Audit Tool lets several users log into one PC with each event recorded by user, time and duration, and admins can rotate passwords centrally while end users see no difference. What I did not find is any description of vault-level permission levels, view-only or time-limited sharing, admin account recovery, or what happens to a leaver's items. 4 5 6
The Skeptic
What is documented is shared-workstation login: users are logged into shared computers without needing to know the account's credentials, each login is recorded with user, time and duration, and admins can change passwords from the console while end users notice no difference. We found no public information on shared vaults with permission levels, view-only or time-limited sharing, admin recovery, emergency access, or what happens to a leaver's items beyond disabling accounts in Active Directory. 4 6 8
SSO, directory sync & provisioning
Show reasoningHide reasoning
How this is scored
How the vault fits into the company's identity stack: SSO with Entra ID, Okta or Google, and the key model behind an SSO unlock; SCIM or directory sync for joiners and leavers; MFA options including hardware keys; and passkey support for users and the vault itself.
0 — A consumer product by the vendor's own description, with no business administration, SSO or directory connection offered.
3 — Users invited by email or CSV with two-factor authentication; SSO, directory sync and hardware keys are basic or not described.
5 — SSO with named identity providers (Entra ID, Okta, Google), SCIM or directory sync for provisioning and deprovisioning, and MFA including FIDO2 or hardware keys.
8 — The SSO unlock documented with how the vault key is derived or released and designed so the vendor cannot derive it, group sync driving vault permissions, automated suspension on deprovisioning, conditional access or device policies, and passkeys stored and used across platforms.
10 — Identity is integrated without trust shortcuts: the SSO key model published and independently reviewed, deprovisioning that revokes vault access and shared items immediately with a log entry, passwordless vault unlock with passkeys, and support for the customer's own key-management or trusted-device approval.
The CISO
The Hub connects to on-premises and Azure Active Directory for onboarding and bulk-adding users, with write access to disable accounts, unlock accounts and change passwords, and an Okta plugin automates login and second-factor entry; hardware tokens (Bluetooth, NFC, phone app) are the core of the product. I found no public information on single sign-on to unlock the vault itself, SCIM, or how the vault key is derived or released. 2 6 7
The Identity Engineer
The Hub connects to on-premise Active Directory or Azure Active Directory over LDAP, lets admins bulk-add users and provision tokens during onboarding, and an Okta plugin automates the Okta login from stored credentials. What I need runs the other direction: the write integration lets admins disable or unlock Active Directory accounts from the Hub, but we found no public information on SCIM, on automated suspension of vault access when the identity account is disabled, on an SSO unlock key model, or on FIDO2 or passkey support — the tokens described are Bluetooth and NFC proximity keys, and the Active Directory integration requires the Ultimate subscription. 2 6 7
The Compliance Auditor
Onboarding through on-premises Active Directory and Azure Active Directory is documented, including bulk user selection, token provisioning during onboarding, and Hub write-back to disable accounts, unlock accounts and change passwords, with MFA via Bluetooth and NFC hardware tokens plus a PIN. I found no public information on SSO unlock of the vault itself, SCIM provisioning, FIDO2 or passkeys; the Okta piece is an auto-login plugin using stored credentials rather than a single sign-on connection. 6 7
The SME Owner
The Hub connects to on-premise and Azure Active Directory to onboard and bulk-add users, and with write permissions admins can disable, unlock and change passwords in the directory from the console, with Bluetooth or NFC hardware tokens plus a PIN as the two factors. An Okta plugin automates logging into Okta using stored credentials. We found no public information on SCIM, on how the vault key relates to a single sign-on unlock, or on group-driven vault permissions. 2 6 7
The DevOps Engineer
Directory integration is real: the Hub connects to on-premise or Azure Active Directory over LDAP to bulk-onboard users, syncs password changes back to AD, and can disable or unlock AD accounts — though only on the Ultimate subscription. Hardware tokens (Bluetooth, NFC, mobile app) with a PIN cover the MFA side and an Okta plugin auto-fills logins, but the pages never document how the vault key is derived or released on a single-sign-on-style unlock, and no SCIM is mentioned. 2 6 7
The Skeptic
The Hub connects to on-premise or Azure Active Directory down to the LDAP ports, with bulk user onboarding, token provisioning during onboarding, and write-back to disable accounts, unlock accounts and change passwords; hardware tokens (Bluetooth, NFC, mobile app) with a PIN second factor are the MFA story. But this is directory onboarding rather than identity integration into the vault: no SSO unlock, SCIM, FIDO2 or passkeys are described, and the Okta plugin works in the other direction — GateKeeper logging the user into Okta with stored credentials. 2 6 7
Audit logs, policies & reporting
Show reasoningHide reasoning
How this is scored
What an administrator and an auditor can see and enforce: event logs of access and changes, password health and breach reports, enforceable policies (master password, MFA, sharing, export), SIEM integration, and reports an ISO 27001 or NIS2 audit can use.
0 — No administration by the vendor's own description: a personal tool with no admin console, logs or policies.
3 — An admin console with an activity list and a password health or strength report; exportable logs and enforceable policies are basic or not described.
5 — Event logs covering logins, item access, sharing and admin changes, enforceable policies for master password and MFA, and password health and breach-monitoring reports.
8 — Logs exportable or available through an API with native SIEM integration to named targets (Splunk, Microsoft Sentinel, Elastic or syslog), policies for sharing, export and browser-extension behaviour, log retention stated, and compliance reports aligned to ISO 27001, NIS2 or BSI IT-Grundschutz.
10 — Auditability is complete: every view, copy, autofill and permission change logged with user and device, logs tamper-evident and retained for a configurable period, alerting on anomalous access, and an auditor role that can read logs without access to secrets.
The CISO
Documented: a comprehensive login audit trail recording user, time and duration, audit traceability for shared computer logins, business-intelligence reporting, automatic logout on inactivity, and central password changes invisible to end users; compliance pages name CJIS, HIPAA, NIS2 and others. I found no public information on exportable logs or SIEM integration, retention periods, password health or breach-monitoring reports, or certification evidence behind the framework list. 4 7 8 9
The Identity Engineer
Login auditing is the heart of the product: a comprehensive login audit trail, individual login events with user, time and duration, business-intelligence reporting, and Hub training covering audits, reports and alerts, with compliance frameworks from CJIS through NIS2 listed. We found no public information on log export or SIEM integration, retention periods, or password-health and breach reports, so I cannot tell whether the trail would carry an ISO 27001 or NIS2 audit. 3 4 7 9
The Compliance Auditor
Each login event is recorded individually with user, time and duration, there is a shared-login audit tool and a comprehensive login audit trail positioned for HIPAA and GDPR, plus business-intelligence reporting and training lessons on reports, audits and alerts. I found no public information on export of logs to a SIEM, log retention, alerting on anomalous access, or enforceable master-password and export policies. 4 7 9
The SME Owner
The backend provides a comprehensive login audit trail — who was logged in, at what time and for how long — alongside business-intelligence reporting, audit logs, and Hub modules covering reports, audits and alerts, with GDPR and NIS2 named in their compliance list. We found no public information on exportable logs, SIEM integration, retention periods, or password health and breach reports. 4 7 9
The DevOps Engineer
Login auditing is documented with real detail — each login event recorded individually with user, time and duration, plus audit traceability for shared-computer logins — and the Hub training course lists lessons on audits, reports and alerts alongside business-intelligence reporting. But I found no public information on exportable logs or SIEM integration, log retention, or password health and breach reports, and the password-policy page confirms only that admins can change passwords without informing users. 4 7 8 9
The Skeptic
Each login event is recorded individually with user, time and duration, the Hub ships with reports, audits and alerts modules per the training curriculum, and business-intelligence reporting extends to time-and-motion tracking of users' movement during the workday. We found no public information on log export, SIEM integration, retention periods, breach-monitoring reports, or enforceable master-password and MFA policies; the captured password-policy page documents admins changing passwords without informing users. 4 7 8 9
Hosting choice, offline access & export
Show reasoningHide reasoning
How this is scored
Where and how the vault runs and how the data leaves it: cloud region choice, a self-hosted or on-premises option, offline access during a vendor outage, client coverage across operating systems and browsers, and a complete, documented export and import path.
0 — Vault data cannot leave the product: the vendor states that no export is offered.
3 — Apps for common platforms and browsers and an export of vault items (for example CSV); hosting region, offline access and export completeness are basic or not described.
5 — Clients for Windows, macOS, iOS, Android and the major browsers, offline access to the vault, an EU region or self-hosted option, and export and import of vault data including from named competitors.
8 — Both EU cloud and self-hosted or on-premises deployment documented, Linux clients, a status page with incident history, an encrypted full-fidelity export covering all item types including attachments, and vault access continuing during an outage of the vendor's service.
10 — The customer can run and leave the vault on their own terms: self-hosting with documented high availability and backup, an open or documented export format that preserves structure, permissions and history, and a stated procedure for continued access if the vendor ends the service.
The CISO
Offline authentication is genuinely documented — cached credentials, local hashed-credential databases and cryptographic tokens keep login working without a network — and the Hub can run on the customer's own Windows Server with SQL Server alongside a Cloud Hub option. Clients are documented for Windows, a free Android app and Chrome/Firefox extensions only, and I found no public information on export or import of vault data. 7 10 11 5
The Identity Engineer
Offline access is genuinely documented — cached credentials, cryptographic tokens and local hashed databases authenticate users with no connection to a central server, and the Hub runs on the customer's own Windows Server with SQL Server. Client coverage in the captured pages is Windows-centric with a free Android app and Chrome and Firefox extensions, and we found no public information on macOS or iOS clients, cloud region choice, a status page, or any export path for vault data — that last silence is the one that would stop me at this scale. 7 10 11
The Compliance Auditor
Offline authentication is documented in detail — cached credentials, local authentication databases and cryptographic tokens keep access working without a connection to the central server — and the Hub runs on the customer's own Windows Server with SQL Server, which reads as an on-premises deployment path. Client coverage on the captured pages is Windows and Android with Chrome and Firefox; I found no public information on macOS or iOS clients, an EU hosting region, or any documented export of vault data. 7 10 11
The SME Owner
Offline login is documented — credentials are cached after a successful online login and validated locally, re-syncing with the directory on reconnect — with clients for Windows machines, a free Android app, password management in Chrome and Firefox, and the Hub supported on Windows Server 2012+ and SQL Server 2007+, plus a Cloud Hub named in the deployment story. We found no public information on macOS or iOS clients, on where the cloud is hosted, or on any export path for vault data. 7 10 11
The DevOps Engineer
Offline access is genuinely documented — cached credentials and cryptographic tokens authenticate without a server connection and resync on reconnect — and the Hub's stated requirements of Windows Server 2012+ and SQL Server 2007+ suggest you can run the management server on your own iron, which I like. But I found no public information on any export of vault data, no macOS, iOS or Linux clients, and no documented backup or high-availability setup for a self-run Hub, so getting your data out intact is an open question. 7 10 11
The Skeptic
Windows clients (7 through 11 and Embedded), Chrome and Firefox browser password management, and a free Android app are documented, offline access is well covered through cached credentials and local validation, and the Hub's system requirements (Windows Server 2012+, SQL Server 2007+) indicate it runs on the customer's own server. We found no public information on an export or import path for vault data, macOS or iOS clients, Linux, cloud region choice, or a status page with incident history; a Cloud Hub variant is named without a hosting location. 5 7 10 11
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where vault data and metadata are hosted, and who the subprocessors are. Independently sourced by the sovereignty pipeline; end-to-end encryption narrows what a foreign authority could compel, but metadata, logs and the update channel for the client software remain in the vendor's hands, so the chain still counts.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU or self-hosted option stated.
3 — One European element proven: an EU data region, an EU contracting entity or EU representative, a self-hosted option, or a published DPA, with the rest of the chain unstated.
5 — EU hosting as standard or selectable, or a self-hosted option, and an EU contracting entity or EU representative, with a DPA offered; the parent company or parts of the chain (support, analytics, email, client distribution) are unstated or non-EU.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published with locations, a DPA covering vault metadata and logs, and a self-hosted option that removes the vendor from the data path.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, certifications published (ISO 27001, BSI C5 or equivalent), and source code or builds verifiable so the client update channel is not a blind trust in the vendor.
The CISO
The contracting entity is proven US — Untethered Labs, Inc. of College Park, Maryland — and I found no public information on hosting regions, a DPA, subprocessor locations or EU representation; GDPR appears only as a name in a compliance list. The one element outside the US chain is the documented on-premises Hub server option. 3 7 11
The Identity Engineer
The contracting entity is proven American — Untethered Labs, Inc. at 5000 College Avenue, College Park, Maryland — and the Hub's Windows Server requirements indicate an on-premises deployment path. Beyond that we found no public information on where vault data and metadata are hosted, on subprocessors, or on a data processing agreement, and no European element appears in the captured pages. 3 7 11
The Compliance Auditor
The contracting and copyright entity is Untethered Labs, Inc. with a College Park, Maryland address, so the one proven element of the chain is non-EU. GDPR appears only among the compliance frameworks the product claims to support; I found no public information on where vault data and metadata are hosted, the subprocessors, a data processing agreement, or any EU entity or hosting region. 3 11
The SME Owner
The captured pages identify the vendor as Untethered Labs, Inc. with an address in College Park, Maryland, so the contracting company is American, and a Cloud Hub is named with no stated location. Data residency, hosting options, subprocessors and a data-processing agreement are marked unknown on every dimension covered, and GDPR appears only inside a list of compliance frameworks — so beyond the US entity I have nothing proven about the rest of the chain. 3 10 11
The DevOps Engineer
The contracting entity is proven American — Untethered Labs, Inc. of College Park, Maryland — and a Cloud Hub variant is named in the deployment material, but I found no public information on where vault data or metadata are hosted, the subprocessors, a data-processing agreement, or any European element. The only European trace is GDPR appearing in a list of compliance frameworks the product is said to help customers meet. 3 10 11
The Skeptic
The vendor and contracting entity are proven American — Untethered Labs, Inc. of College Park, Maryland — and we found no public information on data residency, subprocessors, or a data processing agreement for the captured pages. The only European-relevant element is that the Hub can run on the customer's own Windows Server alongside on-premise Active Directory, while GDPR and NIS2 appear solely as names on a compliance list. 3 7 8 10 11
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per user and tier, which features (SSO, SCIM, SIEM, self-hosting) sit in which tier, minimum seats, add-ons, and the minimum term.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one priced tier, per user or flat.
5 — Per-user prices public for the business tiers with the billing period stated and the main features per tier listed.
8 — Every tier priced publicly with its feature set and seat minimum, add-on prices listed, self-hosted licensing stated, minimum term and VAT treatment given.
10 — Complete price computability: annual invoice derivable for a given number of users, with every add-on, self-hosting licence, support level and renewal condition published.
The CISO
The captured pages show a 15-day free trial, name an Ultimate subscription as required for Active Directory integration, and offer an online store and a sales phone number — but no per-user or flat price for any tier; the only figure captured, "Price Free", belongs to a training course. 6 7 9 10
The Identity Engineer
The captured pricing facts are structure without numbers: a free trial, a 15-day Enterprise trial, an online store, and the note that Active Directory integration requires the Ultimate subscription. No per-user or per-tier price, seat minimum, billing period or minimum term appears on these pages — the only price figure captured is "Price Free" on a training course — so an annual cost cannot be computed from the public information I read. 1 6 7 9 10
The Compliance Auditor
The captured pages show a 15-day free trial, an online store and a sales phone number, and name an Ultimate subscription as required for the Active Directory integration, but no price figure for any tier appears on them. A buyer cannot compute an annual cost from the pages I read; the only stated price is "Free" for a training course. 1 6 7 10
The SME Owner
Across the captured pages, no subscription price appears — no per-user figure, no tier pricing, just 'Call Sales' alongside a free trial and a 15-day Enterprise trial. The one tier fact is that Active Directory integration 'will need the Ultimate subscription' — the top tier, unpriced — which as a buyer I cannot turn into an annual invoice, and the directory feature being gated to the top tier is exactly the pattern I refuse to budget blind on. 1 6 7
The DevOps Engineer
No price figures appear anywhere I read: a 15-day Enterprise trial is offered, an online store and a sales phone are promoted, and the only tier named is an Ultimate subscription required for Active Directory integration, with no per-user price, seat minimum, billing period or term stated. A buyer cannot compute an annual cost from these pages. 1 6 7 10
The Skeptic
No product price appears on any captured page: there is a free trial (15 days for Enterprise), one captured price of "Free" that belongs to a training course, and a tier name — the Ultimate subscription required for Active Directory integration — with no figure attached. Every purchase path on these pages ends at the sales phone number, so an annual cost cannot be computed from public information. 1 6 7 9
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about GateKeeper Enterprise
Is GateKeeper Enterprise European?
Not determined: the vendor’s pages as captured do not say where GateKeeper Enterprise is based.
Where does GateKeeper Enterprise store data?
Not stated on the vendor’s pages as of 17 Nov 2026.
Does GateKeeper Enterprise have a free plan?
Yes. GateKeeper Enterprise has a free plan, per the vendor’s page captured 17 Nov 2026.
What are the best alternatives to GateKeeper Enterprise?
As of 18 Nov 2026, the panel rates Passbolt (3.5/5), Password Depot (3.5/5) and 1Password (3.5/5) highest among the other 30 Password Management products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Passbolt (EU-Made, Luxembourg). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: GateKeeper Enterprise alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 24 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page gkaccess.com Checked 17 Nov 2026 Details →
- 2 Encryption model & independent audits — found from sitemap gkaccess.com Checked 17 Nov 2026 Details →
- 3 Encryption model & independent audits — found from sitemap gkaccess.com Checked 17 Nov 2026 Details →
- 4 Sharing, roles & recovery — found from sitemap gkaccess.com Checked 17 Nov 2026 Details →
- 5 Sharing, roles & recovery — found from sitemap gkaccess.com Checked 17 Nov 2026 Details →
- 6 SSO, directory sync & provisioning — found from sitemap gkaccess.com Checked 17 Nov 2026 Details →
- 7 SSO, directory sync & provisioning — found from sitemap gkaccess.com Checked 17 Nov 2026 Details →
- 8 Audit logs, policies & reporting — found from sitemap gkaccess.com Checked 17 Nov 2026 Details →
- 9 Audit logs, policies & reporting — found from sitemap gkaccess.com Checked 17 Nov 2026 Details →
- 10 Hosting choice, offline access & export — found from sitemap gkaccess.com Checked 17 Nov 2026 Details →
- 11 Hosting choice, offline access & export — found from sitemap gkaccess.com Checked 17 Nov 2026 Details →