
# Identity & access management on AWS

Compare documented Identity & access management deployments on AWS, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/aws/identity-access-management/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: AWS account
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.aws.amazon.com/accounts/latest/reference/getting-started.html (checked 2026-11-20).
- Network: VPC
- Identity and access: IAM roles and policies
- Installation guidance: CloudFormation or Terraform; review stack changes and requested IAM permissions.
- Guidance source: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html
- Guidance reviewed: 2026-11-10


### Private offers

AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge.
Source: https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-private-offers-subscribing.html (reviewed 2026-11-14).

### Private connectivity

PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service.
Source: https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html (reviewed 2026-11-14).

### Cross-account operations

Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access.
Source: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html (reviewed 2026-11-14).

### Government environments

AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there.
Source: https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/whatis.html (reviewed 2026-11-14).

The listings below have evidence for Amazon Web Services. Read each cloud evidence note for the applicable package, edition and support qualifications.

9 listings.


## authentik

Identity provider for centralized authentication and access policies across connected applications.

- Listing: https://launchinyourcloud.com/directory/authentik/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the upstream core and client JavaScript; authentik/enterprise code is separately licensed.
- Licensing model: open-source
- Installation: Use the official Docker Compose installation for small deployments; configure production secrets, PostgreSQL and application access.
- Architecture: Customer-operated identity application, workers and PostgreSQL storage
- Operations: Customer manages identity data, database, keys, policies, outposts, backups, network exposure and security upgrades.
- Product website: https://goauthentik.io/
- Source review: 2026-11-20; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

MIT for the upstream core and client JavaScript; authentik/enterprise code is separately licensed. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated identity application, workers and PostgreSQL storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- identity-access-management: Self-hosted identity provider for application authentication, federation and policy-controlled access; enterprise-only capabilities require the corresponding license.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.goauthentik.io/install-config/install/aws (checked 2026-11-12). 


### Cloud deployment evidence

- authentik AWS CloudFormation installation (aws): https://docs.goauthentik.io/install-config/install/aws
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The upstream release stream shows active 2026 releases and named contributor participation; public project development and a separate enterprise directory distinguish its editions.

Reviewed 2026-11-10.

- 2026 maintenance and contributors: https://github.com/goauthentik/authentik/releases

- Public project and edition structure: https://github.com/goauthentik/authentik

### Sources

- Official installation and runtime: https://docs.goauthentik.io/install-config/install/docker-compose/

- Upstream project and capabilities: https://github.com/goauthentik/authentik

- Current upstream license: https://raw.githubusercontent.com/goauthentik/authentik/main/LICENSE

- authentik 2026.8.6 patch release: https://github.com/goauthentik/authentik/releases/tag/version/2026.8.6

- authentik 2026.8 upgrade notes and 2026.8.6 fixes: https://docs.goauthentik.io/releases/2026.8/#fixed-in-202686

### Licensing sources

- https://raw.githubusercontent.com/goauthentik/authentik/main/LICENSE

### Infrastructure sources

- https://docs.goauthentik.io/install-config/install/docker-compose/


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. authentik can act as an OIDC identity provider for applications and as a relying party through OAuth/OIDC sources. Each application/provider association and its claims/scopes must be configured. Scope: Identity-platform protocol roles; not automatic SSO for every application. Source: https://docs.goauthentik.io/add-secure-apps/providers/oauth2/ (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. The SCIM 2.0 provider pushes users/groups from authentik into target applications, whose endpoints must be reachable. Static-token and OAuth modes differ; OAuth-based SCIM authentication is an Enterprise feature. Scope: Outbound application provisioning, not automatic inbound directory provisioning; OAuth mode edition-dependent. Source: https://docs.goauthentik.io/add-secure-apps/providers/scim/ (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Compose recipe is intended for testing and small production deployments. Generate PostgreSQL/application secrets and configure the hostname and supporting services before use. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.goauthentik.io/install-config/install/docker-compose/ (reviewed 2026-11-14). Deployment artifact: https://docs.goauthentik.io/compose.yml. Artifact reference: current published Compose file (moving).

- Minimum footprint / sizing: Documented. The Compose guide requires at least 2 CPU cores and 2 GB RAM for testing or small production deployments. Larger deployments and external PostgreSQL need their own capacity plan. Scope: Small-scale Compose installation baseline. Source: https://docs.goauthentik.io/install-config/install/docker-compose/ (reviewed 2026-11-14).

- License pricing: Documented. The published 2026.8.6 licence grants MIT terms to the core while Enterprise code and documentation have separate licences. Self-hosted Enterprise features require a licence key and use the same container images; support/purchase terms depend on the Enterprise plan. Core source rights do not grant paid feature entitlements. Scope: Published upstream core/Enterprise boundary; infrastructure and commercial plan charges are separate. Source: https://github.com/goauthentik/authentik/blob/version/2026.8.6/LICENSE (reviewed 2026-11-20). Supporting source: Self-hosted Enterprise licensing and plans — https://docs.goauthentik.io/enterprise/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed authentik release version/2026.8.6 covers outpost refresh, cleanup, SAML error reporting and WebAuthn signature selection in FIPS mode. The 2026.8 trusted-proxy configuration change is a separate minor-upgrade requirement. Scope: Upstream self-hosted authentik 2026.8 branch; Enterprise features and Helm chart versions have separate scope. Source: https://github.com/goauthentik/authentik/releases/tag/version/2026.8.6 (reviewed 2026-11-20). Supporting source: 2026.8 upgrade requirements and 2026.8.6 fixes — https://docs.goauthentik.io/releases/2026.8/#fixed-in-202686.







## FusionAuth Self-Hosted

Proprietary identity platform with documented customer-account EKS, AKS, GKE, DigitalOcean and Render application/database deployments.

- Listing: https://launchinyourcloud.com/directory/fusionauth-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: FusionAuth Customer License Agreement; Community and paid plans are proprietary, with feature and support limits by plan.
- Licensing model: commercial-only
- Installation: Vendor Kubernetes/Helm guides, DigitalOcean Kubernetes 1-Click package, or Render application/PostgreSQL blueprint; versions and production topology differ
- Architecture: FusionAuth application instances with a customer database and optional search, deployed on cloud Kubernetes or as a customer Render web service and PostgreSQL database.
- Operations: Customer 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.
- Product website: https://fusionauth.io/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

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 is proprietary under its Customer License Agreement, including the no-cost Community plan; paid plan capabilities require corresponding entitlements.

FusionAuth uses provisioned application capacity and persistent database state. Kubernetes and Render have different platform-operation boundaries; the customer selects and configures the application and database deployment.


### Category fit

- identity-access-management: Provides customer-operated authentication, authorization, user management and federation for applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fusionauth.io/docs/deploy/production/kubernetes/eks (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fusionauth.io/docs/deploy/production/kubernetes/aks (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fusionauth.io/docs/deploy/production/kubernetes/gke (checked 2026-11-18). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fusionauth.io/docs/deploy/production/marketplaces/digitalocean (checked 2026-11-18). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://fusionauth.io/docs/deploy/production/marketplaces/render (checked 2026-11-18). 


### Cloud deployment evidence

- FusionAuth on Amazon EKS (aws): https://fusionauth.io/docs/deploy/production/kubernetes/eks
  FusionAuth documents provisioning the cluster, database and full application in customer AWS infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- FusionAuth on Azure AKS (azure): https://fusionauth.io/docs/deploy/production/kubernetes/aks
  FusionAuth documents the full application on a customer AKS cluster and Azure database resources.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- FusionAuth on Google GKE (gcp): https://fusionauth.io/docs/deploy/production/kubernetes/gke
  FusionAuth documents the full application on customer GKE and Google Cloud database resources.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- FusionAuth in customer DigitalOcean Kubernetes (digitalocean): https://fusionauth.io/docs/deploy/production/marketplaces/digitalocean
  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.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- FusionAuth and PostgreSQL in customer Render (render): https://fusionauth.io/docs/deploy/production/marketplaces/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.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Sources

- FusionAuth on Kubernetes: https://fusionauth.io/docs/deploy/production/kubernetes/

- FusionAuth on Amazon EKS: https://fusionauth.io/docs/deploy/production/kubernetes/eks

- FusionAuth on Azure AKS: https://fusionauth.io/docs/deploy/production/kubernetes/aks

- FusionAuth on Google GKE: https://fusionauth.io/docs/deploy/production/kubernetes/gke

- FusionAuth license: https://fusionauth.io/license

- FusionAuth in customer DigitalOcean Kubernetes: https://fusionauth.io/docs/deploy/production/marketplaces/digitalocean

- FusionAuth and PostgreSQL in customer Render: https://fusionauth.io/docs/deploy/production/marketplaces/render

### Licensing sources

- https://fusionauth.io/license

- https://fusionauth.io/docs/concepts/plans-and-limits/plans-features

### Infrastructure sources

- https://fusionauth.io/docs/deploy/production/kubernetes/


### Buyer diligence


Research coverage: 12/12 fields (100%); 9 documented, 3 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Edition-dependent. DigitalOcean documents a FusionAuth Kubernetes 1-Click application, currently packaged as 1.53.3. That older package must not be presented as upstream 1.71.0. FusionAuth’s AWS Marketplace guide instead describes FusionAuth Cloud hosting; it is not the self-hosted EKS product. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://docs.digitalocean.com/products/marketplace/catalog/fusionauth/ (reviewed 2026-11-18). Supporting source: AWS offer is hosted FusionAuth Cloud — https://fusionauth.io/docs/deploy/production/marketplaces/aws. Supporting source: Vendor DigitalOcean package guide — https://fusionauth.io/docs/deploy/production/marketplaces/digitalocean. Offer fusionauth: FusionAuth; Kubernetes 1-Click application; package 1.53.3; https://marketplace.digitalocean.com/apps/fusionauth.

- Cloud commitment eligibility: Sources checked — unresolved. The vendor’s AWS Marketplace subscription is FusionAuth Cloud. Its procurement terms do not establish commitment credit for a self-hosted licence. Confirm the selected self-hosted Enterprise order and buyer agreement separately. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/deploy/production/marketplaces/aws (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. Self-hosted FusionAuth provides SSO between applications through its own login/session system and OIDC/SAML integration. Distinguish FusionAuth acting as the application identity provider from connecting an external IdP, and confirm the selected plan’s optional features. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/authentication/sessions/single-sign-on (reviewed 2026-11-18).

- SCIM provisioning: Edition-dependent. SCIM 2.0 is an Enterprise-plan feature available from 1.36.0. FusionAuth acts as an inbound SCIM server for users/groups, with OAuth client credentials and configurable mappings. It is not a SCIM client provisioning other services; application registration remains separate. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/users/provision/scim (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. FusionAuth’s August 2025 announcement identifies AssurancePoint as its ISO 27001:2022 auditor. The current certificate/SOA and SOC 2 report remain request-gated, so their validity and self-hosted system boundary were not independently checked here. Its licence FAQ limits report access and requires Enterprise plus HA hosting for a BAA. Assess the actual report/customer controls; FIPS mode is explicitly not FIPS certification. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://trust.fusionauth.io/?format=html (reviewed 2026-11-18). Supporting source: Licence and assurance FAQ — https://fusionauth.io/license-faq. Supporting source: FIPS mode versus certification — https://fusionauth.io/docs/security/compliance/. Supporting source: Named auditor and original announcement — https://fusionauth.io/blog/fusionauth-iso27001-2025.

- Security controls: Documented. Enterprise self-hosted FIPS mode is available from 1.62.0 only for new installations and requires every node in the cluster to use that mode, with separately compliant database/search components. This is a scoped configuration feature, not FIPS certification. SSO, token and provisioning controls require explicit configuration. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/security/compliance/ (reviewed 2026-11-18). Supporting source: SCIM access control — https://fusionauth.io/docs/users/provision/scim. Supporting source: Application SSO/session behavior — https://fusionauth.io/docs/authentication/sessions/single-sign-on.

- Air-gapped operation: Edition-dependent. Enterprise documents an air-gapped licence, offline key activation and an expiry without a grace period; network-backed features and update feeds need separate handling. The requirements also state Community can block outbound access without a paid licence. Choose the plan and disable or supply reachable dependencies explicitly. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/deploy/production/install/air-gapping (reviewed 2026-11-18). Supporting source: Community versus paid-plan network requirements — https://fusionauth.io/docs/deploy/production/system-requirements.

- Deployment artifact / IaC: Documented. The vendor’s Render blueprint deploys FusionAuth and PostgreSQL into the customer’s Render account. The repository is a moving source, not an immutable image lockfile; fork/review it and select production capacity. EKS/AKS/GKE have separate production guides. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/deploy/production/marketplaces/render (reviewed 2026-11-18). Deployment artifact: https://github.com/FusionAuth/fusionauth-render-blueprint. Artifact reference: Moving repository default branch; reviewed 2026-11-18. Supporting source: EKS deployment — https://fusionauth.io/docs/deploy/production/kubernetes/eks.

- Minimum footprint / sizing: Documented. The application minimum is 512 MB RAM with 10–50 GB disk for application/log needs; database, operating system and optional search are additional. CPU depends on login rate and password hashing. Current releases bundle Java 25 and recommend tested PostgreSQL versions. Multiple app replicas and HA database/search require separate sizing. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/deploy/production/system-requirements (reviewed 2026-11-18).

- License pricing: Documented. FusionAuth uses its proprietary Customer Licence Agreement, including the no-cost Community plan. Paid plan/MAU terms are separate; SCIM and the documented paid air-gap licence require Enterprise. Free Community is not an open-source software licence. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/license (reviewed 2026-11-18). Supporting source: Self-hosting plan comparison — https://fusionauth.io/pricing?hosting=self-hosting&step=plan. Supporting source: SCIM Enterprise entitlement — https://fusionauth.io/docs/users/provision/scim.

- Operating cost estimate: Sources checked — unresolved. Define monthly active users, peak logins/token operations, password-hash settings, identity/audit retention, database/search HA and selected paid features. One hundred internal users need not equal billable MAU, and 1 TB needs a database/log retention split. Include licences, backups, egress and operations. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://fusionauth.io/docs/deploy/production/system-requirements (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. FusionAuth 1.71.0 was released November 17, 2026. It includes security changes and rejects authorized redirect URLs containing fragments; test SAML and redirect configurations during upgrade. The DigitalOcean package remains 1.53.3 in the reviewed catalog. Scope: FusionAuth Self-Hosted: selected customer-operated edition. Source: https://fusionauth.io/docs/release-notes (reviewed 2026-11-18). Supporting source: Separate DigitalOcean package version — https://docs.digitalocean.com/products/marketplace/catalog/fusionauth/.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- FusionAuth 1.71.0 security and redirect configuration review (security-advisory): The release hardens SAML parsing and rejects redirect URLs containing fragments. It also adds an optional Enterprise passwordless-code rate limit. Scope: FusionAuth 1.71.0 release notes; the vendor does not establish a complete affected-version range or CVE for every change. Conditions: Exposure depends on SAML/redirect configuration. The new Enterprise rate limit is disabled by default and applies to the documented FormField strategy. Action: Remove fragments from registered redirects before upgrading, test SAML integrations and explicitly configure the paid rate limit if required. Recheck older provider packages. Source: https://fusionauth.io/docs/release-notes; reviewed 2026-11-18.




## HashiCorp Boundary Enterprise

Commercial identity-aware remote-access platform deployed as controllers and workers in a customer cloud account.

- Listing: https://launchinyourcloud.com/directory/hashicorp-boundary-enterprise/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Boundary Enterprise license required; HCP Boundary is a separate hosted service.
- Licensing model: commercial-only
- Installation: HashiCorp Validated Design Terraform architectures plus supported apt, yum or binary packages
- Architecture: Customer-operated Boundary controllers and workers with external PostgreSQL, KMS or HSM integration and PKI.
- Operations: Customer manages controllers, workers, PostgreSQL, KMS, PKI, networking, identity integrations, backups, upgrades and availability.
- Product website: https://www.hashicorp.com/en/products/boundary
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

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 is proprietary commercial software. HCP Boundary is a separate managed service, and any community distribution does not grant Enterprise features.

Boundary Enterprise runs persistent controller and worker services on customer virtual machines and depends on external PostgreSQL, key management and TLS infrastructure.


### Category fit

- identity-access-management: Provides identity-aware, policy-controlled access to infrastructure targets without exposing long-lived network credentials.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (checked 2026-11-17). 


### Cloud deployment evidence

- Boundary Enterprise validated self-managed deployment on AWS, Azure and Google Cloud (aws, azure, gcp): https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment
  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.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Boundary self-managed deployment: https://developer.hashicorp.com/boundary/docs/deploy/self-managed

- Boundary Validated Design deployment: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment

- Boundary pricing and editions: https://www.hashicorp.com/en/products/boundary/pricing

- HCSEC-2026-54: https://discuss.hashicorp.com/t/hcsec-2026-54-boundary-vulnerable-to-server-side-request-forgery-in-vault-credential-store/77932

### Licensing sources

- https://www.hashicorp.com/en/products/boundary/pricing

### Infrastructure sources

- https://developer.hashicorp.com/boundary/docs/deploy/self-managed

- https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Sources checked — unresolved. Self-managed Enterprise deployment and pricing do not establish a current Marketplace offer matching this edition. HCP Boundary is a different operating model. Scope: Reviewed public evidence for HashiCorp Boundary Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/boundary/pricing (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Boundary Enterprise pricing did not establish eligible software charges under the buyer’s cloud commitment agreement. Scope: Reviewed public evidence for HashiCorp Boundary Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/boundary/pricing (reviewed 2026-11-17).

- Single sign-on: Documented. Boundary supports OIDC through external providers such as Okta and Entra ID, plus separate password/LDAP methods. A primary auth method can create users on first login; this is not evidence of SCIM lifecycle synchronization. Scope: Self-managed Boundary identity methods. Source: https://developer.hashicorp.com/boundary/docs/authentication (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Boundary documents OIDC/LDAP and first-login account creation, but a self-managed Enterprise SCIM endpoint and deprovisioning semantics were not established. HCP SCIM is separate. Scope: Reviewed public evidence for HashiCorp Boundary Enterprise; unresolved within this edition/deployment. Source: https://developer.hashicorp.com/boundary/docs/authentication (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed HashiCorp Boundary Enterprise material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (reviewed 2026-11-17).

- Security controls: Documented. The deployment design separates controller and worker paths with database and key-management dependencies. Configure TLS, network access and recovery, and protect credentials used for provisioning. Current advisory review: HCSEC-2026-54 covers CVE-2026-13303, a server-side request forgery issue in the Vault credential store. Upgrade to the applicable fixed or later Enterprise build and restrict credential-store egress. Scope: Boundary Enterprise deployment security Fixed in Boundary Enterprise 1.0.2 and 0.21.6.. Source: https://discuss.hashicorp.com/t/hcsec-2026-54-boundary-vulnerable-to-server-side-request-forgery-in-vault-credential-store/77932 (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment.

- Air-gapped operation: Sources checked — unresolved. The Enterprise licence-reporting guide explicitly allows manual utilization reporting for isolated installations. This resolves the reporting dependency, but the complete offline licence-renewal, identity, package and upgrade procedure for the selected deployment still needs confirmation. Scope: Self-managed Boundary Enterprise reporting; not blanket isolation of integrations. Source: https://developer.hashicorp.com/boundary/docs/enterprise/automated-license-reporting (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The validated design provides Terraform deployment of Boundary controllers and workers in AWS, Azure or Google Cloud. PostgreSQL, key management and network configuration are required; this is not HCP Boundary. Scope: Self-managed Boundary Enterprise validated design. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. Controllers, workers, PostgreSQL and KMS are separate components. Session concurrency and recording/egress requirements determine worker and storage capacity; 100 identities alone do not establish an HA sizing model. Scope: Boundary Enterprise architecture; workload capacity requires session metrics. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (reviewed 2026-11-17).

- License pricing: Documented. Boundary Enterprise is proprietary commercial software. HCP Boundary is a separate managed service, and any community distribution does not grant Enterprise features. Scope: HashiCorp Boundary Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.hashicorp.com/en/products/boundary/pricing (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Specify concurrent sessions, recording retention, controller/worker topology, HA PostgreSQL and KMS. Data transfer/session volume and commercial entitlements remain unpriced. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The vendor release API identifies 1.1.1+ent as a supported, non-prerelease Enterprise build. Its record was created 2026-11-05. This is the API record-creation date, not a separately established publication date; verify the licensed release/support path before upgrading. Scope: Enterprise-filtered release API snapshot; community and HCP releases excluded. Source: https://api.releases.hashicorp.com/v1/releases/boundary/latest?license_class=enterprise (reviewed 2026-11-17). Supporting source: Versioned Enterprise binaries and checksums — https://releases.hashicorp.com/boundary/1.1.1+ent/.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- HashiCorp Boundary Vault credential-store SSRF (security-advisory): HCSEC-2026-54 covers CVE-2026-13303, a server-side request forgery issue in the Vault credential store. Scope: Fixed in Boundary Enterprise 1.0.2 and 0.21.6. Conditions: Requires the affected Vault credential-store path and reachable network targets. Action: Upgrade to the applicable fixed or later Enterprise build and restrict credential-store egress. Source: https://discuss.hashicorp.com/t/hcsec-2026-54-boundary-vulnerable-to-server-side-request-forgery-in-vault-credential-store/77932; reviewed 2026-11-18.




## Infisical Self-Hosted

Self-hosted secrets-management platform with application and machine-identity access workflows.

- Listing: https://launchinyourcloud.com/directory/infisical-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT core outside enterprise directories; enterprise features and third-party components have separate terms.
- Licensing model: open-source
- Installation: Official AWS ECS/Fargate and Google GKE deployment guides, or a Vultr Docker Compose guide; configure PostgreSQL, Redis, TLS and encryption keys.
- Architecture: Persistent application containers with PostgreSQL, Redis and cloud networking/secrets services
- Operations: 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.
- Product website: https://infisical.com/
- Source review: 2026-11-19; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

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.

The repository licenses code outside ee directories under MIT, enterprise directories under their own license and incorporated third-party components under their original terms. Paid enterprise entitlements must be checked separately.

Persistent application containers with PostgreSQL, Redis and cloud networking/secrets services. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements.


### Category fit

- identity-access-management: Centralizes application secrets and related access/configuration workflows. Certificate, privileged-access and enterprise features depend on the licensed edition and selected components.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/aws-native.mdx (checked 2026-11-13). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/gcp-native.mdx (checked 2026-11-13). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-deploy-infisical-secrets-management-platform (checked 2026-11-13). 


### Cloud deployment evidence

- Vendor ECS/Fargate installation in the customer AWS account (aws): https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/aws-native.mdx
  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.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor GKE installation in the customer Google Cloud project (gcp): https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/gcp-native.mdx
  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.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vultr application deployment with Docker Compose (vultr): https://docs.vultr.com/how-to-deploy-infisical-secrets-management-platform
  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.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

Upstream has sustained participation from multiple substantive contributors and frequent maintained releases, including 0.167.10 on the review date. This is a maintained community/commercial project, not a configuration-only Terraform provider.

Reviewed 2026-11-13.

- Reviewed application release: https://github.com/Infisical/infisical/releases/tag/v0.167.10

- Contributor history: https://github.com/Infisical/infisical/graphs/contributors

### Sources

- Official AWS application deployment source: https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/aws-native.mdx

- Official GKE application deployment source: https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/gcp-native.mdx

- Standalone runtime requirements: https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/standalone-infisical.mdx

- Vultr application deployment with Docker Compose: https://docs.vultr.com/how-to-deploy-infisical-secrets-management-platform

- Exact upstream license boundaries: https://github.com/Infisical/infisical/blob/main/LICENSE

- Reviewed application release: https://github.com/Infisical/infisical/releases/tag/v0.167.10

- Contributor history: https://github.com/Infisical/infisical/graphs/contributors

- Infisical v0.167.13 release: https://github.com/Infisical/infisical/releases/tag/v0.167.13

- Delegated-token authorization hardening: https://github.com/Infisical/infisical/pull/9607

### Licensing sources

- https://github.com/Infisical/infisical/blob/main/LICENSE

### Infrastructure sources

- https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/aws-native.mdx

- https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/gcp-native.mdx

- https://docs.vultr.com/how-to-deploy-infisical-secrets-management-platform


### Buyer diligence


Research coverage: 7/12 fields (58%); 6 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The detailed SSO guide explicitly includes free Google/GitHub login on self-hosted instances. SAML and OIDC require a self-hosted Enterprise licence, with organization email-domain verification and provider configuration. The Enterprise guide explains licence activation; Cloud Pro prices do not establish a self-hosted quote or SCIM entitlement. Scope: Explicit self-hosted protocol/edition boundary; resolves the earlier Cloud-matrix-only question. Source: https://infisical.com/docs/documentation/platform/sso/overview (reviewed 2026-11-20). Supporting source: Published v0.167.13 SSO guide — https://github.com/Infisical/infisical/blob/v0.167.13/docs/documentation/platform/sso/overview.mdx. Supporting source: Self-hosted Enterprise licence activation — https://github.com/Infisical/infisical/blob/v0.167.13/docs/self-hosting/ee.mdx.

- SCIM provisioning: Sources checked — unresolved. The pricing page advertises Enterprise SCIM, but explicitly separates self-hosted pricing from Cloud. This pass did not establish the exact self-hosted license and provisioning entitlement; obtain the deployment-specific matrix. Scope: Self-hosted commercial scope unresolved; Cloud tier names are not a substitute. Source: https://infisical.com/pricing (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Documented. v0.167.13 denies delegated OAuth-token approval, rejection and bypass operations, enforces scope checks ahead of role-only administration checks and adds an organization-permission check to workspace listing. Retest delegated automation. Scope: Infisical delegated OAuth tokens; the vendor did not publish a complete affected-version range. Source: https://github.com/Infisical/infisical/pull/9607 (reviewed 2026-11-19). Supporting source: v0.167.13 release — https://github.com/Infisical/infisical/releases/tag/v0.167.13.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official self-hosting guide documents Compose with PostgreSQL and Redis. Configure the required encryption/authentication secrets, persistence and HTTPS; commercial features require their own license entitlement. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://infisical.com/docs/self-hosting/deployment-options/docker-compose (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The small-deployment guide specifies at least two application instances, each 2 CPU cores/4 GB RAM, plus PostgreSQL at 2 vCPU/8 GB/100 GB disk and Redis at 2 vCPU/4 GB/30 GB SSD. Redis is a persistent required datastore, not a disposable cache. These component baselines need additional replication/storage planning for your throughput, audit retention and HA targets. Scope: Current self-hosted application, PostgreSQL and Redis resource guidance; not a total operating-cost estimate. Source: https://infisical.com/docs/self-hosting/configuration/requirements (reviewed 2026-11-20).

- License pricing: Documented. The pricing FAQ explicitly says self-hosted pricing differs from Infisical Cloud and directs buyers to contact the vendor. Public Cloud per-identity prices must not be used as a self-hosted quote. Scope: Vendor self-hosted pricing policy; no infrastructure or labor estimate. Source: https://infisical.com/pricing (reviewed 2026-11-14).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Infisical v0.167.13 was published November 19, 2026. It tightens delegated OAuth-token authorization and may cause formerly accepted scope-narrowed administration calls to return 403. Scope: Upstream Infisical self-hosted release; cloud packages and commercial editions may differ. Source: https://github.com/Infisical/infisical/releases/tag/v0.167.13 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/Infisical/infisical/releases/tag/v0.167.10. Supporting source: Authorization change — https://github.com/Infisical/infisical/pull/9607.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Infisical v0.167.13 delegated-token authorization hardening (security-advisory): Infisical now enforces delegated OAuth-token scopes ahead of role-only administration checks and denies approval, rejection and bypass operations. Scope: Delegated OAuth tokens and workspace listing; no complete affected-version range was published. Conditions: Scope-narrowed delegated tokens and automation using administration or workspace-list operations are affected; some calls may newly return 403. Action: Upgrade to v0.167.13 or later and retest least-privilege delegated automation. Source: https://github.com/Infisical/infisical/pull/9607; reviewed 2026-11-19. Supporting source: v0.167.13 release — https://github.com/Infisical/infisical/releases/tag/v0.167.13.




## Keycloak Self-Hosted

Identity and access management for application sign-on, federation and authorization.

- Listing: https://launchinyourcloud.com/directory/keycloak/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source project; commercial support/distribution arrangements are separate
- Licensing model: open-source
- Installation: Official server/container distribution or Kubernetes Operator; configure production database and TLS.
- Architecture: Customer-operated identity server, database and optional clustered caches
- Operations: Customer manages identity-server availability, configuration, updates, database and backups.
- Product website: https://www.keycloak.org/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

This entry covers the open-source Keycloak server. Separately purchased support or a commercial distribution does not change this entry’s code-license classification.

The documented self-hosted runtime uses an application server or container with persistent state services. Hosted vendor editions are outside this listing.


### Category fit

- identity-access-management: Identity and access management with SSO, identity brokering, federation and OpenID Connect/OAuth 2.0/SAML support.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.keycloak.org/server/supported-configurations (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.keycloak.org/server/supported-configurations (checked 2026-11-12). 


### Cloud deployment evidence

- Keycloak supported configurations (aws, azure): https://www.keycloak.org/server/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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Container deployment: https://www.keycloak.org/server/containers

- Installation and production guide index: https://www.keycloak.org/guides

- Identity capabilities: https://www.keycloak.org/

- Keycloak 26.8.2 security release: https://www.keycloak.org/2026/11/keycloak-2682-released

- Keycloak 26.8.2 release details: https://github.com/keycloak/keycloak/releases/tag/26.8.2

### Licensing sources

- https://www.keycloak.org/

### Infrastructure sources

- https://www.keycloak.org/server/containers


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Keycloak acts as an OAuth 2.0, OpenID Connect and SAML identity server. Applications must be configured as compatible clients; this is not automatic SSO for every application. Scope: Keycloak identity-provider role and client integration. Source: https://www.keycloak.org/securing-apps/overview (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official container guide builds and starts an optimized Keycloak server image, with external database and hostname/TLS configuration for production. Select a released image and compatible database; start-dev and an ephemeral local database are separate evaluation paths. Operator deployment is another supported installation option. Scope: Official self-hosted server/container deployment; configure production persistence and recovery separately. Source: https://www.keycloak.org/server/containers (reviewed 2026-11-20). Deployment artifact: https://github.com/keycloak/keycloak/releases/tag/26.8.2. Artifact reference: 26.8.2 upstream server distribution and matching container tag.

- Minimum footprint / sizing: Documented. The HA sizing guide starts at about 1,250 MB per pod including realm caches and 10,000 cached sessions. Its tested password-login profile budgets 1 vCPU per 15 logins/second plus 150% CPU headroom; database capacity is separate. These are load-test assumptions, not a universal host minimum or a 100-user, 1 TB HA guarantee. Scope: Official tested HA sizing model; login rate, password hashing, caches, topology and database determine capacity. Source: https://www.keycloak.org/high-availability/multi-cluster/concepts-memory-and-cpu-sizing (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream application uses Apache License 2.0. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote. Scope: Keycloak 26.8.2 upstream distribution; software terms only, excluding infrastructure and operations. Source: https://github.com/keycloak/keycloak/blob/26.8.2/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Keycloak 26.8.2 security release review (security-advisory): The release fixes authentication, token, authorization, account-takeover, XSS and dependency issues. Scope: Upstream Keycloak 26.8.2 security release; affected ranges and configurations vary by linked CVE. Conditions: Identity-provider, database, organization and authentication-flow settings determine applicability; a single blanket affected range is not established. Action: Review the linked CVEs and migration guide, then install a fixed supported release. Source: https://www.keycloak.org/2026/11/keycloak-2682-released; reviewed 2026-11-17.




## NetBird Self-Hosted Community Edition

Open-source zero-trust networking control plane self-hosted on a customer cloud VM.

- Listing: https://launchinyourcloud.com/directory/netbird-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, hetzner, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mixed open-source terms: BSD-3-Clause generally and AGPL-3.0 for server control-plane directories; Enterprise features require a commercial license.
- Licensing model: open-source
- Installation: Official self-hosting script and Docker Compose on a Linux VM; advanced deployment supports a custom identity provider
- Architecture: Customer-operated management, signal, relay or STUN, dashboard, identity and state services; peers form direct WireGuard tunnels where possible
- Operations: Customer manages the VM, domain, TLS, firewall ports, identity configuration, control-plane state, relay capacity, backups, upgrades and availability.
- Product website: https://netbird.io/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

Community code is open source but mixed-licensed: most repository code is BSD-3-Clause, while server control-plane directories are AGPL-3.0. Enterprise-licensed features are excluded.

The quickstart deploys the full control plane as persistent containers on a customer-operated Linux VM.


### Category fit

- identity-access-management: Provides self-hosted identity-aware zero-trust network access with users, policies, device peers, routes and private-resource controls.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (checked 2026-11-19). 


### Cloud deployment evidence

- NetBird self-hosted control plane on a cloud VM (aws, azure, gcp, digitalocean, hetzner, oci): https://docs.netbird.io/selfhosted/selfhosted-guide
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Edition: Community Edition.


### Community and maintenance

The reviewed upstream contributor history includes mlsmaycon, pascal-fischer, lixmal, with sustained contributions alongside the dated application release and public installation history. This establishes maintained community participation, not a commercial support, compliance or capacity guarantee.

Reviewed 2026-11-19.

- Upstream contributor history: https://github.com/netbirdio/netbird/graphs/contributors

- Reviewed upstream application release: https://github.com/netbirdio/netbird/releases/tag/v0.83.1

### Sources

- NetBird self-hosting quickstart: https://docs.netbird.io/selfhosted/selfhosted-quickstart

- NetBird advanced self-hosting guide: https://docs.netbird.io/selfhosted/selfhosted-guide

- NetBird repository license: https://github.com/netbirdio/netbird/blob/main/LICENSE

- NetBird Enterprise edition boundary: https://docs.netbird.io/selfhosted/enterprise

- Reviewed deployment artifact reference: https://github.com/netbirdio/netbird/releases/download/v0.83.1/getting-started.sh

- Upstream release and published installer digest: https://github.com/netbirdio/netbird/releases/tag/v0.83.1

- Upstream contributor history: https://github.com/netbirdio/netbird/graphs/contributors

### Licensing sources

- https://github.com/netbirdio/netbird/blob/main/LICENSE

- https://docs.netbird.io/selfhosted/enterprise

### Infrastructure sources

- https://docs.netbird.io/selfhosted/selfhosted-quickstart

- https://docs.netbird.io/selfhosted/selfhosted-guide


### Buyer diligence


Research coverage: 12/12 fields (100%); 7 documented, 5 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Sources checked — unresolved. The reviewed deployment and licensing sources did not establish a public cloud-marketplace offer that unambiguously entitles the selected self-hosted edition. Obtain the exact offer ID, seller, delivery artifact and edition terms before treating marketplace procurement as available. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Cloud commitment eligibility: Sources checked — unresolved. Customer-cloud deployment or marketplace delivery does not by itself establish cloud-spend commitment eligibility. Confirm the exact offer, billed dimensions, private-offer terms and buyer agreement. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Single sign-on: Documented. The advanced Community self-hosting guide supports a custom OpenID Connect identity provider and names self-hosted and managed IdP options. Enterprise-only identity lifecycle features are separate. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- SCIM provisioning: Explicitly unsupported. NetBird's edition comparison places SCIM user and group provisioning in the Enterprise Commercial License, not Community Edition. Treat SCIM as unavailable for this selected Community listing. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/enterprise (reviewed 2026-11-19).

- Compliance attestations: Sources checked — unresolved. The reviewed product and deployment sources did not establish an independent compliance attestation whose assessed scope covers this customer-operated edition and its local infrastructure. Obtain the current report and map customer responsibilities. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-quickstart (reviewed 2026-11-19).

- Security controls: Edition-dependent. The self-hosted control plane supports OIDC identity, policy-controlled peer access and customer-managed TLS, firewall and state. Community Edition excludes Enterprise SCIM, traffic-flow logging and active-active HA; secure relay, backup and upgrade operations remain customer responsibilities. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19). Supporting source: Community and Enterprise capability boundary — https://docs.netbird.io/selfhosted/enterprise.

- Air-gapped operation: Sources checked — unresolved. The reviewed sources did not establish a fully disconnected installation, update and license workflow for this selected edition. Identify required registries, package repositories, telemetry, identity, activation and support endpoints before claiming air-gapped operation. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The v0.83.1 release publishes getting-started.sh with a verified SHA-256 digest. The script defaults several NetBird containers to latest, so pinning the script does not pin the complete deployment. Review and lock the generated Compose images and persistent state before production use. Scope: Community combined-server quickstart script; advanced multi-container configuration is separate. Source: https://docs.netbird.io/selfhosted/selfhosted-quickstart (reviewed 2026-11-19). Deployment artifact: https://github.com/netbirdio/netbird/releases/download/v0.83.1/getting-started.sh. Artifact reference: v0.83.1/getting-started.sh; sha256:25ee5000a7421cb51a7c4c0f9090788951f531aba171d1fbff676f66d3265bfe. Supporting source: Upstream release and published installer digest — https://github.com/netbirdio/netbird/releases/tag/v0.83.1.

- Minimum footprint / sizing: Documented. The quickstart specifies one publicly reachable Linux VM with at least 1 CPU and 2 GB RAM plus Docker Compose, a domain and required TCP/UDP ports. This is a small single-node baseline, not an HA or large-fleet sizing recommendation. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-quickstart (reviewed 2026-11-19).

- License pricing: Documented. The selected Community Edition is open source under mixed BSD-3-Clause and AGPL-3.0 terms and does not require the Enterprise license. Enterprise HA, SCIM and related capabilities are separately commercial. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://github.com/netbirdio/netbird/blob/main/LICENSE (reviewed 2026-11-19). Supporting source: Enterprise license boundary — https://docs.netbird.io/selfhosted/enterprise.

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. Define provider and region, workload, availability, retention, storage growth, network transfer, support, software entitlement and operating labor before estimating total cost. Scope: NetBird Self-Hosted Community Edition: selected customer-operated edition. Source: https://docs.netbird.io/selfhosted/selfhosted-guide (reviewed 2026-11-19).

- Release snapshot / cadence: Documented. The reviewed upstream v0.83.1 release was published 2026-11-13. Provider images and installer/component packages can differ; this snapshot does not promise a support window or future cadence. Scope: NetBird Self-Hosted Community Edition upstream application, independently versioned from provider packages. Source: https://github.com/netbirdio/netbird/releases/tag/v0.83.1 (reviewed 2026-11-19).







## OpenVPN Access Server

Self-hosted business VPN and network-access server deployed in the customer's cloud account.

- Listing: https://launchinyourcloud.com/directory/openvpn-access-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial subscription, fixed and cloud-marketplace licenses; unlicensed mode is limited to two connections.
- Licensing model: commercial-only
- Installation: Official cloud marketplace image or AWS CloudFormation stack, or package or container on a supported Linux VM
- Architecture: Customer-operated Access Server VM or container with Admin Web UI, VPN data plane and optional multi-node clustering
- Operations: Customer manages compute, routing, network exposure, identity integration, certificates, upgrades, backups and availability.
- Product website: https://openvpn.net/access-server/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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 is commercially licensed even though it permits two connections without a paid key; OpenVPN Community Edition is a separate product.

The full Access Server application runs on customer-operated compute; marketplace images and CloudFormation deployments create customer-cloud VMs and networking.


### Category fit

- identity-access-management: Provides a self-hosted business VPN and policy-controlled remote or site-to-site network access server.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openvpn.net/as-docs/v3/aws/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openvpn.net/as-docs/v3/azure/ (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openvpn.net/as-docs/v3/google-cloud/ (checked 2026-11-19). 


### Cloud deployment evidence

- Access Server AWS customer-account deployment (aws): https://openvpn.net/as-docs/v3/aws/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Access Server Azure Marketplace VM (azure): https://openvpn.net/as-docs/v3/azure/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Access Server Google Cloud Marketplace deployment (gcp): https://openvpn.net/as-docs/v3/google-cloud/
  The official guide deploys the self-hosted Access Server instance into the customer's selected Google Cloud project and VPC.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- OpenVPN Access Server installation overview: https://openvpn.net/as-docs/installation-overview/

- OpenVPN Access Server on AWS: https://openvpn.net/as-docs/v3/aws/

- OpenVPN Access Server on Azure: https://openvpn.net/as-docs/v3/azure/

- OpenVPN Access Server on Google Cloud: https://openvpn.net/as-docs/v3/google-cloud/

- OpenVPN Access Server subscription licensing: https://openvpn.net/as-docs/subscription/

- Buyer evidence: iac: https://openvpn.net/as-docs/v3/docker/

- Reviewed deployment artifact reference: https://hub.docker.com/r/openvpn/openvpn-as/tags?name=3.2.4-f3c295a7-Ubuntu26

- Published tag and manifest digest: https://hub.docker.com/v2/repositories/openvpn/openvpn-as/tags?page_size=5

- Access Server pricing: https://openvpn.net/access-server/pricing/

### Licensing sources

- https://openvpn.net/as-docs/subscription/

- https://openvpn.net/access-server/pricing/

### Infrastructure sources

- https://openvpn.net/as-docs/installation-overview/


### Buyer diligence


Research coverage: 12/12 fields (100%); 4 documented, 8 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Documented. OpenVPN documents Access Server Marketplace deployment for AWS, Azure and Google Cloud, with provider-specific bring-your-own-license, pay-as-you-go or fixed licensing choices. Confirm the exact offer and connection entitlement. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/v3/aws/ (reviewed 2026-11-19). Supporting source: Azure Marketplace deployment — https://openvpn.net/as-docs/v3/azure/. Supporting source: Google Cloud Marketplace deployment — https://openvpn.net/as-docs/v3/google-cloud/.

- Cloud commitment eligibility: Sources checked — unresolved. Customer-cloud deployment or marketplace delivery does not by itself establish cloud-spend commitment eligibility. Confirm the exact offer, billed dimensions, private-offer terms and buyer agreement. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/v3/aws/ (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The reviewed installation and edition sources did not establish the exact SSO protocols, identity-provider support and entitlement for this selected edition. Confirm authentication, role mapping and break-glass access before deployment. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/installation-overview/ (reviewed 2026-11-19).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/installation-overview/ (reviewed 2026-11-19).

- Compliance attestations: Sources checked — unresolved. The reviewed product and deployment sources did not establish an independent compliance attestation whose assessed scope covers this customer-operated edition and its local infrastructure. Obtain the current report and map customer responsibilities. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/installation-overview/ (reviewed 2026-11-19).

- Security controls: Edition-dependent. Access Server is deployed as a customer-controlled VPN data plane and administration service with customer-managed routing, identity, certificates and network exposure. The reviewed cloud guides require explicit security-group or firewall configuration; validate TLS, MFA, logging and administrator access for the chosen license and topology. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/installation-overview/ (reviewed 2026-11-19).

- Air-gapped operation: Sources checked — unresolved. The reviewed sources did not establish a fully disconnected installation, update and license workflow for this selected edition. Identify required registries, package repositories, telemetry, identity, activation and support endpoints before claiming air-gapped operation. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/v3/aws/ (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. OpenVPN documents its official Access Server Docker image as an additional installation option. The registry identifies tag 3.2.4-f3c295a7-Ubuntu26 and its manifest digest. Persist /openvpn and review the TUN device and NET_ADMIN/MKNOD capabilities. This container reference does not establish the version of any provider marketplace VM image. Scope: Official commercial Access Server container, separate from the AWS/Azure/GCP marketplace AMIs. Source: https://openvpn.net/as-docs/v3/docker/ (reviewed 2026-11-19). Deployment artifact: https://hub.docker.com/r/openvpn/openvpn-as/tags?name=3.2.4-f3c295a7-Ubuntu26. Artifact reference: docker.io/openvpn/openvpn-as:3.2.4-f3c295a7-Ubuntu26; sha256:b5091b2b5dbebd302c1a61fe8154453e3ff84bd9df7894e530d45e22c76dcdf8. Supporting source: Published tag and manifest digest — https://hub.docker.com/v2/repositories/openvpn/openvpn-as/tags?page_size=5.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed sources describe the deployment components but do not provide one complete production sizing model for the buyer's users, data volume, traffic, retention and availability target. Size every application and managed-service dependency. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/v3/aws/ (reviewed 2026-11-19).

- License pricing: Edition-dependent. Access Server supports commercial subscription, fixed and marketplace licensing, while unlicensed mode is capped at two connections. Price the selected connection entitlement and HA nodes separately from cloud infrastructure. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/subscription/ (reviewed 2026-11-19). Supporting source: Access Server pricing — https://openvpn.net/access-server/pricing/.

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. Define provider and region, workload, availability, retention, storage growth, network transfer, support, software entitlement and operating labor before estimating total cost. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://openvpn.net/as-docs/v3/aws/ (reviewed 2026-11-19).

- Release snapshot / cadence: Sources checked — unresolved. The official registry identifies Docker image 3.2.4-f3c295a7-Ubuntu26 and its manifest digest. Registry update time is not an application release-publication timestamp, and provider VM images are separately versioned. Confirm the intended application build, marketplace image and upgrade path before treating them as one release snapshot. Scope: OpenVPN Access Server: selected customer-operated edition. Source: https://hub.docker.com/v2/repositories/openvpn/openvpn-as/tags?page_size=5 (reviewed 2026-11-19).







## Teleport Enterprise Self-Hosted

Commercial access platform deployed as a high-availability Teleport cluster in the customer's cloud.

- Listing: https://launchinyourcloud.com/directory/teleport-enterprise-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Teleport Enterprise Self-Hosted subscription and license file required.
- Licensing model: commercial-only
- Installation: Teleport Helm charts on EKS, AKS or GKE; official Terraform deployment paths are also documented
- Architecture: Customer-operated Teleport Auth and Proxy services with provider databases, object storage, DNS and load balancing.
- Operations: Customer manages Kubernetes or VMs, backend state, storage, DNS, TLS, upgrades, capacity, backups and the Enterprise license.
- Product website: https://goteleport.com/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

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

The selected Enterprise Self-Hosted edition requires a commercial subscription and license file.

Teleport runs persistent authentication and proxy services with provider-backed state and network dependencies.


### Category fit

- identity-access-management: Provides identity-aware access to servers, Kubernetes, databases and applications through customer-operated authentication and proxy services.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://goteleport.com/docs/installation/self-hosted/helm-deployments/aws/ (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://goteleport.com/docs/installation/self-hosted/helm-deployments/azure/ (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://goteleport.com/docs/installation/self-hosted/helm-deployments/gcp/ (checked 2026-11-18). 


### Cloud deployment evidence

- Teleport Enterprise on AWS EKS (aws): https://goteleport.com/docs/installation/self-hosted/helm-deployments/aws/
  Teleport documents a full HA Auth and Proxy deployment on customer EKS with AWS backing services.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Teleport Enterprise on Azure AKS (azure): https://goteleport.com/docs/installation/self-hosted/helm-deployments/azure/
  Teleport documents a full HA deployment on customer AKS.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Teleport Enterprise on Google GKE (gcp): https://goteleport.com/docs/installation/self-hosted/helm-deployments/gcp/
  Teleport documents a full HA deployment on customer GKE.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Sources

- Self-hosting Teleport: https://goteleport.com/docs/installation/self-hosted/

- Teleport deployment guides: https://goteleport.com/docs/installation/self-hosted/deployments/

- Teleport on AWS EKS: https://goteleport.com/docs/installation/self-hosted/helm-deployments/aws/

- Teleport on Azure AKS: https://goteleport.com/docs/installation/self-hosted/helm-deployments/azure/

- Teleport on Google GKE: https://goteleport.com/docs/installation/self-hosted/helm-deployments/gcp/

### Licensing sources

- https://goteleport.com/docs/installation/self-hosted/

- https://goteleport.com/docs/feature-matrix/

### Infrastructure sources

- https://goteleport.com/docs/installation/self-hosted/deployments/


### Buyer diligence


Research coverage: 12/12 fields (100%); 9 documented, 3 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Sources checked — unresolved. Teleport’s Marketplace announcement describes cloud or self-hosted deployment, but the linked current AWS offer prodview-fnmgbsyr3kwko prices its dimension as Cloud only and excludes support. It does not establish self-hosted licence terms. Obtain a self-hosted order/private-offer identifier, entitlement and support terms rather than transferring the public Cloud price to this deployment. Scope: Current linked public AWS offer versus separately negotiated Enterprise Self-Hosted entitlement. Source: https://aws.amazon.com/marketplace/pp/prodview-fnmgbsyr3kwko (reviewed 2026-11-18). Supporting source: Broader vendor Marketplace announcement — https://goteleport.com/about/newsroom/press-releases/teleport-infrastructure-identity-platform-in-aws-marketplace-ai-agents-tools/.

- Cloud commitment eligibility: Sources checked — unresolved. The linked AWS public offer prices Cloud only; it does not establish eligible spend for Enterprise Self-Hosted. Confirm a self-hosted private offer, its billed entitlement/support dimensions and the buyer’s applicable AWS commitment terms. Do not transfer the public Cloud offer’s procurement or credits to a self-hosted order. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-fnmgbsyr3kwko (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Edition-dependent. The feature matrix assigns SAML and OIDC SSO to Enterprise Self-Hosted. Configure the IdP connector, roles and login policy; the Community GitHub-login option is a separate edition boundary. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://goteleport.com/docs/feature-matrix/ (reviewed 2026-11-18).

- SCIM provisioning: Edition-dependent. Teleport Enterprise Identity Governance documents SCIM 2.0 for users/groups with SAML SSO, OAuth client credentials and matching Access Lists. It requires v17.6.1 or v18.0.3+; the IdP pushes changes into Teleport, not the reverse. Confirm the Identity Governance entitlement and tested deactivation/session-lock behavior. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://goteleport.com/docs/identity-governance/integrations/scim/ (reviewed 2026-11-18).

- Compliance attestations: Edition-dependent. Teleport’s v18.11.10 documentation identifies BoringCrypto fips-20220613, CMVP 4735, in Enterprise FIPS builds from 17.7.3/18.0.0. NIST lists the FIPS 140-3 Level 1 module as active, with a July 22, 2029 sunset and approved-mode/tested-configuration conditions. This validates the cryptographic module, not Teleport as a whole, every OS/CPU combination or a customer’s FedRAMP authorisation. Scope: Enterprise FIPS-build cryptographic-module boundary; operating environment and approved-mode conditions still require assessment. Source: https://github.com/gravitational/teleport/blob/v18.11.10/docs/pages/zero-trust-access/compliance-frameworks/fedramp.mdx (reviewed 2026-11-18). Supporting source: NIST module status, caveats and tested configurations — https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4735.

- Security controls: Documented. The chart separates Auth/Proxy services and configures TLS, backing storage and Enterprise licence secrets. Avoid treating standalone local storage as HA. Authentication, roles, short-lived certificates, audit/session storage and backup protection need an explicit deployment policy. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://goteleport.com/docs/reference/helm-reference/teleport-cluster/ (reviewed 2026-11-18). Supporting source: HA scaling and service separation — https://goteleport.com/docs/reference/deployment/scaling/. Supporting source: Identity governance provisioning controls — https://goteleport.com/docs/identity-governance/integrations/scim/.

- Air-gapped operation: Edition-dependent. Teleport explicitly supports fully air-gapped clusters, including privately reachable Auth and Proxy services. Enterprise uses a local licence file. Automatic licence updates require api.teleport.sh, but the cluster continues without that access while its local licence remains valid. Transfer renewed licences and release artifacts deliberately, and provide internal IdP, DNS, certificates, audit/storage backends and client access. Scope: Fully self-hosted Teleport Enterprise with a valid local licence and internally reachable dependencies. Source: https://goteleport.com/docs/reference/deployment/networking/ (reviewed 2026-11-18). Supporting source: Offline licence behavior and expiry boundary — https://goteleport.com/docs/installation/self-hosted/license/. Supporting source: Vendor statement of air-gapped self-hosting — https://goteleport.com/use-cases/data-centers/.

- Deployment artifact / IaC: Documented. The upstream teleport-cluster Helm chart configures Enterprise images using enterprise: true and a customer licence secret. The reviewed chart source is pinned to v18.11.10. Follow the separate EKS/AKS/GKE backend and network configuration guides. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://goteleport.com/docs/reference/helm-reference/teleport-cluster/ (reviewed 2026-11-18). Deployment artifact: https://github.com/gravitational/teleport/tree/v18.11.10/examples/chart/teleport-cluster. Artifact reference: Teleport v18.11.10 chart source.

- Minimum footprint / sizing: Documented. Teleport publishes an illustrative HA configuration for up to 10,000 SSH nodes: two Proxy instances at 4 vCPU/8 GB and two Auth at 8 vCPU/16 GB, with appropriate external storage. It is a scale example, not the minimum for 100 users. Kubernetes API request rate, sessions, registered clusters and recording volume require measurement. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://goteleport.com/docs/reference/deployment/scaling/ (reviewed 2026-11-18).

- License pricing: Documented. The June 16, 2026 Enterprise guide bills Monthly Active Users and Teleport Protected Resources, with Standard/Premium feature bundles; Priority Support is included for self-hosted deployments. It publishes metric definitions, not numeric rates. Request a self-hosted quote with protected resources, machine identities and entitlements; public Cloud Marketplace prices are not self-hosted rates. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://goteleport.com/api/files/teleport-pricing-guide.pdf (reviewed 2026-11-18). Supporting source: Public offer explicitly prices Cloud only — https://aws.amazon.com/marketplace/pp/prodview-fnmgbsyr3kwko.

- Operating cost estimate: Sources checked — unresolved. The current pricing guide defines MAUs and hourly/monthly averaged Protected Resources but gives no rates. One hundred internal users is at most a user assumption, not a resource or machine-identity count; 1 TB is not a session-recording retention model. Supply MAUs, protected resources/bots, recording volume/retention, auth/proxy/backend HA design and a self-hosted licence quote before completing the AWS us-east-1 budget. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://goteleport.com/api/files/teleport-pricing-guide.pdf (reviewed 2026-11-18). Supporting source: Self-hosted topology and backend sizing — https://goteleport.com/docs/reference/deployment/scaling/. Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. Teleport v18.11.10 was published November 16, 2026. Match Enterprise images, cluster chart, clients and Terraform provider to the supported upgrade path. Community repository publication does not itself establish the buyer’s commercial support term. Scope: Teleport Enterprise Self-Hosted: selected customer-operated edition. Source: https://github.com/gravitational/teleport/releases/tag/v18.11.10 (reviewed 2026-11-18). Supporting source: Teleport application change log — https://goteleport.com/docs/changelog/.







## Vault Enterprise Self-Managed

Commercial self-managed secrets and identity security platform deployed as a customer-operated high-availability cluster.

- Listing: https://launchinyourcloud.com/directory/vault-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Vault Enterprise license required.
- Licensing model: commercial-only
- Installation: Official HashiCorp Validated Design Terraform modules for AWS EC2, Azure VMs or Google GCE
- Architecture: High-availability Vault Enterprise VM cluster with integrated storage, load balancing, TLS and cloud key-management dependencies
- Operations: Customer 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.
- Product website: https://developer.hashicorp.com/vault
- Source review: 2026-11-15; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

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.

The selected Vault Enterprise edition requires a commercial license and supports license autoloading or explicit license configuration.

The validated design deploys a persistent high-availability Vault Enterprise VM cluster with integrated storage and provider key-management services.


### Category fit

- identity-access-management: Provides centrally governed secrets, encryption, authentication methods, dynamic credentials and identity-based access policies.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform (checked 2026-11-15). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform (checked 2026-11-15). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform (checked 2026-11-15). 


### Cloud deployment evidence

- Vault Enterprise inside a customer cloud account (aws, azure, gcp): https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform
  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.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Sources

- Deploy Vault Enterprise with official Terraform modules: https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform

- Vault Enterprise license keys: https://developer.hashicorp.com/vault/docs/license

- Vault editions: https://developer.hashicorp.com/vault/tutorials/get-started/available-editions

### Licensing sources

- https://developer.hashicorp.com/vault/docs/license

- https://developer.hashicorp.com/vault/tutorials/get-started/available-editions

### Infrastructure sources

- https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Vault documents OIDC browser login from the UI and CLI, using configured identity providers, callback URLs, roles and claim-bound policies. OIDC authentication is distinct from Kubernetes/JWT machine login and from downstream applications consuming secrets. Configure authorization and the selected Enterprise feature entitlements separately. Scope: Self-managed Vault user authentication via the JWT/OIDC auth method. Source: https://developer.hashicorp.com/vault/docs/auth/jwt (reviewed 2026-11-20). Supporting source: Identity-provider configuration examples — https://developer.hashicorp.com/vault/docs/auth/jwt/oidc-providers.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. HashiCorp publishes validated Terraform modules for Vault Enterprise on AWS EC2, Azure VMs and Google Cloud. Provider-specific networking, encryption keys, TLS material and a valid Enterprise license are prerequisites. These modules do not include an Enterprise entitlement. Scope: Vault Enterprise VM installation, HashiCorp Validated Designs. Source: https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. The integrated-storage reference recommends 2–4 cores, 8–16 GB RAM and 100+ GB SSD at 3,000+ IOPS per small-cluster server; larger workloads have higher tiers. Its resilient topology uses five nodes across three zones. Audit-log I/O, replication and secret/request rates need separate sizing; these figures are not a complete 1 TB HA design. Scope: Official Vault integrated-storage per-server and cluster reference; not an application-data storage estimate. Source: https://developer.hashicorp.com/vault/tutorials/day-one-raft/raft-reference-architecture (reviewed 2026-11-20).

- License pricing: Documented. Vault Enterprise requires a commercial licence key governing feature access and use dates. The current policy distinguishes expiration from termination: release date and termination conditions affect restart, unseal and security-upgrade eligibility. Obtain the applicable self-managed quote, feature/replication entitlements and term; HCP Vault Dedicated uses a separate commercial model. Scope: Current Vault Enterprise self-managed licence-key policy; no public numeric quote established. Source: https://developer.hashicorp.com/vault/docs/license (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






