{"catalog":"https://launchinyourcloud.com/api/v1/catalog.json","catalogRevision":"170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde","category":{"description":"Business automation, integrations, scripts and API workflows.","id":"workflow-automation","name":"Workflow automation"},"cloud":{"boundary":"Google Cloud project","classificationReview":{"reviewed":"2026-11-20","source":"https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects","summary":"Navigation group for the documented infrastructure offering; read each application path for its actual account boundary."},"defaultBoundary":"cloud-account","diligence":[{"reviewed":"2026-11-14","source":"https://docs.cloud.google.com/marketplace/docs/offers/discover-private-offers","summary":"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.","topic":"Private offers"},{"reviewed":"2026-11-14","source":"https://docs.cloud.google.com/vpc/docs/private-service-connect","summary":"Private Service Connect connects VPC consumers to supported managed or producer services. Confirm the actual product endpoint and network/DNS architecture.","topic":"Private connectivity"},{"reviewed":"2026-11-14","source":"https://docs.cloud.google.com/iam/docs/workload-identity-federation","summary":"Workload Identity Federation can grant external workloads scoped Google Cloud access without long-lived service-account keys. Validate the trust configuration and exact roles.","topic":"External workload access"},{"reviewed":"2026-11-14","source":"https://docs.cloud.google.com/assured-workloads/docs/overview","summary":"Assured Workloads applies control packages for residency and access boundaries. Confirm supported services, regions and the product deployment; it is not automatic product certification.","topic":"Regulated environments"}],"id":"gcp","identity":"IAM policies and service accounts","install":"Terraform, optionally using Infrastructure Manager for resource provisioning; deploy the application separately.","name":"Google Cloud","network":"VPC network","providerType":"cloud-infrastructure","reviewed":"2026-11-10","short":"Google Cloud","source":"https://docs.cloud.google.com/infrastructure-manager/docs/overview"},"kind":"cloud-category","listings":[{"architecture":"Application and worker containers with deployment-specific database and queue services","categories":["workflow-automation"],"category":"Workflow automation","categoryFit":{"workflow-automation":"Builds event-driven business automations from triggers and actions, with customer-operated workers and integrations."},"cloudEvidence":[{"clouds":["aws"],"notes":"The vendor-maintained Pulumi template deploys Activepieces into the operator's AWS account and can create VPC, compute, RDS PostgreSQL, Redis, load-balancing, ECR and Route 53 resources. Review template defaults, image versions, IAM permissions, secrets and production hardening.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Activepieces deployment into a customer AWS account with Pulumi","url":"https://www.activepieces.com/docs/install/options/aws","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The vendor documents running the Activepieces application container on a Google Cloud VM or instance group. Its example uses SQLite and in-memory Redis; confirm compatibility with the selected release and follow current production database, queue and security requirements.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Google Cloud VM deployment","url":"https://www.activepieces.com/docs/install/options/gcp","vendorSupport":"not-assessed"},{"clouds":["railway"],"notes":"The vendor documents a Railway template that deploys the Activepieces application with PostgreSQL and Redis into the operator's project. Railway manages the underlying infrastructure; the operator configures secrets, application access, persistence and backups. This is separate from Activepieces Cloud and does not establish ownership of an underlying hyperscaler account.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Railway project deployment","url":"https://www.activepieces.com/docs/install/options/railway","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-13","clouds":["aws","gcp","railway"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Self-hosted workflow automation platform with integrations, triggers, actions and worker execution.","diligence":{"footprint":{"reviewed":"2026-11-14","scope":"Activepieces Compose baseline; not guaranteed workflow throughput","source":"https://www.activepieces.com/docs/install/options/docker-compose","status":"documented","summary":"The Compose guide requires at least 2 vCPU and 4 GB RAM. Workflow concurrency and the default worker replica count require workload-specific sizing; the hobbyist embedded-database install is a different topology."},"iac":{"artifactRef":"repository default branch (moving; select matching application release)","artifactUrl":"https://github.com/activepieces/activepieces","reviewed":"2026-11-14","scope":"Compose deployment; not the embedded-database hobbyist mode","source":"https://www.activepieces.com/docs/install/options/docker-compose","status":"documented","summary":"The official Compose workflow generates secrets and runs application/worker/database/cache services. Its worker replica count needs sizing and encryption keys need backup; the hobbyist single-container mode has different limits."},"licensePricing":{"reviewed":"2026-11-20","scope":"Self-hosted core versus commercially entitled enterprise features; no hosted-plan price used as a self-hosted quote","source":"https://github.com/activepieces/activepieces/blob/0.93.0/docs/about/license.mdx","status":"documented","summary":"The 0.93.0 licensing guide identifies the core as MIT-licensed and enterprise/cloud feature code as commercially licensed. Using those enterprise features in a self-hosted installation requires an Activepieces licence obtained from sales."},"release":{"releasePublishedAt":"2026-11-08T14:30:22Z","releaseTag":"0.93.0","reviewed":"2026-11-14","scope":"Upstream activepieces/activepieces release record; commercial editions and deployment packages may differ","source":"https://github.com/activepieces/activepieces/releases/tag/0.93.0","status":"documented","summary":"The publisher-designated GitHub release checked was 0.93.0, published 2026-11-08. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Self-hosted Enterprise SAML; not the free hobbyist mode","source":"https://www.activepieces.com/docs/admin-guide/guides/sso","status":"documented","summary":"The paid SSO guide explicitly documents SAML for self-hosted Enterprise. Company-domain verification and identity-provider setup are required; Google sign-in has separate self-hosted credentials."}},"id":"activepieces","infrastructure":["servers"],"infrastructureNotes":"The documented deployments run long-lived application and worker containers with persistent data services. Railway operates the underlying platform; managed databases and load balancers do not make the application runtime serverless.","infrastructureReviewed":"2026-11-13","infrastructureSources":["https://www.activepieces.com/docs/install/overview","https://www.activepieces.com/docs/install/options/aws","https://www.activepieces.com/docs/install/options/gcp","https://www.activepieces.com/docs/install/options/railway"],"install":"Official AWS Pulumi stack, Google Cloud VM guide or Railway template; Docker Compose and Kubernetes/Helm are also documented.","installMethods":["pulumi","helm","docker","platform-template"],"kind":"product","license":"MIT-licensed Community Edition core; enterprise and cloud feature directories use commercial terms.","licenseModel":"open-source","licenseModelNotes":"Activepieces Community Edition core is MIT licensed. Enterprise and cloud feature directories use a commercial license; confirm the selected edition and entitlements.","licenseModelSources":["https://github.com/activepieces/activepieces/blob/main/LICENSE","https://github.com/activepieces/activepieces/blob/main/docs/about/license.mdx"],"licenseReviewed":"2026-11-13","model":"Fully in your account","modelLabel":"Customer-operated","name":"Activepieces Self-Hosted","notes":"This entry covers self-hosted Activepieces, not Activepieces Cloud. The AWS template can provision RDS PostgreSQL, Redis, load balancing and Route 53 integration. The Google Cloud guide uses a VM/container example with SQLite and in-memory Redis; confirm release compatibility and use the current production database and queue requirements. Railway deploys into a customer project on platform-managed infrastructure. Enterprise features require a separate license.","operations":"Customer manages application configuration, secrets, integrations, backups and upgrades. AWS and Google Cloud paths require customer-managed infrastructure; Railway operates the underlying platform within the customer project.","publisher":false,"reviewed":"2026-11-13","sources":[{"title":"Self-hosting and installation options","url":"https://www.activepieces.com/docs/install/overview"},{"title":"Official AWS Pulumi deployment","url":"https://www.activepieces.com/docs/install/options/aws"},{"title":"Community and enterprise licensing","url":"https://github.com/activepieces/activepieces/blob/main/docs/about/license.mdx"},{"title":"Google Cloud VM deployment","url":"https://www.activepieces.com/docs/install/options/gcp"},{"title":"Railway project deployment","url":"https://www.activepieces.com/docs/install/options/railway"}],"url":"https://launchinyourcloud.com/directory/activepieces/","website":"https://www.activepieces.com/"},{"advisories":[{"action":"Use the notice's component-specific fixed versions, ensure Keycloak uses a rebuilt image, or remove the named trust roots where Camunda documents that workaround. Apply the Web Modeler fixes separately.","conditions":"Component, branch, bundled Java trust store, Keycloak image build date, and HTTP/2 configuration determine applicability.","disclosedOn":"2026-11-04","id":"camunda-november-2026-security-notices","listingIds":["camunda-self-managed"],"reviewed":"2026-11-18","scope":"Notice 80 affects listed Orchestration Cluster, Connectors, Management Identity, Hub, Web Modeler, Zeebe, Operate, Tasklist, Optimize, Console, and Keycloak builds. Notices 81 and 82 have separate Web Modeler ranges and fixes.","source":"https://docs.camunda.io/docs/reference/notices/","summary":"Camunda Notices 80–82 cover critical eMudhra trust-store exposure plus Web Modeler HTTP parser and custom HTTP/2 denial-of-service issues.","title":"Camunda November 2026 component security notices","type":"security-advisory"},{"action":"Apply the branch-specific Optimize release or a fixed JDK, restart affected processes and verify the mitigation.","conditions":"Camunda states Optimize decodes untrusted Base64 while then-current base and customer JDKs lacked the upstream fix.","disclosedOn":"2026-11-19","id":"camunda-optimize-cve-2026-114938","listingIds":["camunda-self-managed"],"reviewed":"2026-11-19","scope":"Camunda Optimize 8.6 and 8.7 on affected x86-64 AVX-512 JDKs; other components require separate assessment.","source":"https://github.com/camunda/camunda/releases/tag/8.7.32-optimize","summary":"Optimize 8.6.30 and 8.7.32 disable the affected AVX-512 Base64 intrinsic for CVE-2026-114938.","supportingSources":[{"title":"Optimize 8.6.30","url":"https://github.com/camunda/camunda/releases/tag/8.6.30-optimize"},{"title":"OpenJDK fixed versions","url":"https://openjdk.org/groups/vulnerability/advisories/2026-11-17"}],"title":"Camunda Optimize CVE-2026-114938 mitigation","type":"security-advisory"}],"architecture":"Customer-operated orchestration cluster, connectors, identity services and persistent secondary storage","categories":["workflow-automation","workflow-orchestration"],"category":"Workflow orchestration","categoryFit":{"workflow-automation":"Executes modeled business processes, user tasks, connectors and decision-driven automation in customer-operated infrastructure.","workflow-orchestration":"Coordinates durable process instances, service tasks and distributed workers using the Camunda orchestration cluster."},"cloudEvidence":[{"clouds":["aws"],"notes":"Camunda provides current EKS infrastructure and Helm installation guidance for a customer AWS account, including managed persistence dependencies.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"Camunda 8 Self-Managed on Amazon EKS","url":"https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/amazon/amazon-eks/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Camunda provides current AKS and Helm guidance for a customer Azure subscription, with provider-specific reference infrastructure.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"Camunda 8 Self-Managed on Microsoft AKS","url":"https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/azure/microsoft-aks/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Camunda documents its Self-Managed Helm deployment and Google Cloud-specific GKE configuration.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"Camunda 8 Self-Managed on Google GKE","url":"https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/gcp/google-gke/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-14","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Commercial self-managed process orchestration and workflow automation platform.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Current manual host floor plus versioned application/component planning; not a throughput guarantee","source":"https://docs.camunda.io/docs/self-managed/reference-architecture/manual/","status":"documented","summary":"The manual-deployment reference suggests at least 2 CPU cores, 4 GB RAM and 32 GB SSD per host, then requires workload benchmarking. The 8.10 resource-planning guide separately sizes brokers, secondary storage, identity and optional Optimize; retention and replicas materially change storage. Per-host minima are not a complete 1 TB HA platform bill of materials.","supportingSources":[{"title":"Self-Managed resource planning and component baselines","url":"https://docs.camunda.io/docs/components/best-practices/architecture/sizing-self-managed/"}]},"iac":{"artifactRef":"repository default branch (moving; select a supported chart release)","artifactUrl":"https://github.com/camunda/camunda-platform-helm","reviewed":"2026-11-14","scope":"Camunda 8 Self-Managed chart family; not a SaaS subscription","source":"https://github.com/camunda/camunda-platform-helm","status":"documented","summary":"Camunda publishes Self-Managed Helm charts. Select a chart/application version combination supported by the deployment guide and account for external services, storage and licensed components."},"licensePricing":{"reviewed":"2026-11-20","scope":"Current Camunda 8 component licensing and self-managed production boundary","source":"https://docs.camunda.io/docs/reference/licenses/","status":"documented","summary":"Camunda 8.6+ compiled platform components use proprietary Self-Managed Non-Production or Enterprise terms; production requires the Enterprise licence. Some SDKs/connectors and Desktop Modeler have different source licences. The free development option is not a production grant; obtain the component-specific self-managed quote and support terms separately from Cloud and infrastructure.","supportingSources":[{"title":"Self-Managed development versus licensed production pricing","url":"https://camunda.com/pricing/"}]},"securityControls":{"reviewed":"2026-11-19","scope":"Camunda Optimize 8.6 and 8.7 on affected x86-64 AVX-512 JDKs; other Camunda components require separate assessment","source":"https://github.com/camunda/camunda/releases/tag/8.7.32-optimize","status":"documented","summary":"Current advisory review: Camunda Notices 80–82 cover critical eMudhra trust-store exposure plus Web Modeler HTTP parser and custom HTTP/2 denial-of-service issues. Use the notice's component-specific fixed versions, ensure Keycloak uses a rebuilt image, or remove the named trust roots where Camunda documents that workaround. Apply the Web Modeler fixes separately. Current review: Optimize 8.6.30 and 8.7.32 mitigate CVE-2026-114938, an AVX-512 Base64 intrinsic memory-corruption issue, by forcing -XX:-UseBASE64Intrinsics. Camunda says Optimize decodes untrusted Base64 while then-current base and customer JDKs lacked the upstream fix. Use the branch-specific Optimize release or a fixed JDK 21.0.13.1 or 25.0.5.1 and restart affected processes.","supportingSources":[{"title":"Prior security-controls source","url":"https://docs.camunda.io/docs/reference/notices/"},{"title":"Optimize 8.6.30 mitigation","url":"https://github.com/camunda/camunda/releases/tag/8.6.30-optimize"},{"title":"OpenJDK fixed versions","url":"https://openjdk.org/groups/vulnerability/advisories/2026-11-17"}]},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Current Camunda 8 Orchestration Cluster authentication; not automatic uniform SSO for every component/version","source":"https://docs.camunda.io/docs/self-managed/concepts/authentication/authentication-to-orchestration-cluster/","status":"documented","summary":"The current Orchestration Cluster guide documents OIDC for Web UI users and OAuth2 API access through an external IdP, with identity mapping and role/authorization configuration. Basic authentication is a different default. Management Identity/Hub and older component releases have separate configurations; configure the selected self-managed version and licensed components."}},"id":"camunda-self-managed","infrastructure":["servers"],"infrastructureNotes":"The documented production topology uses persistent Kubernetes workloads plus databases or search services. Managed provider dependencies do not make the Camunda runtime serverless.","infrastructureReviewed":"2026-11-14","infrastructureSources":["https://docs.camunda.io/docs/self-managed/reference-architecture/kubernetes/","https://docs.camunda.io/docs/reference/supported-environments/"],"install":"Official Helm charts on EKS, AKS or GKE","installMethods":["helm"],"kind":"product","license":"Commercial Enterprise license required for production; unlicensed use is limited to non-production conditions.","licenseModel":"commercial-only","licenseModelNotes":"Camunda documents unlicensed Self-Managed components as non-production and requires a Camunda Self-Managed Enterprise Edition license for production use.","licenseModelSources":["https://docs.camunda.io/docs/self-managed/components/orchestration-cluster/core-settings/configuration/licensing/"],"licenseReviewed":"2026-11-14","model":"Fully in your account","modelLabel":"Customer-operated","name":"Camunda 8 Self-Managed","notes":"This entry covers Camunda 8 Self-Managed, not Camunda SaaS. Match Helm and component versions, size persistent storage for the workload and review external database/search dependencies. A valid Enterprise license is required for production use. Camunda Notice 80 covers critical eMudhra trust-store issues, including CVE-2026-114820, across multiple 8.6–8.10 components; fixed versions differ by component, and Keycloak requires a sufficiently recent rebuilt image. Notices 81 and 82 also patch Web Modeler HTTP parser and custom HTTP/2 denial-of-service paths. Follow the component matrix instead of treating one Helm version as a universal fix. Camunda Optimize 8.6.30 and 8.7.32 mitigate CVE-2026-114938 by disabling the affected AVX-512 Base64 intrinsic. Apply the branch-specific Optimize update, or move to a fixed JDK when supplied, and do not treat a single Helm version as a universal Camunda fix.","operations":"Customer manages Kubernetes, supported databases or search services, storage, ingress, identity, backups, scaling and upgrades.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Supported self-managed environments","url":"https://docs.camunda.io/docs/reference/supported-environments/"},{"title":"Amazon EKS deployment","url":"https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/amazon/amazon-eks/"},{"title":"Microsoft AKS deployment","url":"https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/azure/microsoft-aks/"},{"title":"Google GKE deployment","url":"https://docs.camunda.io/docs/self-managed/deployment/helm/cloud-providers/gcp/google-gke/"},{"title":"Self-managed licensing","url":"https://docs.camunda.io/docs/self-managed/components/orchestration-cluster/core-settings/configuration/licensing/"},{"title":"Camunda security notices","url":"https://docs.camunda.io/docs/reference/notices/"},{"title":"Camunda Optimize 8.6.30","url":"https://github.com/camunda/camunda/releases/tag/8.6.30-optimize"},{"title":"Camunda Optimize 8.7.32","url":"https://github.com/camunda/camunda/releases/tag/8.7.32-optimize"},{"title":"OpenJDK November 2026 advisory","url":"https://openjdk.org/groups/vulnerability/advisories/2026-11-17"}],"url":"https://launchinyourcloud.com/directory/camunda-self-managed/","website":"https://camunda.com/platform/"},{"architecture":"Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP.","categories":["workflow-automation","internal-tools"],"category":"Workflow automation","categoryFit":{"internal-tools":"Commercial rules and workflow platform with provider-specific container deployments.","workflow-automation":"Commercial rules and workflow platform with provider-specific container deployments."},"cloudEvidence":[{"clouds":["aws"],"notes":"Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"AWS ECS Deploy","url":"https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Azure Deploy","url":"https://documentation.decisions.com/docs/deploying-containers-on-azure-1.md","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"GCP Deploy","url":"https://documentation.decisions.com/docs/deploying-containers-on-gcp-1.md","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Commercial rules and workflow platform with provider-specific container deployments.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"General self-hosted application-server guidance; not a cost estimate or validated reference-workload HA design","source":"https://documentation.decisions.com/docs/installation-requirements","status":"documented","summary":"The installation requirements list an AWS production example using t3.xlarge (4 vCPU, 16 GB RAM) and 100 GB storage. Database requirements are separate, and enterprise/HA topology and workload can require larger or multiple servers. This server example does not include 1 TB of application data."},"iac":{"reviewed":"2026-11-20","scope":"Licensed self-hosted installer/container workflow; application, database and HA setup are separate","source":"https://documentation.decisions.com/docs/deploying-containers-on-aws-1","status":"documented","summary":"The installation guide provides the v10.x installer and supported database setup. The ECS guide documents task definitions using the vendor container image, environment variables and persistent file storage; it is a console recipe rather than a supplied Terraform/CloudFormation stack. Pin a compatible released image rather than copying latest.","supportingSources":[{"title":"v10 installation guide and release download","url":"https://documentation.decisions.com/version-10/docs/installation-guide"}]},"licensePricing":{"reviewed":"2026-11-19","scope":"Decisions Self-Hosted; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://decisions.com/terms-of-use","status":"documented","summary":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Self-hosted application user SSO; module/release and IdP configuration required","source":"https://documentation.decisions.com/docs/saml","status":"documented","summary":"The vendor documents SAML login through an installed identity-provider module, certificate and IdP settings, with accounts updated before enforcement and at least one working admin SSO account. It warns that Active Directory Sync cannot run simultaneously with SAML/OpenID SSO modules."}},"id":"decisions-platform","infrastructure":["servers"],"infrastructureNotes":"Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md","https://documentation.decisions.com/docs/deploying-containers-on-azure-1.md","https://documentation.decisions.com/docs/deploying-containers-on-gcp-1.md"],"install":"Docker / Compose; Kubernetes manifests","installMethods":["docker","kubernetes"],"kind":"platform","license":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.","licenseModel":"commercial-only","licenseModelNotes":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.","licenseModelSources":["https://decisions.com/terms-of-use","https://documentation.decisions.com/docs/licensing-a-container.md"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Decisions Self-Hosted","notes":"The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.","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.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"AWS ECS Deploy","url":"https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md"},{"title":"Azure Deploy","url":"https://documentation.decisions.com/docs/deploying-containers-on-azure-1.md"},{"title":"GCP Deploy","url":"https://documentation.decisions.com/docs/deploying-containers-on-gcp-1.md"},{"title":"AWS EKS Deploy","url":"https://documentation.decisions.com/docs/deploying-an-aws-kubernetes-cluster.md"},{"title":"Azure AKS Deploy","url":"https://documentation.decisions.com/docs/deploying-azure-kubernetes-services-aks.md"},{"title":"Financial Services","url":"https://decisions.com/solutions/industry/financial-services"},{"title":"Terms of Use","url":"https://decisions.com/terms-of-use"},{"title":"Container Licensing","url":"https://documentation.decisions.com/docs/licensing-a-container.md"},{"title":"v10.4.x Release Notes","url":"https://documentation.decisions.com/v99/docs/version-104x-release-notes.md"}],"url":"https://launchinyourcloud.com/directory/decisions-platform/","website":"https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md"},{"advisories":[{"action":"Upgrade to 3.3.8 or later, restart every Ruby process and verify the active runtime.","conditions":"Every web and background process still using the affected Ruby runtime remains exposed; the advisory documents no workaround.","disclosedOn":"2026-11-19","id":"docuseal-ghsa-78g6-f52x-q3jx","listingIds":["docuseal"],"reviewed":"2026-11-19","scope":"DocuSeal versions earlier than 3.3.8.","source":"https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx","summary":"GHSA-78g6-f52x-q3jx allows one unauthenticated request to crash a Ruby application worker before routing or authentication.","supportingSources":[{"title":"3.3.8 security release","url":"https://github.com/docusealco/docuseal/releases/tag/3.3.8"}],"title":"DocuSeal 3.3.8 unauthenticated denial-of-service fix","type":"security-advisory"}],"alternativeTo":[{"id":"docusign","reviewed":"2026-11-16","source":"https://www.docuseal.com/","summary":"The publisher positions DocuSeal as an alternative for document-signing workflows."},{"id":"pandadoc","reviewed":"2026-11-16","source":"https://www.docuseal.com/","summary":"The publisher positions DocuSeal as an alternative for document-signing workflows."}],"architecture":"Rails web application and document-processing jobs with a database, attachments and signing configuration","categories":["workflow-automation"],"category":"Workflow automation","categoryFit":{"workflow-automation":"Automates document form filling, signature collection and completion workflows through a self-hosted application, API and webhooks. This does not establish full contract lifecycle management or regulated-record compliance."},"cloudEvidence":[{"clouds":["aws"],"notes":"DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.","reviewed":"2026-11-13","sourceType":"marketplace-offer","title":"Cloudron EC2 AMI and application installation","url":"https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"deploymentBoundaries":{"digitalocean":"platform-workspace"},"notes":"DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.","reviewed":"2026-11-13","sourceType":"marketplace-offer","title":"Cloudron customer Droplet deployment","url":"https://marketplace.digitalocean.com/apps/cloudron","vendorSupport":"not-assessed"},{"clouds":["linode"],"notes":"DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.","reviewed":"2026-11-13","sourceType":"provider-guide","title":"Cloudron customer Linode deployment","url":"https://www.linode.com/docs/marketplace-docs/guides/cloudron/","vendorSupport":"not-assessed"},{"clouds":["vultr"],"notes":"DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established. Cloudron currently names the Vultr Marketplace offer; use current Cloudron OS requirements, not the historical Ubuntu 20.04 tutorial.","reviewed":"2026-11-13","sourceType":"package-platform-documentation","title":"Cloudron named-provider installation and Marketplace availability","url":"https://docs.cloudron.io/installation/","vendorSupport":"not-assessed"},{"clouds":["hostinger"],"notes":"DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.","reviewed":"2026-11-13","sourceType":"provider-guide","title":"Hostinger customer VPS Cloudron template","url":"https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/","vendorSupport":"not-assessed"},{"clouds":["lumadock"],"notes":"DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.","reviewed":"2026-11-13","sourceType":"provider-guide","title":"LumaDock customer VPS Cloudron template","url":"https://lumadock.com/vps-hosting/cloudron","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Installs the actual application container in a customer Azure resource group with PostgreSQL and Blob Storage. Configure secrets, storage and production database network restrictions rather than retaining permissive example firewall rules.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Vendor Azure Web Apps deployment","url":"https://www.docuseal.com/docs/deploying-docuseal-on-azure-web-apps","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Installs the actual application container in a customer project with Cloud SQL and Google Cloud Storage. Configure keys, bucket access and production database network restrictions. This is application hosting, not a storage-only integration.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Vendor Google Cloud Run deployment","url":"https://www.docuseal.com/docs/deploying-docuseal-on-google-cloud-run","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"deploymentBoundaries":{"digitalocean":"platform-workspace"},"notes":"Creates the vendor application container and PostgreSQL in a customer App Platform account. Database persistence does not preserve attachments: configure durable object storage and back up both. Pin the application image and configure real mail.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Vendor DigitalOcean application specification","url":"https://github.com/docusealco/docuseal-digitalocean/blob/master/.do/deploy.template.yaml","vendorSupport":"not-assessed"},{"clouds":["railway"],"notes":"Installs the vendor application and PostgreSQL in a customer Railway project. The database volume alone does not preserve attachments: configure an application volume at the image data path or durable object storage. Review secrets, SMTP and backups.","reviewed":"2026-11-13","sourceType":"community-template","title":"Vendor-linked Railway application template","url":"https://railway.com/deploy/IGoDnc","vendorSupport":"not-assessed"},{"clouds":["heroku"],"notes":"Creates a container application and PostgreSQL add-on in a customer Heroku account. Dyno filesystems are ephemeral: configure durable object storage for documents, retain encryption keys and back up the database.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Vendor Heroku application specification","url":"https://github.com/docusealco/docuseal-heroku/blob/master/app.json","vendorSupport":"not-assessed"},{"clouds":["render"],"notes":"Creates the application and PostgreSQL in a customer Render account. The example selects free services; Render does not recommend those for production and the free database expires after 30 days. Use suitable paid compute/database, durable attachment storage, secrets and working outbound mail.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Vendor Render application blueprint","url":"https://github.com/docusealco/docuseal-render/blob/master/render.yaml","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-13","clouds":["aws","digitalocean","linode","vultr","hostinger","lumadock","azure","gcp","railway","heroku","render"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Contributor history","url":"https://github.com/docusealco/docuseal/graphs/contributors"},{"title":"Reviewed maintenance and security release 3.3.8","url":"https://github.com/docusealco/docuseal/releases/tag/3.3.8"},{"title":"Release history","url":"https://www.docuseal.com/changelog"}],"summary":"The current core has sustained work by two principal maintainers, external code contributions and continuing security releases. Public contributor and release histories establish ongoing maintenance; they do not independently validate every paid feature or customer deployment."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"platform-workspace","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[1,8],"operator":"customer"},{"boundary":"cloud-account","cloud":"linode","controlPlane":"not-assessed","evidence":[2],"operator":"customer"},{"boundary":"cloud-account","cloud":"vultr","controlPlane":"not-assessed","evidence":[3],"operator":"customer"},{"boundary":"vps-account","cloud":"hostinger","controlPlane":"not-assessed","evidence":[4],"operator":"customer"},{"boundary":"vps-account","cloud":"lumadock","controlPlane":"not-assessed","evidence":[5],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[6],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[7],"operator":"customer"},{"boundary":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[9],"operator":"customer"},{"boundary":"platform-workspace","cloud":"heroku","controlPlane":"not-assessed","evidence":[10],"operator":"customer"},{"boundary":"platform-workspace","cloud":"render","controlPlane":"not-assessed","evidence":[11],"operator":"customer"}],"description":"Self-hosted document forms and electronic-signature workflows with API and webhook integration.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Approximate document-based examples, not a 1-TB or HA installation baseline","source":"https://www.docuseal.com/docs/on-premises-server-requirements","status":"documented","summary":"The vendor sizes examples for 10,000 signed documents. For one-off templates with one signer and 500-KB average files it lists 1 vCPU, 1 GB RAM and 12 GB disk; larger files, reused templates and multiple signers have different storage needs. PostgreSQL is recommended for heavy production/API use."},"iac":{"artifactRef":"master (moving branch)","artifactUrl":"https://github.com/docusealco/docuseal/blob/master/docker-compose.yml","reviewed":"2026-11-14","scope":"Upstream Compose example; not a hardened production baseline","source":"https://github.com/docusealco/docuseal/blob/master/docker-compose.yml","status":"documented","summary":"The upstream Compose example defines DocuSeal, PostgreSQL and Caddy with persistent storage. It uses moving application/proxy images and example database credentials; pin compatible versions and replace credentials before deployment."},"licensePricing":{"reviewed":"2026-11-20","scope":"Self-hosted core versus paid Pro; advertised amounts are not a 100-user total or infrastructure cost","source":"https://www.docuseal.com/on-premises","status":"documented","summary":"The 3.3.8 core is AGPLv3. The on-premises page offers free self-hosting and separately prices Pro at $240 per user/year plus $0.20 per document signed through API or embedding. Confirm billable user/document definitions, currency and current terms before quoting.","supportingSources":[{"title":"Versioned core licence","url":"https://github.com/docusealco/docuseal/blob/3.3.8/LICENSE"}]},"marketplace":{"availability":"available","offers":[{"cloud":"aws","delivery":"Platform AMI; external Cloudron license","id":"prodview-aep3gt5elubci","publisher":"Cloudron UG","url":"https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci","version":"Cloudron 10.0.5 (platform, not application)"}],"reviewed":"2026-11-14","scope":"Cloudron platform plus separate application package","source":"https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci","status":"documented","summary":"AWS delivery uses Cloudron’s platform AMI and a separate application package. Cloudron publishes the platform offer; application versions, licensing and support are separate.","supportingSources":[{"title":"Cloudron application package","url":"https://docs.cloudron.io/packages/docuseal/"}]},"release":{"releasePublishedAt":"2026-11-19T10:05:21Z","releaseTag":"3.3.8","reviewed":"2026-11-19","scope":"Upstream DocuSeal core release; separately packaged provider images may lag","source":"https://github.com/docusealco/docuseal/releases/tag/3.3.8","status":"documented","summary":"DocuSeal 3.3.8 was published November 19, 2026. It updates Ruby to address GHSA-78g6-f52x-q3jx; all web and background processes must be restarted so the fixed runtime is active.","supportingSources":[{"title":"Prior reviewed release context","url":"https://github.com/docusealco/docuseal/releases/tag/3.3.7"},{"title":"Security advisory","url":"https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx"}]},"securityControls":{"reviewed":"2026-11-19","scope":"DocuSeal versions earlier than 3.3.8","source":"https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx","status":"documented","summary":"GHSA-78g6-f52x-q3jx affects DocuSeal before 3.3.8. A single unauthenticated request can crash a Ruby application worker before routing or authentication. No workaround is documented; update and restart every web and background process.","supportingSources":[{"title":"3.3.8 security release","url":"https://github.com/docusealco/docuseal/releases/tag/3.3.8"}]},"sso":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Self-hosted Pro","source":"https://www.docuseal.com/on-premises","status":"documented","summary":"SAML SSO appears in the self-hosted Pro feature list. It is not established here for the free edition."}},"id":"docuseal","infrastructure":["servers"],"infrastructureNotes":"Web application containers and document-processing jobs with durable database and attachment storage on Cloudron or managed application platforms. Cloud Run container hosting does not establish event-driven function deployment support.","infrastructureReviewed":"2026-11-13","infrastructureSources":["https://docs.cloudron.io/packages/docuseal/","https://docs.cloudron.io/installation/","https://www.docuseal.com/docs/deploying-docuseal-on-azure-web-apps","https://www.docuseal.com/docs/deploying-docuseal-on-google-cloud-run"],"install":"Vendor Azure, Google Cloud, DigitalOcean, Railway, Heroku and Render deployment paths, or a Cloudron package on a customer VM.","installMethods":["package","platform-template","cloudron"],"kind":"product","license":"AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms.","licenseModel":"open-source","licenseModelNotes":"AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms. Cloudron packaging and platform plans have separate terms; the application license does not grant a free platform subscription.","licenseModelSources":["https://github.com/docusealco/docuseal/blob/3.3.6/LICENSE","https://www.docuseal.com/docs/on-premises-pro-installation","https://www.cloudron.io/legal/terms.html","https://www.cloudron.io/pricing.html"],"licenseReviewed":"2026-11-13","model":"Fully in your account","modelLabel":"Customer-operated","name":"DocuSeal Self-Hosted","notes":"Reviewed core 3.3.7 includes security hardening, bug fixes, and performance improvements. The separately reviewed Cloudron package snapshot is 1.21.3 with core 3.3.6; pin a current image and confirm package lag before upgrading. Back up the database and attachments, and preserve SECRET_KEY_BASE. Native deployment examples need production configuration: restrict database access and configure durable storage; Heroku/Render app filesystems are ephemeral, and the free Render database expires. Paid features require appropriate entitlements; Pro uses a license/usage connection to DocuSeal. Qualified electronic signatures are not available in the on-premises edition. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations. DocuSeal 3.3.8 fixes GHSA-78g6-f52x-q3jx, a High-severity unauthenticated denial of service in Ruby versions used by earlier DocuSeal builds. Versions before 3.3.8 are affected and no workaround is documented. Upgrade, restart every Ruby web and background process, and verify all workers use the updated runtime.","operations":"Customer manages administrator access, signing workflows, HTTPS, secrets, database networking, mail, durable attachment storage, database/file/key recovery and image upgrades. Platform providers operate the underlying managed services. For 3.3.8 security remediation, restart every Ruby web and background process after deployment.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Self-hosted edition and boundaries","url":"https://www.docuseal.com/on-premises"},{"title":"Vendor installation options","url":"https://www.docuseal.com/install"},{"title":"Production runtime requirements","url":"https://www.docuseal.com/docs/on-premises-server-requirements"},{"title":"Configuration, secrets and storage","url":"https://www.docuseal.com/docs/configuring-docuseal-via-environment-variables"},{"title":"Cloudron application operations","url":"https://docs.cloudron.io/packages/docuseal/"},{"title":"Core application and installation","url":"https://github.com/docusealco/docuseal/blob/3.3.6/README.md"},{"title":"Attachment storage configuration","url":"https://github.com/docusealco/docuseal/blob/3.3.6/config/storage.yml"},{"title":"Default storage selection","url":"https://github.com/docusealco/docuseal/blob/3.3.6/config/environments/production.rb"},{"title":"Pro image, licensing and usage connection","url":"https://www.docuseal.com/docs/on-premises-pro-installation"},{"title":"Qualified signature edition limitation","url":"https://www.docuseal.com/faq/how-to-use-qes-signing-with-docuseal-on-premises"},{"title":"Current security release","url":"https://github.com/docusealco/docuseal/releases/tag/3.3.7"},{"title":"Release and security history","url":"https://www.docuseal.com/changelog"},{"title":"Core AGPL license","url":"https://github.com/docusealco/docuseal/blob/3.3.6/LICENSE"},{"title":"Contributor history","url":"https://github.com/docusealco/docuseal/graphs/contributors"},{"title":"Cloudron application packages and persistent data","url":"https://docs.cloudron.io/apps/"},{"title":"Cloudron application updates","url":"https://docs.cloudron.io/updates/"},{"title":"Cloudron database and application-data backups","url":"https://docs.cloudron.io/backups/"},{"title":"Cloudron platform plans","url":"https://www.cloudron.io/pricing.html"},{"title":"Cloudron account and platform terms","url":"https://www.cloudron.io/legal/terms.html"},{"title":"Cloudron account and installation metadata","url":"https://www.cloudron.io/legal/privacy.html"},{"title":"Exact Cloudron application package versions","url":"https://www.cloudron.io/store/index.html"},{"title":"Cloudron EC2 AMI and application installation","url":"https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci"},{"title":"Cloudron customer Droplet deployment","url":"https://marketplace.digitalocean.com/apps/cloudron"},{"title":"Cloudron customer Linode deployment","url":"https://www.linode.com/docs/marketplace-docs/guides/cloudron/"},{"title":"Cloudron named-provider installation and Marketplace availability","url":"https://docs.cloudron.io/installation/"},{"title":"Hostinger customer VPS Cloudron template","url":"https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/"},{"title":"LumaDock customer VPS Cloudron template","url":"https://lumadock.com/vps-hosting/cloudron"},{"title":"Vendor Azure Web Apps deployment","url":"https://www.docuseal.com/docs/deploying-docuseal-on-azure-web-apps"},{"title":"Vendor Google Cloud Run deployment","url":"https://www.docuseal.com/docs/deploying-docuseal-on-google-cloud-run"},{"title":"Vendor DigitalOcean application specification","url":"https://github.com/docusealco/docuseal-digitalocean/blob/master/.do/deploy.template.yaml"},{"title":"Vendor-linked Railway application template","url":"https://railway.com/deploy/IGoDnc"},{"title":"Vendor Heroku application specification","url":"https://github.com/docusealco/docuseal-heroku/blob/master/app.json"},{"title":"Vendor Render application blueprint","url":"https://github.com/docusealco/docuseal-render/blob/master/render.yaml"},{"title":"Railway application Docker source","url":"https://github.com/docusealco/docuseal-railway"},{"title":"Railway volume persistence","url":"https://docs.railway.com/volumes/reference"},{"title":"Heroku ephemeral dyno filesystem","url":"https://devcenter.heroku.com/articles/dyno-isolation"},{"title":"Render free-service production limitations","url":"https://render.com/docs/free"},{"title":"Vendor application upgrade instructions","url":"https://www.docuseal.com/docs/update-docuseal-to-the-latest-version"},{"title":"Security-hardening changes in 3.3.7","url":"https://github.com/docusealco/docuseal/compare/3.3.6...3.3.7"},{"title":"DocuSeal 3.3.8 security release","url":"https://github.com/docusealco/docuseal/releases/tag/3.3.8"},{"title":"GHSA-78g6-f52x-q3jx","url":"https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx"}],"url":"https://launchinyourcloud.com/directory/docuseal/","website":"https://www.docuseal.com/"},{"architecture":"Customer-hosted enterprise application, document storage and database; deployment sizing and modules require implementation planning.","categories":["document-management","records-management","contract-management","financial-application-management","case-management","correspondence-management","vendor-supplier-document-management","hr-employee-records-management","policy-procedure-management","claims-management","workflow-automation"],"category":"Document management","categoryFit":{"case-management":"Configurable case applications connect case data, documents, tasks and approvals.","claims-management":"Document capture and workflows integrated with insurance claims systems; not a replacement for claims adjudication software.","contract-management":"Configurable WorkView contract applications and document workflows; confirm modules and implementation scope.","correspondence-management":"Configurable OnBase workflows can store and route correspondence documents with related case work; implementation is solution-specific.","document-management":"Enterprise content repository with capture, document workflows and integration with business applications.","financial-application-management":"Loan-document tracking and integration with loan origination systems; this supports the document process rather than replacing a lending core.","hr-employee-records-management":"Employee-file access, applicant-document routing and employee onboarding/offboarding workflows.","policy-procedure-management":"Electronic policy distribution and policy/procedure sign-off workflows in the HR document-management scope.","records-management":"Retention and destruction workflows for electronic documents; WorkView also supports tracking physical records.","vendor-supplier-document-management":"Vendor case records and supporting documents in WorkView and accounts-payable workflows; not a dedicated supplier-risk service.","workflow-automation":"Content and case workflows with routing, rules and low-code WorkView applications."},"cloudEvidence":[{"applicableVersions":["OnBase 18+ in partner statement; confirm current release"],"clouds":["aws","azure","gcp"],"notes":"Hyland-authorized integration partner Reveille explicitly describes OnBase 18+ in customer-managed AWS, Azure and Google Cloud environments, separately from OnBase Cloud. This is the partner's compatibility statement, not a Hyland installation guide or cloud-support certification. Confirm the current OnBase release, Windows/database topology, licenses and vendor support agreement; Reveille itself is not required for self-hosting.","reviewed":"2026-11-12","sourceType":"partner-evidence","title":"Hyland partner statement on customer-managed OnBase cloud deployments","url":"https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/","vendorSupport":"not-assessed"},{"clouds":["aws","azure","gcp"],"notes":"Hyland identifies Reveille as an authorized build partner for OnBase and other Hyland platforms. This corroborates the source relationship, not an independent certification of every deployment listed by the partner; use its customer-managed-cloud statement together with OnBase installation and commercial requirements.","reviewed":"2026-11-12","sourceType":"partner-relationship","title":"Hyland identification of Reveille as an authorized integration partner","url":"https://www.hyland.com/en/partners/reveille","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0,1],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0,1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0,1],"operator":"customer"}],"description":"Customer-hosted enterprise content and case platform for document-heavy business processes.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"OnBase Foundation 26.1 Web/Application role minima; not the complete solution","source":"https://docs.hyland.com/r/OnBase/Technical-Requirements-Overview-for-New-Installations-and-Upgrades/Foundation-26.1/Technical-Requirements-Overview-for-New-Installations-and-Upgrades/Part-6-Web/Application-Server-and-Core-Services-Hardware-Requirements/64-Bit-Server-Hardware-Requirements?contentId=UToZTDrd9HvkQpjb7tURJQ","status":"documented","summary":"Foundation 26.1 lists a 2.4-GHz dual-core minimum, 4 GB RAM for Web Server and 8 GB for 64-bit Application Server, with 16 GB recommended for each. These are dedicated-role requirements; database, files, other modules, HA and workload capacity are additional."},"iac":{"reviewed":"2026-11-20","scope":"Vendor-supplied OnBase Web Server installation media, not public IaC","source":"https://docs.hyland.com/r/OnBase/Web-Server/Foundation-26.1/Web-Server/Installation/Installation/Running-the-Installer?contentId=6JGslGq~Cra0GizajFYkbA","status":"documented","summary":"The Foundation 26.1 Web Server is delivered through vendor setup.exe/MSI installation media with documented interactive and silent configuration. Application Server installation is a prerequisite; no public cloud-provisioning template is established by this installer guide."},"licensePricing":{"reviewed":"2026-11-16","scope":"OnBase on-premises terms v1.2, effective 2026-06-23; customer order may add conditions","source":"https://legal.hyland.com/pst-on-premise-multi-products","status":"documented","summary":"The current on-premises terms distinguish production, disaster-recovery and separately licensed non-production use. Confirm the purchased product/client/API permissions and environments in the agreement; these terms do not supply a public total price."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"OnBase Foundation 26.1 Web Client configuration; not a blanket claim for every module","source":"https://docs.hyland.com/r/OnBase/Web-Server/Foundation-26.1/Web-Server/Configuration/Web.config-Configuration/appSettings?contentId=stz0b9kK0lYB~c4sf1hbkA","status":"documented","summary":"The Foundation 26.1 Web Client documents Integration for Single Sign-On and configuration of automatic login. Hyland identity-service authentication is also module-specific; confirm client coverage, identity-provider compatibility and licensed integrations for the selected solution."}},"id":"onbase","infrastructure":["servers"],"infrastructureNotes":"Customer-hosted enterprise application, document storage and database; deployment sizing and modules require implementation planning.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://legal.hyland.com/pst-on-premise-multi-products"],"install":"Vendor or partner-assisted on-premises installation","installMethods":["other"],"kind":"platform","license":"Commercial OnBase licenses and separately scoped modules","licenseModel":"commercial-only","licenseModelNotes":"The selected OnBase on-premises product is commercially licensed. Its current on-premises terms restrict production copies and require applicable fees for additional environments and certain access; modules and integrations follow the contracted scope.","licenseModelSources":["https://legal.hyland.com/pst-on-premise-multi-products"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Hyland OnBase On-Premise","notes":"This entry covers licensed OnBase on-premises deployments. Category memberships describe documented platform configurations and integrations, not separately included turnkey applications. Loan tracking, claims integrations and other service solutions need scope and licensing confirmation.","operations":"Customer maintains on-premises infrastructure and backups; agree implementation, upgrades and support responsibilities with Hyland or its partner.","publisher":false,"reviewed":"2026-11-13","sources":[{"title":"OnBase platform capabilities","url":"https://www.hyland.com/en/solutions/products/onbase"},{"title":"On-premises product terms","url":"https://legal.hyland.com/pst-on-premise-multi-products"},{"title":"WorkView business application examples","url":"https://www.hyland.com/en/resources/articles/workview-product-overview"},{"title":"HR files and policy sign-offs","url":"https://www.hyland.com/en/resources/terminology/human-resources/document-management"},{"title":"OnBase workflow routing","url":"https://docs.hyland.com/r/OnBase/Workflow/Foundation-23.1/Workflow/Overview/Workflow-Overview"},{"title":"Correspondence document integration","url":"https://docs.hyland.com/r/OnBase/Application-Client-Connector/Foundation-24.1/Application-Client-Connector/Overview/Introduction"},{"title":"Loan-document tracking solution","url":"https://community.hyland.com/kb/articles/1332-hyland-services-loan-document-tracking"},{"title":"Insurance claims integration case study","url":"https://www.hyland.com/en/customers/p-c-insurer"}],"url":"https://launchinyourcloud.com/directory/onbase/","website":"https://www.hyland.com/"},{"advisories":[{"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.","conditions":"Applicability depends on the installed server build and use of the affected authentication/delegation endpoints.","id":"medplum-5-2-17-authentication-delegation-hardening","listingIds":["medplum-self-hosted"],"reviewed":"2026-11-19","scope":"The authentication/me and delegation paths named in the v5.2.17 release; no universal affected-version range or CVE is asserted.","source":"https://github.com/medplum/medplum/releases/tag/v5.2.17","summary":"The v5.2.17 release strips ClientApplication secrets from auth/me responses and changes on-behalf-of identity and delegation handling.","title":"Medplum 5.2.17 authentication and delegation hardening","type":"security-advisory"}],"architecture":"Containerized API and web application with PostgreSQL, cache, object storage, secrets and load-balancing or CDN services","categories":["backend-platforms","workflow-automation"],"category":"Backend platforms","categoryFit":{"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."},"cloudEvidence":[{"clouds":["aws"],"notes":"Medplum describes a complete production-ready installation in the customer's AWS environment and deploys the application and supporting AWS resources with CDK.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Complete Medplum installation in a customer AWS account","url":"https://www.medplum.com/docs/self-hosting/install-on-aws","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The official Terraform and Helm workflow deploys Medplum into the customer's Azure subscription with AKS, PostgreSQL, Redis, storage, gateway and frontend resources.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Production-validated Medplum deployment on Azure","url":"https://www.medplum.com/docs/self-hosting/install-on-azure","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The official Terraform and Helm workflow deploys Medplum into the customer's Google Cloud project with GKE, Cloud SQL, Redis, storage and frontend resources.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Production-validated Medplum deployment on Google Cloud","url":"https://www.medplum.com/docs/self-hosting/install-on-gcp","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","azure","gcp"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Upstream contributor history","url":"https://github.com/medplum/medplum/graphs/contributors"},{"title":"Reviewed upstream application release","url":"https://github.com/medplum/medplum/releases/tag/v5.2.17"}],"summary":"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."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Open-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.","diligence":{"airGap":{"reviewed":"2026-11-19","scope":"Medplum Self-Hosted: selected customer-operated edition","source":"https://www.medplum.com/docs/self-hosting/install-on-aws","status":"inconclusive","summary":"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."},"commitments":{"reviewed":"2026-11-19","scope":"Medplum Self-Hosted: selected customer-operated edition","source":"https://www.medplum.com/docs/self-hosting/install-on-aws","status":"inconclusive","summary":"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."},"compliance":{"reviewed":"2026-11-19","scope":"Medplum Self-Hosted: selected customer-operated edition","source":"https://www.medplum.com/docs/self-hosting/install-on-aws","status":"inconclusive","summary":"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."},"cost":{"reviewed":"2026-11-19","scope":"Medplum Self-Hosted: selected customer-operated edition","source":"https://www.medplum.com/docs/self-hosting/install-on-aws","status":"inconclusive","summary":"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."},"footprint":{"reviewed":"2026-11-19","scope":"Medplum Self-Hosted: selected customer-operated edition","source":"https://www.medplum.com/docs/self-hosting/install-on-aws","status":"inconclusive","summary":"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."},"iac":{"artifactRef":"@medplum/cdk 5.2.17 at upstream tag v5.2.17","artifactUrl":"https://github.com/medplum/medplum/tree/v5.2.17/packages/cdk","availability":"available","reviewed":"2026-11-19","scope":"Medplum Community AWS IaC source, independently versioned from other deployment components","source":"https://www.medplum.com/docs/self-hosting/install-on-aws","status":"documented","summary":"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."},"licensePricing":{"availability":"available","reviewed":"2026-11-19","scope":"Medplum Self-Hosted: selected customer-operated edition","source":"https://www.medplum.com/open-source","status":"documented","summary":"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.","supportingSources":[{"title":"Commercial support plans","url":"https://www.medplum.com/pricing"}]},"marketplace":{"reviewed":"2026-11-19","scope":"Medplum Self-Hosted: selected customer-operated edition","source":"https://www.medplum.com/docs/self-hosting/install-on-aws","status":"inconclusive","summary":"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."},"release":{"releasePublishedAt":"2026-11-11T01:34:07Z","releaseTag":"v5.2.17","reviewed":"2026-11-19","scope":"Medplum Self-Hosted upstream application, independently versioned from provider packages","source":"https://github.com/medplum/medplum/releases/tag/v5.2.17","status":"documented","summary":"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."},"scim":{"reviewed":"2026-11-19","scope":"Medplum Self-Hosted: selected customer-operated edition","source":"https://www.medplum.com/docs/self-hosting/install-on-aws","status":"inconclusive","summary":"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."},"securityControls":{"availability":"edition-dependent","reviewed":"2026-11-19","scope":"Medplum Self-Hosted: selected customer-operated edition","source":"https://www.medplum.com/docs/self-hosting/install-on-aws","status":"documented","summary":"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."},"sso":{"reviewed":"2026-11-19","scope":"Medplum Self-Hosted: selected customer-operated edition","source":"https://www.medplum.com/docs/self-hosting/install-on-aws","status":"inconclusive","summary":"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."}},"id":"medplum-self-hosted","infrastructure":["hybrid"],"infrastructureNotes":"The deployment combines customer Kubernetes or container compute with managed database, cache, storage, secrets and network services.","infrastructureReviewed":"2026-11-19","infrastructureSources":["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"],"install":"AWS CDK, or Terraform and Helm on Azure AKS or Google GKE","installMethods":["cloudformation","terraform","helm","kubernetes"],"kind":"platform","license":"Apache-2.0 Community software; an optional commercial Enterprise Self-Hosted support plan is separate.","licenseModel":"open-source","licenseModelNotes":"The Community software is Apache-2.0; Enterprise Self-Hosted support is a separate commercial service.","licenseModelSources":["https://www.medplum.com/open-source","https://www.medplum.com/pricing"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Medplum Self-Hosted","notes":"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.","operations":"Customer operates the cloud infrastructure and application lifecycle; Medplum offers an Enterprise Self-Hosted support plan.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Medplum production installation on AWS","url":"https://www.medplum.com/docs/self-hosting/install-on-aws"},{"title":"Medplum production installation on Azure","url":"https://www.medplum.com/docs/self-hosting/install-on-azure"},{"title":"Medplum production installation on Google Cloud","url":"https://www.medplum.com/docs/self-hosting/install-on-gcp"},{"title":"Medplum open-source terms","url":"https://www.medplum.com/open-source"},{"title":"Medplum self-hosted support plans","url":"https://www.medplum.com/pricing"},{"title":"Reviewed deployment artifact reference","url":"https://github.com/medplum/medplum/tree/v5.2.17/packages/cdk"},{"title":"Buyer evidence: release","url":"https://github.com/medplum/medplum/releases/tag/v5.2.17"},{"title":"Upstream contributor history","url":"https://github.com/medplum/medplum/graphs/contributors"}],"url":"https://launchinyourcloud.com/directory/medplum-self-hosted/","website":"https://www.medplum.com/"},{"architecture":"Mendix Operator, application runtimes, database and file storage on the documented managed-Kubernetes providers.","categories":["internal-tools","workflow-automation"],"category":"Internal tools","categoryFit":{"internal-tools":"Commercial low-code application runtime operated in customer Kubernetes infrastructure.","workflow-automation":"Commercial low-code application runtime operated in customer Kubernetes infrastructure."},"cloudEvidence":[{"clouds":["aws","azure","gcp","stackit"],"notes":"Mendix Operator, application runtimes, database and file storage on the documented managed-Kubernetes providers. The selected connected deployment registers the cluster with the external Mendix Portal control plane. A customer cluster is not a packaged insurance-claims application. Runtime licences, operator versions and application versions have different lifecycles; standalone modes need their own review.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Supported Clouds","url":"https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","azure","gcp","stackit"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"vendor-hosted","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"vendor-hosted","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"vendor-hosted","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"stackit","controlPlane":"vendor-hosted","evidence":[0],"operator":"customer"}],"description":"Commercial low-code application runtime operated in customer Kubernetes infrastructure.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"One simple app baseline, excluding cluster overhead and HA/1-TB workload capacity","source":"https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/","status":"documented","summary":"The supported-provider guide requires at least 2 CPU cores, 2 GB memory and 3 GB ephemeral storage available on a node for one simple app, excluding Kubernetes core components. Production databases, file storage, image building and multiple replicas need additional sizing; experimental ARM64 support is limited to non-production Connected Mode."},"iac":{"reviewed":"2026-11-20","scope":"Mendix on Kubernetes deployment workflow; operator, runtime and application releases are separate","source":"https://docs.mendix.com/developerportal/deploy/private-cloud-deploy/","status":"documented","summary":"The Kubernetes deployment guides register a cluster/namespace, install the Mendix Operator and deploy app environments from the Mendix Portal or Kubernetes custom resources. Database, file storage, registry, network access and licensed runtime configuration remain deployment inputs.","supportingSources":[{"title":"Cluster and operator setup","url":"https://docs.mendix.com/developerportal/deploy/private-cloud-cluster/"}]},"licensePricing":{"reviewed":"2026-11-19","scope":"Mendix on Kubernetes; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/","status":"documented","summary":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Application end-user federation on a compatible Mendix runtime; verify module dependencies and app configuration","source":"https://docs.mendix.com/appstore/modules/saml/","status":"documented","summary":"Mendix documents SAML and OIDC modules for end-users of deployed apps, with module/runtime compatibility and app-level configuration. The SAML guide explicitly addresses apps outside Mendix Cloud and requires external file storage. This is separate from developer-portal or Private Mendix Platform login.","supportingSources":[{"title":"OIDC module and supported runtime versions","url":"https://docs.mendix.com/appstore/modules/oidc/"}]}},"id":"mendix-private-cloud","infrastructure":["servers"],"infrastructureNotes":"Mendix Operator, application runtimes, database and file storage on the documented managed-Kubernetes providers. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/"],"install":"Helm / Kubernetes operator; Kubernetes manifests","installMethods":["helm","kubernetes"],"kind":"platform","license":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.","licenseModel":"commercial-only","licenseModelNotes":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.","licenseModelSources":["https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/","https://www.mendix.com/legal/"],"licenseReviewed":"2026-11-19","model":"BYOC","modelLabel":"Customer-operated · vendor control plane","name":"Mendix on Kubernetes","notes":"The selected connected deployment registers the cluster with the external Mendix Portal control plane. A customer cluster is not a packaged insurance-claims application. Runtime licences, operator versions and application versions have different lifecycles; standalone modes need their own review.","operationReview":{"controlPlane":"vendor-hosted","modelLabel":"Customer-operated · vendor control plane","operator":"customer","reviewed":"2026-11-20","source":"https://docs.mendix.com/developerportal/deploy/private-cloud/","summary":"In the selected Connected mode the customer supplies and operates the Kubernetes runtime, database, storage and backups. The Mendix Portal controls deployments through an in-cluster agent. This is not a vendor-operated application service."},"operations":"Customer operates the application runtime; the documented connected deployment also depends on the Mendix management portal and its configured access.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Supported Clouds","url":"https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/"},{"title":"Private Cloud Deploy","url":"https://docs.mendix.com/developerportal/deploy/private-cloud-deploy/"},{"title":"Insurance Claims","url":"https://www.mendix.com/industries/insurance/"},{"title":"Outside-Cloud Licensing","url":"https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/"},{"title":"Mendix Legal","url":"https://www.mendix.com/legal/"},{"title":"Mendix on K8s RN","url":"https://docs.mendix.com/releasenotes/developer-portal/mendix-for-private-cloud/"}],"url":"https://launchinyourcloud.com/directory/mendix-private-cloud/","website":"https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/"},{"architecture":"Customer-operated workflow runtime, credentials store and persistent execution data","categories":["workflow-automation","ai-tools"],"category":"Workflow automation","categoryFit":{"ai-tools":"Orchestrates AI providers, agents, tools and memory as workflows. Model inference and external service dependencies are configured separately.","workflow-automation":"Visual integration/workflow automation with custom code and connectors; connected systems and AI providers may receive workflow data."},"cloudEvidence":[{"clouds":["aws"],"notes":"Project instructions deploy n8n and PostgreSQL on customer-operated EKS. Review persistence, ingress and production scaling requirements.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"n8n deployment on AWS","url":"https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-aws","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Project instructions deploy n8n with PostgreSQL on Azure Kubernetes Service in the customer subscription.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"n8n deployment on Azure","url":"https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-azure","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The project documents Cloud Run deployment. Its easy mode is not the production configuration; follow the durable-mode guidance for production and review execution and persistence constraints.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"n8n deployment on Google Cloud Run","url":"https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-google-cloud-run","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"n8n self-hosted deployment on DigitalOcean","url":"https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean","vendorSupport":"not-assessed"},{"clouds":["heroku"],"notes":"The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"n8n self-hosted deployment on Heroku","url":"https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku","vendorSupport":"not-assessed"},{"clouds":["hetzner"],"notes":"The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"n8n self-hosted deployment on Hetzner","url":"https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp","digitalocean","heroku","hetzner"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"},{"boundary":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[3],"operator":"customer"},{"boundary":"platform-workspace","cloud":"heroku","controlPlane":"not-assessed","evidence":[4],"operator":"customer"},{"boundary":"cloud-account","cloud":"hetzner","controlPlane":"not-assessed","evidence":[5],"operator":"customer"}],"description":"Automate integrations and business processes with a customer-hosted workflow editor and runtime.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Self-hosted workflow-dependent sizing; complete production footprint unresolved","source":"https://docs.n8n.io/hosting/scaling/memory-errors/","status":"inconclusive","summary":"The self-hosted memory guide ties RAM usage to execution concurrency, JSON/binary payload size and workflow behavior. It does not establish one safe server minimum. Size main processes, workers/task runners, PostgreSQL, queue-mode Redis, binary storage and HA after measuring representative workflows.","supportingSources":[{"title":"Production topology and dependencies","url":"https://docs.n8n.io/deploy/host-n8n/install-options/production-requirements.md"}]},"iac":{"artifactRef":"Select and pin a compatible versioned application image","artifactUrl":"https://github.com/n8n-io/n8n-hosting","reviewed":"2026-11-20","scope":"Official self-hosted Compose deployment","source":"https://docs.n8n.io/hosting/installation/server-setups/docker-compose/","status":"documented","summary":"The vendor documents Linux Compose installation and links n8n-hosting configurations for different architectures. Configure persistent data, database, encryption key, domain and TLS; choose the production topology rather than treating the minimal single-server recipe as HA."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/n8n-io/n8n/master/LICENSE.md","status":"documented","summary":"The Sustainable Use License permits internal business or non-commercial/personal use under its conditions. Enterprise files are separately licensed, and other branches have specific restrictions. Commercial redistribution or embedded use must be checked against vendor terms; self-hosting does not grant every Enterprise feature."},"release":{"releasePublishedAt":"2026-11-19T08:29:57Z","releaseTag":"n8n@2.48.6","reviewed":"2026-11-19","scope":"Upstream n8n 2.x release; the 1.x maintenance line has a separate fixed build","source":"https://github.com/n8n-io/n8n/releases/tag/n8n%402.48.6","status":"documented","summary":"n8n n8n@2.48.6 was published November 19, 2026. Official 2.x images use a patched Node 26.13.0 runtime carrying a V8 process-abort fix. Maintained 1.x users should use n8n@1.123.99 or later, which moves to Node 24.22.3.","supportingSources":[{"title":"Prior reviewed release context","url":"https://github.com/n8n-io/n8n/releases/tag/n8n%402.47.7"},{"title":"Maintained 1.x runtime fix","url":"https://github.com/n8n-io/n8n/releases/tag/n8n%401.123.99"},{"title":"Patched V8 runtime integration","url":"https://github.com/n8n-io/n8n/pull/43703"}]},"sso":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Self-hosted Business and Enterprise; not the unlicensed Community edition","source":"https://docs.n8n.io/deploy/host-n8n/configure-n8n/security/configure-sso.md","status":"documented","summary":"SAML or OIDC SSO is documented for self-hosted Business and Enterprise. Instance-owner or administrator privileges are required to configure it."}},"id":"n8n","infrastructure":["servers"],"infrastructureNotes":"Reviewed topology runs long-lived containers and persistent workflow/credential storage. Event triggers do not make the self-hosted control/runtime stack function-based serverless.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.n8n.io/deploy/host-n8n/install-options/install-using-docker-compose"],"install":"Docker Compose with persistent data; database and worker topology selected for workload","installMethods":["docker"],"kind":"product","license":"Sustainable Use License for covered code; separate commercial Enterprise license for enterprise components","licenseModel":"source-available","licenseModelNotes":"The core is under the Sustainable Use License with use restrictions, not an OSI open-source license. Enterprise-marked code requires a separate commercial Enterprise license. A free self-hosted option does not change the core license model.","licenseModelSources":["https://github.com/n8n-io/n8n/blob/master/LICENSE.md"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"n8n Self-Hosted","notes":"This entry excludes n8n Cloud. The Sustainable Use License has use restrictions and should not be described as unrestricted open-source licensing. Enterprise components require the appropriate commercial license. External integrations, AI providers and optional assistant services require separate data-flow review. n8n@2.48.6 and the maintained n8n@1.123.99 line move official images to patched Node runtimes carrying a V8 process-abort fix. The 1.x image also moves to Node 24.22.3, while 2.x pins a patched Node 26.13.0. Update the selected line and verify custom images use the fixed runtime.","operations":"Customer manages servers/containers, secrets, database, backup/restore, scaling and upgrades.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Current self-hosted Docker Compose guide","url":"https://docs.n8n.io/deploy/host-n8n/install-options/install-using-docker-compose"},{"title":"Official license boundaries","url":"https://github.com/n8n-io/n8n/blob/master/LICENSE.md"},{"title":"Workflow automation project","url":"https://github.com/n8n-io/n8n"},{"title":"AI workflow components and integrations","url":"https://docs.n8n.io/build/integrate-ai.md"},{"title":"n8n self-hosted deployment on DigitalOcean","url":"https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-digital-ocean"},{"title":"n8n self-hosted deployment on Heroku","url":"https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku"},{"title":"n8n self-hosted deployment on Hetzner","url":"https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-hetzner"},{"title":"n8n@2.48.6 release","url":"https://github.com/n8n-io/n8n/releases/tag/n8n%402.48.6"},{"title":"n8n@1.123.99 release","url":"https://github.com/n8n-io/n8n/releases/tag/n8n%401.123.99"},{"title":"Patched V8 runtime integration","url":"https://github.com/n8n-io/n8n/pull/43703"}],"url":"https://launchinyourcloud.com/directory/n8n/","website":"https://n8n.io/"},{"architecture":"Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE.","categories":["workflow-automation","case-management"],"category":"Workflow automation","categoryFit":{"case-management":"Commercial workflow and case-management platform installed in customer-managed Kubernetes infrastructure.","workflow-automation":"Commercial workflow and case-management platform installed in customer-managed Kubernetes infrastructure."},"cloudEvidence":[{"clouds":["aws"],"notes":"Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"EKS Runbook","url":"https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-EKS.md","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"AKS Runbook","url":"https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-AKS.md","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"GKE Runbook","url":"https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-GKE.md","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Commercial workflow and case-management platform installed in customer-managed Kubernetes infrastructure.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Moving chart web-tier defaults, not a vendor-certified minimum or a complete 100-user/1-TB HA sizing","source":"https://github.com/pegasystems/pega-helm-charts/blob/master/charts/pega/values.yaml","status":"documented","summary":"The reviewed upstream chart gives the web-user tier a per-pod request of 3 CPU and 12 GiB memory, with limits of 4 CPU and 12 GiB. These are configurable chart defaults; background/search tiers, database, autoscaling, replica counts and cluster overhead are additional."},"iac":{"artifactRef":"master (moving branch); select a chart compatible with the licensed Pega release","artifactUrl":"https://github.com/pegasystems/pega-helm-charts/tree/master/charts/pega","reviewed":"2026-11-20","scope":"Client-managed licensed platform deployment; no ECS support inferred from generic container capability","source":"https://github.com/pegasystems/pega-helm-charts/blob/master/docs/Deploying-Pega-on-EKS.md","status":"documented","summary":"Pega publishes Helm charts and EKS/AKS/GKE runbooks for client-managed Kubernetes. The EKS guide requires separately obtained Pega images, registry access and a supported database. Match chart, application, search and database versions; chart source access does not grant platform software rights."},"licensePricing":{"reviewed":"2026-11-19","scope":"Pega Platform Client-Managed; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://www.pega.com/terms","status":"documented","summary":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Pega Platform application user federation; confirm the chosen client-managed release and identity-service configuration","source":"https://docs.pega.com/bundle/platform/page/platform/security/create-authentication-service.html","status":"documented","summary":"Pega Platform documents SAML 2.0 and OIDC authentication services for user SSO. A security administrator creates the service and configures identity/claim mapping and any operator provisioning; token credentials for API integrations are a separate authentication type.","supportingSources":[{"title":"Public documentation API with article body","url":"https://docs-be.pega.com/api/bundle/platform/page/platform/security/create-authentication-service.html"}]}},"id":"pega-platform-client-managed","infrastructure":["servers"],"infrastructureNotes":"Pega application Helm charts, supported database and runtime dependencies on EKS, AKS or GKE. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-EKS.md","https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-AKS.md","https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-GKE.md"],"install":"Helm / Kubernetes operator; Kubernetes manifests","installMethods":["helm","kubernetes"],"kind":"platform","license":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.","licenseModel":"commercial-only","licenseModelNotes":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.","licenseModelSources":["https://www.pega.com/terms"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Pega Platform Client-Managed","notes":"This listing covers the platform established by the deployment runbooks. It does not imply that a separately licensed Pega Government Platform package or municipal-permit application is installed. The chart's open-source licence does not license the Pega runtime.","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.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"EKS Runbook","url":"https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-EKS.md"},{"title":"AKS Runbook","url":"https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-AKS.md"},{"title":"GKE Runbook","url":"https://raw.githubusercontent.com/pegasystems/pega-helm-charts/master/docs/Deploying-Pega-on-GKE.md"},{"title":"Pega Terms","url":"https://www.pega.com/terms"},{"title":"PGP Release Notes","url":"https://docs.pega.com/bundle/pega-government-platform/page/pega-government-platform/releasenotes/constellation/cons-newfeatures.html"},{"title":"Helm Releases","url":"https://github.com/pegasystems/pega-helm-charts/releases"}],"url":"https://launchinyourcloud.com/directory/pega-platform-client-managed/","website":"https://docs.pega.com/bundle/platform/page/platform/deployment/client-managed-cloud/containerized-deployments-kubernetes.html"},{"architecture":"Customer-operated automation controller, execution and platform services on RHEL or OpenShift.","categories":["devops","workflow-automation"],"category":"DevOps","categoryFit":{"devops":"Enterprise configuration, provisioning and operations automation across infrastructure and applications.","workflow-automation":"Controller, event-driven automation and reusable automation content coordinate governed operational workflows."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Red Hat documents self-managed Ansible Automation Platform deployments on infrastructure hosted in AWS, Azure and Google Cloud. The customer operates the RHEL or OpenShift environment and supplies the subscription.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Self-managed Ansible Automation Platform in named public clouds","url":"https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-17","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Enterprise IT automation platform installed and managed by the customer in a public-cloud environment.","diligence":{"airGap":{"availability":"available","reviewed":"2026-11-17","scope":"AAP 2.7 containerized disconnected installation","source":"https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-assembly_aap_containerized_disconnected_installation","status":"documented","summary":"The containerized installer supports disconnected installation using a downloaded setup bundle, local RHEL RPM repositories and bundle_install=true. Required metrics service works without internet access; content and update transfers remain operator responsibilities."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Red Hat Ansible Automation Platform Self-Managed; unresolved within this edition/deployment","source":"https://aws.amazon.com/marketplace/pp/prodview-4hz3uo55uaemk","status":"inconclusive","summary":"Managed AAP Marketplace committed-spend claims do not establish treatment of this self-managed subscription. Obtain the selected offer and buyer-agreement eligibility."},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-configure_your_ansible_automation_platform_deployment","status":"inconclusive","summary":"The reviewed Red Hat Ansible Automation Platform Self-Managed 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."},"cost":{"reviewed":"2026-11-17","scenario":{"availability":"HA","dataGB":1000,"hoursPerMonth":730,"provider":"aws","region":"us-east-1","usage":"Average usage; no measured concurrency/throughput supplied","users":100},"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://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-ref_cont_aap_system_requirements","status":"inconclusive","summary":"Choose the supported HA inventory and count managed nodes, execution jobs, execution environments, controller/hub/database hosts and RHEL/AAP subscriptions. Human users and data size alone do not size automation capacity. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"AAP 2.7 containerized topology, not portal-only sizing","source":"https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-ref_cont_aap_system_requirements","status":"documented","summary":"The containerized system requirements distinguish the supported RHEL host, subscriptions, database and component resources. Use the deployment-model inventory and execution capacity to size each host; portal-only appliance requirements do not size the complete platform."},"iac":{"reviewed":"2026-11-17","scope":"AAP 2.7 installation methods; not AWX or Ansible Core","source":"https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-con_choosing_installation_type","status":"documented","summary":"The subscription-gated containerized setup bundle uses a configured inventory to install platform components with Podman; OpenShift uses the supported Operator path. AAP 2.7 does not use the removed RPM installer."},"licensePricing":{"reviewed":"2026-11-17","scope":"Red Hat Ansible Automation Platform Self-Managed: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-set_up_your_subscription","status":"documented","summary":"The selected Red Hat Ansible Automation Platform requires a commercial subscription and valid manifest. Upstream Ansible Core and AWX do not change this enterprise product's license classification."},"marketplace":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Red Hat Ansible Automation Platform Self-Managed; unresolved within this edition/deployment","source":"https://aws.amazon.com/marketplace/pp/prodview-4hz3uo55uaemk","status":"inconclusive","summary":"AWS lists Red Hat subscriptions including AAP, alongside a different managed AAP service. Confirm an offer/order explicitly entitling this self-managed 2.7 installation."},"release":{"reviewed":"2026-11-17","scope":"Self-managed AAP documentation line and patch index","source":"https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/","status":"documented","summary":"The reviewed self-managed documentation is the AAP 2.7 line, with separate patch-release notes and component updates. Select a supported patch and matching bundle; this is a version-line review, not a claim about a latest patch timestamp."},"scim":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Red Hat Ansible Automation Platform Self-Managed; unresolved within this edition/deployment","source":"https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/secure-proc_controller_set_up_saml","status":"inconclusive","summary":"Platform gateway documents SAML/LDAP/OIDC and group/role mapping, but a supported AAP 2.7 SCIM lifecycle endpoint was not established."},"securityControls":{"reviewed":"2026-11-17","scope":"AAP 2.7 gateway and deployment configuration","source":"https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-configure_your_ansible_automation_platform_deployment","status":"documented","summary":"AAP 2.7 centralizes external authentication at platform gateway and documents HTTPS redirects and CSRF settings. Restrict component access and configure the chosen identity provider and role mappings."},"sso":{"availability":"available","reviewed":"2026-11-17","scope":"Self-managed AAP 2.7 platform gateway","source":"https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/secure-proc_controller_set_up_saml","status":"documented","summary":"AAP 2.7 documents SAML identity-provider configuration through platform gateway. External authentication must use the gateway; legacy direct component authentication is no longer supported.","supportingSources":[{"title":"Mandatory gateway authentication","url":"https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/secure-mandatory_platform_gateway_authentication_in_ansible_automation_platform_2_7"}]}},"id":"ansible-automation-platform-self-managed","infrastructure":["servers"],"infrastructureNotes":"Self-managed Ansible Automation Platform uses persistent RHEL containers or customer-operated OpenShift workloads with databases and execution capacity.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/plan-ref_installation_deployment_models"],"install":"Containerized installer on RHEL with Podman or the OpenShift Operator","installMethods":["kubernetes","package","other"],"kind":"platform","license":"Commercial Red Hat Ansible Automation Platform subscription required.","licenseModel":"commercial-only","licenseModelNotes":"The selected Red Hat Ansible Automation Platform requires a commercial subscription and valid manifest. Upstream Ansible Core and AWX do not change this enterprise product's license classification.","licenseModelSources":["https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-set_up_your_subscription"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"Red Hat Ansible Automation Platform Self-Managed","notes":"This entry covers Red Hat Ansible Automation Platform, not the managed cloud service and not upstream Ansible Core or AWX. Current 2.7 deployment models use the containerized RHEL installer or OpenShift Operator; the RPM installer was removed in 2.7. Validate supported RHEL or OpenShift versions, execution environments and subscription manifests before installation.","operations":"Customer manages the platform, execution capacity, infrastructure, secrets, backups and upgrades; Red Hat supplies subscribed software updates and support.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Named-cloud and self-managed installation overview","url":"https://docs.redhat.com/en/learn/learning-paths/getting-started-red-hat-ansible-automation-platform/installation-and-key-functionalities"},{"title":"Current 2.7 deployment models","url":"https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/plan-ref_installation_deployment_models"},{"title":"Set up the Ansible Automation Platform subscription","url":"https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.7/install-set_up_your_subscription"}],"url":"https://launchinyourcloud.com/directory/ansible-automation-platform-self-managed/","website":"https://www.redhat.com/en/technologies/management/ansible"},{"architecture":"Distributed Retool containers on Kubernetes with external PostgreSQL, object storage, ingress and optional Temporal services","categories":["internal-tools","workflow-automation"],"category":"Internal tools","categoryFit":{"internal-tools":"Provides a self-hosted low-code platform for building internal applications and operational interfaces.","workflow-automation":"Runs Retool Workflows and related automation services inside the customer-operated deployment."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Retool provides production Terraform blueprints for AWS, Azure and Google Cloud and explicitly targets Amazon EKS, Azure AKS and Google GKE. Customers may alternatively deploy with Helm into an existing supported cluster.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Official Retool Terraform and Helm deployment paths","url":"https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-16","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Commercial single-tenant Retool deployment installed and operated on customer-managed Kubernetes infrastructure.","diligence":{"airGap":{"availability":"edition-dependent","reviewed":"2026-11-16","scope":"Enterprise commercial air-gap option is confirmed; deployment-specific procedure and integration dependencies require account-team coordination","source":"https://retool.com/pricing","status":"documented","summary":"Retool’s current Enterprise pricing explicitly offers air-gapped deployments. The standard self-managed guide still requires outbound license/authentication/usage services, so obtain the separate air-gap license, artifacts and procedure from Retool rather than applying the standard online setup unchanged.","supportingSources":[{"title":"Standard deployment outbound requirements","url":"https://docs.retool.com/self-hosted/self-managed/quickstart"}]},"commitments":{"availability":"edition-dependent","reviewed":"2026-11-16","scope":"Google Cloud private-offer procurement; buyer agreement controls eligibility","source":"https://retool.com/blog/retool-google-cloud-marketplace-announcement","status":"documented","summary":"Retool states that eligible Google Cloud Marketplace purchases can draw down a Google Cloud commitment and that Marketplace procurement preserves deployment options. Purchases use a private offer; the amount credited depends on the buyer’s Google agreement and accepted offer. This is not a blanket credit promise for all purchases or providers."},"compliance":{"reviewed":"2026-11-16","scope":"Vendor controls and audit availability; customer-environment scope/period needs the actual report","source":"https://docs.retool.com/legal/security","status":"inconclusive","summary":"Retool’s legal security practices describe independent SOC 2/ISO audits and direct readers to its Trust Center. Those public practices alone do not establish report dates or coverage of the customer-operated self-managed environment."},"footprint":{"reviewed":"2026-11-16","scope":"Current production Helm stack with app-builder/agent services; not the older Compose baseline","source":"https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes/kubernetes-helm","status":"documented","summary":"The current Helm guide calls for at least 32 CPU cores and 64 GiB available across the workload-node pool. Agent sandbox pods scale with builder sessions; the external PostgreSQL database, storage and peak autoscaling capacity must also be planned."},"iac":{"artifactRef":"main (moving branch)","artifactUrl":"https://github.com/tryretool/terraform-retool-self-hosted-blueprints/tree/main","reviewed":"2026-11-16","scope":"Self-managed Retool 4.0+; select matching chart and application versions","source":"https://docs.retool.com/self-hosted/self-managed/quickstart","status":"documented","summary":"Retool provides Terraform blueprints that provision EKS, AKS or GKE and deploy Helm. Kubernetes with Helm is the production path for 4.0 and later; Compose is for development and proofs of concept. AWS agent sandboxes require EC2-backed EKS workers rather than Fargate."},"licensePricing":{"reviewed":"2026-11-16","scope":"Self-hosted Enterprise procurement; excludes cloud infrastructure and operating labor","source":"https://retool.com/pricing","status":"documented","summary":"Current pricing places self-hosted and air-gapped deployment in Enterprise, with custom annual pricing. Its published cloud per-seat prices do not price a self-hosted Enterprise installation. The subscription and license-key terms govern use.","supportingSources":[{"title":"Self-hosted legal terms","url":"https://docs.retool.com/legal/product-specific-terms"}]},"marketplace":{"availability":"edition-dependent","offers":[{"cloud":"aws","delivery":"SaaS contract/private offer; select self-managed Enterprise entitlement","id":"prodview-cqgbgmrm63i4y","publisher":"Retool","url":"https://aws.amazon.com/marketplace/pp/prodview-cqgbgmrm63i4y"}],"reviewed":"2026-11-16","scope":"Vendor-published AWS offer; procurement and application hosting are distinct","source":"https://aws.amazon.com/marketplace/pp/prodview-cqgbgmrm63i4y","status":"documented","summary":"Retool’s AWS Marketplace listing explicitly describes self-hosted and Retool-managed AWS environments, with private-contract procurement. AWS classifies delivery as a SaaS contract; confirm the self-managed Enterprise entitlement rather than assuming an AMI installer or included infrastructure. Retool also announces Google Cloud private-offer purchasing with the same deployment options; the exact offer and agreement must match the self-hosted subscription.","supportingSources":[{"title":"Google Cloud Marketplace procurement and commitment conditions","url":"https://retool.com/blog/retool-google-cloud-marketplace-announcement"}]},"release":{"releasePublishedOn":"2026-11-11","releaseTag":"4.86.0","reviewed":"2026-11-16","scope":"Self-hosted stable-channel release, separate from cloud/edge versions; source supplies a publication day, not a timestamp","source":"https://docs.retool.com/releases/stable/version/4.86","status":"documented","summary":"The reviewed vendor release is 4.86.0, published 2026-11-11. This is a dated, scoped snapshot; it does not establish compatibility with another chart, cloud package or commercial edition. Retool documents quarterly stable releases and six months of support for each stable version."},"scim":{"availability":"edition-dependent","reviewed":"2026-11-16","scope":"Self-hosted technical configuration; selected subscription governs commercial entitlement; current pricing includes this capability in Enterprise","source":"https://docs.retool.com/sso/guides/scim-user-provisioning","status":"documented","summary":"SCIM provisioning is documented for self-hosted versions 2.32.1+, with bearer-token authentication and /api/scim/v2/* endpoints. The guide covers Okta and Entra ID; the identity provider must reach the instance through its firewall.","supportingSources":[{"title":"Enterprise entitlement matrix","url":"https://retool.com/pricing"}]},"securityControls":{"reviewed":"2026-11-16","scope":"Self-managed code-executor container; not an attestation for every Retool service","source":"https://docs.retool.com/self-hosted/self-managed/quickstart","status":"documented","summary":"The code-executor uses nsjail, which needs privileged container access. The documented fallback runs code without sandboxing if that access is unavailable. Review this specific container’s isolation separately from agent and JavaScript executors."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-16","scope":"Retool organization SSO; protocol support does not establish every plan entitlement; current pricing includes this capability in Enterprise","source":"https://docs.retool.com/sso/quickstart","status":"documented","summary":"Retool documents SAML and OIDC providers, including Entra ID and Okta, plus identity-provider group/role mapping. Apply the self-hosted instance configuration and subscription entitlements; Google Group sync is a separate integration.","supportingSources":[{"title":"Enterprise entitlement matrix","url":"https://retool.com/pricing"}]}},"id":"retool-self-hosted","infrastructure":["servers"],"infrastructureNotes":"Production deployments run persistent Retool services on customer EKS, AKS or GKE infrastructure with external database and object-storage dependencies.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://docs.retool.com/self-hosted/self-managed/quickstart","https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes/kubernetes-helm"],"install":"Official Terraform blueprints for Amazon EKS, Azure AKS or Google GKE, or Helm into an existing supported Kubernetes cluster","installMethods":["terraform","helm","kubernetes"],"kind":"product","license":"Commercial Enterprise subscription with custom annual pricing and a self-hosted license key.","licenseModel":"commercial-only","licenseModelNotes":"Current pricing places self-hosted and air-gapped deployments in Enterprise with custom annual pricing. Product-specific subscription and license-key terms apply; cloud per-seat prices do not price this deployment.","licenseModelSources":["https://docs.retool.com/legal/product-specific-terms","https://retool.com/pricing"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"Retool Self-Hosted, Self-Managed","notes":"This entry covers self-hosted, self-managed Retool, not Retool-managed hosting. Kubernetes with Helm is the supported production path for Retool 4.0 and later; Docker Compose is non-production only. EKS must use EC2-backed workers rather than Fargate for the agent sandbox. The standard deployment requires outbound access for license checks, authentication and usage reporting; Enterprise pricing separately offers air-gapped deployment, requiring the appropriate license and vendor-provided procedure. Workflows and Agents require Temporal, and Retool recommends its managed Temporal Cloud service unless the customer operates a compatible cluster.","operations":"Customer manages Kubernetes, PostgreSQL, object storage, DNS, TLS, secrets, networking, backups, capacity, upgrades and the Retool license.","publisher":false,"reviewed":"2026-11-16","sources":[{"title":"Self-hosted, self-managed Retool","url":"https://docs.retool.com/self-hosted/self-managed"},{"title":"Self-managed Retool quickstart","url":"https://docs.retool.com/self-hosted/self-managed/quickstart"},{"title":"Retool Kubernetes deployment tutorials","url":"https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes"},{"title":"Deploy Retool on Kubernetes with Helm","url":"https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes/kubernetes-helm"},{"title":"Retool product-specific terms","url":"https://docs.retool.com/legal/product-specific-terms"},{"title":"Enterprise deployment options and pricing","url":"https://retool.com/pricing"}],"url":"https://launchinyourcloud.com/directory/retool-self-hosted/","website":"https://retool.com/self-hosted"},{"advisories":[{"action":"Migrate DinD pools to operator-managed Kubernetes workers. Separately move CloudFormation installations to Terraform/OpenTofu while on v7 before considering v8.","conditions":"Only installations using the DinD chart require this worker migration. CloudFormation has a separate version-based boundary: v7 is its last supported major.","effectiveDate":"2027-02-01","id":"spacelift-dind-worker-chart-eol","listingIds":["spacelift-self-hosted"],"reviewed":"2026-11-18","scope":"DinD worker Helm chart only; Docker workers on EC2 and the main self-hosted service are not retired by this notice.","source":"https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog","summary":"The Docker-in-Docker worker chart reaches end of life February 1, 2027. Existing charts remain available/runnable, but receive no new versions, fixes or support.","title":"Spacelift DinD worker Helm chart support ends February 2027","type":"lifecycle"},{"action":"Use a self-hosted release containing the fix, refresh affected worker/launcher images and upgrade stack OpenTofu versions according to the changelog.","conditions":"TLS trust depends on component/binary version and connection path. The vendor also identifies fixed OpenTofu versions; updating the backend alone does not replace every stack binary.","id":"spacelift-7-1-0-ca-trust-review","listingIds":["spacelift-self-hosted"],"reviewed":"2026-11-18","scope":"Self-hosted components, launchers/workers and shipped Docker images covered by the vendor’s v7.1.0 security entry; IaC binaries used by stacks are separate.","source":"https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog","summary":"The v7.1.0 changelog updates shipped Go components/images to reject compromised eMudhra intermediate certificate chains and names CVE-2026-111943.","title":"Spacelift self-hosted component CA trust update","type":"security-advisory"}],"architecture":"Customer-operated Spacelift backend, gateway, workers and data services on cloud compute or Kubernetes.","categories":["devops","workflow-automation"],"category":"DevOps","categoryFit":{"devops":"Provides self-hosted infrastructure-as-code runs, policy, state, integrations and private workers.","workflow-automation":"Orchestrates governed infrastructure workflows, approvals and automated runs."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Spacelift explicitly documents a customer-maintained self-hosted product for AWS, Azure and GCP and links provider-specific reference architectures.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"Spacelift in customer AWS, Azure or GCP infrastructure","url":"https://docs.spacelift.io/self-hosted","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-18","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Commercial infrastructure-as-code automation platform deployed to customer AWS, Azure or Google Cloud infrastructure.","diligence":{"airGap":{"availability":"available","reviewed":"2026-11-18","scope":"Spacelift Self-Hosted: selected customer-operated edition","source":"https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/air-gapped","status":"documented","summary":"The vendor documents isolated deployment, local VCS, cached IaC providers/CLI binaries, custom runner images and manual usage/licence handling. EC2 launchers require customer-staged artifacts. Repeat this preparation for upgrades and ensure IdP/cloud targets are reachable within the selected boundary."},"commitments":{"reviewed":"2026-11-18","scope":"Spacelift Self-Hosted: selected customer-operated edition","source":"https://spacelift.io/pricing","status":"inconclusive","summary":"Spacelift’s pricing FAQ says it qualifies as a SaaS partner for AWS PPA commitments. That statement does not identify a Self-Hosted private-offer entitlement or its eligible billed dimensions. Confirm the selected Enterprise Self-Hosted order and buyer agreement; private-worker SaaS procurement is a separate boundary.","supportingSources":[{"title":"AWS commitment qualification is product/agreement-specific","url":"https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html"},{"title":"Public versus sales-assisted private procurement","url":"https://docs.spacelift.io/product/billing/aws-marketplace"}]},"compliance":{"reviewed":"2026-11-18","scope":"Spacelift Self-Hosted: selected customer-operated edition","source":"https://trust.spacelift.io/faq","status":"inconclusive","summary":"Spacelift’s Trust Center says it uses ISO 27001 internally but is not ISO 27001 certified, and instead maintains SOC 2 Type II assurance. The self-hosted security guide also claims SOC 2. Obtain the current report period, system boundary and customer controls before applying that claim to a customer-operated backend; a SaaS/private-worker assessment alone would not settle this boundary.","supportingSources":[{"title":"Self-hosted security statement and customer patch responsibilities","url":"https://docs.spacelift.io/self-hosted/latest/product/security"}]},"cost":{"reviewed":"2026-11-18","scenario":{"availability":"HA","dataGB":1000,"hoursPerMonth":730,"provider":"aws","region":"us-east-1","usage":"Average usage; no measured concurrency/throughput supplied","users":100},"scope":"Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput","source":"https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/environment-requirements","status":"inconclusive","summary":"Specify parallel runs, worker instance sizes and run duration, state/artifact/log retention, HA backend/DB, optional messaging transport, source-control/IdP dependencies and Enterprise pricing. One hundred users do not determine worker concurrency or the cloud resources those jobs manage.","supportingSources":[{"title":"Current AWS Linux EC2 rates; workload/topology still required","url":"https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json"},{"title":"Storage performance and charging inputs","url":"https://aws.amazon.com/ebs/pricing/"}]},"footprint":{"reviewed":"2026-11-18","scope":"Spacelift Self-Hosted: selected customer-operated edition","source":"https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/environment-requirements","status":"documented","summary":"The reference architecture requires PostgreSQL 14+, object storage, container orchestration, encryption keys and separate application/worker connectivity. This establishes component dependencies, not a fixed CPU/RAM minimum. Concurrent runs and worker jobs drive capacity independently of user count."},"iac":{"artifactRef":"Spacelift self-hosted Helm chart v7.2.0","artifactUrl":"https://github.com/spacelift-io/spacelift-self-hosted-helm-chart/releases/tag/v7.2.0","reviewed":"2026-11-18","scope":"Spacelift Self-Hosted: selected customer-operated edition","source":"https://github.com/spacelift-io/spacelift-self-hosted-helm-chart/releases/tag/v7.2.0","status":"documented","summary":"The self-hosted Helm chart is versioned v7.2.0 and now tracks the application release. Provider-specific Terraform/OpenTofu modules provision backing infrastructure separately. Pin chart, images, modules and worker artifacts as a compatible set; do not confuse old 0.x chart versions with application versions.","supportingSources":[{"title":"EKS reference deployment","url":"https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-eks"}]},"licensePricing":{"reviewed":"2026-11-18","scope":"Spacelift Self-Hosted: selected customer-operated edition","source":"https://spacelift.io/pricing","status":"documented","summary":"Self-Hosted is a commercial Enterprise purchase requiring a quote and licence. Public SaaS plan/worker prices do not price this deployment. Confirm backend, private workers, feature entitlement, usage reporting and renewal terms.","supportingSources":[{"title":"Isolated deployment licence/usage handling","url":"https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/air-gapped"}]},"marketplace":{"reviewed":"2026-11-18","scope":"Spacelift Self-Hosted: selected customer-operated edition","source":"https://docs.spacelift.io/product/billing/aws-marketplace","status":"inconclusive","summary":"Spacelift documents public AWS contracts and a sales-assisted private-offer route. Its pricing FAQ says plans are available through AWS, but the reviewed public offer/registration describes SaaS. A private worker is not a self-hosted backend. Obtain an order/private offer that explicitly entitles Enterprise Self-Hosted, its package and support scope before applying Marketplace availability to this listing.","supportingSources":[{"title":"Plan, Self-Hosted and Marketplace FAQ statements","url":"https://spacelift.io/pricing"},{"title":"Backend versus SaaS/private-worker boundary","url":"https://docs.spacelift.io/self-hosted"}]},"release":{"releasePublishedAt":"2026-11-11T08:09:59Z","releaseTag":"v7.2.0","reviewed":"2026-11-18","scope":"Spacelift Self-Hosted: selected customer-operated edition","source":"https://github.com/spacelift-io/spacelift-self-hosted-helm-chart/releases/tag/v7.2.0","status":"documented","summary":"Spacelift self-hosted chart v7.2.0 was published November 11, 2026 and aligns with the application release. Review the self-hosted changelog and upgrade path. The DinD worker chart reaches EOL February 1, 2027; v7 is also the last major with CloudFormation installation support.","supportingSources":[{"title":"Self-hosted changes and deprecations","url":"https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog"}]},"scim":{"availability":"available","reviewed":"2026-11-18","scope":"Spacelift Self-Hosted: selected customer-operated edition","source":"https://docs.spacelift.io/self-hosted/latest/integrations/single-sign-on/scim","status":"documented","summary":"The self-hosted SCIM 2.0 integration provisions users/groups with OAuth client credentials and requires configured SSO. Provisioning does not grant roles by itself; the corresponding group claims must also be sent during login. The self-hosted change log confirms availability from v6.1.0.","supportingSources":[{"title":"Self-hosted v6.1.0 release boundary","url":"https://docs.spacelift.io/self-hosted/latest/installing-spacelift/changelog"}]},"securityControls":{"reviewed":"2026-11-18","scope":"Spacelift Self-Hosted: selected customer-operated edition","source":"https://docs.spacelift.io/self-hosted/latest/product/security","status":"documented","summary":"Spacelift documents security boundaries for code/state/secrets and integrations. Self-hosting adds customer-managed encryption keys, backend database/object storage and private workers. SSO/SCIM configuration and worker permissions remain distinct from cloud-target authorization.","supportingSources":[{"title":"Customer backend dependencies","url":"https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/environment-requirements"},{"title":"SSO administrator behavior","url":"https://docs.spacelift.io/self-hosted/latest/integrations/single-sign-on/"}]},"sso":{"availability":"available","reviewed":"2026-11-18","scope":"Spacelift Self-Hosted: selected customer-operated edition","source":"https://docs.spacelift.io/self-hosted/latest/integrations/single-sign-on/","status":"documented","summary":"The self-hosted documentation supports SAML 2.0 or OIDC SSO and describes the transition from managed-IdP bootstrap to SSO administration. Login policies are not evaluated for the bootstrap/SSO admin, so protect and govern those accounts explicitly."}},"id":"spacelift-self-hosted","infrastructure":["servers"],"infrastructureNotes":"Spacelift Self-Hosted runs persistent backend and worker services with database and object-storage dependencies.","infrastructureReviewed":"2026-11-18","infrastructureSources":["https://docs.spacelift.io/self-hosted"],"install":"Official Terraform/OpenTofu reference architectures and Helm charts for EKS/ECS, AKS or GKE","installMethods":["terraform","helm","kubernetes"],"kind":"platform","license":"Commercial Spacelift Self-Hosted Enterprise subscription and license token required.","licenseModel":"commercial-only","licenseModelNotes":"Self-hosting is a commercial Enterprise capability governed by Spacelift subscription and license terms.","licenseModelSources":["https://docs.spacelift.io/self-hosted/latest/legal/terms","https://spacelift.io/pricing"],"licenseReviewed":"2026-11-18","model":"Fully in your account","modelLabel":"Customer-operated","name":"Spacelift Self-Hosted","notes":"This entry covers Spacelift Self-Hosted, not the Spacelift SaaS service. New features can reach SaaS before self-hosted releases; match the deployment artifacts and architecture to the licensed version.","operations":"Customer manages compute or Kubernetes, database and object storage, networking, secrets, workers, backups, scaling, upgrades and licensing.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Spacelift Self-Hosted","url":"https://docs.spacelift.io/self-hosted"},{"title":"Deploy Spacelift to EKS","url":"https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-eks"},{"title":"Deploy Spacelift to AKS","url":"https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-aks"},{"title":"Deploy Spacelift to GKE","url":"https://docs.spacelift.io/self-hosted/latest/installing-spacelift/reference-architecture/guides/deploying-to-gke"},{"title":"Spacelift pricing","url":"https://spacelift.io/pricing"}],"url":"https://launchinyourcloud.com/directory/spacelift-self-hosted/","website":"https://spacelift.io/"},{"architecture":"Customer-operated Kubernetes cluster, managed PostgreSQL and object storage, Fleet Manager and runner virtual machines.","categories":["devops","workflow-automation"],"category":"DevOps","categoryFit":{"devops":"Coordinates coding agents, source control, CI, review and verified software-delivery work.","workflow-automation":"Defines durable automation lines, approvals, checks and repair loops for recurring engineering work."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"SuperPlane documents Terraform-created EKS, AKS and GKE clusters with managed PostgreSQL, object storage and Helm releases in the customer's account. Enterprise licensing is required; Google Cloud runner images must currently be built by the operator with Packer.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"SuperPlane Enterprise on EKS, AKS and GKE","url":"https://docs.superplane.com/self-hosting/overview/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-17","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Enterprise software-factory and agent-workflow platform installed with Terraform and Helm in a customer cloud account.","diligence":{"airGap":{"reviewed":"2026-11-17","scope":"Enterprise installation; no inference from running in a private VPC","source":"https://docs.superplane.com/self-hosting/install/","status":"inconclusive","summary":"The standard installer downloads charts, images and provider tooling and configures public DNS/certificates. A supported offline licensing, dependency-transfer and upgrade workflow was not established in this guide."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for SuperPlane Enterprise Self-Hosted; unresolved within this edition/deployment","source":"https://docs.superplane.com/self-hosting/overview/","status":"inconclusive","summary":"Enterprise custom terms do not establish an eligible Marketplace offer, qualifying fees or cloud-commitment treatment."},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://docs.superplane.com/self-hosting/install/","status":"inconclusive","summary":"The reviewed SuperPlane Enterprise Self-Hosted 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."},"cost":{"reviewed":"2026-11-17","scenario":{"availability":"HA","dataGB":1000,"hoursPerMonth":730,"provider":"aws","region":"us-east-1","usage":"Average usage; no measured concurrency/throughput supplied","users":100},"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://docs.superplane.com/self-hosting/install/","status":"inconclusive","summary":"Price EKS, RDS HA PostgreSQL, storage and runner pools after the Enterprise bill of materials and active-runner concurrency are confirmed. Hosted sandbox/model charges do not price this deployment. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"Enterprise topology requirements; size the cluster and runners separately","source":"https://docs.superplane.com/self-hosting/install/","status":"documented","summary":"The Enterprise guide requires managed Kubernetes, PostgreSQL, object storage and separately provisioned runners. Runner defaults and example machine types are component settings, not a measured minimum for the complete Enterprise service."},"iac":{"reviewed":"2026-11-17","scope":"Enterprise installer and provider dependencies; community VM is a different path","source":"https://docs.superplane.com/self-hosting/install/","status":"documented","summary":"Provider-specific Terraform creates the managed Kubernetes, PostgreSQL and storage dependencies; Helm installs the application and Fleet Manager controls runners. GCP requires building runner images with Packer rather than using the published AWS/Azure images."},"licensePricing":{"reviewed":"2026-11-17","scope":"SuperPlane Enterprise Self-Hosted: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://docs.superplane.com/self-hosting/overview/","status":"documented","summary":"The documented AWS, Azure and Google Cloud Kubernetes installation requires a SuperPlane Enterprise license. The Apache-2.0 community engine and single-VM deployment do not grant Enterprise feature or support entitlements."},"marketplace":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for SuperPlane Enterprise Self-Hosted; unresolved within this edition/deployment","source":"https://docs.superplane.com/self-hosting/overview/","status":"inconclusive","summary":"Enterprise installation and direct commercial terms are documented; a current cloud Marketplace offer for this Kubernetes edition was not established."},"release":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for SuperPlane Enterprise Self-Hosted; unresolved within this edition/deployment","source":"https://docs.superplane.com/self-hosting/install/","status":"inconclusive","summary":"The installer names component/chart revisions, while the latest GitHub release is Fleet Manager v0.1.7. Neither alone establishes the current Enterprise application bundle and supported upgrade compatibility."},"scim":{"reviewed":"2026-11-17","scope":"Enterprise automated provisioning; protocol not established","source":"https://superplane.com/pricing/","status":"inconclusive","summary":"Enterprise includes automated user provisioning, but the pricing table does not name SCIM or document its endpoint, operations and identity-provider limitations."},"securityControls":{"reviewed":"2026-11-17","scope":"Enterprise Kubernetes provider installation","source":"https://docs.superplane.com/self-hosting/install/","status":"documented","summary":"The provider installation separates infrastructure provisioning, application secrets and runner management. Protect Terraform state, generated credentials and license material; configure TLS/DNS and restrict the provider permissions used by the installer."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"Enterprise self-hosting plan","source":"https://superplane.com/pricing/","status":"documented","summary":"The plan comparison includes SSO in Enterprise together with Enterprise self-hosting. Confirm the required IdP protocol and configuration with the vendor; these entitlements do not apply to the separate community VM edition."}},"id":"superplane-self-hosted","infrastructure":["servers"],"infrastructureNotes":"Terraform provisions persistent Kubernetes application services, managed PostgreSQL and object storage, while Fleet Manager creates runner virtual machines.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://docs.superplane.com/self-hosting/overview/","https://docs.superplane.com/self-hosting/install/"],"install":"Vendor Terraform modules provision EKS, AKS or GKE, managed data services and the SuperPlane Helm release","installMethods":["terraform","helm","kubernetes"],"kind":"platform","license":"Commercial SuperPlane Enterprise license required for the documented Kubernetes deployment.","licenseModel":"commercial-only","licenseModelNotes":"The documented AWS, Azure and Google Cloud Kubernetes installation requires a SuperPlane Enterprise license. The Apache-2.0 community engine and single-VM deployment do not grant Enterprise feature or support entitlements.","licenseModelSources":["https://docs.superplane.com/self-hosting/overview/","https://superplane.com/pricing/"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"SuperPlane Enterprise Self-Hosted","notes":"This entry scopes only the Enterprise Kubernetes deployment on AWS, Azure and Google Cloud. The Apache-2.0 community engine and single-VM Compose installation are separate. Google Cloud public runner images are not yet published and must be built with Packer. Connected source-control, model and workflow services can move code or data outside the cluster according to their own configuration and terms.","operations":"Customer manages the cloud account, cluster, database, object storage, runner images and VMs, DNS, TLS, backups, upgrades and connected model or tool credentials.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Self-hosted editions and provider architectures","url":"https://docs.superplane.com/self-hosting/overview/"},{"title":"Provider-specific Enterprise installation","url":"https://docs.superplane.com/self-hosting/install/"},{"title":"SuperPlane pricing and Enterprise self-hosting","url":"https://superplane.com/pricing/"},{"title":"Upstream Apache-2.0 project","url":"https://github.com/superplanehq/superplane"}],"url":"https://launchinyourcloud.com/directory/superplane-self-hosted/","website":"https://superplane.com/"},{"advisories":[{"action":"Upgrade to v1.877.0 or later, retest API clients and have an administrator resave existing GitHub App repository resources.","conditions":"Workspace members with direct API access could previously spend the configured key on other provider models; direct callers now need JSON with a string model.","disclosedOn":"2026-11-18","id":"windmill-1-877-configured-ai-key-model-policy","listingIds":["windmill"],"reviewed":"2026-11-19","scope":"Workspace or instance AI keys and GitHub App repository resources in self-hosted Windmill.","source":"https://github.com/windmill-labs/windmill/pull/12527","summary":"Windmill now rejects direct configured-key calls to provider models outside the administrator-enabled list.","supportingSources":[{"title":"v1.877.0 release","url":"https://github.com/windmill-labs/windmill/releases/tag/v1.877.0"},{"title":"Repository approval persistence","url":"https://github.com/windmill-labs/windmill/pull/12524"}],"title":"Windmill v1.877.0 configured-AI-key policy hardening","type":"security-advisory"}],"architecture":"Customer-operated server, worker processes and PostgreSQL job/state storage","categories":["workflow-automation"],"category":"Workflow automation","categoryFit":{"workflow-automation":"Code-first scripts, flows, schedules and internal apps with worker execution; enterprise controls and quotas vary."},"cloudEvidence":[{"clouds":["aws","azure","gcp","digitalocean","render","hetzner","fly","ubicloud"],"deploymentBoundaries":{"digitalocean":"not-assessed"},"notes":"The upstream self-hosting section explicitly names AWS EKS/ECS, Google Cloud, Azure, Ubicloud, Fly.io, Render, Hetzner and DigitalOcean, paired with Docker Compose and Helm installation commands. This is an upstream application-hosting compatibility statement; image licensing and enterprise features are separate. Operate the application in a customer cloud account or managed-platform project as appropriate to the selected provider.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Windmill upstream self-hosting provider compatibility","url":"https://github.com/windmill-labs/windmill","vendorSupport":"not-assessed"},{"clouds":["ubicloud"],"notes":"Ubicloud documents customer account setup, PostgreSQL and Kubernetes provisioning, Windmill Helm deployment, application access and TLS configuration. This is a full customer application deployment, not a PostgreSQL connector or GitHub Actions runner integration.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"Windmill production deployment on Ubicloud Kubernetes","url":"https://www.ubicloud.com/docs/managed-kubernetes/windmill-tutorial","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","cloudScope":"Documented customer-operated deployment guides for AWS, Azure and Google Cloud","clouds":["aws","azure","gcp","digitalocean","render","hetzner","fly","ubicloud"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"not-assessed","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"platform-workspace","cloud":"render","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"hetzner","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"platform-workspace","cloud":"fly","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"ubicloud","controlPlane":"not-assessed","evidence":[0,1],"operator":"customer"}],"description":"Run scripts and workflows with customer-operated execution workers and an app builder.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Worker rule of thumb, not a complete host minimum or a 100-user/1-TB HA design","source":"https://www.windmill.dev/docs/advanced/self_host","status":"documented","summary":"The self-hosting guide suggests roughly one worker per vCPU with 1–2 GB RAM per worker. PostgreSQL, server, proxy and optional editor services require additional capacity; worker concurrency and job isolation change sizing."},"iac":{"artifactRef":"main (moving branch)","artifactUrl":"https://github.com/windmill-labs/windmill/blob/main/docker-compose.yml","reviewed":"2026-11-14","scope":"Upstream self-hosted stack; database upgrades require explicit migration planning","source":"https://github.com/windmill-labs/windmill/blob/main/docker-compose.yml","status":"documented","summary":"The upstream Compose stack includes PostgreSQL and application/worker services. Follow its database-major-version migration notes and choose matching application and dependency releases."},"licensePricing":{"reviewed":"2026-11-20","scope":"Versioned source and distributed-binary terms differ; cloud infrastructure and support are separate","source":"https://github.com/windmill-labs/windmill/blob/v1.878.0/LICENSE","status":"documented","summary":"At v1.878.0, compilable non-enterprise source is AGPLv3, with Apache-licensed clients/specifications. Published Community binaries also contain proprietary features with free internal-use rights and restrictions on redistribution, resale and embedding. Enterprise rights require a commercial licence."},"release":{"releasePublishedAt":"2026-11-19T10:43:10Z","releaseTag":"v1.878.0","reviewed":"2026-11-19","scope":"Upstream Windmill self-hosted release","source":"https://github.com/windmill-labs/windmill/releases/tag/v1.878.0","status":"documented","summary":"Windmill v1.878.0 was published November 19, 2026. The preceding v1.877.0 release tightened configured AI-key model authorization and changed direct API validation, while also requiring administrators to resave existing GitHub App repository resources before non-admin use.","supportingSources":[{"title":"Prior reviewed release context","url":"https://github.com/windmill-labs/windmill/releases/tag/v1.875.0"},{"title":"v1.877.0 policy changes","url":"https://github.com/windmill-labs/windmill/releases/tag/v1.877.0"},{"title":"AI model allowlist enforcement","url":"https://github.com/windmill-labs/windmill/pull/12527"},{"title":"GitHub App repository approvals","url":"https://github.com/windmill-labs/windmill/pull/12524"}]},"securityControls":{"reviewed":"2026-11-19","scope":"Windmill configured AI-key proxy and GitHub App repository-resource authorization","source":"https://github.com/windmill-labs/windmill/pull/12527","status":"documented","summary":"v1.877.0 blocks workspace members from spending configured workspace or instance AI keys on models outside the admin-enabled list. Direct configured-key calls now require JSON with a string model; retest clients. Existing GitHub App repository resources require one administrator save before non-admin access.","supportingSources":[{"title":"v1.877.0 release","url":"https://github.com/windmill-labs/windmill/releases/tag/v1.877.0"},{"title":"Repository approval behavior","url":"https://github.com/windmill-labs/windmill/pull/12524"}]},"sso":{"availability":"edition-dependent","reviewed":"2026-11-20","scope":"Instance user login; built-in SSO and Enterprise SAML have different entitlements","source":"https://www.windmill.dev/docs/advanced/setup_oauth","status":"documented","summary":"The self-hosted OAuth/SSO guide documents user login through Google, Microsoft, GitHub and other configured providers, separately from OAuth resource connections. SAML and SCIM are explicitly Enterprise features; identity-group synchronization and custom claim settings also have edition limits.","supportingSources":[{"title":"Enterprise SAML and SCIM","url":"https://www.windmill.dev/docs/advanced/saml_and_scim"}]}},"id":"windmill","infrastructure":["servers"],"infrastructureNotes":"Classified servers for the documented long-lived server/worker containers and PostgreSQL queue/state. Fargate compatibility is managed-container hosting, not a function-only software stack.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://www.windmill.dev/docs/advanced/self_host"],"install":"Docker Compose or Kubernetes/Helm with PostgreSQL and worker replicas","installMethods":["helm","docker"],"kind":"product","license":"AGPLv3 open-source components; commercial Enterprise licensing and plan-dependent limits","licenseModel":"open-source","licenseModelNotes":"Official repository licensing combines AGPLv3/Apache-2.0 components with proprietary Enterprise feature code. The broad listing includes both community and commercial editions; current plan limits must be checked separately.","licenseModelSources":["https://github.com/windmill-labs/windmill/blob/main/LICENSE","https://www.windmill.dev/pricing"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Windmill Self-Hosted","notes":"This entry excludes hosted Windmill Cloud. Review current community limits and Enterprise features rather than assuming all features are included. Workflow code can reach external services; worker sandboxing and credentials need explicit configuration. Official self-hosting documentation gives AWS/Azure/GCP guidance. Windmill v1.877.0 prevents workspace members from bypassing the configured AI-model allowlist through direct proxy or completion API calls. Direct configured-key POSTs must now contain JSON with a string model, and existing GitHub App repository resources remain admin-only until an administrator saves them once. Retest API callers and repository-resource access. v1.878.0 is the reviewed current follow-up release.","operations":"Customer operates server/worker containers, PostgreSQL, TLS, job isolation, backups and upgrades.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Self-host architecture, Docker and provider guidance","url":"https://www.windmill.dev/docs/advanced/self_host"},{"title":"Project capabilities and license files","url":"https://github.com/windmill-labs/windmill"},{"title":"Self-hosted edition limits","url":"https://www.windmill.dev/pricing"},{"title":"Licensing and edition terms","url":"https://github.com/windmill-labs/windmill/blob/main/LICENSE"},{"title":"Windmill production deployment on Ubicloud Kubernetes","url":"https://www.ubicloud.com/docs/managed-kubernetes/windmill-tutorial"},{"title":"Windmill v1.878.0 release","url":"https://github.com/windmill-labs/windmill/releases/tag/v1.878.0"},{"title":"Windmill v1.877.0 policy hardening","url":"https://github.com/windmill-labs/windmill/releases/tag/v1.877.0"},{"title":"Configured AI-key model enforcement","url":"https://github.com/windmill-labs/windmill/pull/12527"},{"title":"GitHub App repository approval persistence","url":"https://github.com/windmill-labs/windmill/pull/12524"}],"url":"https://launchinyourcloud.com/directory/windmill/","website":"https://www.windmill.dev/"}],"schemaVersion":1,"url":"https://launchinyourcloud.com/clouds/gcp/workflow-automation/"}