Identity & access management

Application sign-on, identity federation and access controls.

11 listings, including 11 from other publishers. Entries cover the deployment options documented on their individual pages.

Watch this category with RSS · Build a requirements shortlist

Deployment comparison

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
authentikAWSCustomer-operated
Servers / containers
Open Source / Open Core

MIT for the upstream core and client JavaScript; authentik/enterprise code is separately licensed.

Use the official Docker Compose installation for small deployments; configure production secrets, PostgreSQL and application access.Customer manages identity data, database, keys, policies, outposts, backups, network exposure and security upgrades.
Scope and evidence

The reviewed Compose path targets tests and smaller production setups. The default worker configuration can mount the Docker socket; review the documented permissions and outpost architecture. External identity, email and application endpoints remain separate. The 2026.8.6 patch addresses outpost refresh, cleanup, SAML error handling and WebAuthn signature selection when FIPS is enabled. When moving from an older minor release to 2026.8, verify the reverse proxy's address is trusted and that it sends the required forwarding headers before upgrading.

  • authentik AWS CloudFormation installation — The project template provisions a customer VPC, ECS Fargate server and worker services, RDS PostgreSQL, EFS and an application load balancer. Review certificate validation, sizing, retained resources and production access controls; this is not an authentication connector to a separately hosted service.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

FusionAuth Self-HostedAWS, Azure, Google Cloud, DigitalOcean, RenderCustomer-operated
Servers / containers
Commercial Only

FusionAuth Customer License Agreement; Community and paid plans are proprietary, with feature and support limits by plan.

Vendor Kubernetes/Helm guides, DigitalOcean Kubernetes 1-Click package, or Render application/PostgreSQL blueprint; versions and production topology differCustomer configures application releases, plan features, database/search, networking, TLS, secrets, backups and capacity. Kubernetes operations apply to cluster deployments; Render operates its platform while the customer configures the web service and managed database.
Scope and evidence

This is self-hosted FusionAuth, not FusionAuth Cloud. The AWS Marketplace guide sells hosted Cloud service; EKS remains a separately documented customer-hosted path. DigitalOcean’s 1-Click package is 1.53.3, distinct from upstream 1.71.0. SCIM and paid air-gap/FIPS options have Enterprise conditions; Render uses a customer-owned application/database blueprint.

  • FusionAuth on Amazon EKS — FusionAuth documents provisioning the cluster, database and full application in customer AWS infrastructure.

    Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • FusionAuth on Azure AKS — FusionAuth documents the full application on a customer AKS cluster and Azure database resources.

    Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • FusionAuth on Google GKE — FusionAuth documents the full application on customer GKE and Google Cloud database resources.

    Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • FusionAuth in customer DigitalOcean Kubernetes — The vendor and provider document a full FusionAuth 1-Click Kubernetes application. The provider catalog packages 1.53.3, older than the reviewed upstream release; validate upgrades and production database/HA design.

    Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • FusionAuth and PostgreSQL in customer Render — FusionAuth provides a Render blueprint deploying the full application and PostgreSQL in the customer’s account/project. Production needs paid resource capacity and a deliberate database/backup design.

    Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-18

HashiCorp Boundary EnterpriseAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial Boundary Enterprise license required; HCP Boundary is a separate hosted service.

HashiCorp Validated Design Terraform architectures plus supported apt, yum or binary packagesCustomer manages controllers, workers, PostgreSQL, KMS, PKI, networking, identity integrations, backups, upgrades and availability.
Scope and evidence

This entry covers self-managed Boundary Enterprise, not HCP Boundary. Production deployment requires multiple controllers and workers, an external PostgreSQL database, KMS or HSM-backed key management, TLS and a deliberate worker topology. Validate provider modules, identity integrations and recovery procedures before rollout. HCSEC-2026-54 covers CVE-2026-13303, a Vault credential-store SSRF issue. Fixed Enterprise builds are 1.0.2 and 0.21.6; upgrade the installed maintained branch and restrict credential-store network reachability.

  • Boundary Enterprise validated self-managed deployment on AWS, Azure and Google Cloud — HashiCorp documents self-managed Boundary Enterprise architectures and Terraform deployments in customer AWS, Azure and Google Cloud environments. Customers operate controllers, workers, PostgreSQL and key management.

    Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-17

Infisical Self-HostedAWS, Google Cloud, VultrCustomer-operated
Servers / containers
Open Source / Open Core

MIT core outside enterprise directories; enterprise features and third-party components have separate terms.

Official AWS ECS/Fargate and Google GKE deployment guides, or a Vultr Docker Compose guide; configure PostgreSQL, Redis, TLS and encryption keys.Customer owns the AWS account, Google project or Vultr instance and manages application identity, encryption keys, database recovery and upgrades. Providers operate selected managed infrastructure services.
Scope and evidence

Review used upstream 0.167.10. Vendor AWS/GCP examples contain older version placeholders; pin a current compatible image/chart and use the complete installation steps, not the abbreviated infrastructure snippets alone. Preserve encryption keys independently of database backups. Configure telemetry, mail and external secret/infrastructure connections for the intended boundary. Infisical Cloud and agent-only integrations are separate. Infisical v0.167.13 tightens delegated OAuth-token authorization: scope-narrowed tokens no longer pass role-only administration checks, approval/rejection/bypass operations are denied, and workspace listing checks organization permission. Previously accepted delegated-token calls may return 403; retest automation with least-privilege scopes.

  • Vendor ECS/Fargate installation in the customer AWS account — Includes application task definition and service creation, RDS PostgreSQL, ElastiCache, load balancing, IAM/secrets and upgrade steps. The optional Terraform/CloudFormation summaries are incomplete examples. Use current pinned application versions and review networking, database transport and credentials.

    Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Vendor GKE installation in the customer Google Cloud project — Provisions GKE, Cloud SQL and Memorystore and installs the application Helm release in the operator project. Review supported chart/image versions, VPC access, TLS, key backup and database migrations. This is an application deployment, distinct from connecting Infisical to Google secrets APIs.

    Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Vultr application deployment with Docker Compose — Provider instructions install the application, PostgreSQL, Redis and TLS proxy on an operator-controlled Ubuntu server. Customer manages OS, application updates and data/key recovery; generic cloud integrations are not additional hosting evidence.

    Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-13

Keycloak Self-HostedAWS, AzureCustomer-operated
Servers / containers
Open Source / Open Core

Open-source project; commercial support/distribution arrangements are separate

Official server/container distribution or Kubernetes Operator; configure production database and TLS.Customer manages identity-server availability, configuration, updates, database and backups.
Scope and evidence

The official guides cover physical/virtual servers, containers and Kubernetes. Development defaults are separate from the production configuration. Connections to external identity providers are customer-configured; hosting the server does not eliminate those dependencies. Keycloak 26.8.2 is a security release addressing authentication, token issuance and revocation, authorization, account takeover, admin API, stored XSS, denial-of-service, and bundled Brotli issues. Review the migration guide and upgrade to 26.8.2 or later.

  • Keycloak supported configurations — The project names Amazon EKS and Azure Kubernetes Service as non-OpenShift Kubernetes deployments supported on a best-effort basis. Distribution-specific issues may fall outside that support; check the documented Kubernetes API versions.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

NetBird Self-Hosted Community EditionAWS, Azure, Google Cloud, DigitalOcean, Hetzner, Oracle CloudCustomer-operated
Servers / containers
Open Source / Open Core

Mixed open-source terms: BSD-3-Clause generally and AGPL-3.0 for server control-plane directories; Enterprise features require a commercial license.

Official self-hosting script and Docker Compose on a Linux VM; advanced deployment supports a custom identity providerCustomer manages the VM, domain, TLS, firewall ports, identity configuration, control-plane state, relay capacity, backups, upgrades and availability.
Scope and evidence

This entry covers the Community self-hosted edition, not NetBird Cloud or the Enterprise Commercial License. The quickstart is single-node; high availability and commercial SCIM or traffic-flow features are outside this edition. The cited advanced guide also establishes DigitalOcean, Hetzner and OCI paths. Its multi-container configuration differs from the combined-server quickstart; preserve version and migration boundaries. The pinned quickstart script still uses latest for several images, which must be locked separately.

  • NetBird self-hosted control plane on a cloud VM — The advanced self-hosting guide explicitly names AWS, DigitalOcean, Hetzner, Google Cloud and Azure VMs, uses Hetzner for its worked installation and documents OCI guest-firewall requirements for UDP 3478. It describes the older multi-container layout; the current quickstart uses the combined netbird-server layout. Select compatible files and configure provider and guest firewalls for the chosen architecture.

    Vendor / upstream documentation · Reviewed 2026-11-19 · Scope: Community Edition. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-19

OpenBaoLinodeCustomer-operated
Servers / containers
Open Source / Open Core

MPL-2.0 core; dependencies and external plugins retain their licenses.

Official binaries/containers or Helm chart; Akamai documents the full server on Linode Kubernetes Engine.Customer manages initialization, unseal/recovery keys, policy, TLS, durable storage, snapshots, audit logs and upgrades. Akamai operates LKE infrastructure; the customer operates the OpenBao service.
Scope and evidence

Default standalone/file storage and development examples are not production HA configurations; follow the production checklist, configure TLS and test recovery. Cloud authentication and KMS unseal integrations do not imply additional hosting providers. OpenBao v2.7.3 corrects auth-alias handling and enforcement of listener settings when HA standbys forward requests to the active node. Newly created auth mounts use case-sensitive aliases by default. Review alias behavior and listener configuration when upgrading, and pin compatible server and chart versions. Inspect case_sensitive_alias on existing mounts rather than assuming the new default reconfigures them. HA review includes forwarded client certificates, unauthenticated rekey/root endpoint restrictions and request-size/duration limits.

  • Akamai full OpenBao server deployment on LKE — The provider guide creates an LKE cluster and installs, initializes and unseals the OpenBao server, then covers persistence, HA, TLS and access restrictions. It includes older illustrative chart output and standalone defaults; use supported pinned releases and production storage/TLS configuration, not development defaults.

    Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-13

OpenVPN Access ServerAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial subscription, fixed and cloud-marketplace licenses; unlicensed mode is limited to two connections.

Official cloud marketplace image or AWS CloudFormation stack, or package or container on a supported Linux VMCustomer manages compute, routing, network exposure, identity integration, certificates, upgrades, backups and availability.
Scope and evidence

This entry covers OpenVPN Access Server, not CloudConnexa or OpenVPN Community Edition. Bring-your-own-license, pay-as-you-go and fixed marketplace entitlements differ by provider.

  • Access Server AWS customer-account deployment — Official documentation covers CloudFormation resources in the signed-in AWS account, Linux or Docker on customer AWS infrastructure, and Marketplace bring-your-own-license or pay-as-you-go options.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Access Server Azure Marketplace VM — The official bring-your-own-license guide creates the Access Server VM, network interface, public IP and network security group in the selected Azure subscription and resource group.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Access Server Google Cloud Marketplace deployment — The official guide deploys the self-hosted Access Server instance into the customer's selected Google Cloud project and VPC.

    Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-19

Teleport Enterprise Self-HostedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial Teleport Enterprise Self-Hosted subscription and license file required.

Teleport Helm charts on EKS, AKS or GKE; official Terraform deployment paths are also documentedCustomer manages Kubernetes or VMs, backend state, storage, DNS, TLS, upgrades, capacity, backups and the Enterprise license.
Scope and evidence

This entry covers Enterprise Self-Hosted, not Teleport Enterprise Cloud. Community licensing and feature availability differ; confirm the purchased edition and current upgrade compatibility.

  • Teleport Enterprise on AWS EKS — Teleport documents a full HA Auth and Proxy deployment on customer EKS with AWS backing services.

    Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Teleport Enterprise on Azure AKS — Teleport documents a full HA deployment on customer AKS.

    Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Teleport Enterprise on Google GKE — Teleport documents a full HA deployment on customer GKE.

    Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-18

Vault Enterprise Self-ManagedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial Vault Enterprise license required.

Official HashiCorp Validated Design Terraform modules for AWS EC2, Azure VMs or Google GCECustomer manages VPC or VNet infrastructure, VMs, load balancers, storage, cloud KMS or Key Vault, TLS, initialization and unseal controls, audit logs, backups, replication, upgrades and licensing.
Scope and evidence

This entry covers Vault Enterprise self-managed, not HCP Vault Dedicated or the separately licensed Community edition. Protect recovery and root credentials, design unseal and disaster-recovery procedures, and review the Terraform modules' requested permissions before deployment.

  • Vault Enterprise inside a customer cloud account — HashiCorp provides official validated-design modules for AWS EC2, Azure VMs and Google GCE and states that the modules deploy a complete Vault Enterprise environment inside the customer's own cloud account.

    Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-15

ZITADEL Self-HostedRailwayCustomer-operated
Servers / containers
Open Source / Open Core

GNU Affero General Public License version 3 for the reviewed upstream code; commercial products and agreements are separate.

Deploy the official Docker Compose stack with ZITADEL API, login application, reverse proxy and PostgreSQL, then apply the documented hardening configuration.Customer manages identity storage, cryptographic keys, proxy/TLS, backups, email/SMS providers and updates.
Scope and evidence

The Compose guide is a starting point for a homelab or semi-production installation. The current contribution guide states that engineering focus on next-generation work limits community PR review capacity for this codebase; evaluate the supported release roadmap. External identity and message providers remain separate. ZITADEL v4.20.4 enables PKCE by default for Google, GitHub, GitLab, and Azure AD identity providers and hardens SMS OTP and password history. Revalidate external IdP callbacks and authentication policy after upgrading. ZITADEL v4.20.5 fixes a Login V2 MFA bypass in which a first-factor-only session could add a new authenticator even when a second factor was already configured. Upgrade and verify authenticator-enrolment policy.

  • ZITADEL community deployment template on Railway — The community template uses official ZITADEL server and login images with PostgreSQL in a customer Railway project. Review server/login version alignment, initial administrator credentials and the production checklist; Login V2 requires additional service-user configuration. This is separate from ZITADEL Cloud.

    Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Choose 2–4 listings to compare

Browse listing cards

How these listings fit

authentik
Self-hosted identity provider for application authentication, federation and policy-controlled access; enterprise-only capabilities require the corresponding license.
FusionAuth Self-Hosted
Provides customer-operated authentication, authorization, user management and federation for applications.
HashiCorp Boundary Enterprise
Provides identity-aware, policy-controlled access to infrastructure targets without exposing long-lived network credentials.
Infisical Self-Hosted
Centralizes application secrets and related access/configuration workflows. Certificate, privileged-access and enterprise features depend on the licensed edition and selected components.
Keycloak Self-Hosted
Identity and access management with SSO, identity brokering, federation and OpenID Connect/OAuth 2.0/SAML support.
NetBird Self-Hosted Community Edition
Provides self-hosted identity-aware zero-trust network access with users, policies, device peers, routes and private-resource controls.
OpenBao
Manages secrets, keys, certificates and policy-controlled access through a customer-operated service. Agent-only and external-server modes do not by themselves install that service.
OpenVPN Access Server
Provides a self-hosted business VPN and policy-controlled remote or site-to-site network access server.
Teleport Enterprise Self-Hosted
Provides identity-aware access to servers, Kubernetes, databases and applications through customer-operated authentication and proxy services.
Vault Enterprise Self-Managed
Provides centrally governed secrets, encryption, authentication methods, dynamic credentials and identity-based access policies.
ZITADEL Self-Hosted
Application identity and access management with user/organization administration and configured authentication flows.

Review dates and sources appear on each listing. Functionality, edition, deployment and licensing must be checked together. Filter this category with cloud and deployment controls →

All categories · Suggest a listing or correction