
# Backend platforms on Google Cloud

Compare documented Backend platforms deployments on Google Cloud, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/gcp/backend-platforms/
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: Google Cloud project
- 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.cloud.google.com/resource-manager/docs/creating-managing-projects (checked 2026-11-20).
- Network: VPC network
- Identity and access: IAM policies and service accounts
- Installation guidance: Terraform, optionally using Infrastructure Manager for resource provisioning; deploy the application separately.
- Guidance source: https://docs.cloud.google.com/infrastructure-manager/docs/overview
- Guidance reviewed: 2026-11-10


### Private offers

Cloud Marketplace vendors can negotiate a private offer for a specified Cloud Billing account. Check duration, renewal terms and commitment treatment in the actual agreement.
Source: https://docs.cloud.google.com/marketplace/docs/offers/discover-private-offers (reviewed 2026-11-14).

### Private connectivity

Private Service Connect connects VPC consumers to supported managed or producer services. Confirm the actual product endpoint and network/DNS architecture.
Source: https://docs.cloud.google.com/vpc/docs/private-service-connect (reviewed 2026-11-14).

### External workload access

Workload Identity Federation can grant external workloads scoped Google Cloud access without long-lived service-account keys. Validate the trust configuration and exact roles.
Source: https://docs.cloud.google.com/iam/docs/workload-identity-federation (reviewed 2026-11-14).

### Regulated environments

Assured Workloads applies control packages for residency and access boundaries. Confirm supported services, regions and the product deployment; it is not automatic product certification.
Source: https://docs.cloud.google.com/assured-workloads/docs/overview (reviewed 2026-11-14).

The listings below have evidence for Google Cloud. Read each cloud evidence note for the applicable package, edition and support qualifications.

10 listings.


## Appwrite Self-Hosted

Self-hosted backend services for authentication, databases, storage, functions and messaging.

- Listing: https://launchinyourcloud.com/directory/appwrite/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: BSD-3-Clause core; enterprise services and feature terms should be confirmed separately
- Licensing model: open-source
- Installation: Docker installer or official Kubernetes Helm chart
- Architecture: Customer-operated container services, database and storage
- Operations: Customer configures the environment and handles software updates, scaling, security and backups.
- Product website: https://appwrite.io/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers self-hosting rather than Appwrite Cloud. Official deployment guides document EC2/EKS, Azure VMs/AKS and Google Compute Engine/GKE. Configure external email, SMS and other integrations deliberately; enterprise support and compliance offerings have separate terms. Appwrite 2.7.3 includes the 2.7.2 security fixes across authentication, abuse limits, storage, realtime, messaging, functions, VCS, proxy handling, and vulnerable base-image packages. It additionally rebuilds appwrite/base and openruntimes/executor to clear remaining image vulnerability findings. Upgrading from 2.7.2 requires no schema changes; use the normal upgrade command and migration step.

This classification covers the public Appwrite self-hosted distribution under BSD-3-Clause. Appwrite separately markets a premium enterprise self-hosted edition; its additional tooling and terms are outside this classification and should not be assumed to inherit the public core license.

Appwrite runs as persistent Docker services or an official Helm deployment on Kubernetes. The function feature does not make the complete backend a serverless deployment.


Cloud evidence scope: Official guides document AWS, Azure and Google Cloud customer-infrastructure deployments.

### Category fit

- backend-platforms: Application backend APIs for authentication, databases, storage, functions, messaging and realtime, deployed on customer infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://appwrite.io/docs/advanced/self-hosting/platforms/aws (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://appwrite.io/docs/advanced/self-hosting/platforms/azure (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://appwrite.io/docs/advanced/self-hosting/platforms/google-cloud (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://appwrite.io/docs/advanced/self-hosting/platforms/digitalocean (checked 2026-11-12). 


### Cloud deployment evidence

- Appwrite self-hosting on AWS (aws): https://appwrite.io/docs/advanced/self-hosting/platforms/aws
  The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Appwrite self-hosting on Azure (azure): https://appwrite.io/docs/advanced/self-hosting/platforms/azure
  The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Appwrite self-hosting on google-cloud (gcp): https://appwrite.io/docs/advanced/self-hosting/platforms/google-cloud
  The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Appwrite self-hosting on digitalocean (digitalocean): https://appwrite.io/docs/advanced/self-hosting/platforms/digitalocean
  The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Backend capabilities: https://appwrite.io/docs

- Self-hosting responsibilities: https://appwrite.io/docs/advanced/self-hosting

- Docker installation: https://appwrite.io/docs/advanced/self-hosting/installation

- AWS deployment: https://appwrite.io/docs/advanced/self-hosting/platforms/aws

- Azure deployment: https://appwrite.io/docs/advanced/self-hosting/platforms/azure

- Google Cloud deployment: https://appwrite.io/docs/advanced/self-hosting/platforms/google-cloud

- Core license: https://raw.githubusercontent.com/appwrite/appwrite/main/LICENSE

- Licensing and edition terms: https://appwrite.io/enterprise

- Infrastructure deployment documentation: https://appwrite.io/docs/advanced/self-hosting/platforms/kubernetes

- Appwrite self-hosting on digitalocean: https://appwrite.io/docs/advanced/self-hosting/platforms/digitalocean

- Appwrite 2.7.2 security patch: https://github.com/appwrite/appwrite/releases/tag/2.7.2

- Appwrite 2.7.3 image security update: https://github.com/appwrite/appwrite/releases/tag/2.7.3

### Licensing sources

- https://raw.githubusercontent.com/appwrite/appwrite/main/LICENSE

- https://appwrite.io/docs/advanced/self-hosting

- https://appwrite.io/enterprise

### Infrastructure sources

- https://appwrite.io/docs/advanced/self-hosting/installation

- https://appwrite.io/docs/advanced/self-hosting/platforms/kubernetes


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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: Edition-dependent. Appwrite documents OAuth2 identity providers for users of applications you build. Separately, the vendor advertises centralized Console SSO in its premium Enterprise platform, available as self-hosted or Cloud. Do not treat core application-user OAuth as administrator SAML: confirm the chosen self-hosted Enterprise package, IdP/protocol and organization policy for Console SSO. Scope: Application-user OAuth versus premium self-hosted Console identity; product/edition boundaries apply. Source: https://appwrite.io/enterprise (reviewed 2026-11-20). Supporting source: Application-user OAuth2 flow and provider setup — https://appwrite.io/docs/products/auth/oauth2.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installer generates a Compose stack and environment/configuration files. Replace encryption/executor secrets, retain all required files and select the worker/database configuration; a Kubernetes Helm option is separate. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://appwrite.io/docs/advanced/self-hosting/installation (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The current installation guide requires at least 2 CPU cores, 4 GB RAM and 2 GB swap on a Docker-capable host. Models, functions, worker topology and workload can raise requirements. Scope: Appwrite installation baseline; not every production workload. Source: https://appwrite.io/docs/advanced/self-hosting/installation (reviewed 2026-11-14).

- License pricing: Documented. The reviewed upstream application uses BSD 3-Clause licence. 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: Appwrite 2.7.3 upstream core; not Cloud or Enterprise entitlements; software terms only, excluding infrastructure and operations. Source: https://github.com/appwrite/appwrite/blob/2.7.3/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is 2.7.3, published 2026-11-17. This is a dated release snapshot, not a support designation, a future cadence promise or approval to replace a provider package. Scope: Upstream appwrite/appwrite release record; commercial editions, LTS branches and provider packages can differ. Source: https://github.com/appwrite/appwrite/releases/tag/2.7.3 (reviewed 2026-11-17).




### Security and lifecycle reviews

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

- Appwrite container security maintenance (security-advisory): Appwrite 2.7.3 refreshes its base and executor images after the 2.7.2 security update. Scope: Self-hosted Appwrite 2.7.3, appwrite/base 2.2.12 and openruntimes/executor 1.3.5; not Appwrite Cloud. Conditions: Container dependency findings depend on the actual deployed images. The release is not proof that every image or integration is vulnerability-free. Action: Back up and use the normal upgrade/migrate procedure; the release says moving from 2.7.2 introduces no schema changes. Source: https://github.com/appwrite/appwrite/releases/tag/2.7.3; reviewed 2026-11-17.




## Gravitee API Management Self-Hosted

Open-source and commercial self-hosted API management platform with documented EKS, AKS and GKE deployment paths.

- Listing: https://launchinyourcloud.com/directory/gravitee-apim-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 Community Edition; Enterprise Edition requires a commercial license.
- Licensing model: open-source
- Installation: Official Helm chart, Docker deployment or Linux packages on customer infrastructure
- Architecture: Self-hosted management API and user interfaces, API gateways, MongoDB and Elasticsearch, with optional Redis, PostgreSQL and enterprise services
- Operations: Customer manages Kubernetes or hosts, databases, search, networking, ingress, TLS, identity, secrets, monitoring, backups, scaling, upgrades and any Enterprise license.
- Product website: https://www.gravitee.io/platform/api-management
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers Gravitee APIM with both control and data planes self-hosted. Gravitee recommends its cloud option for new installations, and multi-environment self-hosted configuration requires a connection to Gravitee Cloud. The provider-specific Kubernetes guides are development and quick-start material, not production reference architectures. Gravitee APIM 4.10.36 fixes Kafka OAUTHBEARER reauthentication, subscription metadata deletion, dead-letter-queue failure handling, and health-check POST bodies. Supported 4.13.4 also fixes upgrade and Redis-cache behavior; v2 APIs are scheduled for removal in October 2027, and unqualified images move from Alpine to Debian in March 2027 before Alpine images stop in June 2027.

Gravitee APIM Community Edition is Apache-2.0 licensed. Enterprise Edition capabilities require a separate commercial license.

Gravitee APIM runs persistent management, gateway, portal, database and analytics services on customer hosts or Kubernetes.


### Category fit

- backend-platforms: Provides a self-hosted API gateway, management control plane, developer portal, policy engine and API lifecycle tooling.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides (checked 2026-11-16). 


### Cloud deployment evidence

- Gravitee APIM self-hosted deployment on EKS, AKS or GKE (aws, azure, gcp): https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides
  Gravitee's current self-hosted guide lists AWS EKS, Azure AKS and Google GKE as Kubernetes deployment methods and states that the customer manages both the control plane and data plane. Provider quick starts are development guidance rather than production architecture commitments.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed. Versions: 4.10.


### Community and maintenance

Gravitee maintains public releases and contributor history for its Apache-licensed API Management project. This evidence establishes continuing upstream activity, not Enterprise support or production support for a particular cloud configuration.

Reviewed 2026-11-16.

- Gravitee APIM releases: https://github.com/gravitee-io/gravitee-api-management/releases

- Gravitee APIM contributor history: https://github.com/gravitee-io/gravitee-api-management/graphs/contributors

### Sources

- Gravitee APIM self-hosted installation guides: https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides

- Gravitee APIM Enterprise Edition: https://documentation.gravitee.io/apim/4.10/readme/enterprise-edition

- Gravitee APIM editions: https://documentation.gravitee.io/apim/4.10/getting-started

- Gravitee APIM Apache 2.0 license: https://github.com/gravitee-io/gravitee-api-management/blob/master/LICENSE.txt

- Gravitee APIM releases: https://github.com/gravitee-io/gravitee-api-management/releases

- Gravitee APIM contributor history: https://github.com/gravitee-io/gravitee-api-management/graphs/contributors

- Gravitee APIM 4.10 changelog: https://documentation.gravitee.io/apim/4.10/release-information/changelog/apim-4.10.x

- Gravitee APIM 4.13 changelog: https://documentation.gravitee.io/apim/4.13/release-information/changelog/apim-4.13.x

- Gravitee APIM support model: https://documentation.gravitee.io/apim/release-information/support-model

- Gravitee APIM 4.13 release notes: https://github.com/gravitee-io/gravitee-platform-docs/blob/main/docs/gamma/4.13/platform-management/gamma-release-notes.md

### Licensing sources

- https://github.com/gravitee-io/gravitee-api-management/blob/master/LICENSE.txt

- https://documentation.gravitee.io/apim/4.10/readme/enterprise-edition

### Infrastructure sources

- https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides

- https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides/kubernetes/azure-aks


### 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: Documented. APIM documents delegating Console and Portal authentication to a corporate OAuth2/OIDC provider or LDAP, with role/group mapping. The New Developer Portal has its own SSO configuration and requires APIM 4.10+. Scope: Self-hosted APIM 4.10 Console/Portal; not a blanket entitlement to the separate Access Management product. Source: https://documentation.gravitee.io/apim/4.10/prepare-a-production-environment/production-best-practices/authentication (reviewed 2026-11-16). Supporting source: New Portal SSO setup — https://documentation.gravitee.io/apim/4.10/developer-portal/new-developer-portal/configure-authentication/configure-authentication-with-sso.

- SCIM provisioning: Not researched.

- Compliance attestations: Sources checked — unresolved. The security page’s printed certificate scope describes a marketing platform rather than APIM. That mismatch does not establish assurance for this listing; obtain a current certificate/report identifying the APIM organization, product boundary and validity dates. Scope: Published certificate-scope mismatch; current self-hosted APIM assurance remains unresolved. Source: https://www.gravitee.io/security-at-gravitee (reviewed 2026-11-16).

- Security controls: Documented. Production guidance recommends external identity, least-privilege roles/groups and signed session cookies. Operators must replace example JWT/cookie secrets and scope cookies to the correct environment. These are configuration requirements, not a compliance attestation. Scope: APIM 4.10 production authentication configuration. Source: https://documentation.gravitee.io/apim/4.10/prepare-a-production-environment/production-best-practices/authentication (reviewed 2026-11-16).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The current APIM chart source is in the API Management repository; the older standalone helm-charts repository points there. Use the versioned installation guide and a compatible chart release, database and search backend. Scope: Self-hosted APIM 4.10 installation guidance; chart repository moves independently. Source: https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides/kubernetes (reviewed 2026-11-16). Deployment artifact: https://github.com/gravitee-io/gravitee-api-management/tree/master/helm. Artifact reference: master (moving branch; select a chart compatible with APIM 4.10). Supporting source: APIM chart relocation — https://github.com/gravitee-io/helm-charts.

- Minimum footprint / sizing: Documented. The APIM 4.10 guide gives the combined Portal/Console/REST API a baseline of 2 vCPU, 4 GB RAM and 20 GB disk. Gateways, analytics and configuration databases are additional; production HA recommends multiple nodes and traffic-dependent sizing. Scope: Self-hosted component baselines, not the total platform footprint or guaranteed throughput. Source: https://documentation.gravitee.io/apim/4.10/prepare-a-production-environment/gateway-resource-sizing-guidelines (reviewed 2026-11-16).

- License pricing: Documented. Gravitee APIM Community Edition is Apache-2.0 licensed. Enterprise Edition capabilities require a separate commercial license. Scope: Gravitee API Management Self-Hosted: software license terms; infrastructure and operating costs are separate. Source: https://github.com/gravitee-io/gravitee-api-management/blob/master/LICENSE.txt (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://documentation.gravitee.io/apim/4.10/readme/enterprise-edition.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Gravitee APIM 4.10.36 and supported 4.13.4 were released November 13, 2026. Plan separately for v2 API removal in October 2027 and the 2027 Alpine-to-Debian image transition. Scope: Gravitee APIM self-hosted 4.10 branch, with 4.13 support and migration context. Source: https://documentation.gravitee.io/apim/4.10/release-information/changelog/apim-4.10.x (reviewed 2026-11-18). Supporting source: 4.13.4 changelog — https://documentation.gravitee.io/apim/4.13/release-information/changelog/apim-4.13.x.







## HashiCorp Consul Enterprise

Commercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/hashicorp-consul-enterprise/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Consul Enterprise license required for the selected validated design.
- Licensing model: commercial-only
- Installation: HashiCorp Validated Design Terraform modules for AWS, Azure or Google Cloud
- Architecture: Customer-operated Consul server quorum and clients with provider load balancers, KMS, secrets and snapshot storage.
- Operations: Customer manages cluster nodes, TLS, ACLs, gossip keys, secret handling, snapshots, upgrades, service integrations and availability.
- Product website: https://www.hashicorp.com/en/products/consul
- 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 Consul Enterprise, not HCP Consul and not the separately licensed Community Edition. The validated designs require a commercial license and production security material, including TLS certificates, ACL configuration and gossip encryption. Protect bootstrap tokens and snapshot storage and validate the selected module release before deployment. HCSEC-2026-49 and 50 cover a health-check registration authorization bypass and a consul-k8s cross-namespace ACL binding-rule bypass. Fixed builds are Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18.

Consul Enterprise is proprietary commercial software. The separate Community Edition and HCP service do not determine this entry's entitlement.

Consul Enterprise runs persistent server and client agents on customer infrastructure with consensus state, snapshots and network dependencies.


### Category fit

- backend-platforms: Provides service discovery, configuration, connectivity and service-mesh control for distributed application platforms.

- devops: Automates service networking, health discovery and policy across deployment environments.

### Deployment boundaries


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

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

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


### Cloud deployment evidence

- Consul Enterprise Terraform deployments on AWS, Azure and Google Cloud (aws, azure, gcp): https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform
  HashiCorp provides validated Terraform deployment paths for Consul Enterprise in customer AWS, Azure and Google Cloud environments. Customers manage the deployed cluster, security material and backups.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Deploy Consul Enterprise using Terraform on AWS, Azure and Google Cloud: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform

- Consul pricing and editions: https://www.hashicorp.com/en/products/consul/pricing

- HCSEC-2026-49: https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914

- HCSEC-2026-50: https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915

### Licensing sources

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

### Infrastructure sources

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


### 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. The reviewed Enterprise pricing and Terraform deployment establish the licensed product, but not a current Consul Enterprise-specific Marketplace offer. HCP procurement is separate. Scope: Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/consul/pricing (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Consul Enterprise price/edition material did not establish qualifying Marketplace charges and commitment treatment for the buyer agreement. Scope: Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/consul/pricing (reviewed 2026-11-17).

- Single sign-on: Edition-dependent. The OIDC authentication method requires self-managed Consul Enterprise 1.8.0+. It supports browser-based UI/CLI login through a configured IdP, with ACL tokens and claim mappings. Scope: Self-managed Consul Enterprise, not HCP account SSO. Source: https://developer.hashicorp.com/consul/docs/secure/acl/auth-method/oidc (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Enterprise OIDC exchanges claims for ACL tokens; it does not establish a SCIM user/group lifecycle endpoint. HCP account SCIM was excluded. Scope: Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment. Source: https://developer.hashicorp.com/consul/docs/secure/acl/auth-method/oidc (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed HashiCorp Consul 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/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- Security controls: Documented. The Enterprise Terraform workflow configures cluster secrets and cloud permissions. Apply ACL, TLS/gossip, backup and key-management requirements rather than treating provisioning completion as a security review. Current advisory review: HCSEC-2026-49 and 50 cover health-check registration and consul-k8s cross-namespace authorization bypasses. Upgrade Consul Enterprise and consul-k8s to the applicable fixed or later builds. Scope: Consul Enterprise deployment controls Fixed in Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18.. Source: https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914 (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform. Supporting source: HCSEC-2026-50 — https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915.

- 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 Consul Enterprise reporting; not blanket isolation of integrations. Source: https://developer.hashicorp.com/consul/docs/enterprise/license/reporting (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The validated design provides provider-specific Terraform deployment for Consul Enterprise on AWS, Azure and Google Cloud. Configure the licence, secrets, network access and snapshot storage before production use. Scope: Self-managed Enterprise validated Terraform deployment. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. The design deploys a fault-tolerant Consul server cluster; service count, agent placement, traffic, mesh gateways and availability requirements determine total capacity. Human-user count does not size the service mesh. Scope: Consul topology and workload boundary. Source: https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- License pricing: Documented. Consul Enterprise is proprietary commercial software. The separate Community Edition and HCP service do not determine this entry's entitlement. Scope: HashiCorp Consul Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.hashicorp.com/en/products/consul/pricing (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Specify service/agent count, mesh traffic, gateways and Enterprise server topology. Human users and 1 TB application data do not size a Consul service mesh. 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/consul/installation-guide/deploying-consul-using-terraform (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The vendor release API identifies 2.1.0+ent as a supported, non-prerelease Enterprise build. Its record was created 2026-10-22. 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/consul/latest?license_class=enterprise (reviewed 2026-11-17). Supporting source: Versioned Enterprise binaries and checksums — https://releases.hashicorp.com/consul/2.1.0+ent/.




### Security and lifecycle reviews

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

- HashiCorp Consul authorization-bypass updates (security-advisory): HCSEC-2026-49 and 50 cover health-check registration and consul-k8s cross-namespace authorization bypasses. Scope: Fixed in Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18. Conditions: Health-check registration permissions and Kubernetes component ACL binding rules determine exposure. Action: Upgrade Consul Enterprise and consul-k8s to the applicable fixed or later builds. Source: https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914; reviewed 2026-11-18. Supporting source: HCSEC-2026-50 — https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915.




## Hasura GraphQL Engine v2

GraphQL API engine that exposes connected databases through permission-aware application APIs.

- Listing: https://launchinyourcloud.com/directory/hasura-graphql-engine/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream open-source GraphQL Engine components. Default distributions can include separately licensed enterprise components; -ce images contain open-source components.
- Licensing model: open-source
- Installation: Deploy the documented v2 Docker Compose setup; select the versioned -ce image when only open-source components are required.
- Architecture: Customer-operated API engine with PostgreSQL metadata database and connected data sources
- Operations: Customer manages engine and metadata storage, database access, admin secrets, authorization, TLS, and coordinated engine/database upgrades.
- Product website: https://hasura.io/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-16

### Scope and qualifications

This listing is specifically for the self-operated v2 engine, not Hasura Cloud or DDN. Authentication webhooks, remote schemas, event handlers and database destinations can cross account boundaries. GraphQL Engine v2.51.6 and v2.50.9 fix source-catalog initialization and upgrades when PostgreSQL 15.15, 16.11, 17.7, or 18 and later enforce replica identity for INSERT ... ON CONFLICT DO UPDATE in a logical-replication publication. Upgrade GraphQL Engine before PostgreSQL. For older engine versions, the documented workaround is ALTER TABLE hdb_catalog.hdb_source_catalog_version REPLICA IDENTITY FULL on every data source, repeated whenever a new source is added.

Apache License 2.0 for upstream open-source GraphQL Engine components. Default distributions can include separately licensed enterprise components; -ce images contain open-source components. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated API engine with PostgreSQL metadata database and connected data sources. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. Coordinate PostgreSQL patch upgrades with the GraphQL Engine version. Older engines can break source-catalog initialization or logical replication after upgrading to PostgreSQL 15.15, 16.11, 17.7, or 18 and later.


### Category fit

- backend-platforms: Database-backed GraphQL API layer with authorization, subscriptions and configured remote actions. It does not supply a complete standalone application database or identity provider.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://hasura.io/docs/2.0/deployment/deployment-guides/azure-container-instances-postgres/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://hasura.io/docs/2.0/deployment/deployment-guides/google-kubernetes-engine-cloud-sql/ (checked 2026-11-12). 


### Cloud deployment evidence

- Hasura GraphQL Engine on Azure Container Instances (azure): https://hasura.io/docs/2.0/deployment/deployment-guides/azure-container-instances-postgres/
  The v2 project documentation deploys the GraphQL Engine container on Azure Container Instances with PostgreSQL. Review secrets, database access and production hardening; Hasura Cloud regions are not used as evidence.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Hasura GraphQL Engine on Google Kubernetes Engine (gcp): https://hasura.io/docs/2.0/deployment/deployment-guides/google-kubernetes-engine-cloud-sql/
  The v2 project documentation deploys the GraphQL Engine on GKE with Cloud SQL. This establishes application hosting in the customer project, not just connectivity to a Google-hosted database.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The upstream v2 release stream includes current security maintenance. Hasura documents a long-running developer community, public community calls and community contributions around GraphQL Engine.

Reviewed 2026-11-10.

- Current GraphQL Engine release maintenance: https://github.com/hasura/graphql-engine/releases

- Public developer community and calls: https://hasura.io/help/

- GraphQL Engine contribution history: https://hasura.io/blog/call-for-open-source-contributions

### Sources

- Official installation and runtime: https://hasura.io/docs/2.0/deployment/deployment-guides/docker/

- Upstream project and capabilities: https://github.com/hasura/graphql-engine

- Current upstream license: https://raw.githubusercontent.com/hasura/graphql-engine/master/LICENSE

- Official image and -ce licensing distinction: https://hub.docker.com/r/hasura/graphql-engine/

- v2 capabilities and Community Edition: https://hasura.io/docs/2.0/index/

- Hasura v2.51.6 PostgreSQL upgrade-order fix: https://github.com/hasura/graphql-engine/releases/tag/v2.51.6

- Hasura v2.50.9 PostgreSQL upgrade-order fix: https://github.com/hasura/graphql-engine/releases/tag/v2.50.9

### Licensing sources

- https://raw.githubusercontent.com/hasura/graphql-engine/master/LICENSE

### Infrastructure sources

- https://hasura.io/docs/2.0/deployment/deployment-guides/docker/

- https://github.com/hasura/graphql-engine/releases/tag/v2.51.6

- https://github.com/hasura/graphql-engine/releases/tag/v2.50.9


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 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. Self-hosted Enterprise Console can integrate ADFS SAML through Dex from v2.25.0, with a valid license key. Console authentication is separate from GraphQL API JWT/webhook authorization and is not a CE entitlement. Scope: Hasura v2 Enterprise administrative Console, not every API client. Source: https://hasura.io/docs/2.0/enterprise/sso/adfs/ (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 v2 guide links an upstream Compose manifest with PostgreSQL metadata storage. Select the appropriate community/commercial image and set administrator/database credentials rather than exposing the defaults. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://hasura.io/docs/2.0/deployment/deployment-guides/docker/ (reviewed 2026-11-14). Deployment artifact: https://raw.githubusercontent.com/hasura/graphql-engine/master/install-manifests/docker-compose/docker-compose.yaml. Artifact reference: master v2 example (moving).

- Minimum footprint / sizing: Sources checked — unresolved. The v2 production checklist and subscription-tuning guide require database connection/concurrency planning and CPU/memory monitoring, but do not establish a numeric whole-stack minimum. Query complexity, live subscriptions, metadata/source databases and replicas determine capacity. Old tutorial VM allocations or Cloud auto-scaling are not a current 100-user, 1 TB HA sizing guarantee. Scope: Hasura v2 production and tuning guidance; current workload-specific compute/storage sizing remains unconfirmed. Source: https://hasura.io/docs/2.0/deployment/production-checklist/ (reviewed 2026-11-20). Supporting source: v2 subscription saturation and performance tuning — https://hasura.io/docs/2.0/subscriptions/observability-and-performance/.

- License pricing: Documented. The v2.51.6 open-source GraphQL Engine core is Apache-2.0 licensed. Hasura v2 Enterprise has separate commercial entitlements; the official image distribution distinguishes the -ce variant from images that include Enterprise components. Enterprise Console SSO is not granted by the CE licence, and DDN/Cloud pricing is not a self-hosted v2 quote. Scope: GraphQL Engine v2 CE versus commercial image/features; not Hasura v3 DDN. Source: https://github.com/hasura/graphql-engine/blob/v2.51.6/LICENSE (reviewed 2026-11-20). Supporting source: Official image and CE variant distinction — https://hub.docker.com/r/hasura/graphql-engine/. Supporting source: Self-Hosted Enterprise v2 scope — https://hasura.io/docs/2.0/enterprise/overview/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v2.51.6, published 2026-11-11. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream hasura/graphql-engine release record; commercial editions and deployment packages may differ. Source: https://github.com/hasura/graphql-engine/releases/tag/v2.51.6 (reviewed 2026-11-14).







## Kong Gateway Self-Managed

Open-source and commercial self-managed API gateway with supported AWS, Azure and Google Cloud deployment platforms.

- Listing: https://launchinyourcloud.com/directory/kong-gateway/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the open-source core; Enterprise features use separate commercial licensing.
- Licensing model: open-source
- Installation: Official Linux packages, Docker images, Helm chart or Kubernetes Operator
- Architecture: Gateway proxy and administration services in database-backed, database-less or hybrid topologies on customer compute or Kubernetes
- Operations: Customer manages compute or Kubernetes, datastore topology, networking, TLS, plugins, secrets, configuration, monitoring, backups, scaling and upgrades. Enterprise users also manage subscription and license configuration.
- Product website: https://www.konghq.com/products/kong-gateway
- Source review: 2026-11-19; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers self-managed Kong Gateway, not Kong Konnect or Kong-managed cloud gateways. The open-source core and Enterprise distribution have different features and support entitlements. Validate the selected topology, package version, datastore mode and cloud-platform compatibility before deployment. Kong Gateway Enterprise 3.16.0.2 fixes authentication-context cache leakage, request-callout cache keys, SAML audience validation, Admin API RBAC self-protection, unsafe forwarded paths, and LLM usage-counter SQL injection. This Enterprise plugin guidance is separate from the listing's community/core 3.9.4 snapshot; exact SAML Audience and issuer matching may require configuration changes. Kong Gateway community/core 3.9.5 applies nginx patches for CVE-2026-123007 and CVE-2026-123633, HTTP/2 memory-corruption and use-after-free vulnerabilities. Upgrade the applicable maintained core line and separately follow Enterprise guidance for the installed edition.

Kong Gateway's upstream core is Apache-2.0 licensed. Kong Gateway Enterprise adds separately licensed proprietary features and commercial support.

Kong Gateway runs persistent proxy and administration processes on Linux, Docker or Kubernetes, with an optional customer-managed datastore and control-plane services.


### Category fit

- backend-platforms: Provides a self-managed API gateway for routing, authentication, traffic control, transformation, observability and extensible API policies.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.konghq.com/gateway/version-support-policy/ (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.konghq.com/gateway/version-support-policy/ (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.konghq.com/gateway/version-support-policy/ (checked 2026-11-16). 


### Cloud deployment evidence

- Kong Gateway supported public-cloud deployment platforms (aws, azure, gcp): https://developer.konghq.com/gateway/version-support-policy/
  Kong lists supported self-managed deployment platforms including Amazon EKS, ECS and Fargate; Azure AKS, Container Instances and Container Apps; and Google GKE, GKE Autopilot and Cloud Run. Edition-specific support entitlements should be confirmed separately.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Community and maintenance

Kong maintains public upstream releases and contributor history for the Apache-licensed Kong Gateway core. This evidence establishes continuing project activity, not Enterprise support or support for every listed cloud topology.

Reviewed 2026-11-16.

- Kong Gateway releases: https://github.com/Kong/kong/releases

- Kong Gateway contributor history: https://github.com/Kong/kong/graphs/contributors

### Sources

- Install Kong Gateway: https://developer.konghq.com/gateway/install/

- Kong Gateway public-cloud platform support: https://developer.konghq.com/gateway/version-support-policy/

- Kong Gateway edition comparison: https://www.konghq.com/products/kong-gateway

- Kong Gateway Apache 2.0 license: https://github.com/Kong/kong/blob/master/LICENSE

- Kong Gateway releases: https://github.com/Kong/kong/releases

- Kong Gateway contributor history: https://github.com/Kong/kong/graphs/contributors

- Kong Gateway Enterprise changelog: https://developer.konghq.com/gateway/changelog/

- Kong Gateway 3.9.5 release: https://github.com/Kong/kong/releases/tag/3.9.5

- Kong Gateway 3.9.5 changelog: https://github.com/Kong/kong/blob/release/3.9.x/CHANGELOG.md#395

- nginx security advisories: https://nginx.org/en/security_advisories.html

### Licensing sources

- https://github.com/Kong/kong/blob/master/LICENSE

- https://www.konghq.com/products/kong-gateway

### Infrastructure sources

- https://developer.konghq.com/gateway/install/

- https://developer.konghq.com/gateway/version-support-policy/


### Buyer diligence


Research coverage: 9/12 fields (75%); 8 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: Sources checked — unresolved. Kong’s Gateway policy names AWS, Azure and Google Cloud marketplaces. The reviewed policy does not identify exact offers, publishers, delivery types or packaged versions. Confirm those records and the Gateway entitlement before treating a Konnect or third-party offer as the self-managed product. Scope: Vendor Marketplace availability statement; exact self-managed offer records remain unverified. Source: https://developer.konghq.com/gateway/version-support-policy/ (reviewed 2026-11-16).

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. Self-managed Kong Manager can authenticate administrators through OIDC using the Enterprise-only OpenID Connect plugin. The v3.6+ procedure uses kong.conf and differs from Konnect SSO and from authenticating API consumers. Scope: Kong Gateway Enterprise Manager, v3.6+; not the Apache-licensed core alone. Source: https://developer.konghq.com/gateway/kong-manager/openid-connect/ (reviewed 2026-11-16). Supporting source: Enterprise-only OIDC plugin — https://developer.konghq.com/plugins/openid-connect/.

- SCIM provisioning: Not researched.

- Compliance attestations: Documented. Kong explicitly says the Gateway FIPS package has not itself been submitted to a NIST testing lab for product validation. Its use of a validated cryptographic provider must not be presented as a certificate for the entire customer deployment. Scope: Vendor-stated product-versus-module validation boundary; not an assessment of other certifications. Source: https://developer.konghq.com/gateway/fips-support/ (reviewed 2026-11-16).

- Security controls: Edition-dependent. Enterprise v3.14+ offers an AMD64 FIPS 140-3 package using approved algorithms and an OpenSSL FIPS provider. Kong explicitly distinguishes its compliant package from a product submitted for NIST validation; configure the supported distribution and FIPS mode. Current advisory review: Enterprise 3.16.0.2 fixes cache leakage across authentication contexts, request-callout cache keys, SAML audience validation, Admin API RBAC bypass, unsafe forwarded paths, and LLM usage-counter SQL injection. Upgrade Enterprise deployments to 3.16.0.2 or later and retest exact SAML Audience and issuer matching. Current review: Community/core 3.9.5 applies nginx fixes for CVE-2026-123007 and CVE-2026-123633, HTTP/2 memory-corruption and use-after-free vulnerabilities. Upgrade the applicable maintained branch; do not substitute the 3.9 core tag for separately versioned Enterprise guidance. Scope: Kong Gateway community/core 3.9 line with affected nginx HTTP/2 code. Source: https://github.com/Kong/kong/blob/release/3.9.x/CHANGELOG.md#395 (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://developer.konghq.com/gateway/changelog/. Supporting source: Prior security-controls source — https://developer.konghq.com/gateway/fips-support/. Supporting source: 3.9.5 release — https://github.com/Kong/kong/releases/tag/3.9.5. Supporting source: nginx advisories — https://nginx.org/en/security_advisories.html.

- Air-gapped operation: Documented. Self-managed Enterprise license validation does not require network connectivity: each node reads a supplied license at startup. This resolves offline license validation, but does not certify every plugin, integration, image source or update workflow as disconnected. Scope: Enterprise offline license validation only; not Konnect or blanket end-to-end air-gap certification. Source: https://developer.konghq.com/gateway/entities/license/ (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. The upstream Kong Helm chart deploys Gateway on Kubernetes. Select compatible chart, image and database settings; an Enterprise image/license does not follow automatically from installing the chart. Scope: Kong Gateway chart; open-source and Enterprise image entitlements differ. Source: https://developer.konghq.com/gateway/install/ (reviewed 2026-11-16). Deployment artifact: https://github.com/Kong/charts/tree/main/charts/kong. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. Kong publishes workload-based sizing rather than a fixed universal minimum. Its small per-node starting example is 1–2 CPU cores and 2–4 GB RAM; database/Redis, enabled plugins, configuration size and traffic must be sized separately. Scope: Self-managed Gateway sizing guidelines, v3.4+; example resources are not throughput guarantees. Source: https://developer.konghq.com/gateway/resource-sizing-guidelines/ (reviewed 2026-11-16).

- License pricing: Documented. Kong Gateway's upstream core is Apache-2.0 licensed. Kong Gateway Enterprise adds separately licensed proprietary features and commercial support. Scope: Kong Gateway Self-Managed: software license terms; infrastructure and operating costs are separate. Source: https://github.com/Kong/kong/blob/master/LICENSE (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://www.konghq.com/products/kong-gateway.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Kong Gateway community/core 3.9.5 was published November 19, 2026. It applies nginx patches for CVE-2026-123007 and CVE-2026-123633. Enterprise releases, plugins and cloud packages remain separately versioned. Scope: Upstream Kong Gateway community/core 3.9 line; Enterprise and deployment packages may differ. Source: https://github.com/Kong/kong/releases/tag/3.9.5 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/Kong/kong/releases/tag/3.9.4. Supporting source: 3.9.5 changelog — https://github.com/Kong/kong/blob/release/3.9.x/CHANGELOG.md#395.




### Security and lifecycle reviews

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

- Kong Gateway Enterprise 3.16.0.2 security patch (security-advisory): Enterprise 3.16.0.2 fixes cache leakage across authentication contexts, request-callout cache keys, SAML audience validation, Admin API RBAC bypass, unsafe forwarded paths, and LLM usage-counter SQL injection. Scope: Kong Gateway Enterprise plugins and features; the listing's separate community/core release snapshot is not replaced by this Enterprise build. Conditions: Applicability depends on the enabled Enterprise authentication, cache, SAML, RBAC, forwarded-path, and LLM plugins. Action: Upgrade Enterprise deployments to 3.16.0.2 or later and retest exact SAML Audience and issuer matching. Source: https://developer.konghq.com/gateway/changelog/; reviewed 2026-11-18.

- Kong Gateway 3.9.5 nginx HTTP/2 fixes (security-advisory): Kong Gateway community/core 3.9.5 applies nginx patches for CVE-2026-123007 and CVE-2026-123633. Scope: Kong Gateway community/core 3.9 line with affected nginx HTTP/2 code; Enterprise and other branches are separately versioned. Conditions: HTTP/2 exposure and the exact bundled nginx build determine applicability. Action: Upgrade the applicable maintained core branch and separately follow Enterprise guidance for the installed edition. Source: https://github.com/Kong/kong/blob/release/3.9.x/CHANGELOG.md#395; reviewed 2026-11-19. Supporting source: Kong Gateway 3.9.5 — https://github.com/Kong/kong/releases/tag/3.9.5. Supporting source: nginx security advisories — https://nginx.org/en/security_advisories.html.




## Medplum Self-Hosted

Open-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/medplum-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: hybrid
- License: Apache-2.0 Community software; an optional commercial Enterprise Self-Hosted support plan is separate.
- Licensing model: open-source
- Installation: AWS CDK, or Terraform and Helm on Azure AKS or Google GKE
- Architecture: Containerized API and web application with PostgreSQL, cache, object storage, secrets and load-balancing or CDN services
- Operations: Customer operates the cloud infrastructure and application lifecycle; Medplum offers an Enterprise Self-Hosted support plan.
- Product website: https://www.medplum.com/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The official AWS, Azure and GCP guides deploy both backend and frontend components. Enterprise support is optional and does not change the Apache-2.0 classification of the selected Community software; validate healthcare compliance scope and local operating controls separately. The v5.2.17 release strips ClientApplication secrets from auth/me responses and changes on-behalf-of identity and delegation handling. Upgrade a compatible server/application bundle to v5.2.17 or later and test identity/delegation flows. Assess whether application secrets were exposed and rotate them where appropriate.

The Community software is Apache-2.0; Enterprise Self-Hosted support is a separate commercial service.

The deployment combines customer Kubernetes or container compute with managed database, cache, storage, secrets and network services.


### Category fit

- backend-platforms: Provides a FHIR datastore, APIs, OAuth identity, application SDKs and clinical backend services on customer infrastructure.

- workflow-automation: Medplum Bots, cron jobs, subscriptions and triggers automate clinical and operational workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.medplum.com/docs/self-hosting/install-on-azure (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.medplum.com/docs/self-hosting/install-on-gcp (checked 2026-11-19). 


### Cloud deployment evidence

- Complete Medplum installation in a customer AWS account (aws): https://www.medplum.com/docs/self-hosting/install-on-aws
  Medplum describes a complete production-ready installation in the customer's AWS environment and deploys the application and supporting AWS resources with CDK.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Production-validated Medplum deployment on Azure (azure): https://www.medplum.com/docs/self-hosting/install-on-azure
  The official Terraform and Helm workflow deploys Medplum into the customer's Azure subscription with AKS, PostgreSQL, Redis, storage, gateway and frontend resources.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Production-validated Medplum deployment on Google Cloud (gcp): https://www.medplum.com/docs/self-hosting/install-on-gcp
  The official Terraform and Helm workflow deploys Medplum into the customer's Google Cloud project with GKE, Cloud SQL, Redis, storage and frontend resources.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes codyebberson, mattwiller, ThatOneBro, 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/medplum/medplum/graphs/contributors

- Reviewed upstream application release: https://github.com/medplum/medplum/releases/tag/v5.2.17

### Sources

- Medplum production installation on AWS: https://www.medplum.com/docs/self-hosting/install-on-aws

- Medplum production installation on Azure: https://www.medplum.com/docs/self-hosting/install-on-azure

- Medplum production installation on Google Cloud: https://www.medplum.com/docs/self-hosting/install-on-gcp

- Medplum open-source terms: https://www.medplum.com/open-source

- Medplum self-hosted support plans: https://www.medplum.com/pricing

- Reviewed deployment artifact reference: https://github.com/medplum/medplum/tree/v5.2.17/packages/cdk

- Buyer evidence: release: https://github.com/medplum/medplum/releases/tag/v5.2.17

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

### Licensing sources

- https://www.medplum.com/open-source

- https://www.medplum.com/pricing

### Infrastructure sources

- https://www.medplum.com/docs/self-hosting/install-on-aws

- https://www.medplum.com/docs/self-hosting/install-on-azure

- https://www.medplum.com/docs/self-hosting/install-on-gcp


### 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: 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: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (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: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-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: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (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: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (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: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Security controls: Edition-dependent. The production guides deploy secrets, TLS termination, identity and private data services within the customer's cloud environment. Healthcare compliance still depends on the buyer's configuration, agreements, audit controls and operating procedures. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (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: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The tagged @medplum/cdk 5.2.17 source supplies the AWS CDK application used by the installation guide. The CLI, server image, frontend build and Azure/GCP Terraform/Helm packages remain separately selected artifacts; one CDK tag does not pin the whole stack. Scope: Medplum Community AWS IaC source, independently versioned from other deployment components. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19). Deployment artifact: https://github.com/medplum/medplum/tree/v5.2.17/packages/cdk. Artifact reference: @medplum/cdk 5.2.17 at upstream tag v5.2.17.

- 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: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- License pricing: Documented. Medplum Community is Apache-2.0 and can be self-hosted without a software license fee; the Enterprise Self-Hosted support plan is separately commercial. Infrastructure, support and healthcare compliance work are separate. Scope: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/open-source (reviewed 2026-11-19). Supporting source: Commercial support plans — https://www.medplum.com/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: Medplum Self-Hosted: selected customer-operated edition. Source: https://www.medplum.com/docs/self-hosting/install-on-aws (reviewed 2026-11-19).

- Release snapshot / cadence: Documented. The reviewed upstream v5.2.17 release was published 2026-11-11. Provider images and installer/component packages can differ; this snapshot does not promise a support window or future cadence. It includes authentication-response secret removal and on-behalf-of delegation hardening. Scope: Medplum Self-Hosted upstream application, independently versioned from provider packages. Source: https://github.com/medplum/medplum/releases/tag/v5.2.17 (reviewed 2026-11-19).




### Security and lifecycle reviews

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

- Medplum 5.2.17 authentication and delegation hardening (security-advisory): The v5.2.17 release strips ClientApplication secrets from auth/me responses and changes on-behalf-of identity and delegation handling. Scope: The authentication/me and delegation paths named in the v5.2.17 release; no universal affected-version range or CVE is asserted. Conditions: Applicability depends on the installed server build and use of the affected authentication/delegation endpoints. Action: Upgrade a compatible server/application bundle to v5.2.17 or later and test identity/delegation flows. Assess whether application secrets were exposed and rotate them where appropriate. Source: https://github.com/medplum/medplum/releases/tag/v5.2.17; reviewed 2026-11-19.




## Parse Server

Node.js application backend for data APIs, users, permissions and server-side application logic.

- Listing: https://launchinyourcloud.com/directory/parse-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, heroku
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Parse Server.
- Licensing model: open-source
- Installation: Install the upstream Node.js package and configure a supported MongoDB or PostgreSQL backend; run standalone or in an Express application.
- Architecture: Customer-operated Node.js backend with database and selected file/push integrations
- Operations: Customer manages Node services, database, class/object permissions, master keys, storage adapters, backups and upgrades.
- Product website: https://parseplatform.org/
- Source review: 2026-11-15; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Cloud Code is code executed in the server environment, not evidence of a vendor-operated cloud dependency. External storage, push-notification providers and third-party adapters have their own boundaries and licenses. GHSA-43rg-r2xr-q686 affects Parse Server versions before 9.12.0-alpha.3: creating a user with an existing user's auth data can return protected fields and hidden auth-adapter data, including MFA secrets and recovery codes. The advisory concerns the logging-in user's own object and requires that user's auth data or an applicable session token; it is not an arbitrary-user disclosure. Requests using the master or maintenance key are unaffected. There is no known workaround; Parse Server 8 is not patched, and the first published patched version is the 9.12.0-alpha.3 prerelease.

Apache License 2.0 for upstream Parse Server. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated Node.js backend with database and selected file/push integrations. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- backend-platforms: Application backend with data APIs, user authentication, access rules and server-side Cloud Code; database and file adapters are separately configured.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.parseplatform.org/parse-server/guide/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.parseplatform.org/parse-server/guide/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.parseplatform.org/parse-server/guide/ (checked 2026-11-12). 

- digitalocean: Boundary not confirmed; Customer-operated; control plane: not-assessed. Source: https://docs.parseplatform.org/parse-server/guide/ (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.parseplatform.org/parse-server/guide/ (checked 2026-11-12). 


### Cloud deployment evidence

- Parse Server cloud hosting options (aws, azure, gcp, digitalocean): https://docs.parseplatform.org/parse-server/guide/
  The upstream guide explicitly lists AWS, Google Cloud, Azure and DigitalOcean as hosts for the Parse Server application and provides installation guidance. This compatibility statement is separate from the DigitalOcean Spaces file adapter; select current Node.js/database versions and secure the deployed server.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Parse Server deployment on Heroku (heroku): https://docs.parseplatform.org/parse-server/guide/
  The upstream guide documents the Parse Server application on Heroku with MongoDB Atlas, including project configuration and validation. The application and database are in separate customer-controlled services; verify database network access, current runtime versions, secrets and production security.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Parse Community maintains an established public project, contributor review process and community forum. The current release stream includes November 2026 stable and LTS maintenance.

Reviewed 2026-11-10.

- Current stable and LTS releases: https://github.com/parse-community/parse-server/releases

- Community contribution process: https://github.com/parse-community/parse-server/blob/alpha/CONTRIBUTING.md

- Long-running community governance discussion: https://community.parseplatform.org/t/official-discord-server/1506

### Sources

- Official installation and runtime: https://docs.parseplatform.org/parse-server/guide/

- Upstream project and capabilities: https://github.com/parse-community/parse-server

- Current upstream license: https://raw.githubusercontent.com/parse-community/parse-server/alpha/LICENSE

- Security advisory GHSA-43rg-r2xr-q686: https://github.com/parse-community/parse-server/security/advisories/GHSA-43rg-r2xr-q686

### Licensing sources

- https://raw.githubusercontent.com/parse-community/parse-server/alpha/LICENSE

### Infrastructure sources

- https://docs.parseplatform.org/parse-server/guide/


### Buyer diligence


Research coverage: 6/12 fields (50%); 5 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: Documented. Parse Server supports external application-user authentication adapters; published 8.6.123 includes a Keycloak adapter that verifies provider tokens and returned user attributes. Configure the adapter/provider and map application users and permissions. This is an app-user backend capability, not proof of administrator SSO in Parse Dashboard, and does not establish SCIM. Scope: Published application-user federation adapter, distinct from separately deployed management dashboards. Source: https://github.com/parse-community/parse-server/blob/8.6.123/src/Adapters/Auth/keycloak.js (reviewed 2026-11-20). Supporting source: Official third-party authentication guide — https://github.com/parse-community/docs/blob/gh-pages/_includes/parse-server/third-party-auth.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. GHSA-43rg-r2xr-q686 can expose protected fields or hidden auth-adapter data in the logging-in user object, including MFA secrets and recovery codes. The advisory affects versions before 9.12.0-alpha.3 and identifies that prerelease as patched; Parse Server 8 is unpatched and no workaround is known. It requires the user auth data or applicable session-token conditions; master/maintenance-key requests are unaffected. Scope: Auth-data login response advisory reviewed November 15; not an arbitrary-user disclosure or a recommendation to adopt a prerelease without compatibility review. Source: https://github.com/parse-community/parse-server/security/advisories/GHSA-43rg-r2xr-q686 (reviewed 2026-11-15).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official server repository documents a Node.js application/package with a separately configured database. The server, dashboard and optional adapters have separate configuration and lifecycle; they are not one cloud appliance. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/parse-community/parse-server (reviewed 2026-11-14). Deployment artifact: https://github.com/parse-community/parse-server. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The published server identifies Node.js plus a supported database and configurable storage/live-query services, but not a workload-specific whole-system CPU/RAM/storage minimum. Size request/query rates, files, live subscriptions, database indexes and replication separately. A managed Parse hosting plan or tutorial allocation is not a self-hosted HA capacity guarantee. Scope: Published upstream runtime/dependency scope; complete production sizing remains unconfirmed. Source: https://github.com/parse-community/parse-server/blob/8.6.123/README.md (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: Parse Server 8.6.123 upstream application; not a managed Parse hosting plan; software terms only, excluding infrastructure and operations. Source: https://github.com/parse-community/parse-server/blob/8.6.123/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was 8.6.123, published 2026-11-09. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. The November 14 advisory GHSA-43rg-r2xr-q686 says Parse Server 8 is unpatched; this historical stable-release snapshot is not a secure-version recommendation. Scope: Upstream parse-community/parse-server release record; commercial editions and deployment packages may differ. Source: https://github.com/parse-community/parse-server/releases/tag/8.6.123 (reviewed 2026-11-15). Supporting source: Parse Server auth-data disclosure advisory — https://github.com/parse-community/parse-server/security/advisories/GHSA-43rg-r2xr-q686.







## Red Hat OpenShift Container Platform

Commercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.

- Listing: https://launchinyourcloud.com/directory/openshift-container-platform/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, ibm, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Red Hat OpenShift subscription.
- Licensing model: commercial-only
- Installation: OpenShift installation on AWS, Azure, Google Cloud or IBM Cloud; Assisted Installer Technology Preview on Alibaba Cloud
- Architecture: Customer-operated control-plane and worker machines with integrated operators, networking, storage and cluster services
- Operations: Customer manages cloud accounts, installer credentials, cluster machines, networking, identity, storage, registry, monitoring, backups, upgrades and Red Hat subscriptions.
- Product website: https://www.redhat.com/en/technologies/cloud-computing/openshift/container-platform
- 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 self-managed OpenShift Container Platform, not OpenShift Dedicated, ROSA, Azure Red Hat OpenShift or other managed services. The installer can provision infrastructure or integrate with customer-provisioned resources; review credential scope, subscription entitlements and lifecycle support before installation. The documented Alibaba Cloud Assisted Installer path is Technology Preview, outside Red Hat production SLAs and not recommended for production.

The selected self-managed OpenShift Container Platform edition is delivered through a commercial Red Hat subscription with entitlement and support terms.

OpenShift Container Platform runs persistent control-plane and worker nodes plus integrated cluster operators and storage services in the customer cloud.


### Category fit

- backend-platforms: Provides a self-managed Kubernetes application platform with integrated operators, developer workflows, networking, registry and cluster services.

- devops: Provides platform engineering, build, deployment and operations workflows for applications across customer-managed clusters.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview (checked 2026-11-15). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview (checked 2026-11-15). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview (checked 2026-11-15). 

- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_ibm_cloud/index (checked 2026-11-15). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_alibaba_cloud/index (checked 2026-11-15). 


### Cloud deployment evidence

- Self-managed OpenShift Container Platform on AWS, Azure or Google Cloud (aws, azure, gcp): https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview
  Red Hat's current installation overview explicitly distinguishes self-managed OpenShift Container Platform and documents installer- and user-provisioned installation paths on AWS, Microsoft Azure and Google Cloud using customer accounts and credentials.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- Self-managed OpenShift on IBM Cloud (ibm): https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_ibm_cloud/index
  Red Hat documents installer-provisioned deployment into customer IBM Cloud infrastructure, including account IAM/API keys, region selection, VPC networking and cluster administration.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed. Versions: 4.21.

- OpenShift on Alibaba Cloud — Technology Preview (alibaba): https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_alibaba_cloud/index
  Red Hat documents Assisted Installer deployment using customer Alibaba Cloud OSS images, ECS machines, VPC and DNS. This 4.21 path is Technology Preview: outside production SLAs, potentially incomplete and not recommended by Red Hat for production.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed. Versions: 4.21 Technology Preview.


### Sources

- OpenShift Container Platform 4.21 installation overview: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview

- Red Hat self-managed OpenShift subscription guide: https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide

- Self-managed OpenShift on IBM Cloud: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_ibm_cloud/index

- OpenShift on Alibaba Cloud — Technology Preview: https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_alibaba_cloud/index

### Licensing sources

- https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide

### Infrastructure sources

- https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview


### 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. The 4.20 Authentication Operator supports an external OIDC identity provider using authorization-code flow, discovery and mapped claims. This authenticates platform users; applications running on the cluster need their own identity integration. Review browser/CLI token workflows and selected provider compatibility. Scope: OpenShift 4.20 platform-user OIDC through the integrated OAuth service. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/observability/authentication_and_authorization/using-rbac (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Red Hat documents installer-provisioned AWS infrastructure using the release-matched openshift-install tool, install configuration, pull secret and cloud credentials. Customer-managed networking and permissions require review. Use the entitled Red Hat release distribution; the upstream installer source alone is not the product entitlement. Scope: OpenShift Container Platform 4.20 AWS installer path. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/installing_on_aws/installer-provisioned-infrastructure (reviewed 2026-11-20). Deployment artifact: https://github.com/openshift/installer. Artifact reference: Upstream installer source; obtain matching Red Hat release tooling and pull secret.

- Minimum footprint / sizing: Documented. The 4.20 AWS installation matrix gives bootstrap/control-plane minima of 4 vCPUs, 16 GB RAM and 100 GB disk, and compute nodes 2 vCPUs, 8 GB and 100 GB. A standard cluster uses multiple control-plane and worker machines; workload pods, operators, storage, bootstrap and HA capacity are additional. Scope: OpenShift 4.20 per-machine installation floors, not complete workload sizing. Source: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/installing_on_aws/installer-provisioned-infrastructure (reviewed 2026-11-20).

- License pricing: Documented. Self-managed subscriptions can use core-pairs or bare-metal nodes. On hyperscaler VMs, one core-pair covers four vCPUs; aggregate compute-node entitlement and support level must be sized. AI accelerators may require separate subscriptions. Obtain the applicable order and price. Scope: Red Hat self-managed OpenShift Container Platform subscription guide. Source: https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Sunbird RC (Registries & Credentials)

Open-source registries and verifiable-credential building blocks with named-cloud deployments.

- Listing: https://launchinyourcloud.com/directory/sunbird-rc/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: CloudFormation; Terraform; Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Sunbird RC services, database and identity/storage dependencies deployed by AWS CDK/Helm or GKE Terraform/Helm.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://rc.sunbird.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The product is a registry and credential platform. Municipal permitting or licence-renewal workflows require a separate configured application. Deployment packaging and individual registry-component releases have independent versions and licences.

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Sunbird RC services, database and identity/storage dependencies deployed by AWS CDK/Helm or GKE Terraform/Helm. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- backend-platforms: Open-source registries and verifiable-credential building blocks with named-cloud deployments.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/Sunbird-RC/aws-cdk/main/README.md (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/Sunbird-RC/gcp-devops/main/README.md (checked 2026-11-19). 


### Cloud deployment evidence

- AWS CDK (aws): https://raw.githubusercontent.com/Sunbird-RC/aws-cdk/main/README.md
  Sunbird RC services, database and identity/storage dependencies deployed by AWS CDK/Helm or GKE Terraform/Helm. The product is a registry and credential platform. Municipal permitting or licence-renewal workflows require a separate configured application. Deployment packaging and individual registry-component releases have independent versions and licences.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Terraform (gcp): https://raw.githubusercontent.com/Sunbird-RC/gcp-devops/main/README.md
  Sunbird RC services, database and identity/storage dependencies deployed by AWS CDK/Helm or GKE Terraform/Helm. The product is a registry and credential platform. Municipal permitting or licence-renewal workflows require a separate configured application. Deployment packaging and individual registry-component releases have independent versions and licences.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes tejash-jl, jyotsnaraveendran, dileepbapat, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/Sunbird-RC/sunbird-rc-core/graphs/contributors

- Upstream project: https://github.com/Sunbird-RC/sunbird-rc-core

### Sources

- AWS CDK: https://raw.githubusercontent.com/Sunbird-RC/aws-cdk/main/README.md

- GCP Terraform: https://raw.githubusercontent.com/Sunbird-RC/gcp-devops/main/README.md

- MIT: https://raw.githubusercontent.com/Sunbird-RC/sunbird-rc-core/main/LICENSE

- Releases: https://github.com/Sunbird-RC/sunbird-rc-core/releases

### Licensing sources

- https://raw.githubusercontent.com/Sunbird-RC/sunbird-rc-core/main/LICENSE

### Infrastructure sources

- https://raw.githubusercontent.com/Sunbird-RC/aws-cdk/main/README.md

- https://raw.githubusercontent.com/Sunbird-RC/gcp-devops/main/README.md


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 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: Sources checked — unresolved. The registry architecture uses Keycloak for authentication and its entity API documents token generation. A separate guide describes Meripehchaan SSO using a custom Keycloak 14-based build with configurable nonce validation. This does not confirm a currently supported, version-matched external IdP/browser-login path for every RC 2.1 deployment or frontend; verify broker/client, claims/roles and dependency compatibility. Scope: Documented custom integration and old dependency boundary; current release/installation-wide federation remains unconfirmed. Source: https://rc.sunbird.org/use/developer-guide/custom-keycloak-build (reviewed 2026-11-20). Supporting source: Registry identity component scope — https://rc.sunbird.org/registry/technical-overview/high-level-architecture. Supporting source: Entity authentication is a separate token path — https://rc.sunbird.org/registry/api-reference/registry/authenticating-as-an-entity.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The reviewed source supplies deployment configuration for Sunbird RC services, database and identity/storage dependencies deployed by AWS CDK/Helm or GKE Terraform/Helm. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: Reviewed deployment source collection; application images and infrastructure components have separate versions. Source: https://raw.githubusercontent.com/Sunbird-RC/aws-cdk/main/README.md (reviewed 2026-11-19). Deployment artifact: https://github.com/Sunbird-RC/aws-cdk/tree/main. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The official architecture and deployment recipes span registry, PostgreSQL, identity, search and optional workflow/queue services, but do not establish a current whole-stack CPU/RAM/storage minimum for this workload. Enabled services, registry records, credentials, query rate and replicas must be sized separately; a sample cluster is not a 1 TB HA capacity guarantee. Scope: Registry component scope; current numeric workload and HA sizing remains unconfirmed. Source: https://rc.sunbird.org/registry/technical-overview/high-level-architecture (reviewed 2026-11-20). Supporting source: Official AWS CDK/Helm deployment collection — https://github.com/Sunbird-RC/aws-cdk/blob/main/README.md.

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Sunbird RC (Registries & Credentials); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/Sunbird-RC/sunbird-rc-core/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v2.1.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Sunbird RC (Registries & Credentials) upstream application; verify compatibility with the selected package. Source: https://github.com/Sunbird-RC/sunbird-rc-core/releases/tag/v2.1.0 (reviewed 2026-11-19).







## Tyk Self-Managed

Commercial self-managed API management platform with documented AWS, Azure and Google Cloud deployments.

- Listing: https://launchinyourcloud.com/directory/tyk-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Tyk Self-Managed license required for the full platform; Gateway and Pump are available without that license.
- Licensing model: commercial-only
- Installation: Docker, Helm, Linux packages or Ansible on customer cloud infrastructure
- Architecture: Tyk Gateway, Dashboard, Pump and Developer Portal services with Redis and MongoDB or supported SQL data stores
- Operations: Customer manages hosts or Kubernetes, data stores, networking, TLS, identities, secrets, monitoring, backups, scaling, upgrades and the Tyk license.
- Product website: https://tyk.io/self-managed/
- Source review: 2026-11-16; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers the full Tyk Self-Managed platform, not Tyk Cloud or the standalone OSS Gateway. The Dashboard and other full-platform components require a commercial license, and Kubernetes installation requires a multi-node license. Provider tutorials are starter deployments rather than production sizing or high-availability guarantees.

The selected full Tyk Self-Managed platform requires a commercial license. Tyk Gateway and Pump are separately available as open-source components, but they do not constitute the complete listed platform.

Tyk Self-Managed runs persistent gateway, management, analytics, portal and database services on customer virtual machines or Kubernetes.


### Category fit

- backend-platforms: Provides a self-managed API gateway, management dashboard, analytics, developer portal and lifecycle controls for application APIs.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://tyk.io/deploying-on-aws/ (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://tyk.io/deploying-on-azure/ (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://tyk.io/deploying-on-gcp/ (checked 2026-11-16). 


### Cloud deployment evidence

- Tyk Self-Managed on AWS (aws): https://tyk.io/deploying-on-aws/
  Tyk documents creating an Amazon EC2 instance in the customer's AWS account and deploying the licensed Tyk Self-Managed platform with Docker.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- Tyk Self-Managed on Microsoft Azure (azure): https://tyk.io/deploying-on-azure/
  Tyk documents creating an Azure virtual machine and installing the Tyk Self-Managed stack with Docker in the customer's Azure environment.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- Tyk Self-Managed on Google Cloud (gcp): https://tyk.io/deploying-on-gcp/
  Tyk documents deploying its licensed Self-Managed platform on customer Google Cloud infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Install Tyk Self-Managed: https://tyk.io/docs/5.7/tyk-self-managed/

- Deploy Tyk on AWS: https://tyk.io/deploying-on-aws/

- Deploy Tyk on Azure: https://tyk.io/deploying-on-azure/

- Deploy Tyk on Google Cloud: https://tyk.io/deploying-on-gcp/

- Tyk Self-Managed product and pricing model: https://tyk.io/self-managed/

### Licensing sources

- https://tyk.io/docs/5.7/tyk-self-managed/

- https://tyk.io/self-managed/

### Infrastructure sources

- https://tyk.io/docs/5.7/tyk-self-managed/

- https://tyk.io/self-managed/


### Buyer diligence


Research coverage: 8/12 fields (67%); 8 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: Edition-dependent. The vendor AWS offer explicitly covers Cloud, Hybrid and Self-Managed. Its delivery classification is a SaaS contract and its public dimensions price Tyk Cloud; request terms that specifically license the self-managed deployment rather than treating it as an application AMI. Scope: Vendor-published AWS offer; procurement and application hosting are distinct. Source: https://aws.amazon.com/marketplace/pp/prodview-pboluroscnqro (reviewed 2026-11-16). Offer prodview-pboluroscnqro: Tyk Technologies Ltd; SaaS contract listing covering multiple deployment modes; self-managed terms require confirmation; https://aws.amazon.com/marketplace/pp/prodview-pboluroscnqro.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Tyk documents Dashboard SAML login through its internal Identity Broker with Okta, and an OIDC integration with AWS Cognito. Configure the identity profile and user mapping for the licensed Dashboard; API-consumer authentication is a separate concern. Scope: Commercial self-managed Dashboard with internal TIB. Source: https://support.tyk.io/hc/en-gb/articles/8568981329564-SSO-access-using-internal-TIB-SAML-OKTA (reviewed 2026-11-16). Supporting source: Dashboard OIDC with Cognito — https://support.tyk.io/hc/en-gb/articles/21540673255836--Setting-Up-SSO-with-AWS-Cognito-as-IdP-for-Tyk-Dashboard.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. The self-managed guide documents database-backed Dashboard audit-log storage from v5.7 onward. Operators must configure it, size the database and set retention/archive policies; example log sizes are workload assumptions, not a default retention guarantee or an attestation. Scope: Dashboard 5.7+ audit-log configuration and storage responsibilities. Source: https://tyk.io/docs/5.7/tyk-self-managed/ (reviewed 2026-11-16).

- Air-gapped operation: Documented. Tyk documents mirroring all chart images, packaging the Helm chart and installing from private registries; Linux deployments can use local package mirrors. Include optional-component images and arrange the correct commercial licenses and compatible versions. Scope: Documented self-managed offline installation workflow; selected integrations and license terms still require deployment-specific review. Source: https://tyk.io/docs/api-management/air-gapped-deployment (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. Tyk publishes the tyk-stack Helm chart and a trial-ready installation wrapper. Use the current tyk-charts repository; the former tyk-helm-chart repository is archived and deprecated. Select compatible chart/component versions, configure the required Dashboard license and production databases, and review trial defaults before production. Scope: Full self-managed platform; not the standalone open-source gateway. Source: https://tyk.io/docs/tyk-self-managed/install/kubernetes (reviewed 2026-11-16). Deployment artifact: https://github.com/TykTechnologies/tyk-charts/tree/main/tyk-stack. Artifact reference: main (moving branch; select compatible chart release). Supporting source: Archived chart repository and replacement notice — https://github.com/TykTechnologies/tyk-helm-chart.

- Minimum footprint / sizing: Documented. The current Kubernetes tutorial requires at least 4 GB RAM available to the cluster, but explicitly deploys a trial-ready configuration. Production sizing must include Gateway traffic, Redis, PostgreSQL and optional components; 4 GB is not a production capacity guarantee. Scope: Self-managed Kubernetes tutorial prerequisites, not a universal production minimum. Source: https://tyk.io/docs/tyk-self-managed/install/kubernetes (reviewed 2026-11-16).

- License pricing: Documented. The selected full Tyk Self-Managed platform requires a commercial license. Tyk Gateway and Pump are separately available as open-source components, but they do not constitute the complete listed platform. Scope: Tyk Self-Managed: software license terms; infrastructure and operating costs are separate. Source: https://tyk.io/docs/5.7/tyk-self-managed/ (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://tyk.io/self-managed/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed vendor policy lists 5.13 as its current LTS line. Gateway/Dashboard LTS receives 12 months of full support with eight-week patches, then 12 months of critical maintenance. Other components and non-LTS releases have separate compatibility and lifecycle rules. Scope: Published Gateway/Dashboard LTS policy as reviewed; not a single version or support guarantee for the entire platform. Source: https://tyk.io/docs/developer-support/release-types/long-term-support (reviewed 2026-11-16).






