Backend platforms on AWS

Application backends, authentication, APIs, storage and databases.

10 documented options on Amazon Web Services. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
Appwrite Self-HostedAWS, Azure, Google Cloud, DigitalOceanCustomer-operated
Servers / containers
Open Source / Open Core

BSD-3-Clause core; enterprise services and feature terms should be confirmed separately

Docker installer or official Kubernetes Helm chartCustomer configures the environment and handles software updates, scaling, security and backups.
Scope and evidence

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.

  • Appwrite self-hosting on 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.

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

  • Appwrite self-hosting on 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.

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

  • Appwrite self-hosting on 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.

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

  • Appwrite self-hosting on 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.

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

Cloud evidence reviewed 2026-11-12

Gravitee API Management Self-HostedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 Community Edition; Enterprise Edition requires a commercial license.

Official Helm chart, Docker deployment or Linux packages on customer infrastructureCustomer manages Kubernetes or hosts, databases, search, networking, ingress, TLS, identity, secrets, monitoring, backups, scaling, upgrades and any Enterprise license.
Scope and evidence

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 self-hosted deployment on EKS, AKS or GKE — 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.

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

Cloud evidence reviewed 2026-11-16

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

Commercial Consul Enterprise license required for the selected validated design.

HashiCorp Validated Design Terraform modules for AWS, Azure or Google CloudCustomer manages cluster nodes, TLS, ACLs, gossip keys, secret handling, snapshots, upgrades, service integrations and availability.
Scope and evidence

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 Terraform deployments on AWS, Azure and Google Cloud — 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.

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

Cloud evidence reviewed 2026-11-17

Kong Gateway Self-ManagedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for the open-source core; Enterprise features use separate commercial licensing.

Official Linux packages, Docker images, Helm chart or Kubernetes OperatorCustomer manages compute or Kubernetes, datastore topology, networking, TLS, plugins, secrets, configuration, monitoring, backups, scaling and upgrades. Enterprise users also manage subscription and license configuration.
Scope and evidence

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 supported public-cloud deployment platforms — 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.

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

Cloud evidence reviewed 2026-11-16

Medplum Self-HostedAWS, Azure, Google CloudCustomer-operated
Hybrid
Open Source / Open Core

Apache-2.0 Community software; an optional commercial Enterprise Self-Hosted support plan is separate.

AWS CDK, or Terraform and Helm on Azure AKS or Google GKECustomer operates the cloud infrastructure and application lifecycle; Medplum offers an Enterprise Self-Hosted support plan.
Scope and evidence

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.

  • Complete Medplum installation in a customer AWS account — Medplum describes a complete production-ready installation in the customer's AWS environment and deploys the application and supporting AWS resources with CDK.

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

  • Production-validated Medplum deployment 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.

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

  • Production-validated Medplum deployment on Google Cloud — The official Terraform and Helm workflow deploys Medplum into the customer's Google Cloud project with GKE, Cloud SQL, Redis, storage and frontend resources.

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

Cloud evidence reviewed 2026-11-19

Parse ServerAWS, Azure, Google Cloud, DigitalOcean, HerokuCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for upstream Parse Server.

Install the upstream Node.js package and configure a supported MongoDB or PostgreSQL backend; run standalone or in an Express application.Customer manages Node services, database, class/object permissions, master keys, storage adapters, backups and upgrades.
Scope and evidence

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.

  • Parse Server cloud hosting options — 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.

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

  • Parse Server deployment on Heroku — 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.

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

Cloud evidence reviewed 2026-11-12

Red Hat OpenShift Container PlatformAWS, Azure, Google Cloud, IBM Cloud, Alibaba CloudCustomer-operated
Servers / containers
Commercial Only

Commercial Red Hat OpenShift subscription.

OpenShift installation on AWS, Azure, Google Cloud or IBM Cloud; Assisted Installer Technology Preview on Alibaba CloudCustomer manages cloud accounts, installer credentials, cluster machines, networking, identity, storage, registry, monitoring, backups, upgrades and Red Hat subscriptions.
Scope and evidence

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.

  • Self-managed OpenShift Container Platform on AWS, Azure or Google Cloud — 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.

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

  • Self-managed OpenShift on IBM Cloud — Red Hat documents installer-provisioned deployment into customer IBM Cloud infrastructure, including account IAM/API keys, region selection, VPC networking and cluster administration.

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

  • OpenShift on Alibaba Cloud — Technology Preview — 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.

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

Cloud evidence reviewed 2026-11-15

Sunbird RC (Registries & Credentials)AWS, Google CloudCustomer-operated
Servers / containers
Open Source / Open Core

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

CloudFormation; Terraform; Helm / Kubernetes operator; Kubernetes manifestsCustomer 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.
Scope and evidence

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.

  • AWS CDK — 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.

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

  • GCP Terraform — 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.

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

Cloud evidence reviewed 2026-11-19

Supabase Self-HostedAWS, Railway, VultrCustomer-operated
Servers / containers
Open Source / Open Core

Open-source components with individual licenses; the Supabase platform repository uses Apache-2.0

Official Docker Compose distribution, community AWS CloudFormation template, Railway project template, or Vultr Marketplace server imageCustomer manages provisioning, hardening, database maintenance, scaling, backups and monitoring; self-hosting is community-supported.
Scope and evidence

The self-hosted stack runs as one project. Managed-platform capabilities such as branching, managed backups/PITR and the Management API are not included. The Supabase CLI development stack is not a hardened production deployment. Review each bundled component license.

  • Supabase community AWS CloudFormation/CDK deployment — This project-community template deploys Supabase containers on ECS Fargate with Aurora and Studio on Amplify Hosting. It is an alternative to the upstream Compose layout and does not support pg_graphql/GraphQL. Harden Studio access, review feature differences and operate the AWS resources yourself; this is not managed Supabase.

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

  • Self-host Supabase in a Railway project — Railway documents a community template for PostgreSQL, authentication, REST, storage, and Studio. The services communicate over private networking in the customer’s Railway project. Railway operates the underlying platform.

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

  • Deploy the Supabase Marketplace application on Vultr Compute — Vultr documents selecting the Supabase application while provisioning a Compute server in the customer’s account. The customer chooses the region and plan and administers the installed stack.

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

Cloud evidence reviewed 2026-11-21

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

Commercial Tyk Self-Managed license required for the full platform; Gateway and Pump are available without that license.

Docker, Helm, Linux packages or Ansible on customer cloud infrastructureCustomer manages hosts or Kubernetes, data stores, networking, TLS, identities, secrets, monitoring, backups, scaling, upgrades and the Tyk license.
Scope and evidence

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.

  • Tyk Self-Managed 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.

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

  • Tyk Self-Managed on Microsoft Azure — Tyk documents creating an Azure virtual machine and installing the Tyk Self-Managed stack with Docker in the customer's Azure environment.

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

  • Tyk Self-Managed on Google Cloud — Tyk documents deploying its licensed Self-Managed platform on customer Google Cloud infrastructure.

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

Cloud evidence reviewed 2026-11-16

Deployment evidence and category fit

Appwrite Self-Hosted

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

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.

  • Appwrite self-hosting on AWS ↗

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

    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.

Cloud evidence reviewed 2026-11-12. Full listing and qualifications

Gravitee API Management Self-Hosted

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

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 self-hosted deployment on EKS, AKS or GKE ↗

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

    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.

Cloud evidence reviewed 2026-11-16. Full listing and qualifications

HashiCorp Consul Enterprise

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

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 Terraform deployments on AWS, Azure and Google Cloud ↗

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

    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.

Cloud evidence reviewed 2026-11-17. Full listing and qualifications

Kong Gateway Self-Managed

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

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 supported public-cloud deployment platforms ↗

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

    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.

Cloud evidence reviewed 2026-11-16. Full listing and qualifications

Medplum Self-Hosted

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

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.

  • Complete Medplum installation in a customer AWS account ↗

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

    Medplum describes a complete production-ready installation in the customer's AWS environment and deploys the application and supporting AWS resources with CDK.

Cloud evidence reviewed 2026-11-19. Full listing and qualifications

Parse Server

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

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.

  • Parse Server cloud hosting options ↗

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

    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.

Cloud evidence reviewed 2026-11-12. Full listing and qualifications

Red Hat OpenShift Container Platform

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

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.

  • Self-managed OpenShift Container Platform on AWS, Azure or Google Cloud ↗

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

    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.

Cloud evidence reviewed 2026-11-15. Full listing and qualifications

Sunbird RC (Registries & Credentials)

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

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.

  • AWS CDK ↗

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

    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.

Cloud evidence reviewed 2026-11-19. Full listing and qualifications

Supabase Self-Hosted

PostgreSQL-based application backend with authentication, APIs, storage, realtime and functions; self-hosting does not include every managed-platform feature.

The self-hosted stack runs as one project. Managed-platform capabilities such as branching, managed backups/PITR and the Management API are not included. The Supabase CLI development stack is not a hardened production deployment. Review each bundled component license.

  • Supabase community AWS CloudFormation/CDK deployment ↗

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

    This project-community template deploys Supabase containers on ECS Fargate with Aurora and Studio on Amplify Hosting. It is an alternative to the upstream Compose layout and does not support pg_graphql/GraphQL. Harden Studio access, review feature differences and operate the AWS resources yourself; this is not managed Supabase.

Cloud evidence reviewed 2026-11-21. Full listing and qualifications

Tyk Self-Managed

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

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.

  • Tyk Self-Managed on AWS ↗

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

    Tyk documents creating an Amazon EC2 instance in the customer's AWS account and deploying the licensed Tyk Self-Managed platform with Docker.

Cloud evidence reviewed 2026-11-16. Full listing and qualifications

Deployment and procurement checks

Private offers
AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge. Provider source ↗ · Reviewed 2026-11-14
Private connectivity
PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service. Provider source ↗ · Reviewed 2026-11-14
Cross-account operations
Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access. Provider source ↗ · Reviewed 2026-11-14
Government environments
AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there. Provider source ↗ · Reviewed 2026-11-14

For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.

Plan this deployment

Account boundary: AWS account. Access: IAM roles and policies. Network: VPC.

Provider documentation ↗ · Guidance reviewed 2026-11-10. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.

Compare this category across clouds · Search these listings · Compare 2–4 listings