{"catalog":"https://launchinyourcloud.com/api/v1/catalog.json","catalogRevision":"170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde","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","listings":[{"advisories":[{"action":"Apply the latest Admin Console update, restart as directed and verify installed package versions.","conditions":"The exact installed application and operating-system package set determines exposure.","id":"3cx-v20-november-2026-linux-security-hotfix","listingIds":["3cx-self-hosted"],"reviewed":"2026-11-19","scope":"Self-hosted 3CX V20 SP9/SP10 Linux packages; hosted-by-3CX service is outside this listing.","source":"https://www.3cx.com/blog/change-log/pbx-security-updates/","summary":"3CX refreshed V20 SP9/SP10 Linux packages including nginx, the kernel, PostgreSQL, BIND, SASL and rsync.","title":"3CX V20 November 2026 Linux security hotfix","type":"security-advisory"}],"architecture":"Customer-operated PBX/application VM with web client, SIP/RTP media, certificates, firewall rules and external trunk or carrier dependencies.","categories":["collaboration"],"category":"Collaboration","categoryFit":{"collaboration":"Provides business voice, video, chat, web meetings and PBX collaboration in a customer-operated deployment."},"cloudEvidence":[{"clouds":["aws"],"notes":"3CX documents provisioning the PBX in a customer AWS account.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"3CX in the customer's AWS account","url":"https://www.3cx.com/docs/hosted-pbx-aws/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"3CX documents provisioning the PBX in a customer Azure account.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"3CX in the customer's Azure account","url":"https://www.3cx.com/docs/hosted-pbx-azure/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"3CX documents provisioning the PBX in a customer Google Cloud account.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"3CX in the customer's Google Cloud account","url":"https://www.3cx.com/docs/hosted-pbx-google-cloud/","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"The current private-cloud install guide identifies DigitalOcean as a supported customer-account deployment target.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"3CX in the customer's DigitalOcean account","url":"https://www.3cx.com/docs/manual/install/","vendorSupport":"not-assessed"},{"applicableVersions":["20.0.10.1785"],"clouds":["aws"],"notes":"The vendor publishes the full PBX as a Debian 12 x86 AMI in the customer AWS account. Software licensing is external to AWS Marketplace; telecom and infrastructure charges are separate.","reviewed":"2026-11-18","sourceType":"marketplace-offer","title":"3CX-published AWS self-hosted AMI","url":"https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-18","clouds":["aws","azure","gcp","digitalocean"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0,4],"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"}],"description":"Commercial business communications and PBX platform installed into the customer's public-cloud account.","diligence":{"airGap":{"availability":"unavailable","reviewed":"2026-11-18","scope":"3CX standard documented self-hosted activation and operation","source":"https://www.3cx.com/docs/manual/firewall-router-configuration/","status":"documented","summary":"The standard documented self-hosted configuration requires outbound HTTPS to activate.3cx.com for licence activation and other external services for updates and selected functions. It is not a fully disconnected deployment path; a separate offline exception was not established."},"commitments":{"availability":"unavailable","reviewed":"2026-11-18","scope":"Externally billed software licence for the exact reviewed public 3CX AMI offer; not all provider spend or future private offers","source":"https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm","status":"documented","summary":"The reviewed 3CX AMI offer explicitly requires buying the software licence outside AWS Marketplace. That externally billed licence is not a software charge on the AWS Marketplace invoice for this offer. This answers the licence-billing route only; eligible EC2/EBS spend or a separately negotiated private offer still requires the buyer’s AWS agreement and seller order terms.","supportingSources":[{"title":"AWS BYOL pricing boundary","url":"https://docs.aws.amazon.com/marketplace/latest/userguide/BYOL-pricing.html"},{"title":"Commitment qualification remains product/agreement-specific","url":"https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html"}]},"compliance":{"reviewed":"2026-11-18","scope":"3CX Self-Hosted: selected customer-operated edition","source":"https://www.3cx.com/pbx/security/","status":"inconclusive","summary":"3CX describes security reviews with Mandiant, ReversingLabs, Coverity and HackerOne. This establishes a vendor security-testing statement, not a current independent attestation whose scope covers the buyer’s PBX, recordings, carrier/transcription services and operations. Obtain the relevant report, audit period, findings/remediation and deployment boundary."},"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://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/","status":"inconclusive","summary":"Specify concurrent calls, extensions, edition, SIP trunks/minutes, recording/transcription volume, retention and HA/failover requirements. The t3.xlarge sizing example does not include carrier service, a second server, recording backup or external AI services.","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":"3CX Self-Hosted: selected customer-operated edition","source":"https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/","status":"documented","summary":"The current small PBX table lists 2 vCPU/4 GB RAM and 80 GB SSD, with larger tiers and extra recording/log capacity. Its cloud table places up to 250 extensions in the large tier, with AWS t3.xlarge as an example. These are extension/call-capacity guidelines; HA, simultaneous calls and a 1 TB recording policy still need a design."},"iac":{"reviewed":"2026-11-18","scope":"3CX Self-Hosted: selected customer-operated edition","source":"https://www.3cx.com/docs/manual/install/","status":"documented","summary":"The current installation guide provisions a private-cloud PBX in the customer’s chosen AWS, Azure, Google Cloud or DigitalOcean account. This is a vendor deployment workflow, not a reviewed source-controlled Terraform or CloudFormation artifact."},"licensePricing":{"reviewed":"2026-11-18","scope":"3CX Self-Hosted: selected customer-operated edition","source":"https://www.3cx.com/ordering/pricing/","status":"documented","summary":"3CX publishes annual system licences by edition and simultaneous-call capacity, with extension limits and feature differences. Obtain the selected self-hosted tier; a count of internal users alone does not price licences, trunks or calling charges. The reviewed AWS offer bills its software licence outside AWS Marketplace.","supportingSources":[{"title":"External licence billing in the exact AWS offer","url":"https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm"}]},"marketplace":{"availability":"available","offers":[{"cloud":"aws","delivery":"Amazon Machine Image (AMI), x86","id":"prodview-f5qwwdeeq4uvm","publisher":"3CX","url":"https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm","version":"20.0.10.1785"}],"reviewed":"2026-11-18","scope":"3CX AWS self-hosted AMI 20.0.10.1785, externally licensed","source":"https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm","status":"documented","summary":"3CX publishes prodview-f5qwwdeeq4uvm as an x86 AWS AMI, package 20.0.10.1785 on Debian 12. Its pricing explicitly requires an external 3CX billing/licence relationship; the software licence is purchased outside AWS Marketplace. AWS infrastructure charges remain separate. This is the customer-operated PBX, not Hosted by 3CX.","supportingSources":[{"title":"Vendor AWS Marketplace installation guide","url":"https://www.3cx.com/docs/pbx-amazon-aws-marketplace/"}]},"release":{"releasePublishedOn":"2026-11-11","releaseTag":"20.0.10.1785","reviewed":"2026-11-18","scope":"3CX Self-Hosted: selected customer-operated edition","source":"https://www.3cx.com/blog/releases/ai-agents-mcp-local-ai/","status":"documented","summary":"3CX announced V20 Update 10 on November 11, 2026; the V20 change log identifies production build 20.0.10.1785. Exclude release candidates and separately versioned mobile clients from this PBX snapshot.","supportingSources":[{"title":"Production PBX build number","url":"https://www.3cx.com/blog/change-log/phone-system-change-log-v20/"},{"title":"AWS AMI package 20.0.10.1785","url":"https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm"}]},"scim":{"reviewed":"2026-11-18","scope":"3CX Self-Hosted: selected customer-operated edition","source":"https://www.3cx.com/docs/manual/microsoft-365/","status":"inconclusive","summary":"The M365 guide documents nightly one-way sync, not a SCIM endpoint. A user deleted or disabled in M365 remains in 3CX and must be removed manually; deleting only in 3CX causes recreation at the next sync while the M365 account remains. This confirms a manual offboarding requirement, but does not establish SCIM operations or active-session/extension revocation through a SCIM integration."},"securityControls":{"reviewed":"2026-11-19","scope":"Self-hosted 3CX V20 SP9/SP10 Linux packages; hosted-by-3CX service is outside this listing","source":"https://www.3cx.com/blog/change-log/pbx-security-updates/","status":"documented","summary":"The firewall guide specifies SIP/RTP, tunnel and HTTPS connectivity and requires uninspected outbound HTTPS for activation. Configure the required ports and TLS/FQDN correctly; external SIP trunks, push and meeting services create separate dependencies. M365 sync does not remove users deleted/disabled at the IdP; explicitly remove them in 3CX and review sessions, SIP/extension credentials and retained data. Current review: The November 2026 V20 SP9/SP10 security-hotfix log refreshes Linux packages including nginx, kernel, PostgreSQL, BIND, SASL and rsync. Apply the latest Admin Console update and verify the installed package set.","supportingSources":[{"title":"Prior security-controls source","url":"https://www.3cx.com/docs/manual/firewall-router-configuration/"},{"title":"Microsoft 365 SSO configuration","url":"https://www.3cx.com/docs/manual/microsoft-365/"}]},"sso":{"availability":"edition-dependent","reviewed":"2026-11-18","scope":"3CX Self-Hosted: selected customer-operated edition","source":"https://www.3cx.com/docs/manual/microsoft-365/","status":"documented","summary":"The Microsoft 365 integration documents SSO to the 3CX web client and one-way scheduled user synchronization. It requires a supported Microsoft 365 Exchange plan and configured application permissions. This does not establish SCIM or every client’s login behavior. Deleted/disabled M365 users remain in 3CX until manually removed; SSO is not a substitute for offboarding.","supportingSources":[]}},"id":"3cx-self-hosted","infrastructure":["servers"],"infrastructureNotes":"3CX runs as a persistent PBX and communications application on a customer-managed cloud VM.","infrastructureReviewed":"2026-11-18","infrastructureSources":["https://www.3cx.com/docs/manual/install/"],"install":"3CX deployment wizard or provider Marketplace path for AWS, Azure, Google Cloud or DigitalOcean","installMethods":["platform-template","vm-image"],"kind":"product","license":"Proprietary annual 3CX system license; edition and simultaneous-call entitlements vary.","licenseModel":"commercial-only","licenseModelNotes":"3CX is proprietary commercial software licensed by edition and capacity; cloud hosting and telecom services are separate.","licenseModelSources":["https://www.3cx.com/ordering/pricing/"],"licenseReviewed":"2026-11-18","model":"Fully in your account","modelLabel":"Customer-operated","name":"3CX Self-Hosted","notes":"This entry excludes the Hosted by 3CX service. External SIP trunks, carriers, calling charges and endpoint hardware remain separate. Review provider sizing and media-network requirements before deployment. The AWS AMI is vendor-published package 20.0.10.1785 on Debian 12, with its 3CX licence billed outside AWS Marketplace. 3CX's November 2026 security-hotfix log updates V20 SP9/SP10 Linux packages including nginx, the kernel, PostgreSQL, BIND, SASL and rsync. Apply the latest update through the Admin Console, restart as directed and verify the deployed package set; do not treat the application build number alone as proof that OS hotfixes are current.","operations":"Customer manages the cloud instance, networking and firewall, DNS/FQDN, backups, upgrades, monitoring, trunks, endpoints and licensing.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Install 3CX in a private cloud","url":"https://www.3cx.com/docs/manual/install/"},{"title":"Deploy 3CX on AWS","url":"https://www.3cx.com/docs/hosted-pbx-aws/"},{"title":"Deploy 3CX on Azure","url":"https://www.3cx.com/docs/hosted-pbx-azure/"},{"title":"Deploy 3CX on Google Cloud","url":"https://www.3cx.com/docs/hosted-pbx-google-cloud/"},{"title":"3CX pricing","url":"https://www.3cx.com/ordering/pricing/"},{"title":"Exact vendor AWS AMI and external licence billing","url":"https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm"},{"title":"3CX PBX security updates change log","url":"https://www.3cx.com/blog/change-log/pbx-security-updates/"}],"url":"https://launchinyourcloud.com/directory/3cx-self-hosted/","website":"https://www.3cx.com/"},{"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/"},{"architecture":"Customer-operated platform services, connector jobs, metadata database and object storage","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Moves data between APIs, databases, files, warehouses and lakes using customer-operated connectors and synchronization jobs."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Airbyte documents its Helm deployment for Kubernetes and explicitly names AWS, Google Cloud and Azure, including EC2/EKS and GCE/GKE examples. This is the self-managed application path; configure provider policies, external storage, secrets and production ingress separately.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Airbyte self-managed deployment on named cloud providers","url":"https://docs.airbyte.com/platform/deploying-airbyte","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"DigitalOcean lists an Airbyte-published 1-Click Droplet image, version 0.30.25 on Ubuntu 20.04, and provides creation instructions for the customer account. This is legacy, version-specific application deployment evidence, not verification of the current Helm-based release or current vendor support. Confirm image availability, compatibility, upgrade paths and support before selecting this route.","reviewed":"2026-11-13","sourceType":"marketplace-offer","title":"Airbyte-published v0.30.25 DigitalOcean Droplet image","url":"https://marketplace.digitalocean.com/apps/airbyte","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-13","clouds":["aws","azure","gcp","digitalocean"],"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":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Self-managed data movement and ELT platform with customer-operated connectors and job execution.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Airbyte Core local installation; production HA excluded","source":"https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart","status":"documented","summary":"The Core quickstart recommends at least 4 CPUs and 8 GB RAM; low-resource mode can run with 2 CPUs and 8 GB but disables Connector Builder. This is a local deployment profile. Connector concurrency, storage and production/HA components require separate sizing."},"iac":{"artifactRef":"Choose an abctl release and compatible chart version","artifactUrl":"https://github.com/airbytehq/abctl","reviewed":"2026-11-20","scope":"Official Core installation tooling; local cluster is not an HA architecture","source":"https://docs.airbyte.com/platform/deploying-airbyte/abctl","status":"documented","summary":"Airbyte publishes abctl to install a local Kubernetes-based Core instance and a Helm deployment path for customer infrastructure. Local abctl creates its own cluster using Docker; production requires separately configured ingress, storage, secrets and chart/application compatibility."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/airbytehq/airbyte/master/LICENSE","status":"documented","summary":"The platform is under Elastic License 2.0, including restrictions on offering a substantial hosted/managed service and bypassing licence keys. Connector licences vary. Enterprise features, support and alternative commercial rights require separate terms; this does not price infrastructure."},"marketplace":{"offers":[{"cloud":"digitalocean","delivery":"Droplet 1-Click","id":"airbyte","publisher":"Airbyte","url":"https://marketplace.digitalocean.com/apps/airbyte","version":"0.30.25"}],"reviewed":"2026-11-14","scope":"Legacy DigitalOcean image; current upstream deployment requires separate validation","source":"https://marketplace.digitalocean.com/apps/airbyte","status":"documented","summary":"The DigitalOcean 1-Click page still identifies Airbyte 0.30.25 on Ubuntu 20.04. This is legacy package evidence, not confirmation of a current release, current support or suitability for a new production deployment."},"sso":{"reviewed":"2026-11-20","scope":"Self-managed OIDC workflow; Core edition entitlement unresolved","source":"https://docs.airbyte.com/platform/access-management/sso","status":"inconclusive","summary":"The vendor documents OIDC login for self-managed instances, but the current plan comparison emphasizes Cloud/Enterprise Flex while Core quickstart uses local credentials. The reviewed pages do not unambiguously establish federation entitlement for the selected Core distribution; obtain edition/version confirmation.","supportingSources":[{"title":"Current self-managed and hybrid plan scope","url":"https://docs.airbyte.com/platform"},{"title":"Core quickstart authentication","url":"https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart"}]}},"id":"airbyte","infrastructure":["servers"],"infrastructureNotes":"The documented deployment uses long-lived Kubernetes platform services and connector job pods, with a metadata database and object storage. Managed cloud databases or object stores do not make the application runtime serverless.","infrastructureReviewed":"2026-11-13","infrastructureSources":["https://docs.airbyte.com/platform/deploying-airbyte","https://marketplace.digitalocean.com/apps/airbyte"],"install":"Official Helm chart for current Kubernetes deployments; cloud VMs are also documented. DigitalOcean separately lists a legacy 1-Click Droplet image.","installMethods":["helm","vm-image"],"kind":"product","license":"Elastic License 2.0 for the Airbyte platform; connector and component licenses vary. Enterprise and Cloud offerings use separate commercial terms.","licenseModel":"source-available","licenseModelNotes":"The Airbyte platform uses Elastic License 2.0, which permits self-hosting and source modification but restricts managed-service use and protected license functionality. Connectors and development tooling can carry different licenses; inspect the selected component and release. Commercial Enterprise and Cloud terms are separate.","licenseModelSources":["https://github.com/airbytehq/airbyte/blob/master/LICENSE","https://github.com/airbytehq/airbyte/blob/master/docs/community/licenses/license-faq.md"],"licenseReviewed":"2026-11-13","model":"Fully in your account","modelLabel":"Customer-operated","name":"Airbyte Self-Managed","notes":"This entry covers Airbyte Self-Managed, not Airbyte Cloud or the hybrid offering. Connector jobs communicate with configured external sources and destinations. Elastic License 2.0 permits internal self-hosting but restricts offering the software as a managed service and bypassing license-key functionality. DigitalOcean lists a separate legacy v0.30.25 Marketplace image on Ubuntu 20.04. That evidence does not establish current Helm-release compatibility or current vendor support; verify image availability, upgrade paths and support for the selected release.","operations":"Customer manages Kubernetes or VM capacity, the metadata database, object storage, secrets, connector images, network access, backups and upgrades.","publisher":false,"reviewed":"2026-11-13","sources":[{"title":"Airbyte platform and self-managed plans","url":"https://docs.airbyte.com/platform"},{"title":"Self-managed Kubernetes and cloud deployment","url":"https://docs.airbyte.com/platform/deploying-airbyte"},{"title":"Elastic License 2.0 FAQ","url":"https://github.com/airbytehq/airbyte/blob/master/docs/community/licenses/license-faq.md"},{"title":"Airbyte platform Elastic License 2.0","url":"https://github.com/airbytehq/airbyte/blob/master/LICENSE"},{"title":"Legacy Airbyte v0.30.25 DigitalOcean Marketplace image","url":"https://marketplace.digitalocean.com/apps/airbyte"}],"url":"https://launchinyourcloud.com/directory/airbyte/","website":"https://airbyte.com/"},{"architecture":"Persistent Kafka workload nodes run in the customer's custom cloud. In the documented private topology, the Aiven management plane connects through a bastion.","categories":["streaming"],"category":"Streaming","categoryFit":{"streaming":"Managed Apache Kafka brokers in the customer's cloud account, operated by Aiven."},"cloudEvidence":[{"clouds":["aws"],"notes":"The customer applies a Terraform template in its AWS account and grants Aiven permissions through an IAM role.","reviewed":"2026-11-21","sourceType":"vendor-documentation","title":"Aiven custom cloud on AWS","url":"https://aiven.io/docs/platform/howto/byoc/create-cloud/create-aws-custom-cloud","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The customer sets up an Azure custom cloud in its subscription before provisioning Kafka.","reviewed":"2026-11-21","sourceType":"vendor-documentation","title":"Aiven custom cloud on Azure","url":"https://aiven.io/docs/platform/howto/byoc/create-cloud/create-azure-custom-cloud","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The customer sets up a Google Cloud custom cloud in its project before provisioning Kafka.","reviewed":"2026-11-21","sourceType":"vendor-documentation","title":"Aiven custom cloud on Google Cloud","url":"https://aiven.io/docs/platform/howto/byoc/create-cloud/create-google-custom-cloud","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-21","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"vendor-hosted","evidence":[0],"operator":"vendor"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"vendor-hosted","evidence":[1],"operator":"vendor"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"vendor-hosted","evidence":[2],"operator":"vendor"}],"description":"Managed Apache Kafka brokers in the customer's cloud account, operated by Aiven.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Managed Kafka BYOC sizing unresolved; do not substitute Aiven-hosted Free/Developer plans.","source":"https://aiven.io/docs/products/kafka/get-started/create-kafka-service-byoc","status":"inconclusive","summary":"The Kafka BYOC guide requires a fixed Classic Kafka plan and gives business-4 as a CLI example, but does not establish a quantitative minimum topology for the customer's provider, region and workload. Diskless topics have separate eligible plans and can add a PostgreSQL service. Obtain broker counts, instance resources, storage and availability-zone design from Aiven; the example plan name is not a sizing guarantee."},"iac":{"availability":"available","reviewed":"2026-11-21","scope":"AWS custom-cloud Terraform onboarding; obtain and review the generated template and permissions.","source":"https://aiven.io/docs/platform/howto/byoc/create-cloud/create-aws-custom-cloud","status":"documented","summary":"After BYOC approval, Aiven generates a customer-specific Terraform template in Console or CLI. The customer downloads and applies it to prepare the cloud account and delegated access, then provisions Kafka in the custom cloud. This is account-specific managed-service onboarding, not a public standalone self-managed Kafka installer.","supportingSources":[{"title":"Google Cloud generated Terraform onboarding","url":"https://aiven.io/docs/platform/howto/byoc/create-cloud/create-google-custom-cloud"},{"title":"Azure custom-cloud onboarding","url":"https://aiven.io/docs/platform/howto/byoc/create-cloud/create-azure-custom-cloud"}]},"licensePricing":{"reviewed":"2026-11-21","scope":"Commercial Kafka BYOC eligibility and separate billing; request the supported plan and a quote.","source":"https://aiven.io/docs/platform/concepts/byoc","status":"documented","summary":"BYOC is a bespoke commercial managed service requiring an Aiven commitment and Advanced or Premium support. Pricing depends on the agreement. Aiven bills managed-service fees separately from the customer's cloud infrastructure and network traffic; standard all-inclusive Aiven Cloud rates do not establish BYOC charges."},"sso":{"availability":"available","reviewed":"2026-11-21","scope":"Aiven organization / Console identity for the managed BYOC service, not Kafka protocol clients.","source":"https://aiven.io/docs/platform/howto/saml/add-identity-providers","status":"documented","summary":"Organization administrators can configure a SAML identity provider and verified domains for Aiven Console users. BYOC Kafka is provisioned through that same Aiven organization and Console. This authenticates the vendor-hosted management plane; Kafka client authentication is a separate configuration.","supportingSources":[{"title":"Kafka BYOC Console prerequisites","url":"https://aiven.io/docs/products/kafka/get-started/create-kafka-service-byoc"}]}},"id":"aiven-kafka-byoc","infrastructure":["servers"],"infrastructureNotes":"Persistent Kafka workload nodes run in the customer's custom cloud. In the documented private topology, the Aiven management plane connects through a bastion.","infrastructureReviewed":"2026-11-21","infrastructureSources":["https://aiven.io/docs/platform/howto/byoc/networking-security"],"install":"Enable BYOC with Aiven, apply the provider-specific Terraform template, then provision Classic Kafka through the Aiven Console or CLI.","installMethods":["terraform","vendor-assisted"],"kind":"platform","license":"Commercial managed service. BYOC requires an Aiven commitment and Advanced or Premium support. Aiven and the cloud provider bill separately.","licenseModel":"commercial-only","licenseModelNotes":"Commercial managed service. BYOC requires an Aiven commitment and Advanced or Premium support. Aiven and the cloud provider bill separately.","licenseModelSources":["https://aiven.io/docs/platform/concepts/byoc"],"licenseReviewed":"2026-11-21","model":"BYOC","modelLabel":"Vendor-operated BYOC","name":"Aiven for Apache Kafka BYOC","notes":"Classic Kafka uses fixed service plans. Diskless topics require enablement and an eligible custom cloud and plan. Aiven documents limited OCI access for its wider BYOC program. Confirm product and region eligibility. Metrics and logs reach Aiven, and controlled support access is documented. Agree how to migrate topics and remove delegated access before exit.","operationReview":{"controlPlane":"vendor-hosted","modelLabel":"Vendor-operated BYOC","operator":"vendor","reviewed":"2026-11-21","source":"https://aiven.io/docs/products/kafka/get-started/create-kafka-service-byoc","summary":"Aiven operates and maintains Kafka in the customer's custom cloud. Its separate management plane provisions and monitors the service through delegated access; the customer supplies cloud-account, network and policy prerequisites.","supportingSources":[{"title":"BYOC networking and control plane","url":"https://aiven.io/docs/platform/howto/byoc/networking-security"}]},"operations":"Aiven manages provisioning and maintenance. The customer provides the cloud account, network configuration, IAM, quotas, and backup storage access.","publisher":false,"reviewed":"2026-11-21","sources":[{"title":"Kafka BYOC provisioning","url":"https://aiven.io/docs/products/kafka/get-started/create-kafka-service-byoc"},{"title":"Private networking and vendor access","url":"https://aiven.io/docs/platform/howto/byoc/networking-security"},{"title":"BYOC eligibility and billing","url":"https://aiven.io/docs/platform/concepts/byoc"},{"title":"Shared responsibility matrix","url":"https://aiven.io/responsibility-matrix"},{"title":"Aiven custom cloud on AWS","url":"https://aiven.io/docs/platform/howto/byoc/create-cloud/create-aws-custom-cloud"},{"title":"Aiven custom cloud on Azure","url":"https://aiven.io/docs/platform/howto/byoc/create-cloud/create-azure-custom-cloud"},{"title":"Aiven custom cloud on Google Cloud","url":"https://aiven.io/docs/platform/howto/byoc/create-cloud/create-google-custom-cloud"}],"url":"https://launchinyourcloud.com/directory/aiven-kafka-byoc/","website":"https://aiven.io/kafka"},{"advisories":[{"action":"Upgrade the server and extension to compatible 1.20+ releases and review optional MCP identity forwarding.","conditions":"Applicability depends on enabled embedding, extensions, agents, recovery, and document tools.","id":"anythingllm-1-20-0-access-hardening","listingIds":["anythingllm"],"reviewed":"2026-11-18","scope":"Upstream v1.20.0 release notes; no consolidated affected-version range is asserted.","source":"https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0","summary":"AnythingLLM v1.20.0 hardens embed history, extension API-key authorization, workspace-agent access, password recovery, framing, and document-tool downloads.","title":"AnythingLLM 1.20.0 access hardening","type":"security-advisory"}],"architecture":"Customer-operated web application and document/retrieval storage with configurable inference providers","categories":["ai-applications-rag","ai-tools"],"category":"AI applications \u0026 RAG","categoryFit":{"ai-applications-rag":"Multi-user application for document-grounded chat, RAG and agents with configurable model and vector-database integrations.","ai-tools":"Self-hosted AI application interface and retrieval/agent integrations; model inference is separately configured."},"cloudEvidence":[{"clouds":["aws","gcp","railway"],"notes":"The project explicitly names AWS, Google Cloud and Railway for self-hosting the Docker edition, paired with its Docker installation workflow. This is an upstream hosting compatibility statement. Model endpoints, embeddings and external vector stores are separately configured and can have different data boundaries.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"AnythingLLM Docker installation overview","url":"https://docs.anythingllm.com/installation-docker/overview","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","gcp","railway"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Release maintenance and contributor credits","url":"https://github.com/Mintplex-Labs/anything-llm/releases"},{"title":"Community contribution process","url":"https://github.com/Mintplex-Labs/anything-llm"}],"summary":"Public release notes credit named contributors and new contributors across multiple releases, alongside an established open contribution process."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Self-hosted application for document-grounded AI chat, retrieval and agents.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Self-hosted Docker baseline; model services, data and HA additional","source":"https://docs.anythingllm.com/installation-docker/system-requirements","status":"documented","summary":"The Docker requirements list 2 GB RAM, a two-core CPU with AVX2 and 5 GB storage as a small starting profile. Model inference, embeddings, vector storage, documents and concurrency can require much more; verify AVX2 passthrough on virtual machines. This is not an HA or 1-TB production recommendation."},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://docs.anythingllm.com/installation-docker/local-docker","status":"documented","summary":"The Docker guide documents a prebuilt application image or source-built Compose setup. Persistent storage and user permissions must be configured; local model/vector endpoints and their resources are separate."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/master/LICENSE","status":"documented","summary":"The reviewed upstream core is MIT licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Model weights and external model APIs require their own review."},"release":{"releasePublishedAt":"2026-11-17T20:38:19Z","releaseTag":"v1.20.0","reviewed":"2026-11-18","scope":"Upstream AnythingLLM self-hosted release","source":"https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0","status":"documented","summary":"AnythingLLM v1.20.0 was published November 17, 2026. It includes access and session hardening plus MCP identity forwarding and timeout changes; keep server and extension versions compatible."},"securityControls":{"reviewed":"2026-11-18","scope":"Upstream v1.20.0 release notes; no consolidated affected-version range is asserted.","source":"https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0","status":"documented","summary":"Current advisory review: AnythingLLM v1.20.0 hardens embed history, extension API-key authorization, workspace-agent access, password recovery, framing, and document-tool downloads. Upgrade the server and extension to compatible 1.20+ releases and review optional MCP identity forwarding."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Docker Simple SSO passthrough; not standards-based federation","source":"https://docs.anythingllm.com/configuration","status":"documented","summary":"The self-hosted Docker configuration offers Simple SSO passthrough: a trusted application uses an API key to issue short-lived single-use login links for existing users. It requires multi-user mode and a configured admin. This is a bespoke integration, not native SAML/OIDC federation; the vendor recommends internally exposed instances."}},"id":"anythingllm","infrastructure":["servers"],"infrastructureNotes":"Customer-operated web application and document/retrieval storage with configurable inference providers. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.anythingllm.com/installation-docker/overview"],"install":"Run the official Docker edition on a customer-operated host with persistent application storage and configured model/vector endpoints.","installMethods":["docker"],"kind":"product","license":"MIT License for upstream AnythingLLM; model weights, connectors and provider services have separate terms.","licenseModel":"open-source","licenseModelNotes":"MIT License for upstream AnythingLLM; model weights, connectors and provider services have separate terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.","licenseModelSources":["https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/master/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"AnythingLLM Docker","notes":"The Docker edition supports multi-user operation and differs from the desktop application. Local inference is an option; configured external LLMs, embeddings, vector stores and agent tools can send data outside the account. AnythingLLM v1.20.0 hardens embed history, extension API-key authorization, workspace-agent access, password recovery, framing, and document-tool downloads. Optional MCP identity forwarding creates a new outbound identity path; keep the server and extension on compatible 1.20+ versions.","operations":"Customer manages users, documents, persistent storage, model access, integration secrets, backups and upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Official installation and runtime","url":"https://docs.anythingllm.com/installation-docker/overview"},{"title":"Upstream project and capabilities","url":"https://github.com/Mintplex-Labs/anything-llm"},{"title":"Current upstream license","url":"https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/master/LICENSE"},{"title":"AnythingLLM v1.20.0 release","url":"https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0"}],"url":"https://launchinyourcloud.com/directory/anythingllm/","website":"https://anythingllm.com/"},{"architecture":"Customer-operated JVM analytics services, metadata store and deep storage","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Real-time OLAP database for SQL analysis of ingested streaming and batch data; this is an analytics engine rather than a dashboard authoring application."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"The Apache project explicitly identifies AWS, Google Cloud and Azure as deployment environments for Druid. This is a project compatibility statement paired with the installation documentation, not a managed service or certification; configure metadata, deep storage and cluster operations separately.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Apache Druid cloud deployment FAQ","url":"https://druid.apache.org/faq/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Current Druid releases","url":"https://github.com/apache/druid/releases"},{"title":"Named production adopters","url":"https://druid.apache.org/druid-powered/"}],"summary":"Apache project with a maintained upstream release history and a project-curated production adopter directory including Adikteev, AdsWizz and Airbnb."},"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":"Column-oriented analytics database for interactive queries over streaming and historical event data.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Druid 39 local tutorial baseline; production capacity excluded","source":"https://druid.apache.org/docs/latest/tutorials/index.html","status":"documented","summary":"The current 39.0.0 local quickstart requires at least 6 GiB RAM and Java 25. It is an introductory single-machine ingestion/query setup, not a production or HA footprint. Data volume, ingestion tasks, service roles and availability requirements need separate sizing."},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://druid.apache.org/docs/latest/operations/single-server/","status":"documented","summary":"The server distribution includes bin/start-druid, which derives memory settings from host resources. Older single-server reference scripts are deprecated; production cluster storage/services need a separate architecture plan."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/apache/druid/master/LICENSE","status":"documented","summary":"The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate."},"release":{"releasePublishedAt":"2026-11-19T09:32:39Z","releaseTag":"druid-39.0.0","reviewed":"2026-11-19","scope":"Upstream Apache Druid release; deployment packages and commercial distributions may differ","source":"https://github.com/apache/druid/releases/tag/druid-39.0.0","status":"documented","summary":"Apache Druid druid-39.0.0 was published November 19, 2026. It requires Java 25, changes SQL write authorization and monitoring labels, replaces SysMonitor, changes Netty direct-memory behavior and updates MariaDB Connector/J. Review the complete incompatible-change and upgrade notes.","supportingSources":[{"title":"Prior reviewed release context","url":"https://github.com/apache/druid/releases/tag/druid-38.0.0"},{"title":"Version-specific upgrade notes","url":"https://druid.apache.org/docs/39.0.0/release-info/upgrade-notes"}]},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Upstream HTTP Kerberos/SPNEGO authentication extension","source":"https://druid.apache.org/docs/latest/development/extensions-core/druid-kerberos/","status":"documented","summary":"The druid-kerberos extension provides SPNEGO/GSSAPI authentication for Druid HTTP endpoints, with service principals, keytabs, cookies and authorizer mapping. Configure compatible browser/API clients and protect every endpoint; this is Kerberos federation, not native SAML/OIDC."}},"id":"apache-druid","infrastructure":["servers"],"infrastructureNotes":"Customer-operated JVM analytics services, metadata store and deep storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://druid.apache.org/docs/latest/operations/single-server/"],"install":"Run the official server distribution with bin/start-druid; distributed production deployments require the documented cluster services and storage configuration.","installMethods":["package"],"kind":"product","license":"Apache License 2.0 for upstream Apache Druid.","licenseModel":"open-source","licenseModelNotes":"Apache License 2.0 for upstream Apache Druid. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.","licenseModelSources":["https://github.com/apache/druid/blob/master/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Apache Druid","notes":"The smallest bundled configurations are evaluation examples. Data ingestion connectors and storage destinations can involve external services; configure their account and network boundaries separately. Apache Druid 39.0.0 requires Java 25 and drops Java 21 support. Its upgrade notes also change SQL INSERT/REPLACE authorization, replace SysMonitor with OshiSysMonitor, add taskStatus to task/run/time metrics, change Netty direct-memory behavior, and move the bundled MariaDB driver to 3.5.10 with jdbc:mariadb: preferred. Test permissions, dashboards, memory limits and metadata-store URLs before rollout.","operations":"Customer manages cluster sizing, ingestion, metadata and deep storage, access controls, backups and upgrades.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Official installation and runtime","url":"https://druid.apache.org/docs/latest/operations/single-server/"},{"title":"Upstream project and capabilities","url":"https://github.com/apache/druid"},{"title":"Current upstream license","url":"https://github.com/apache/druid/blob/master/LICENSE"},{"title":"Analytics functionality","url":"https://druid.apache.org/"},{"title":"Apache Druid 39.0.0 release","url":"https://github.com/apache/druid/releases/tag/druid-39.0.0"},{"title":"Apache Druid 39.0.0 upgrade notes","url":"https://druid.apache.org/docs/39.0.0/release-info/upgrade-notes"}],"url":"https://launchinyourcloud.com/directory/apache-druid/","website":"https://druid.apache.org/"},{"architecture":"Customer-operated Kafka brokers/controllers with persistent replicated topic partitions","categories":["streaming"],"category":"Streaming","categoryFit":{"streaming":"Distributed event log with topics, producers, consumers and stream processing integrations; applications and connectors determine downstream processing."},"cloudEvidence":[{"clouds":["gcp"],"notes":"Google documents creating customer GKE infrastructure and deploying Apache Kafka through the Strimzi operator. This is upstream Kafka operated in the customer project, not Confluent Cloud. The published tutorial includes version-specific ZooKeeper/KRaft assumptions; verify current Kafka and Strimzi compatibility and production security.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"Apache Kafka deployment on GKE using Strimzi","url":"https://docs.cloud.google.com/kubernetes-engine/docs/tutorials/apache-kafka-strimzi","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["gcp"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Official current distribution and maintenance","url":"https://kafka.apache.org/quickstart/"},{"title":"Named production adopters","url":"https://kafka.apache.org/powered-by/"}],"summary":"Established Apache project with an actively updated distribution/quickstart and a project-maintained Powered By directory of named organizations."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Distributed event streaming platform for durable publication, storage and consumption of event streams.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Published Kafka 4.4 hardware example and buffering heuristic; not a validated 100-user/1-TB HA footprint","source":"https://kafka.apache.org/44/operations/hardware-and-os/","status":"documented","summary":"The Kafka 4.4 operations guide publishes a reference machine with dual quad-core Xeons and 24 GB RAM, and estimates buffering memory from write throughput multiplied by 30 seconds. This is a hardware/reference formula, not a modern cloud minimum or an HA design; separately size brokers, KRaft controllers, replication, retention, disks and recovery capacity."},"iac":{"artifactRef":"4.4.0 JVM image; production topology requires separate planning","artifactUrl":"https://hub.docker.com/r/apache/kafka","reviewed":"2026-11-14","scope":"Apache Kafka upstream 4.4.0 quickstart","source":"https://kafka.apache.org/quickstart/","status":"documented","summary":"The upstream quickstart identifies the official apache/kafka:4.4.0 JVM image and apache/kafka-native:4.4.0 native image. Its single-container example is a basic environment, not a replicated production cluster or managed Kafka service."},"licensePricing":{"reviewed":"2026-11-21","scope":"Apache Kafka upstream software, not a managed-service or commercial distribution quote","source":"https://github.com/apache/kafka/blob/4.4.0/LICENSE","status":"documented","summary":"The upstream 4.4.0 core is Apache-2.0 licensed. This does not confer a managed Kafka subscription, commercial support entitlement or rights to separately licensed vendor add-ons; infrastructure and operations costs are separate."},"sso":{"reviewed":"2026-11-21","scope":"Apache Kafka 4.4 core broker/client identity; web-console user SSO remains unconfirmed","source":"https://kafka.apache.org/44/security/authentication-using-sasl/","status":"inconclusive","summary":"Kafka 4.4 documents production SASL/OAUTHBEARER authentication with an identity provider for broker/client access, while the default unsecured token implementation is development-only. That establishes protocol authentication, not a browser administration-console SSO path; select and verify the actual user-facing interface separately."}},"id":"apache-kafka","infrastructure":["servers"],"infrastructureNotes":"Customer-operated Kafka brokers/controllers with persistent replicated topic partitions. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://kafka.apache.org/quickstart/"],"install":"Run the official Java distribution or Apache Kafka container image; configure the documented broker/controller topology for production.","installMethods":["docker"],"kind":"product","license":"Apache License 2.0 for upstream Apache Kafka.","licenseModel":"open-source","licenseModelNotes":"Apache License 2.0 for upstream Apache Kafka. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.","licenseModelSources":["https://github.com/apache/kafka/blob/trunk/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Apache Kafka","notes":"The single-node quickstart is an evaluation starting point. Commercial Kafka distributions, hosted services and independently licensed connectors are outside this upstream listing.","operations":"Customer manages broker capacity, replication, retention, authentication, authorization, monitoring and upgrades.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Official installation and runtime","url":"https://kafka.apache.org/quickstart/"},{"title":"Upstream project and capabilities","url":"https://github.com/apache/kafka"},{"title":"Current upstream license","url":"https://github.com/apache/kafka/blob/trunk/LICENSE"}],"url":"https://launchinyourcloud.com/directory/apache-kafka/","website":"https://kafka.apache.org/"},{"architecture":"Appian Operator and Helm on EKS, AKS or GKE, an Appian system database and a separate supported business database.","categories":["contract-management"],"category":"Contract management","categoryFit":{"contract-management":"Commercial contract lifecycle application installed into a licensed, self-managed Appian platform."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Appian Operator and Helm on EKS, AKS or GKE, an Appian system database and a separate supported business database. CLM 1.2.0 requires the documented Appian 25.3 Advanced or Premium tier and a separate CLM purchase. Platform/operator versions and CLM packages are separate. Newly issued Kubernetes licences require Operator 0.205.0 or later from November 2026; exclude Fargate, GKE Autopilot and Azure ACI from this persistent-cluster path.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Appian on K8s","url":"https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html","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":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Commercial contract lifecycle application installed into a licensed, self-managed Appian platform.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Appian 26.10 platform-level Kubernetes sizing classes; CLM workload and dependencies need validation","source":"https://docs.appian.com/suite/help/26.10/resource-requests-and-limits.html","status":"documented","summary":"The self-managed Kubernetes guide gives Extra Small sites a non-HA reference of 8 CPU/64 GB RAM plus 115 GB RWO and 100 GB log storage; HA increases CPU/RAM threefold and changes persistent storage. These are Appian platform starting points, not a CLM-only or validated 100-user/1-TB capacity estimate."},"iac":{"artifactRef":"Appian 26.10 / Kubernetes guide k8s-0.205.0","artifactUrl":"https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html","reviewed":"2026-11-21","scope":"Appian 26.10 platform and separately imported CLM solution; package access and configuration required","source":"https://docs.appian.com/suite/help/26.10/clm-25.3.1.2/clm-install-guide.html","status":"documented","summary":"The Appian-on-Kubernetes guide deploys the licensed platform/operator; the separate CLM guide installs plugins, database SQL and an imported application package/customisation file. Obtain entitled images/packages and compatible versions. Platform provisioning alone does not install or configure the CLM solution.","supportingSources":[{"title":"Platform Kubernetes installation","url":"https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html"}]},"licensePricing":{"reviewed":"2026-11-19","scope":"Appian Connected Contract Lifecycle Management (CLM); software terms only, excluding cloud charges, labour and separately licensed services","source":"https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html#request-licenses","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-21","scope":"Self-managed Appian platform authentication underlying CLM","source":"https://docs.appian.com/suite/help/26.10/SAML_for_Single_Sign-On.html","status":"documented","summary":"Appian 26.10 documents SAML browser SSO configured in its Admin Console with IdP metadata, certificates and account mapping. CLM runs on that Appian identity platform; confirm users, groups and any external integration identities separately rather than treating every connected service as federated."}},"id":"appian-clm","infrastructure":["servers"],"infrastructureNotes":"Appian Operator and Helm on EKS, AKS or GKE, an Appian system database and a separate supported business database. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html"],"install":"Helm / Kubernetes operator; Kubernetes manifests","installMethods":["helm","kubernetes"],"kind":"product","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.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html#request-licenses","https://appian.com/legal/terms-of-use"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Appian Connected Contract Lifecycle Management (CLM)","notes":"CLM 1.2.0 requires the documented Appian 25.3 Advanced or Premium tier and a separate CLM purchase. Platform/operator versions and CLM packages are separate. Newly issued Kubernetes licences require Operator 0.205.0 or later from November 2026; exclude Fargate, GKE Autopilot and Azure ACI from this persistent-cluster path.","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":"Appian on K8s","url":"https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html"},{"title":"CLM Self-Managed Install","url":"https://docs.appian.com/suite/help/26.10/clm-25.3.1.2/clm-install-guide.html"},{"title":"K8s License Request","url":"https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html#request-licenses"},{"title":"Appian Terms (Website ToU)","url":"https://appian.com/legal/terms-of-use"},{"title":"Release Notes","url":"https://docs.appian.com/suite/help/26.10/Appian_Release_Notes.html"}],"url":"https://launchinyourcloud.com/directory/appian-clm/","website":"https://docs.appian.com/suite/help/26.10/k8s-0.205.0/install-appian-on-k8s.html"},{"advisories":[{"action":"Review the security changes and Helm probe defaults before applying a compatible update.","conditions":"Applicability depends on custom JS-library access, fork permissions and configured datasource endpoints; no complete affected range is asserted.","id":"appsmith-2-7-0-security-review","listingIds":["appsmith"],"reviewed":"2026-11-17","scope":"Upstream Appsmith 2.7.0 release; Airgapped Edition packaging follows its separate update policy.","source":"https://github.com/appsmithorg/appsmith/releases/tag/v2.7.0","summary":"The release adds missing app-access checks and extends restricted-host rules to S3-compatible and DynamoDB datasources.","title":"Appsmith 2.7.0 access and datasource hardening","type":"security-advisory"}],"architecture":"Customer-operated application and supporting databases/cache; vendor licensing/template endpoint","categories":["internal-tools"],"category":"Internal tools","categoryFit":{"internal-tools":"Low-code development of dashboards, admin panels and internal apps connected to databases/APIs; not a turnkey business application."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"The vendor documents AWS AMI and ECS, Azure Container Instances and Google Cloud Run installation of the application. These are self-hosted installations, with edition-specific licensing and vendor connectivity requirements described separately.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Appsmith provider-specific installation index","url":"https://docs.appsmith.com/getting-started/setup/installation-guides","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"The vendor walks through choosing the Appsmith Marketplace image, creating a Droplet in the customer account and registering its application administrator. Free and licensed features have separate entitlements; configure domain, TLS, email and recovery for production.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Appsmith on a customer DigitalOcean Droplet","url":"https://docs.appsmith.com/getting-started/setup/installation-guides/digitalocean","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","cloudScope":"Documented customer-operated deployment guides for AWS, Azure and Google Cloud","clouds":["aws","azure","gcp","digitalocean"],"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":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Build internal applications with visual widgets, queries and JavaScript on customer-operated infrastructure.","diligence":{"airGap":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Separately arranged Airgapped Edition, not every Appsmith installation","source":"https://docs.appsmith.com/getting-started/setup/installation-guides/air-gapped","status":"documented","summary":"A separate Airgapped Edition is obtained through sales. Offline operation limits templates, SaaS integrations and third-party libraries; disabling telemetry alone is not air-gapped deployment."},"footprint":{"reviewed":"2026-11-14","scope":"All-in-one Docker host; not a universal per-application requirement","source":"https://docs.appsmith.com/getting-started/setup/installation-guides/docker","status":"documented","summary":"The all-in-one Docker installation guidance calls for at least 8 GB host RAM because supporting services run inside the container. Externalized services require a different capacity plan."},"iac":{"reviewed":"2026-11-20","scope":"Official all-in-one installation example; choose the edition and a compatible pinned container release","source":"https://docs.appsmith.com/getting-started/setup/installation-guides/docker","status":"documented","summary":"The official Docker guide supplies run and Compose configurations using an Appsmith image and persistent /appsmith-stacks storage. Choose the Community or commercial image deliberately, pin the intended release and configure the host, secrets, HTTPS and backups."},"licensePricing":{"reviewed":"2026-11-20","scope":"Versioned core versus commercially licensed features; displayed Cloud limits and prices are not applied as a self-hosted quote","source":"https://github.com/appsmithorg/appsmith/blob/v2.7.0/LICENSE","status":"documented","summary":"The v2.7.0 core is Apache-2.0. The vendor distinguishes free Community from paid Business and Enterprise plans; SAML/OIDC, provisioning and air-gapped add-ons have separate commercial entitlements. Confirm self-hosted feature, user and support terms with the vendor.","supportingSources":[{"title":"Edition and feature pricing","url":"https://www.appsmith.com/pricing"}]},"release":{"reviewed":"2026-11-14","scope":"Airgapped Edition update policy; not the cadence of all Appsmith editions","source":"https://docs.appsmith.com/getting-started/setup/installation-guides/air-gapped","status":"documented","summary":"The Airgapped Edition documentation specifies quarterly packaged updates transferred manually into the isolated environment. This is separate from the normal upstream release stream."},"scim":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Self-hosted Enterprise; identity-provider and network requirements apply","source":"https://docs.appsmith.com/advanced-concepts/user-provisioning-group-sync","status":"documented","summary":"Self-hosted Enterprise documents SCIM v2 user and group provisioning. The identity provider must reach the instance SCIM endpoint over HTTPS."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-20","scope":"Self-hosted Enterprise user login; Google/GitHub login and enterprise federation are different options","source":"https://docs.appsmith.com/getting-started/setup/instance-configuration/authentication/security-assertion-markup-language-saml","status":"documented","summary":"The self-hosting authentication guides document SAML and OIDC SSO as Enterprise features. SAML can migrate from the bundled Keycloak broker to native server handling starting in v2.7; configure the provider and migration for the selected release.","supportingSources":[{"title":"Enterprise OIDC SSO","url":"https://docs.appsmith.com/getting-started/setup/instance-configuration/authentication/openid-connect-oidc"}]}},"id":"appsmith","infrastructure":["servers"],"infrastructureNotes":"Classified as servers under this directory convention: the application is a long-running container/service. Official Fargate/Cloud Run paths reduce host management but retain application, database and persistence operations. For Helm upgrades, partial probe overrides now inherit new 10-second period and 5-second timeout defaults; invalid probe values fail installation or upgrade. Review custom probe settings before rollout.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://docs.appsmith.com/getting-started/setup/installation-guides/docker","https://github.com/appsmithorg/appsmith/releases/tag/v2.7.0"],"install":"Docker Compose or Kubernetes; documented cloud VM/managed-container installation guides","installMethods":["docker"],"kind":"product","license":"Apache-2.0 Community core; commercial edition and plan-dependent features","licenseModel":"open-source","licenseModelNotes":"The broad self-hosted listing spans Apache-2.0 Community code and commercially licensed Enterprise functionality requiring an enterprise key. Match the selected image and plan to these terms.","licenseModelSources":["https://www.appsmith.com/terms-and-conditions","https://github.com/appsmithorg/appsmith","https://docs.appsmith.com/getting-started/setup/installation-guides/docker"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Appsmith Self-Hosted","notes":"Community and commercial images differ. Documentation requires outbound HTTPS to cs.appsmith.com for self-hosted license/template services and describes separate air-gapped arrangements. Official setup guides name AWS, Azure and Google Cloud. Fargate and Cloud Run are long-running container hosting options, not evidence that the entire stack is function-based. Appsmith v2.7.0 fixes app and datasource authorization issues, extends restricted-host enforcement to S3-compatible and DynamoDB sources, and updates vulnerable dependencies.","operations":"Customer manages deployment, persistent databases, backups, networking and upgrades; confirm edition-specific vendor connectivity.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Self-hosted Docker installation","url":"https://docs.appsmith.com/getting-started/setup/installation-guides/docker"},{"title":"Deployment architecture and vendor connectivity","url":"https://docs.appsmith.com/getting-started/setup/deployment-architecture"},{"title":"Provider-specific installation guides","url":"https://docs.appsmith.com/getting-started/setup/installation-guides"},{"title":"Community project and license","url":"https://github.com/appsmithorg/appsmith"},{"title":"Licensing and edition terms","url":"https://www.appsmith.com/terms-and-conditions"},{"title":"Appsmith on a customer DigitalOcean Droplet","url":"https://docs.appsmith.com/getting-started/setup/installation-guides/digitalocean"},{"title":"Appsmith v2.7.0 security and upgrade notes","url":"https://github.com/appsmithorg/appsmith/releases/tag/v2.7.0"}],"url":"https://launchinyourcloud.com/directory/appsmith/","website":"https://www.appsmith.com/"},{"advisories":[{"action":"Back up and use the normal upgrade/migrate procedure; the release says moving from 2.7.2 introduces no schema changes.","conditions":"Container dependency findings depend on the actual deployed images. The release is not proof that every image or integration is vulnerability-free.","id":"appwrite-2-7-3-security-review","listingIds":["appwrite"],"reviewed":"2026-11-17","scope":"Self-hosted Appwrite 2.7.3, appwrite/base 2.2.12 and openruntimes/executor 1.3.5; not Appwrite Cloud.","source":"https://github.com/appwrite/appwrite/releases/tag/2.7.3","summary":"Appwrite 2.7.3 refreshes its base and executor images after the 2.7.2 security update.","title":"Appwrite container security maintenance","type":"security-advisory"}],"architecture":"Customer-operated container services, database and storage","categories":["backend-platforms"],"category":"Backend platforms","categoryFit":{"backend-platforms":"Application backend APIs for authentication, databases, storage, functions, messaging and realtime, deployed on customer infrastructure."},"cloudEvidence":[{"clouds":["aws"],"notes":"The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Appwrite self-hosting on AWS","url":"https://appwrite.io/docs/advanced/self-hosting/platforms/aws","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Appwrite self-hosting on Azure","url":"https://appwrite.io/docs/advanced/self-hosting/platforms/azure","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Appwrite self-hosting on google-cloud","url":"https://appwrite.io/docs/advanced/self-hosting/platforms/google-cloud","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Appwrite self-hosting on digitalocean","url":"https://appwrite.io/docs/advanced/self-hosting/platforms/digitalocean","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","cloudScope":"Official guides document AWS, Azure and Google Cloud customer-infrastructure deployments.","clouds":["aws","azure","gcp","digitalocean"],"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"}],"description":"Self-hosted backend services for authentication, databases, storage, functions and messaging.","diligence":{"footprint":{"reviewed":"2026-11-14","scope":"Appwrite installation baseline; not every production workload","source":"https://appwrite.io/docs/advanced/self-hosting/installation","status":"documented","summary":"The current installation guide requires at least 2 CPU cores, 4 GB RAM and 2 GB swap on a Docker-capable host. Models, functions, worker topology and workload can raise requirements."},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://appwrite.io/docs/advanced/self-hosting/installation","status":"documented","summary":"The official installer generates a Compose stack and environment/configuration files. Replace encryption/executor secrets, retain all required files and select the worker/database configuration; a Kubernetes Helm option is separate."},"licensePricing":{"reviewed":"2026-11-20","scope":"Appwrite 2.7.3 upstream core; not Cloud or Enterprise entitlements; software terms only, excluding infrastructure and operations","source":"https://github.com/appwrite/appwrite/blob/2.7.3/LICENSE","status":"documented","summary":"The reviewed upstream application uses BSD 3-Clause licence. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote."},"release":{"releasePublishedAt":"2026-11-17T12:55:27Z","releaseTag":"2.7.3","reviewed":"2026-11-17","scope":"Upstream appwrite/appwrite release record; commercial editions, LTS branches and provider packages can differ","source":"https://github.com/appwrite/appwrite/releases/tag/2.7.3","status":"documented","summary":"The reviewed upstream release is 2.7.3, published 2026-11-17. This is a dated release snapshot, not a support designation, a future cadence promise or approval to replace a provider package."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-20","scope":"Application-user OAuth versus premium self-hosted Console identity; product/edition boundaries apply","source":"https://appwrite.io/enterprise","status":"documented","summary":"Appwrite documents OAuth2 identity providers for users of applications you build. Separately, the vendor advertises centralized Console SSO in its premium Enterprise platform, available as self-hosted or Cloud. Do not treat core application-user OAuth as administrator SAML: confirm the chosen self-hosted Enterprise package, IdP/protocol and organization policy for Console SSO.","supportingSources":[{"title":"Application-user OAuth2 flow and provider setup","url":"https://appwrite.io/docs/products/auth/oauth2"}]}},"id":"appwrite","infrastructure":["servers"],"infrastructureNotes":"Appwrite runs as persistent Docker services or an official Helm deployment on Kubernetes. The function feature does not make the complete backend a serverless deployment.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://appwrite.io/docs/advanced/self-hosting/installation","https://appwrite.io/docs/advanced/self-hosting/platforms/kubernetes"],"install":"Docker installer or official Kubernetes Helm chart","installMethods":["helm","docker","package"],"kind":"product","license":"BSD-3-Clause core; enterprise services and feature terms should be confirmed separately","licenseModel":"open-source","licenseModelNotes":"This classification covers the public Appwrite self-hosted distribution under BSD-3-Clause. Appwrite separately markets a premium enterprise self-hosted edition; its additional tooling and terms are outside this classification and should not be assumed to inherit the public core license.","licenseModelSources":["https://raw.githubusercontent.com/appwrite/appwrite/main/LICENSE","https://appwrite.io/docs/advanced/self-hosting","https://appwrite.io/enterprise"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Appwrite Self-Hosted","notes":"This entry covers self-hosting rather than Appwrite Cloud. Official deployment guides document EC2/EKS, Azure VMs/AKS and Google Compute Engine/GKE. Configure external email, SMS and other integrations deliberately; enterprise support and compliance offerings have separate terms. Appwrite 2.7.3 includes the 2.7.2 security fixes across authentication, abuse limits, storage, realtime, messaging, functions, VCS, proxy handling, and vulnerable base-image packages. It additionally rebuilds appwrite/base and openruntimes/executor to clear remaining image vulnerability findings. Upgrading from 2.7.2 requires no schema changes; use the normal upgrade command and migration step.","operations":"Customer configures the environment and handles software updates, scaling, security and backups.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Backend capabilities","url":"https://appwrite.io/docs"},{"title":"Self-hosting responsibilities","url":"https://appwrite.io/docs/advanced/self-hosting"},{"title":"Docker installation","url":"https://appwrite.io/docs/advanced/self-hosting/installation"},{"title":"AWS deployment","url":"https://appwrite.io/docs/advanced/self-hosting/platforms/aws"},{"title":"Azure deployment","url":"https://appwrite.io/docs/advanced/self-hosting/platforms/azure"},{"title":"Google Cloud deployment","url":"https://appwrite.io/docs/advanced/self-hosting/platforms/google-cloud"},{"title":"Core license","url":"https://raw.githubusercontent.com/appwrite/appwrite/main/LICENSE"},{"title":"Licensing and edition terms","url":"https://appwrite.io/enterprise"},{"title":"Infrastructure deployment documentation","url":"https://appwrite.io/docs/advanced/self-hosting/platforms/kubernetes"},{"title":"Appwrite self-hosting on digitalocean","url":"https://appwrite.io/docs/advanced/self-hosting/platforms/digitalocean"},{"title":"Appwrite 2.7.2 security patch","url":"https://github.com/appwrite/appwrite/releases/tag/2.7.2"},{"title":"Appwrite 2.7.3 image security update","url":"https://github.com/appwrite/appwrite/releases/tag/2.7.3"}],"url":"https://launchinyourcloud.com/directory/appwrite/","website":"https://appwrite.io/"},{"architecture":"Customer-operated trace/evaluation application with persistent trace and dataset storage","categories":["ai-observability","ai-tools"],"category":"AI observability \u0026 LLMOps","categoryFit":{"ai-observability":"AI trace collection, evaluation, datasets, experiments and prompt analysis for instrumented model applications.","ai-tools":"AI development and operations tooling for tracing and evaluation rather than a model-serving runtime."},"cloudEvidence":[{"clouds":["aws","azure","gcp","railway"],"notes":"The current Phoenix self-hosting index includes a Railway one-click template as well as AWS CloudFormation, Azure ARM and Google Cloud Run. These deploy the Phoenix application, not the separately licensed Arize AX product. A Railway project is customer-controlled while Railway manages its infrastructure.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Phoenix self-hosting deployment options","url":"https://arize.com/docs/phoenix/self-hosting","vendorSupport":"not-assessed"},{"clouds":["render"],"notes":"The vendor self-hosting index offers a Render one-click Blueprint for Phoenix alongside its Railway, AWS, Azure and Google Cloud options. This is the self-hosted Phoenix application, separate from Arize AX; customer workspace control does not imply ownership of the platform infrastructure.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Phoenix self-hosted Render Blueprint","url":"https://arize.com/docs/phoenix/self-hosting","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp","railway","render"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Maintainer account of user-contributed authentication and integrations","url":"https://arize.com/blog/phoenix-10k/"},{"title":"Current Phoenix maintenance releases","url":"https://github.com/Arize-ai/phoenix/releases"}],"summary":"Arize's June 2026 maintainer account describes actual participation outside the core team: it attributes OIDC authentication to users needing Keycloak/Cognito and credits contributors with expanding framework integrations and OpenInference. The upstream release history shows continuing maintenance. This concerns concrete community involvement rather than repository star counts; it does not certify any named customer's deployment model."},"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":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"platform-workspace","cloud":"render","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"AI observability and evaluation server for traces, datasets and application experiments.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Phoenix self-hosted application and data services; numeric workload sizing unresolved","source":"https://arize.com/docs/phoenix/self-hosting/deploying-phoenix.md","status":"inconclusive","summary":"The self-hosting guide documents deployment, storage/database configuration and trace retention, but does not establish a complete CPU/RAM minimum for a specified workload. Size span ingestion, retention, database, evaluation/model dependencies and redundant service instances. Hosted Arize AX sizing is a separate offering."},"iac":{"artifactRef":"repository default branch (moving; select matching application release)","artifactUrl":"https://github.com/arize-ai/phoenix","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://github.com/arize-ai/phoenix","status":"documented","summary":"The upstream Phoenix repository provides self-hosting/container documentation for the observability server. Match persistence and authentication settings to the chosen release; instrumented applications and model services remain separate."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE","status":"documented","summary":"Phoenix uses Elastic License 2.0, including limits on offering substantial hosted/managed functionality and bypassing licence controls. This is not an unrestricted Apache/MIT licence or a hosted-service price; review commercial service/support terms separately."},"release":{"releasePublishedAt":"2026-11-13T06:26:01Z","releaseTag":"arize-phoenix-v21.1.0","reviewed":"2026-11-14","scope":"Upstream Arize-ai/phoenix release record; commercial editions and deployment packages may differ","source":"https://github.com/Arize-ai/phoenix/releases/tag/arize-phoenix-v21.1.0","status":"documented","summary":"The publisher-designated GitHub release checked was arize-phoenix-v21.1.0, published 2026-11-13. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Self-hosted Phoenix UI OAuth2/OIDC","source":"https://arize.com/docs/phoenix/deployment/authentication","status":"documented","summary":"Phoenix documents OAuth2 authorization-code login with OIDC provider discovery, configured alongside application authentication and secret settings. Configure the trusted provider, callback and account policy; client API keys remain a separate surface."}},"id":"phoenix","infrastructure":["servers"],"infrastructureNotes":"Customer-operated trace/evaluation application with persistent trace and dataset storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://arize.com/docs/phoenix/self-hosting"],"install":"Use the official self-hosted Docker/Compose or Kubernetes deployment instructions and configure persistent storage and instrumentation endpoints.","installMethods":["docker"],"kind":"product","license":"Elastic License 2.0; includes restrictions on providing the software as a hosted/managed service and on license-key circumvention. This is source-available.","licenseModel":"source-available","licenseModelNotes":"Elastic License 2.0; includes restrictions on providing the software as a hosted/managed service and on license-key circumvention. This is source-available. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.","licenseModelSources":["https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Arize Phoenix Self-Hosted","notes":"The self-hosted product is distinct from commercial Arize offerings. Traces may contain prompts and outputs; evaluation jobs can call separately configured external model services even when trace storage is local.","operations":"Customer manages trace capture, storage, authentication, retention, evaluation providers, backups and upgrades.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Official installation and runtime","url":"https://arize.com/docs/phoenix/self-hosting"},{"title":"Upstream project and capabilities","url":"https://github.com/Arize-ai/phoenix"},{"title":"Current upstream license","url":"https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE"}],"url":"https://launchinyourcloud.com/directory/phoenix/","website":"https://arize.com/phoenix/"},{"architecture":"Customer-operated application services with PostgreSQL, Redis and file storage","categories":["no-code-databases"],"category":"No-code databases","categoryFit":{"no-code-databases":"No-code relational tables, views and APIs for collaborative business data; premium capabilities require the applicable license."},"cloudEvidence":[{"clouds":["aws"],"notes":"The vendor documents EC2, ECS/Fargate and EKS application deployment options in the customer AWS account. Select the documented image, persistent database and Redis configuration appropriate to the topology.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Baserow AWS installation options","url":"https://baserow.io/docs/installation%2Finstall-on-aws","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The upstream guide explicitly designs the all-in-one application image for simple container services such as Google Cloud Run. Use external PostgreSQL, Redis and durable file storage for a stateless runtime; this is an application-hosting compatibility statement, not evidence based only on a Google storage adapter.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Baserow Docker image compatibility with Google Cloud Run","url":"https://baserow.io/docs/installation/install-with-docker","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"deploymentBoundaries":{"digitalocean":"platform-workspace"},"notes":"The vendor guide deploys the Baserow application container, managed PostgreSQL and Redis, and Spaces storage in the customer DigitalOcean account, with application URL and scaling configuration. The example image tag is version-specific; choose and test the intended supported release.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Baserow on DigitalOcean App Platform","url":"https://baserow.io/docs/installation%2Finstall-on-digital-ocean","vendorSupport":"not-assessed"},{"clouds":["railway"],"notes":"The upstream guide creates a Railway project from the Baserow template and configures the deployed application. The guide requires enough memory and a paid plan rather than assuming the free trial is adequate. Railway operates the underlying infrastructure; the customer controls the application project.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Baserow Railway installation","url":"https://baserow.io/docs/installation%2Finstall-on-railway","vendorSupport":"not-assessed"},{"clouds":["render"],"notes":"The upstream guide provides a full application template using paid Render compute and PostgreSQL plans. Its published plan prices and repository branch examples can age; verify the current template, compatible release, resources and data persistence rather than assuming a free production tier.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Baserow Render application template","url":"https://baserow.io/docs/installation%2Finstall-on-render","vendorSupport":"not-assessed"},{"clouds":["heroku"],"notes":"The upstream guide documents a beta deployment template for the Baserow application and supporting Heroku services, with configuration and scaling instructions. It requires paid resources; review the current template, image, database and file-storage settings before production use.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Baserow Heroku application template","url":"https://baserow.io/docs/installation%2Finstall-on-heroku","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","cloudScope":"Official documentation establishes AWS deployments; other provider compatibility is not inferred.","clouds":["aws","gcp","digitalocean","railway","render","heroku"],"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":"digitalocean","controlPlane":"not-assessed","evidence":[2],"operator":"customer"},{"boundary":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[3],"operator":"customer"},{"boundary":"platform-workspace","cloud":"render","controlPlane":"not-assessed","evidence":[4],"operator":"customer"},{"boundary":"platform-workspace","cloud":"heroku","controlPlane":"not-assessed","evidence":[5],"operator":"customer"}],"description":"Self-hosted no-code database for organizing, relating and collaborating on business data.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Provider-specific stateless application baseline, not a universal all-in-one minimum or HA design","source":"https://baserow.io/docs/installation/install-on-digital-ocean","status":"documented","summary":"The official DigitalOcean App Platform guide specifies at least one application container with 1 vCPU and 2 GB RAM, plus separately provisioned managed PostgreSQL, Redis and Spaces storage. Its smaller database example is not the application or complete-host requirement."},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://baserow.io/docs/installation/install-with-docker","status":"documented","summary":"The all-in-one Docker guide documents persistence, HTTPS and external database/cache configuration. It recommends an external PostgreSQL service for production and describes database-version upgrade handling."},"licensePricing":{"reviewed":"2026-11-20","scope":"Versioned open-source versus paid-edition software rights; excludes hosting and support","source":"https://github.com/baserow/baserow/blob/2.4.3/LICENSE","status":"documented","summary":"The 2.4.3 Open Source Edition is MIT-licensed, with separate Premium and Enterprise directories. Production use of either paid edition requires the corresponding subscription for the correct number of users and applicable subscription terms; do not apply Cloud prices to a self-hosted contract.","supportingSources":[{"title":"Premium edition licence","url":"https://github.com/baserow/baserow/blob/2.4.3/premium/LICENSE"},{"title":"Enterprise edition licence","url":"https://github.com/baserow/baserow/blob/2.4.3/enterprise/LICENSE"}]},"release":{"releasePublishedAt":"2026-11-14T09:40:29Z","releaseTag":"2.4.3","reviewed":"2026-11-14","scope":"Upstream baserow/baserow release record; commercial editions and deployment packages may differ","source":"https://github.com/baserow/baserow/releases/tag/2.4.3","status":"documented","summary":"The publisher-designated GitHub release checked was 2.4.3, published 2026-11-14. 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 Advanced/Enterprise authentication","source":"https://baserow.io/user-docs/enable-single-sign-on-sso","status":"documented","summary":"Instance administrators can configure SAML and OAuth/OIDC providers on Advanced or Enterprise with an activated license. This is not established for the free self-hosted edition."}},"id":"baserow","infrastructure":["servers"],"infrastructureNotes":"The official guides deploy persistent application containers with PostgreSQL and Redis, either on a server or orchestrated container infrastructure. Fargate is an available hosting path, but the application remains a persistent service.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://baserow.io/docs/installation/install-with-docker","https://baserow.io/docs/installation%2Finstall-on-aws"],"install":"Docker, Docker Compose or official Helm chart","installMethods":["helm","docker"],"kind":"product","license":"MIT-licensed core with paid premium features and subscription terms","licenseModel":"open-source","licenseModelNotes":"Baserow Open Source Edition is MIT-licensed. The repository separately licenses Premium and Enterprise feature directories, whose production use requires the corresponding paid subscription; publicly visible source does not make those directories open source.","licenseModelSources":["https://raw.githubusercontent.com/baserow/baserow/develop/LICENSE","https://raw.githubusercontent.com/baserow/baserow/develop/premium/LICENSE","https://raw.githubusercontent.com/baserow/baserow/develop/enterprise/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Baserow Self-Hosted","notes":"Self-hosting is available independently of Baserow Cloud. The core is largely MIT-licensed, while premium features need a paid license. The official AWS guide documents EC2, ECS/Fargate and EKS paths; it does not establish equivalent deployment support on every hyperscaler.","operations":"Customer operates the application, database and storage, applies updates and configures backups.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Product and licensing FAQ","url":"https://baserow.io/faq"},{"title":"Docker installation","url":"https://baserow.io/docs/installation/install-with-docker"},{"title":"AWS installation paths","url":"https://baserow.io/docs/installation%2Finstall-on-aws"},{"title":"Licensing and edition terms","url":"https://raw.githubusercontent.com/baserow/baserow/develop/LICENSE"},{"title":"Licensing and edition terms","url":"https://raw.githubusercontent.com/baserow/baserow/develop/premium/LICENSE"},{"title":"Licensing and edition terms","url":"https://raw.githubusercontent.com/baserow/baserow/develop/enterprise/LICENSE"},{"title":"Baserow on DigitalOcean App Platform","url":"https://baserow.io/docs/installation%2Finstall-on-digital-ocean"},{"title":"Baserow Railway installation","url":"https://baserow.io/docs/installation%2Finstall-on-railway"},{"title":"Baserow Render application template","url":"https://baserow.io/docs/installation%2Finstall-on-render"},{"title":"Baserow Heroku application template","url":"https://baserow.io/docs/installation%2Finstall-on-heroku"}],"url":"https://launchinyourcloud.com/directory/baserow/","website":"https://baserow.io/"},{"architecture":"BigBlueButton media, web, conferencing and recording services on dedicated Linux infrastructure.","categories":["collaboration"],"category":"Collaboration","categoryFit":{"collaboration":"Self-hosted conferencing and virtual classroom platform."},"cloudEvidence":[{"clouds":["aws","azure","gcp","digitalocean","hetzner","scaleway"],"notes":"BigBlueButton media, web, conferencing and recording services on dedicated Linux infrastructure. Use supported installer/Ubuntu combinations, public-address and UDP/media firewall requirements. A small development VM is not a production capacity or HA guarantee.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"\u003cimg width=\"1012\" alt=\"bbb-install-banner\" src=\"https://user-images.githubusercontent.com/1273169/141152865-f497c883-6c9","url":"https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","azure","gcp","digitalocean","hetzner","scaleway"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/bigbluebutton/bigbluebutton/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/bigbluebutton/bigbluebutton"}],"summary":"The reviewed upstream contributor history includes antobinary, ritzalam, ramonlsouza, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee."},"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":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"hetzner","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"scaleway","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Self-hosted conferencing and virtual classroom platform.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Current upstream production conferencing-node requirements; not meeting capacity for every workload","source":"https://docs.bigbluebutton.org/administration/install/","status":"documented","summary":"The production guide recommends Ubuntu 24.04, 8 CPU cores, 16 GB RAM, symmetric 250 Mbit/s networking and 500 GB free recording space, or 50 GB without recording. Smaller 4-core/8-GB development settings are separate. Concurrent media usage and HA need additional design."},"iac":{"artifactRef":"v4.0.x-release (moving maintained 4.0 installer branch)","artifactUrl":"https://github.com/bigbluebutton/bbb-install/blob/v4.0.x-release/bbb-install.sh","reviewed":"2026-11-19","scope":"BigBlueButton 4.0 installer; verify the selected release line, dedicated CPU, public address and media firewall rules","source":"https://docs.bigbluebutton.org/administration/install/","status":"documented","summary":"The official 4.0 installation instructions link the maintained bbb-install.sh branch for Ubuntu 24.04. The older master README describes 2.6 and must not be used as the 4.0 installer reference."},"licensePricing":{"reviewed":"2026-11-19","scope":"BigBlueButton; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://github.com/bigbluebutton/bigbluebutton/blob/develop/LICENSE","status":"documented","summary":"GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"release":{"releasePublishedAt":"2026-11-06T20:50:47Z","releaseTag":"v4.0.2","reviewed":"2026-11-19","scope":"BigBlueButton upstream application; verify compatibility with the selected package","source":"https://github.com/bigbluebutton/bigbluebutton/releases/tag/v4.0.2","status":"documented","summary":"Reviewed upstream v4.0.2 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"BigBlueButton with the separately configured Greenlight v3 front end","source":"https://docs.bigbluebutton.org/greenlight/v3/install/","status":"documented","summary":"The optional Greenlight v3 front end supports external authentication through OpenID Connect and can connect to an external identity server. This is a Greenlight user-login capability, not the conferencing engine shared-secret API or an assurance about every LMS/front-end integration."}},"id":"bigbluebutton","infrastructure":["servers"],"infrastructureNotes":"BigBlueButton media, web, conferencing and recording services on dedicated Linux infrastructure. 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/bigbluebutton/bbb-install/v4.0.x-release/README.md"],"install":"Official bbb-install.sh from the maintained 4.0 installer branch on supported Ubuntu","installMethods":["package"],"kind":"product","license":"GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://github.com/bigbluebutton/bigbluebutton/blob/develop/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"BigBlueButton","notes":"Use supported installer/Ubuntu combinations, public-address and UDP/media firewall requirements. A small development VM is not a production capacity or HA guarantee. The maintained 4.0 installer also explicitly documents Scaleway and Azure behind-NAT deployments.","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":"\u003cimg width=\"1012\" alt=\"bbb-install-banner\" src=\"https://user-images.githubusercontent.com/1273169/141152865-f497c883-6c9","url":"https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md"},{"title":"Official Install Docs","url":"https://docs.bigbluebutton.org/administration/install/"},{"title":"bbb-install README","url":"https://raw.githubusercontent.com/bigbluebutton/bbb-install/master/README.md"},{"title":"LGPL-3.0 LICENSE","url":"https://github.com/bigbluebutton/bigbluebutton/blob/develop/LICENSE"},{"title":"Releases v4.0.2","url":"https://github.com/bigbluebutton/bigbluebutton/releases"}],"url":"https://launchinyourcloud.com/directory/bigbluebutton/","website":"https://bigbluebutton.org"},{"advisories":[{"action":"Review the required license transition with Atlassian; do not infer unrestricted new-customer availability.","conditions":"Eligibility and exact launch date must be confirmed; existing license availability changes on March 28, 2029.","effectiveDate":"2029-03-28","id":"bitbucket-hybrid-license-transition","listingIds":["bitbucket-data-center"],"reviewed":"2026-11-16","scope":"Bitbucket Data Center licensing; separate from the retirement of Jira and Confluence Data Center.","source":"https://www.atlassian.com/migration/bitbucket-hybrid-license","summary":"Bitbucket remains self-managed beyond 2029 through the Hybrid License. Atlassian plans availability in early 2027 for eligible existing Bitbucket/Bamboo customers.","title":"Bitbucket Hybrid License transition","type":"lifecycle"},{"action":"Patch every affected installation to its fixed supported branch. If delayed, restrict internet access and apply the vendor WAF or product-specific rewrite mitigation to all relevant nodes.","conditions":"An attacker needs the exact file name and path; directory enumeration is not provided. Sensitive files in the application root change the risk.","id":"atlassian-cve-2026-21589","listingIds":["jira-software-data-center","jira-service-management-data-center","confluence-data-center","bitbucket-data-center"],"reviewed":"2026-11-17","scope":"Jira Software: 9.12.40/10.3.26/11.3.12; JSM: 5.12.40/10.3.26/11.3.12; Confluence: 9.2.26/10.2.19; Bitbucket: 9.4.26/10.2.8/10.5.1. Versions before the appropriate branch fix are affected.","source":"https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html","summary":"CVE-2026-21589 allows access to specifically named files under the web application root; Atlassian assigns critical severity.","title":"Atlassian Data Center unauthenticated file access","type":"security-advisory"},{"action":"Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility.","conditions":"Installed product, branch, bundled dependency, and Marketplace app compatibility determine applicability.","id":"atlassian-data-center-november-17-2026-bulletin","listingIds":["jira-software-data-center","confluence-data-center","bitbucket-data-center","jira-service-management-data-center"],"reviewed":"2026-11-18","scope":"Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.","source":"https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html","summary":"Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context.","title":"Atlassian Data Center November 17, 2026 bulletin","type":"security-advisory"}],"architecture":"Single-node or clustered Bitbucket application nodes with Git storage or Mesh, an external database, load balancer, shared home and search services","categories":["devops"],"category":"DevOps","categoryFit":{"devops":"Provides self-managed Git repository hosting, pull requests, code review, permissions and software-delivery integrations."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Atlassian documents Bitbucket Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments. Product-specific AWS and Azure pages also direct customers to the Helm path because the older templates are no longer maintained.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Bitbucket Data Center on EKS, AKS or GKE","url":"https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html","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 self-managed Git collaboration and code-review platform for eligible existing Atlassian customers, with an announced Hybrid License transition.","diligence":{"compliance":{"reviewed":"2026-11-16","scope":"Vendor reports versus this self-managed Data Center installation","source":"https://www.atlassian.com/trust/compliance/resources/soc2","status":"inconclusive","summary":"Atlassian’s public SOC 2 page points to product reports, but does not establish the customer-operated Data Center boundary or report validity. Review the actual report before claiming coverage."},"footprint":{"reviewed":"2026-11-16","scope":"Bitbucket 10.4 application-host baseline; not a production cluster total","source":"https://confluence.atlassian.com/bitbucketserver104/supported-platforms-1822592149.html","status":"documented","summary":"The Bitbucket 10.4 platform guide specifies x86-64, at least 2 CPU cores and 3 GB available RAM, including memory for Git operations. Repository activity, concurrency, database, shared storage and Mesh nodes require separate sizing."},"iac":{"artifactRef":"main (moving branch; select product-compatible chart and application release)","artifactUrl":"https://github.com/atlassian/data-center-helm-charts","reviewed":"2026-11-16","scope":"Bitbucket Data Center; existing-customer eligibility and lifecycle conditions apply","source":"https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html","status":"documented","summary":"Atlassian publishes product-specific Data Center Helm charts. Select a chart and application version supported for this product and configure its database, persistent storage, ingress and license; one product’s chart does not establish compatibility for another."},"licensePricing":{"reviewed":"2026-11-16","scope":"Bitbucket Data Center: software license terms; infrastructure and operating costs are separate","source":"https://www.atlassian.com/licensing/data-center","status":"documented","summary":"Bitbucket is exempt from the end-of-life retirement of Jira and Confluence Data Center. Atlassian says eligible existing Bitbucket or Bamboo Data Center/Server customers can move to the Bitbucket Hybrid License, planned for early 2027, to retain self-managed Bitbucket beyond March 28, 2029. The existing standalone license route ends in 2029; without the Hybrid License transition, instances become read-only. Confirm eligibility, availability and renewal terms.","supportingSources":[{"title":"Edition and license conditions","url":"https://www.atlassian.com/licensing/data-center-end-of-life"},{"title":"Edition and license conditions","url":"https://www.atlassian.com/migration/bitbucket-hybrid-license"}]},"release":{"releasePublishedOn":"2026-11-03","releaseTag":"10.2.9","reviewed":"2026-11-16","scope":"Vendor current-download feed; publication day only, with no invented release time","source":"https://my.atlassian.com/download/feeds/current/stash.json","status":"documented","summary":"Atlassian’s current-download feed lists 10.2.9, released 2026-11-03. This is the reviewed download snapshot, not a guarantee that every other release branch, Helm chart, app or upgrade path is compatible. Existing-customer and lifecycle restrictions still apply.","supportingSources":[{"title":"Vendor release notes","url":"https://confluence.atlassian.com/display/BitbucketServer/Bitbucket+Data+Center+10.2+release+notes"}]},"scim":{"reviewed":"2026-11-16","scope":"Native Data Center cloud-IdP integration described by Atlassian; not an assessment of every Marketplace add-on","source":"https://confluence.atlassian.com/enterprise/manage-users-between-cloud-and-data-center-products-1085188069.html","status":"documented","summary":"Atlassian’s native cloud-IdP scenario uses login-time JIT provisioning for Data Center, without regular synchronization or de-provisioning. Its cloud SCIM path is different; third-party Data Center provisioning apps require separate review."},"securityControls":{"reviewed":"2026-11-18","scope":"Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.","source":"https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html","status":"documented","summary":"Current advisory review: Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility.","supportingSources":[]},"sso":{"availability":"available","reviewed":"2026-11-16","scope":"Bitbucket 7.12+ Data Center SSO feature baseline; existing-customer lifecycle restrictions remain","source":"https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html","status":"documented","summary":"Atlassian documents SAML 2.0 and OIDC through its Data Center SSO app. Match app compatibility to Bitbucket 7.12+; authentication does not assign application access or permissions.","supportingSources":[{"title":"OIDC product/version scope","url":"https://confluence.atlassian.com/enterprise/openid-connect-for-atlassian-data-center-applications-987142159.html"}]}},"id":"bitbucket-data-center","infrastructure":["servers"],"infrastructureNotes":"Bitbucket Data Center runs persistent application and Git-storage services with durable database, shared-home and repository storage.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html","https://confluence.atlassian.com/display/BitbucketServer/Supported%2Bplatforms"],"install":"Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based single-node and clustered installation","installMethods":["helm","kubernetes","package"],"kind":"product","license":"Commercial Bitbucket Data Center term license; eligible existing customers must transition to the Bitbucket Hybrid License to continue self-managed use beyond March 28, 2029.","licenseModel":"commercial-only","licenseModelNotes":"Bitbucket is exempt from the end-of-life retirement of Jira and Confluence Data Center. Atlassian says eligible existing Bitbucket or Bamboo Data Center/Server customers can move to the Bitbucket Hybrid License, planned for early 2027, to retain self-managed Bitbucket beyond March 28, 2029. The existing standalone license route ends in 2029; without the Hybrid License transition, instances become read-only. Confirm eligibility, availability and renewal terms.","licenseModelSources":["https://www.atlassian.com/licensing/data-center","https://www.atlassian.com/licensing/data-center-end-of-life","https://www.atlassian.com/migration/bitbucket-hybrid-license"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"Bitbucket Data Center","notes":"This entry covers self-managed Bitbucket Data Center. Atlassian documents EKS, AKS and GKE with its supported Helm chart; the older AWS Quick Start and Azure Resource Manager templates are no longer maintained. Bitbucket and Bamboo are exempt from the retirement of the other affected Data Center products. Continued self-managed use after March 28, 2029 requires the Bitbucket Hybrid License; without transitioning, existing subscription instances become read-only. Atlassian plans availability in early 2027 for eligible existing Bitbucket or Bamboo Data Center/Server customers. The license also includes cloud services, but Atlassian states that the self-managed environment can remain in place without a data transfer. Atlassian rates CVE-2026-21589 critical (9.3). All Bitbucket Data Center versions before the fixed 9.4.26, 10.2.8, or 10.5.1 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Bitbucket URL-rewrite mitigation to every application and mirror node. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.","operations":"Customer manages Kubernetes or hosts, Git and shared storage, Mesh where used, database, search, networking, TLS, identity, backups, monitoring and upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Run Bitbucket Data Center on Kubernetes","url":"https://confluence.atlassian.com/security/running-bitbucket-data-center-on-a-kubernetes-cluster-1409093077.html"},{"title":"Bitbucket Data Center supported platforms","url":"https://confluence.atlassian.com/display/BitbucketServer/Supported%2Bplatforms"},{"title":"Bitbucket Data Center deployment on AWS","url":"https://confluence.atlassian.com/security/deploy-bitbucket-data-center-in-aws-1402669978.html"},{"title":"Bitbucket Data Center deployment on Azure","url":"https://confluence.atlassian.com/security/deploy-bitbucket-data-center-in-azure-1402669984.html"},{"title":"Atlassian Data Center licensing and end of life","url":"https://www.atlassian.com/licensing/data-center"},{"title":"Atlassian Data Center end-of-life exceptions","url":"https://www.atlassian.com/licensing/data-center-end-of-life"},{"title":"Bitbucket Hybrid License eligibility and transition","url":"https://www.atlassian.com/migration/bitbucket-hybrid-license"},{"title":"Atlassian CVE-2026-21589 critical file-access advisory","url":"https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html"},{"title":"Atlassian security bulletin — November 17, 2026","url":"https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html"}],"url":"https://launchinyourcloud.com/directory/bitbucket-data-center/","website":"https://www.atlassian.com/software/bitbucket/enterprise"},{"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/"},{"alternativeTo":[{"id":"zendesk","reviewed":"2026-11-16","source":"https://www.chatwoot.com/pricing/self-hosted-plans","summary":"The self-hosted plan page positions Chatwoot as an alternative for customer-support workflows."},{"id":"intercom","reviewed":"2026-11-16","source":"https://www.chatwoot.com/pricing/self-hosted-plans","summary":"The self-hosted plan page positions Chatwoot as an alternative for customer-support workflows."}],"architecture":"Customer-operated application and workers with PostgreSQL, Redis and upload storage","categories":["customer-support"],"category":"Customer support","categoryFit":{"customer-support":"Shared support inbox, live chat, email and messaging channels, with automation and reporting; feature entitlements depend on edition."},"cloudEvidence":[{"clouds":["aws"],"notes":"The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Chatwoot self-hosted deployment on AWS","url":"https://developers.chatwoot.com/self-hosted/deployment/aws","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Chatwoot self-hosted deployment on Azure","url":"https://developers.chatwoot.com/self-hosted/deployment/azure","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Chatwoot self-hosted deployment on Google Cloud","url":"https://developers.chatwoot.com/self-hosted/deployment/gcp","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Chatwoot self-hosted deployment on digitalocean","url":"https://developers.chatwoot.com/self-hosted/deployment/digitalocean","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","cloudScope":"Official Azure VM and Google Compute Engine guides exist and are marked work in progress; other cloud badges are not inferred.","clouds":["azure","gcp","aws","digitalocean"],"deploymentPaths":[{"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":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[3],"operator":"customer"}],"description":"Self-hosted customer-support inbox combining live chat, email and messaging conversations.","diligence":{"footprint":{"reviewed":"2026-11-14","scope":"Technical requirements; compare the pricing FAQ","source":"https://developers.chatwoot.com/self-hosted/deployment/requirements","status":"documented","summary":"The technical requirements page specifies 4 CPU cores and 4 GB RAM for its smallest example workload; the pricing FAQ separately says 2 CPU cores and 4 GB. Resolve this difference for your workload before sizing.","supportingSources":[{"title":"Self-hosted pricing FAQ: production starting point","url":"https://www.chatwoot.com/pricing/self-hosted-plans"}]},"iac":{"artifactRef":"develop (moving branch)","artifactUrl":"https://github.com/chatwoot/chatwoot/blob/develop/docker-compose.production.yaml","reviewed":"2026-11-14","scope":"Production Docker deployment","source":"https://developers.chatwoot.com/self-hosted/deployment/docker","status":"documented","summary":"The production guide links an upstream Compose stack with Rails, Sidekiq, PostgreSQL and Redis. Its application image uses latest; pin a compatible release, set secrets, and configure TLS, storage and backups."},"licensePricing":{"reviewed":"2026-11-20","scope":"Current self-hosted edition comparison; not a hosted subscription or a total operating-cost estimate","source":"https://www.chatwoot.com/pricing/self-hosted-plans","status":"documented","summary":"Community is free to self-host. The current page lists Premium Support at $19 and Enterprise at $99 per agent/month; SAML is Enterprise-only. These are software/support plan units, excluding your infrastructure, taxes and connected AI usage. Confirm currency and billing terms at checkout."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Self-hosted plan comparison","source":"https://www.chatwoot.com/pricing/self-hosted-plans","status":"documented","summary":"SAML SSO is included in Enterprise, but not Community or Premium Support."}},"id":"chatwoot","infrastructure":["servers"],"infrastructureNotes":"The production Docker guide runs Rails application/worker services alongside PostgreSQL and Redis, or connects to separately managed equivalents. Official cloud guides use VMs and also identify Kubernetes paths.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://developers.chatwoot.com/self-hosted/deployment/docker"],"install":"Production Docker Compose, Linux VM or Kubernetes deployment","installMethods":["docker"],"kind":"product","license":"MIT Community Edition; proprietary enterprise features and paid self-hosted plans","licenseModel":"open-source","licenseModelNotes":"The self-hosted offering combines an MIT Community Edition with proprietary Enterprise feature code. Paid feature entitlements are distinct from community source-code rights; premium support alone is not the basis for this classification.","licenseModelSources":["https://www.chatwoot.com/hc/user-guide/articles/1677776492-enterprise-edition","https://www.chatwoot.com/pricing/self-hosted-plans"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Chatwoot Self-Hosted","notes":"Community Edition excludes paid features such as SSO/SAML, SLA policies and Captain AI. Captain integrations may send data to external model providers. Official Azure and Google Cloud deployment guides are marked work in progress; validate their instructions against current requirements before production.","operations":"Customer maintains the server, database, storage, updates and channel integrations; support differs by plan.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Community support functionality","url":"https://www.chatwoot.com/community"},{"title":"Production Docker installation","url":"https://developers.chatwoot.com/self-hosted/deployment/docker"},{"title":"Edition licensing","url":"https://www.chatwoot.com/hc/user-guide/articles/1677776492-enterprise-edition"},{"title":"Self-hosted plan features","url":"https://www.chatwoot.com/pricing/self-hosted-plans"},{"title":"Azure deployment","url":"https://developers.chatwoot.com/self-hosted/deployment/azure"},{"title":"Google Cloud deployment","url":"https://developers.chatwoot.com/self-hosted/deployment/gcp"},{"title":"Chatwoot self-hosted deployment on aws","url":"https://developers.chatwoot.com/self-hosted/deployment/aws"},{"title":"Chatwoot self-hosted deployment on digitalocean","url":"https://developers.chatwoot.com/self-hosted/deployment/digitalocean"}],"url":"https://launchinyourcloud.com/directory/chatwoot/","website":"https://www.chatwoot.com/"},{"architecture":"Kubernetes-hosted CircleCI services with persistent data services, object storage, networking and machine-execution capacity","categories":["devops"],"category":"DevOps","categoryFit":{"devops":"Provides self-hosted continuous integration and delivery pipelines, execution environments, policy controls and build infrastructure."},"cloudEvidence":[{"applicableVersions":["4.10"],"clouds":["aws"],"notes":"CircleCI documents preparing AWS networking, an EKS cluster, storage, permissions and other prerequisites before installing CircleCI Server with its Helm chart.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"CircleCI Server on Amazon EKS","url":"https://circleci.com/docs/server-admin/latest/installation/phase-1-aws-prerequisites/","vendorSupport":"not-assessed"},{"applicableVersions":["4.10"],"clouds":["gcp"],"notes":"CircleCI documents preparing a customer GCP project, VPC, GKE cluster, Cloud Storage and workload identity before installing CircleCI Server. The guide states that GKE Autopilot is unsupported.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"CircleCI Server on Google GKE","url":"https://circleci.com/docs/server-admin/latest/installation/phase-1-gcp-prerequisites/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-16","clouds":["aws","gcp"],"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"}],"description":"Commercial self-hosted CI/CD platform installed in a customer-operated Amazon EKS or Google GKE cluster.","diligence":{"airGap":{"availability":"available","reviewed":"2026-11-16","scope":"CircleCI Server documented air-gapped installation","source":"https://circleci.com/docs/server-admin/latest/air-gapped-installation/phase-1-prerequisites/","status":"documented","summary":"CircleCI documents a disconnected installation with a local container registry, Kubernetes, S3-compatible storage, GitHub Enterprise and Nomad VMs. Transfer all required release images and charts before installation; follow the remaining configuration and test phases."},"compliance":{"reviewed":"2026-11-16","scope":"Vendor security-program claims versus the customer-operated CircleCI Server boundary","source":"https://circleci.com/security/","status":"inconclusive","summary":"CircleCI publishes corporate SOC 2/FedRAMP claims and offers security reports. The public page does not establish the current report period or assurance scope for a customer-operated Server deployment; obtain the report and map the customer’s responsibilities."},"cost":{"reviewed":"2026-11-16","scope":"Public cost-driver guidance; no dated infrastructure-and-operations estimate","source":"https://circleci.com/docs/server-admin/latest/operator/resource-consumption-cost-management/","status":"inconclusive","summary":"The vendor identifies execution workers, per-job machine instances, Kubernetes capacity, artifacts/caches and block storage as cost drivers, and recommends retention, tagging and budget monitoring. It does not establish a workload- and region-specific operating total; concurrency, job duration, instance choices, retention and staffing still need a budget model."},"footprint":{"reviewed":"2026-11-16","scope":"Server 4.10 control/application cluster on AWS; not a total build-fleet or cost estimate","source":"https://circleci.com/docs/server-admin/latest/installation/phase-1-aws-prerequisites/","status":"documented","summary":"The Server 4.10 AWS guide specifies at least four Kubernetes nodes, 24 CPU cores and 90 GB total RAM below 500 daily active users; 500+ users require six nodes, 48 cores and 240 GB. Job-execution capacity and external services require separate sizing."},"iac":{"artifactRef":"main (moving branch; guide example chart 4.10.1)","artifactUrl":"https://github.com/CircleCI-Public/server-scripts/blob/main/air-gap/extract-images-from-helm-chart.sh","reviewed":"2026-11-16","scope":"Server 4.10 air-gap preparation; guide example chart 4.10.1","source":"https://circleci.com/docs/server-admin/latest/air-gapped-installation/phase-1-prerequisites/","status":"documented","summary":"The Helm chart is distributed through cciserver.azurecr.io. The linked helper enumerates chart images for transfer to a private registry; it is not the chart or a complete infrastructure template. Select a compatible Server/chart release and use CircleCI-provided registry credentials."},"licensePricing":{"reviewed":"2026-11-16","scope":"CircleCI Server: software license terms; infrastructure and operating costs are separate","source":"https://circleci.com/pricing/server/","status":"documented","summary":"CircleCI Server is an enterprise self-hosted offering that requires a commercial license supplied during installation.","supportingSources":[{"title":"Edition and license conditions","url":"https://circleci.com/docs/server-admin/latest/installation/installation-reference/"}]},"marketplace":{"reviewed":"2026-11-16","scope":"Mixed-offering Marketplace description; Server contract coverage remains unresolved","source":"https://aws.amazon.com/marketplace/pp/prodview-puu7lb34aqr66","status":"inconclusive","summary":"The reviewed vendor AWS listing is titled Cloud-Hosted CICD, while its description also mentions Server and customized packages. The public terms do not establish the exact self-hosted Server entitlement; confirm a Server-specific contract before purchase."},"release":{"releasePublishedOn":"2026-08-11","releaseTag":"4.10.1","reviewed":"2026-11-16","scope":"CircleCI Server release; review MongoDB and other upgrade prerequisites; source supplies a publication day, not a timestamp","source":"https://circleci.com/changelog/server-release-4-10-1/","status":"documented","summary":"The reviewed vendor release is 4.10.1, published 2026-08-11. This is a dated, scoped snapshot; it does not establish compatibility with another chart, cloud package or commercial edition."},"scim":{"reviewed":"2026-11-16","scope":"Delegated GitHub Enterprise provisioning; direct Server SCIM remains unconfirmed","source":"https://circleci.com/docs/server-admin/latest/operator/operator-overview/","status":"inconclusive","summary":"The operator guide describes SCIM at the GitHub Enterprise identity-provider layer. It does not establish a direct CircleCI SCIM endpoint or the full lifecycle behavior inside Server."},"securityControls":{"reviewed":"2026-11-16","scope":"Server 4.10 Kubernetes/Nomad/VM network hardening","source":"https://circleci.com/docs/server-admin/latest/installation/hardening-your-cluster/","status":"documented","summary":"The Server hardening guide recommends private resources, permits VPN-only access without public IPs, and requires Nomad client/server mTLS. Job SSH exposure and firewall/security-group rules need deliberate configuration; the documentation is guidance, not proof the installed cluster already enforces it."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-16","scope":"CircleCI Server 4.10; GitHub identity integration","source":"https://circleci.com/docs/server-admin/latest/operator/operator-overview/","status":"documented","summary":"Server uses GitHub or GitHub Enterprise as its identity provider. GitHub Enterprise can federate authentication through SAML; configure that upstream identity boundary rather than assuming a direct CircleCI SAML integration."}},"id":"circleci-server","infrastructure":["servers"],"infrastructureNotes":"CircleCI Server runs persistent application and data-service workloads in a customer Kubernetes cluster and uses cloud object storage and provisioned execution capacity.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://circleci.com/docs/server-admin/latest/overview/circleci-server-overview/","https://circleci.com/docs/server-admin/latest/installation/installation-reference/"],"install":"Official Terraform-assisted infrastructure setup and Helm installation on Amazon EKS or Google GKE","installMethods":["terraform","helm"],"kind":"product","license":"Commercial CircleCI Server license required.","licenseModel":"commercial-only","licenseModelNotes":"CircleCI Server is an enterprise self-hosted offering that requires a commercial license supplied during installation.","licenseModelSources":["https://circleci.com/pricing/server/","https://circleci.com/docs/server-admin/latest/installation/installation-reference/"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"CircleCI Server","notes":"This entry covers CircleCI Server, not CircleCI Cloud or cloud-connected self-hosted runners. EKS and GKE are the tested cloud environments; CircleCI labels Azure and DigitalOcean as untested. GKE Autopilot is unsupported. CircleCI Server currently supports GitHub Enterprise Cloud and GitHub Enterprise Server as version-control providers.","operations":"Customer manages Kubernetes, networking, object storage, databases, secrets, TLS, execution capacity, backups, upgrades and the CircleCI Server license.","publisher":false,"reviewed":"2026-11-16","sources":[{"title":"CircleCI Server 4.10 overview","url":"https://circleci.com/docs/server-admin/latest/overview/circleci-server-overview/"},{"title":"CircleCI Server AWS prerequisites","url":"https://circleci.com/docs/server-admin/latest/installation/phase-1-aws-prerequisites/"},{"title":"CircleCI Server GCP prerequisites","url":"https://circleci.com/docs/server-admin/latest/installation/phase-1-gcp-prerequisites/"},{"title":"CircleCI Server installation reference","url":"https://circleci.com/docs/server-admin/latest/installation/installation-reference/"},{"title":"CircleCI Server plan and hosting model","url":"https://circleci.com/pricing/server/"}],"url":"https://launchinyourcloud.com/directory/circleci-server/","website":"https://circleci.com/pricing/server/"},{"advisories":[{"action":"Upgrade self-managed deployments to the fixed release for the selected branch or later, and confirm managed-service patch status.","conditions":"Network reachability to an affected service is required; validate the exact installed release and exposure.","id":"clickhouse-cve-2026-116366","listingIds":["clickhouse"],"reviewed":"2026-11-18","scope":"Vendor fixes are 26.3.62.3-lts, 26.8.36.3-lts, 26.9.27.3, and 26.10.3.7. ClickHouse states that its Cloud and BYOC services were patched.","source":"https://clickhouse.com/docs/resources/changelogs/security-changelog","summary":"CVE-2026-116366 is a critical unauthenticated network code-execution issue in affected ClickHouse releases.","title":"ClickHouse unauthenticated network code execution","type":"security-advisory"}],"architecture":"Vendor control plane; customer data plane","categories":["databases-vector"],"category":"Databases \u0026 vector","categoryFit":{"databases-vector":"Managed analytical database with its data plane in your cloud account."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"The vendor explicitly offers its managed BYOC service in the customer AWS, Google Cloud or Azure account. This establishes provider compatibility for the commercial BYOC offering rather than a generic open-source Docker deployment; agree availability, access, region and operational boundaries with the vendor.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"ClickHouse BYOC customer account support","url":"https://clickhouse.com/cloud/bring-your-own-cloud","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"vendor-hosted","evidence":[0],"operator":"vendor"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"vendor-hosted","evidence":[0],"operator":"vendor"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"vendor-hosted","evidence":[0],"operator":"vendor"}],"description":"Managed analytical database with its data plane in your cloud account.","diligence":{"commitments":{"availability":"edition-dependent","reviewed":"2026-11-21","scope":"Azure BYOC Marketplace purchase only; agreement and offer qualifications apply.","source":"https://clickhouse.com/blog/clickhouse-expands-collaboration-with-microsoft","status":"documented","summary":"ClickHouse states that its Microsoft Marketplace BYOC offer can count toward Microsoft Azure Consumption Commitments (MACC). Confirm the selected offer and purchase agreement are eligible before procurement; this does not establish AWS or Google Cloud software-commitment eligibility.","supportingSources":[{"title":"Azure BYOC Marketplace offer","url":"https://marketplace.microsoft.com/en-us/product/clickhouse.byoc_clickhouse_cloud?tab=Overview"}]},"compliance":{"reviewed":"2026-11-14","scope":"BYOC marketing statement checked; applicable attestation scope unresolved","source":"https://clickhouse.com/cloud/bring-your-own-cloud","status":"inconclusive","summary":"The BYOC page states SOC 2 and ISO 27001 alignment but does not provide the assessed service boundary, report or certificate scope for this customer-account deployment. Obtain the applicable evidence before treating it as an attestation."},"footprint":{"reviewed":"2026-11-20","scope":"Commercial managed BYOC footprint unresolved","source":"https://clickhouse.com/cloud/bring-your-own-cloud","status":"inconclusive","summary":"The public BYOC offer targets large-scale deployments with vendor onboarding but does not publish a validated minimum CPU/RAM/storage topology. Obtain supported instance types, availability-zone design and workload sizing for the contracted provider and region. Do not substitute open-source single-node minima."},"iac":{"reviewed":"2026-11-20","scope":"Managed BYOC onboarding; public artifact unresolved","source":"https://clickhouse.com/cloud/bring-your-own-cloud","status":"inconclusive","summary":"The public BYOC page establishes personalized vendor onboarding and a customer-cloud data plane, but does not expose a reviewed reusable provisioning artifact. Obtain the region-specific onboarding template, role policy and version from ClickHouse; an open-source ClickHouse Helm chart is a different deployment."},"licensePricing":{"reviewed":"2026-11-21","scope":"Commercial BYOC pricing access and Azure procurement. Confirm offer terms, region availability, and the applicable commitment with ClickHouse.","source":"https://clickhouse.com/cloud/bring-your-own-cloud","status":"documented","summary":"ClickHouse provides BYOC rates through its Trust Center after approving an access request. Azure customers can procure the managed BYOC service through Microsoft Marketplace. ClickHouse says purchases can count toward Microsoft Azure Consumption Commitments.","supportingSources":[{"title":"ClickHouse Cloud BYOC offer in Microsoft Marketplace","url":"https://marketplace.microsoft.com/en-us/product/clickhouse.byoc_clickhouse_cloud?tab=Overview"},{"title":"ClickHouse announcement of Microsoft Marketplace availability","url":"https://clickhouse.com/blog/clickhouse-expands-collaboration-with-microsoft"}]},"marketplace":{"availability":"available","reviewed":"2026-11-21","scope":"ClickHouse Cloud BYOC procurement for Azure; confirm private-offer, region and agreement terms.","source":"https://marketplace.microsoft.com/en-us/product/clickhouse.byoc_clickhouse_cloud?tab=Overview","status":"documented","summary":"Microsoft Marketplace lists ClickHouse Cloud BYOC as a fully managed service deployed into the customer's own Azure account. This is the Azure BYOC offer, separate from vendor-account ClickHouse Cloud."},"securityControls":{"reviewed":"2026-11-18","scope":"Vendor fixes are 26.3.62.3-lts, 26.8.36.3-lts, 26.9.27.3, and 26.10.3.7. ClickHouse states that its Cloud and BYOC services were patched.","source":"https://clickhouse.com/docs/resources/changelogs/security-changelog","status":"documented","summary":"Current advisory review: CVE-2026-116366 is a critical unauthenticated network code-execution issue in affected ClickHouse releases. Upgrade self-managed deployments to the fixed release for the selected branch or later, and confirm managed-service patch status."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Commercial ClickHouse BYOC organization SAML","source":"https://clickhouse.com/blog/introducing-scim-provisioning-in-clickhouse-cloud","status":"documented","summary":"The vendor explicitly includes BYOC organizations in its SAML/SCIM availability statement. Configure the organization SAML connection and verified domains; this concerns vendor-hosted organization/control-plane identity, not autonomous authentication for every database client."}},"id":"clickhouse","infrastructure":["servers"],"infrastructureNotes":"The documented BYOC data plane uses a customer-cloud Kubernetes cluster and ClickHouse servers. Vendor management of the control plane is separate from this runtime classification.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://clickhouse.com/blog/byoc-gcp-ga"],"install":"Vendor-assisted BYOC onboarding","installMethods":["vendor-assisted"],"kind":"platform","license":"Commercial","licenseModel":"commercial-only","licenseModelNotes":"This listing covers the commercially provided managed/BYOC service, not a separately licensed open-source engine or library.","licenseModelSources":["https://clickhouse.com/cloud/bring-your-own-cloud"],"licenseReviewed":"2026-11-10","model":"BYOC","modelLabel":"Vendor-operated BYOC","name":"ClickHouse BYOC","notes":"The vendor lists AWS, Google Cloud and Azure BYOC options. Confirm region availability and commercial requirements during onboarding. This entry does not describe ordinary ClickHouse Cloud hosting. CVE-2026-116366 is a critical unauthenticated network code-execution issue. ClickHouse states that Cloud and BYOC were patched; self-managed fixes are available in 26.3.62.3-lts, 26.8.36.3-lts, 26.9.27.3, and 26.10.3.7.","operationReview":{"controlPlane":"vendor-hosted","modelLabel":"Vendor-operated BYOC","operator":"vendor","reviewed":"2026-11-20","source":"https://clickhouse.com/cloud/bring-your-own-cloud","summary":"The vendor describes a fully managed ClickHouse service in the customer's AWS, Google Cloud or Azure account. Commercial availability and access are agreed during onboarding.","supportingSources":[{"title":"Control-plane and data-plane architecture","url":"https://clickhouse.com/docs/cloud/reference/byoc/overview"}]},"operations":"ClickHouse operates the BYOC service; the customer owns the cloud environment.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Bring Your Own Cloud","url":"https://clickhouse.com/cloud/bring-your-own-cloud"},{"title":"Google Cloud BYOC architecture","url":"https://clickhouse.com/blog/byoc-gcp-ga"},{"title":"ClickHouse security changelog","url":"https://clickhouse.com/docs/resources/changelogs/security-changelog"}],"url":"https://launchinyourcloud.com/directory/clickhouse/","website":"https://clickhouse.com/"},{"architecture":"Cloud Carbon Footprint API deployed to Google App Engine with configured cloud-usage data sources.","categories":["data-analytics","observability"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Open-source cloud-usage, energy and carbon-estimation application.","observability":"Open-source cloud-usage, energy and carbon-estimation application."},"cloudEvidence":[{"clouds":["gcp"],"notes":"Cloud Carbon Footprint API deployed to Google App Engine with configured cloud-usage data sources. The named hosting path is Google App Engine; reading AWS/Azure billing does not establish app deployment there. Estimates and dashboards are not audited emissions or regulatory-compliance certifications. The moving latest release tag is not an immutable application version.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"GCP App Engine","url":"https://www.cloudcarbonfootprint.org/docs/deploying/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["gcp"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/cloud-carbon-footprint/cloud-carbon-footprint"}],"summary":"The reviewed upstream contributor history includes camcash17, dtoakley, 4upz, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Open-source cloud-usage, energy and carbon-estimation application.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Current API example allocation on moving trunk; complete workload sizing remains unconfirmed","source":"https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/packages/api/app.yaml","status":"inconclusive","summary":"The current API App Engine recipe selects instance class B2 with basic scaling capped at one instance. This is a deployment example, not a complete UI/API/cache capacity or HA baseline. Query range, account/project count, billing-data processing and cache/database growth need sizing; do not treat one small API instance as a validated 100-user HA design.","supportingSources":[{"title":"Application and frontend deployment steps","url":"https://www.cloudcarbonfootprint.org/docs/deploying/"}]},"iac":{"artifactRef":"trunk (moving branch)","artifactUrl":"https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/packages/api/app.yaml","reviewed":"2026-11-19","scope":"Cloud Carbon Footprint deployment example; review the full linked installation instructions","source":"https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/packages/api/app.yaml","status":"documented","summary":"The reviewed source supplies deployment configuration for Cloud Carbon Footprint API deployed to Google App Engine with configured cloud-usage data sources. Set organization-specific secrets, networking, storage and compatible image versions before use."},"licensePricing":{"reviewed":"2026-11-19","scope":"Cloud Carbon Footprint; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/LICENSE","status":"documented","summary":"Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"release":{"reviewed":"2026-11-19","scope":"Cloud Carbon Footprint upstream application; verify compatibility with the selected package","source":"https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/releases/tag/latest","status":"documented","summary":"The project publishes a moving latest release marker. The reviewed repository remains active, but this marker does not identify an immutable production application release or support duration."},"sso":{"reviewed":"2026-11-20","scope":"Actual upstream middleware on moving trunk; cloud-source IAM is separate from application-user SSO","source":"https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/packages/api/src/utils/auth.ts","status":"inconclusive","summary":"The reviewed API authentication middleware logs success and calls next without validating a user. Cloud-account credentials in its configuration authenticate usage-data collection, not dashboard users. A supported external IdP login, account/role mapping and protection of both UI/API remain unconfirmed; an identity-aware proxy would need a separately reviewed design.","supportingSources":[{"title":"Cloud data-source authentication configuration","url":"https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/packages/common/src/Config.ts"}]}},"id":"cloud-carbon-footprint","infrastructure":["servers"],"infrastructureNotes":"Cloud Carbon Footprint API deployed to Google App Engine with configured cloud-usage data sources. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://www.cloudcarbonfootprint.org/docs/deploying/"],"install":"Application platform deployment","installMethods":["platform-template"],"kind":"product","license":"Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Cloud Carbon Footprint","notes":"The named hosting path is Google App Engine; reading AWS/Azure billing does not establish app deployment there. Estimates and dashboards are not audited emissions or regulatory-compliance certifications. The moving latest release tag is not an immutable application version.","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":"GCP App Engine","url":"https://www.cloudcarbonfootprint.org/docs/deploying/"},{"title":"app.yaml","url":"https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/packages/api/app.yaml"},{"title":"appengine-deploy.sh","url":"https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/packages/api/appengine-deploy.sh"},{"title":"Apache-2.0","url":"https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/LICENSE"},{"title":"Releases","url":"https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/releases"}],"url":"https://launchinyourcloud.com/directory/cloud-carbon-footprint/","website":"https://cloudcarbonfootprint.org"},{"advisories":[{"action":"Upgrade to 2.580.2.38435 or later, migrate to Java 21, and retire end-of-life controller types.","conditions":"Installed plugins, controller type, and Java runtime determine applicability and upgrade sequencing.","disclosedOn":"2026-10-29","id":"cloudbees-ci-2-580-2-38435-security-update","listingIds":["cloudbees-ci-modern-cloud-platforms"],"reviewed":"2026-11-18","scope":"CloudBees CI modern cloud platforms release 2.580.2.38435; component applicability follows the vendor release notes.","source":"https://docs.cloudbees.com/docs/release-notes/latest/cloudbees-ci/","summary":"CloudBees CI 2.580.2.38435 contains security updates and is on the Java 21-supported line.","title":"CloudBees CI October 2026 security update","type":"security-advisory"}],"architecture":"CloudBees operations center and managed controllers in the customer Kubernetes cluster.","categories":["devops"],"category":"DevOps","categoryFit":{"devops":"Centrally managed enterprise continuous integration and delivery environment."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"CloudBees provides product installation guides for Amazon EKS, Azure AKS and Google GKE, and its supported-platform matrix lists all three. The customer operates the Kubernetes cluster.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"CloudBees CI installation on EKS, AKS and GKE","url":"https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro","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 continuous-integration platform installed with Helm in a Kubernetes cluster you operate.","diligence":{"airGap":{"reviewed":"2026-11-17","scope":"CI plugin mirror; complete offline deployment remains to be established","source":"https://docs.cloudbees.com/docs/cloudbees-ci/latest/casc-plugin-management/alternate-plugin-download-site","status":"inconclusive","summary":"CloudBees documents an update-center mirror for plugin management in air-gapped environments. That establishes a plugin-transfer mechanism, but not every licensing, image, agent and upgrade dependency for a fully isolated deployment."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for CloudBees CI on Modern Cloud Platforms; unresolved within this edition/deployment","source":"https://www.cloudbees.com/partners/platform/aws","status":"inconclusive","summary":"The AWS partnership page establishes CI procurement availability, but not qualifying charges or committed-spend treatment under a buyer agreement."},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://docs.cloudbees.com/docs/cloudbees-ci/latest/secure/saml-setup","status":"inconclusive","summary":"The reviewed CloudBees CI on Modern Cloud Platforms 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.cloudbees.com/docs/cloudbees-ci/latest/cloud-reference-architecture/ra-for-aws/","status":"inconclusive","summary":"Confirm controllers, operations center, build agents, concurrency and licence/support scope. Worker VM hours and artifact storage cannot be inferred from a 100-user headcount. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"AWS Kubernetes reference architecture; not an HA capacity guarantee","source":"https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-reference-architecture/ra-for-aws/","status":"documented","summary":"The AWS reference architecture sizes operations center, managed controllers and build agents separately. Its examples are recommendations rather than universal requirements; build concurrency and agent workloads drive capacity."},"iac":{"reviewed":"2026-11-17","scope":"CloudBees CI modern cloud platforms","source":"https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro","status":"documented","summary":"The modern-platform installation index provides Helm deployment paths for EKS, AKS and GKE. The AWS partnership page also links a CI EKS Blueprints add-on; configure storage, ingress and controllers for the selected supported platform."},"licensePricing":{"reviewed":"2026-11-17","scope":"CloudBees CI on Modern Cloud Platforms: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-admin-guide/","status":"documented","summary":"CloudBees CI is proprietary licensed software; operations center and standalone controllers require valid CloudBees licensing. Upstream Jenkins is a separate product."},"marketplace":{"availability":"available","reviewed":"2026-11-17","scope":"Vendor CI procurement statement; offer details must be selected","source":"https://www.cloudbees.com/partners/platform/aws","status":"documented","summary":"CloudBees identifies CI availability through AWS Marketplace, including a separate GovCloud marketplace route. Confirm the CI offer, subscription and delivery terms rather than substituting CodeShip or Unify listings."},"release":{"releasePublishedOn":"2026-10-29","releaseTag":"2.580.2.38435","reviewed":"2026-11-18","scope":"CloudBees CI modern cloud platforms","source":"https://docs.cloudbees.com/docs/release-notes/latest/cloudbees-ci/","status":"documented","summary":"CloudBees CI 2.580.2.38435 was released October 29, 2026 with security updates. Java 21 is required for supported current releases; Blue Ocean and Team controllers are end of life."},"scim":{"reviewed":"2026-11-17","scope":"CloudBees CI, not Unify or community plugins","source":"https://docs.cloudbees.com/docs/cloudbees-ci/latest/secure/saml-setup","status":"inconclusive","summary":"The SAML guide explicitly separates authentication and group assertions from external group/role synchronization. A supported CI SCIM lifecycle endpoint was not established; CloudBees Unify or generic Jenkins plugins are insufficient evidence."},"securityControls":{"reviewed":"2026-11-18","scope":"CI authentication and authorization configuration CloudBees CI modern cloud platforms release 2.580.2.38435; component applicability follows the vendor release notes.","source":"https://docs.cloudbees.com/docs/release-notes/latest/cloudbees-ci/","status":"documented","summary":"Configure the SAML security realm and CloudBees RBAC separately; signing/encryption and IdP attributes must match the configured trust. Use supported plugins and current security fixes. Current advisory review: CloudBees CI 2.580.2.38435 contains security updates and is on the Java 21-supported line. Upgrade to 2.580.2.38435 or later, migrate to Java 21, and retire end-of-life controller types.","supportingSources":[{"title":"Prior security-controls source","url":"https://docs.cloudbees.com/docs/cloudbees-ci/latest/secure/saml-setup"}]},"sso":{"availability":"available","reviewed":"2026-11-17","scope":"CloudBees CI SAML security realm","source":"https://docs.cloudbees.com/docs/cloudbees-ci/latest/secure/saml-setup","status":"documented","summary":"CloudBees CI documents SAML authentication with the supported SAML plugin and IdP metadata. Group attributes can inform RBAC, but the plugin does not synchronize external groups or roles."}},"id":"cloudbees-ci-modern-cloud-platforms","infrastructure":["servers"],"infrastructureNotes":"The application runs as persistent Kubernetes workloads, including an operations center and managed controllers, in the customer's cluster.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro","https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-onboarding"],"install":"CloudBees Helm chart on EKS, AKS or GKE","installMethods":["helm","kubernetes"],"kind":"platform","license":"Commercial CloudBees CI license required.","licenseModel":"commercial-only","licenseModelNotes":"CloudBees CI is proprietary licensed software; operations center and standalone controllers require valid CloudBees licensing. Upstream Jenkins is a separate product.","licenseModelSources":["https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-admin-guide/"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"CloudBees CI on Modern Cloud Platforms","notes":"This entry covers CloudBees CI on modern cloud platforms, not plain Jenkins or a CloudBees-hosted service. CloudBees publishes separate EKS, AKS and GKE paths and a strict platform/version support matrix. Each standalone controller requires a valid license. CloudBees CI 2.580.2.38435 is the October 29 security release. Java 17 has been unsupported since 2.555.1.36485, so migrate controllers and agents to Java 21; Blue Ocean and Team controllers reached end of life in July 2026.","operations":"Customer provisions and operates Kubernetes, storage, networking, ingress, DNS, certificates and upgrades; CloudBees supports the licensed application within documented boundaries.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"CloudBees CI installation index","url":"https://docs.cloudbees.com/docs/cloudbees-ci/latest/installing/intro"},{"title":"Modern cloud platform onboarding","url":"https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-onboarding"},{"title":"Supported Kubernetes platforms and versions","url":"https://docs.cloudbees.com/docs/cloudbees-common/latest/supported-platforms/cloudbees-ci-cloud"},{"title":"CloudBees CI administration and licensing","url":"https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-admin-guide/"},{"title":"CloudBees CI release notes","url":"https://docs.cloudbees.com/docs/release-notes/latest/cloudbees-ci/"}],"url":"https://launchinyourcloud.com/directory/cloudbees-ci-modern-cloud-platforms/","website":"https://www.cloudbees.com/"},{"advisories":[{"action":"Apply the exact fixed component build and review affected certificate trust.","conditions":"Bundled Brotli and certificate trust stores determine exposure.","id":"cloudera-november-2026-security-bulletins","listingIds":["cloudera-on-cloud"],"reviewed":"2026-11-18","scope":"Affected and fixed versions vary by Runtime and Private Cloud Base component; consult TSB-2026-1007 and TSB-2026-1009.","source":"https://docs.cloudera.com/cdp-private-cloud-base/7.3.3/private-release-notes/topics/tsb-2026-1007.html","summary":"Cloudera TSBs address critical Brotli CVE-2026-111497 and compromised eMudhra certificates in specified CDP components.","supportingSources":[{"title":"TSB-2026-1009","url":"https://docs.cloudera.com/runtime/7.3.3/public-release-notes/topics/tsb-2026-1009.html"}],"title":"Cloudera November 2026 Brotli and certificate bulletins","type":"security-advisory"}],"architecture":"Vendor-operated control plane with data, compute, networking and workload environments in the customer's cloud account.","categories":["data-analytics","streaming","ai-tools"],"category":"Data \u0026 analytics","categoryFit":{"ai-tools":"Machine-learning and AI workload services are available within the Cloudera platform, subject to provider and subscription availability.","data-analytics":"Managed data engineering, warehousing and analytics services operate over data in customer cloud environments.","streaming":"Cloudera provides streaming ingestion and processing services where supported by the selected cloud deployment."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Cloudera documents registering customer AWS, Azure and Google Cloud environments and credentials so its control plane can provision workload resources. Provider service availability differs and must be checked for the selected workload.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Cloudera workloads in customer AWS, Azure and Google Cloud environments","url":"https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-17","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"vendor-hosted","evidence":[0],"operator":"shared"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"vendor-hosted","evidence":[0],"operator":"shared"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"vendor-hosted","evidence":[0],"operator":"shared"}],"description":"Cloudera-managed control plane that provisions data, analytics and AI workload services into a customer's public-cloud account.","diligence":{"airGap":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment","source":"https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html","status":"inconclusive","summary":"This listing uses an external vendor control plane. The reviewed public-cloud setup does not establish complete isolated operation; Cloudera Private Cloud documentation is a different offering."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment","source":"https://www.cloudera.com/products/pricing.html","status":"inconclusive","summary":"Platform pricing and cloud cost-optimization guidance do not establish which software fees qualify for a buyer’s committed-spend agreement."},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://docs.cloudera.com/management-console/cloud/user-management/topics/mc-known_issues_and_troubleshooting_related_to_idp_setup_in_cdp.html","status":"inconclusive","summary":"The reviewed Cloudera on Cloud 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.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html","status":"inconclusive","summary":"Select workload services, Data Lake/runtime topology, data scans/compute-hours and provider-specific service availability. Vendor fees and customer-cloud resources are billed separately. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"Cloudera on cloud workload-specific sizing","source":"https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html","status":"inconclusive","summary":"The platform offers multiple workload services with different node, storage and database needs. The overview does not establish one minimum HA footprint for 100 users/1 TB; select the actual services and workload configuration."},"iac":{"reviewed":"2026-11-17","scope":"Cloudera public-cloud environment setup; services differ by provider","source":"https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html","status":"documented","summary":"Customer-cloud setup requires cloud account credentials, network prerequisites and an environment registration before Cloudera provisions workloads. The vendor control plane remains external to the customer account."},"licensePricing":{"reviewed":"2026-11-17","scope":"Cloudera on Cloud: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://www.cloudera.com/products/pricing.html","status":"documented","summary":"Cloudera on Cloud is a commercial subscription service. Customer cloud-resource charges and Cloudera software/service consumption are separate."},"marketplace":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment","source":"https://www.cloudera.com/partners/solutions/google-cloud-platform.html","status":"inconclusive","summary":"The Google partnership page still labels Marketplace deployment coming soon. A current offer for the selected workload service and provider was not established from these sources."},"release":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment","source":"https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html","status":"inconclusive","summary":"Management Console and customer-cloud workload services have independent release/runtime lines. A single platform latest-version number or universal upgrade schedule was not established."},"scim":{"availability":"available","reviewed":"2026-11-17","scope":"Cloudera account provisioning, not a self-hosted SCIM server","source":"https://docs.cloudera.com/management-console/cloud/user-management/topics/mc-configuring_scim_with_azure_ad.html","status":"documented","summary":"Cloudera documents SCIM with Entra ID alongside SAML federation. Only one SCIM IdP per account is supported; userName and group-name changes are unsupported, so choose stable identifiers."},"securityControls":{"reviewed":"2026-11-18","scope":"Management Console identity synchronization and permissions Affected and fixed versions vary by Runtime and Private Cloud Base component; consult TSB-2026-1007 and TSB-2026-1009.","source":"https://docs.cloudera.com/cdp-private-cloud-base/7.3.3/private-release-notes/topics/tsb-2026-1007.html","status":"documented","summary":"The user-management guidance warns about mutable identity keys and concurrent SAML/SCIM group synchronization. Align stable NameID/userName values and review privileged account/group mappings. Current advisory review: Cloudera TSBs address critical Brotli CVE-2026-111497 and compromised eMudhra certificates in specified CDP components. Apply the exact fixed component build and review affected certificate trust.","supportingSources":[{"title":"Prior security-controls source","url":"https://docs.cloudera.com/management-console/cloud/user-management/topics/mc-known_issues_and_troubleshooting_related_to_idp_setup_in_cdp.html"},{"title":"TSB-2026-1009","url":"https://docs.cloudera.com/runtime/7.3.3/public-release-notes/topics/tsb-2026-1009.html"}]},"sso":{"availability":"available","reviewed":"2026-11-17","scope":"Cloudera-managed control plane for customer-cloud workloads","source":"https://docs.cloudera.com/management-console/cloud/user-management/topics/mc-setting-up-the-identity-provider-in-cdp.html","status":"documented","summary":"Management Console supports federation using enterprise SAML IdP metadata. Identity-provider creation is privileged; duplicate group names across IdPs can grant unintended memberships."}},"id":"cloudera-on-cloud","infrastructure":["servers"],"infrastructureNotes":"The customer account contains persistent data and compute services while Cloudera operates an external control plane. Runtime topology varies by selected workload service.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-public-cloud.html","https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html"],"install":"Register the customer cloud environment and credentials, then provision Cloudera workload services through the control plane","installMethods":["vendor-assisted","other"],"kind":"platform","license":"Commercial Cloudera subscription with cloud infrastructure charges paid separately.","licenseModel":"commercial-only","licenseModelNotes":"Cloudera on Cloud is a commercial subscription service. Customer cloud-resource charges and Cloudera software/service consumption are separate.","licenseModelSources":["https://www.cloudera.com/products/pricing.html"],"licenseReviewed":"2026-11-17","model":"BYOC","modelLabel":"Shared operations · vendor control plane","name":"Cloudera on Cloud","notes":"This entry covers Cloudera's public-cloud BYOC service, not a fully customer-operated software distribution. Workloads and data run in the customer's AWS, Azure or Google Cloud environment while Cloudera operates the control plane. Service availability and implementation details differ by provider, especially on Google Cloud, so confirm each required service before procurement. Cloudera November bulletins cover critical Brotli CVE-2026-111497 and compromised eMudhra certificates. Use the TSB matrices for the exact Runtime or Private Cloud Base component and fixed build rather than applying a generic platform version.","operationReview":{"controlPlane":"vendor-hosted","modelLabel":"Shared operations · vendor control plane","operator":"shared","reviewed":"2026-11-20","source":"https://www.cloudera.com/products/trust-center/shared-responsibility-model.html","summary":"Cloudera operates the control plane while workloads run in the customer's cloud accounts. Customer responsibilities include credentials, account policies, workload configuration and data governance; confirm each selected service's responsibility split."},"operations":"Cloudera operates the service control plane; the customer owns cloud resources, credentials, data governance, network integration, workload sizing and shared operational responsibilities.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Cloudera public-cloud architecture and ownership","url":"https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-public-cloud.html"},{"title":"Cloud prerequisites and credential setup","url":"https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html"},{"title":"Cloudera workload services","url":"https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html"},{"title":"Cloudera pricing","url":"https://www.cloudera.com/products/pricing.html"},{"title":"Cloudera TSB-2026-1007","url":"https://docs.cloudera.com/cdp-private-cloud-base/7.3.3/private-release-notes/topics/tsb-2026-1007.html"},{"title":"Cloudera TSB-2026-1009","url":"https://docs.cloudera.com/runtime/7.3.3/public-release-notes/topics/tsb-2026-1009.html"}],"url":"https://launchinyourcloud.com/directory/cloudera-on-cloud/","website":"https://www.cloudera.com/products/cloudera-cloud.html"},{"architecture":"Cockroach Labs control plane with database data plane in the customer cloud account","categories":["databases-vector"],"category":"Databases \u0026 vector","categoryFit":{"databases-vector":"Provides a managed distributed SQL database whose data-plane resources run inside the customer's cloud account."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Cockroach Labs explicitly offers BYOC in the customer's AWS, Azure or Google Cloud account. The vendor operates database services using scoped cross-account identity while the customer retains the cloud account and data-plane boundary.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"CockroachDB BYOC customer-cloud support","url":"https://www.cockroachlabs.com/product/cloud/bring-your-own-cloud/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-14","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"vendor-hosted","evidence":[0],"operator":"vendor"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"vendor-hosted","evidence":[0],"operator":"vendor"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"vendor-hosted","evidence":[0],"operator":"vendor"}],"description":"Vendor-managed CockroachDB service deployed into the customer's AWS, Azure or Google Cloud account.","diligence":{"commitments":{"reviewed":"2026-11-14","scope":"Customer cloud infrastructure discounts; software/service billing eligibility is separate","source":"https://www.cockroachlabs.com/product/cloud/bring-your-own-cloud/","status":"documented","summary":"The BYOC product page says customer-account infrastructure can use applicable committed-use discounts or reserved instances. This does not establish that Cockroach Labs software charges decrement a particular cloud commitment."},"footprint":{"reviewed":"2026-11-20","scope":"Continuum managed BYOC workload sizing; complete numerical footprint unresolved","source":"https://docs.cockroachlabs.com/docs/continuum/byoc-overview.md","status":"inconclusive","summary":"The BYOC overview requires a customer-sized Mission Critical cluster, cloud quotas and continuous lifecycle permissions. It does not establish a single minimum CPU/RAM/storage/zone topology for 100 users and 1 TB. Select workload concurrency, provisioned storage, regional availability and failure headroom with Cockroach Labs before requesting capacity."},"iac":{"artifactRef":"Current Continuum onboarding policies; agree account/region and supported service version","artifactUrl":"https://docs.cockroachlabs.com/docs/continuum/byoc-aws-deployment.md","reviewed":"2026-11-20","scope":"Vendor-operated Continuum BYOC AWS onboarding artifacts and API path","source":"https://docs.cockroachlabs.com/docs/continuum/byoc-aws-deployment.md","status":"documented","summary":"The AWS onboarding guide publishes customer-account role/trust and lifecycle permission policies, then provisions the managed cluster through Cloud Console or API. Vendor documentation also lists Terraform creation. Use the BYOC-specific role and account preparation; self-hosted CockroachDB manifests are a different deployment."},"licensePricing":{"reviewed":"2026-11-17","scope":"CockroachDB BYOC on Continuum commercial service charges, not a total operating estimate or pricing for separately self-hosted CockroachDB. Public-preview host/virtual clusters are excluded from availability SLAs.","source":"https://www.cockroachlabs.com/blog/byoc-cockroach-continuum/","status":"documented","summary":"Continuum Mission Critical BYOC is USD 1,000 per vCPU per year, metered by the minute, with premium support. The public-preview Cluster Virtualization add-on is USD 200 per host-vCPU per year on AWS and Google Cloud. Invoice billing and per-organization enablement are required. Customer cloud infrastructure is billed separately. Pre-Continuum organizations keep their existing pricing/support until migration is available."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Commercial Cloud organization identity used with BYOC; database-client identity separate","source":"https://www.cockroachlabs.com/cockroachdb-cloud-security/","status":"documented","summary":"The vendor documents Cloud Organization SSO using SAML or OIDC with a customer IdP, enforcement and domain restrictions. A BYOC cluster belongs to that managed organization. This is vendor-hosted Cloud Console identity; SQL-user federation and DB Console policies are separately configured.","supportingSources":[{"title":"BYOC organization and cluster boundary","url":"https://docs.cockroachlabs.com/docs/continuum/byoc-overview.md"}]}},"id":"cockroachdb-byoc","infrastructure":["servers"],"infrastructureNotes":"The database data plane runs as persistent compute and storage inside the customer account, while Cockroach Labs operates it through a separate control plane.","infrastructureReviewed":"2026-11-14","infrastructureSources":["https://www.cockroachlabs.com/blog/cockroachdb-byoc-available/"],"install":"Vendor-assisted BYOC onboarding using scoped cross-account cloud identity","installMethods":["vendor-assisted"],"kind":"platform","license":"Commercial CockroachDB BYOC service.","licenseModel":"commercial-only","licenseModelNotes":"This listing covers the commercial BYOC managed service, not source-code licensing for a separately self-hosted CockroachDB distribution. Cockroach Continuum packages BYOC as a Mission Critical deployment at $1,000 per vCPU per year; the public-preview Cluster Virtualization add-on is $200 per host-vCPU per year. Existing pre-Continuum organizations retain current pricing and support until a migration path is available.","licenseModelSources":["https://www.cockroachlabs.com/product/cloud/bring-your-own-cloud/","https://www.cockroachlabs.com/cockroachdb/pricing/","https://www.cockroachlabs.com/blog/byoc-cockroach-continuum/"],"licenseReviewed":"2026-11-17","model":"BYOC","modelLabel":"Vendor-operated BYOC","name":"CockroachDB BYOC","notes":"This entry covers CockroachDB BYOC on Cockroach Continuum, not ordinary fully managed CockroachDB Cloud or customer-operated self-hosting. BYOC is a Mission Critical deployment in AWS, Azure, or Google Cloud, priced at $1,000 per vCPU per year, with premium support and 99.99% single-region or 99.999% multi-region SLAs. Cluster Virtualization is a $200 per host-vCPU per year public-preview add-on on AWS and Google Cloud; dedicated and virtual clusters are excluded from the availability SLA during preview. Existing BYOC organizations created before Continuum keep their current pricing and support until an account-team migration path is available. Invoice billing and per-organization enablement are required.","operationReview":{"controlPlane":"vendor-hosted","modelLabel":"Vendor-operated BYOC","operator":"vendor","reviewed":"2026-11-20","source":"https://www.cockroachlabs.com/product/cloud/bring-your-own-cloud/","summary":"Cockroach Labs handles provisioning, patching, backups and monitoring in the customer's cloud account. The customer supplies account access, network policy and cloud-resource governance.","supportingSources":[{"title":"BYOC service component locations","url":"https://www.cockroachlabs.com/cockroachdb-master-agreement/byoc/"}]},"operations":"Cockroach Labs manages database provisioning, upgrades, backups, monitoring and incidents; the customer owns the cloud account, network and billing boundary.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"CockroachDB Bring Your Own Cloud","url":"https://www.cockroachlabs.com/product/cloud/bring-your-own-cloud/"},{"title":"BYOC general availability and operating model","url":"https://www.cockroachlabs.com/blog/cockroachdb-byoc-available/"},{"title":"CockroachDB pricing","url":"https://www.cockroachlabs.com/cockroachdb/pricing/"},{"title":"CockroachDB BYOC on Continuum packaging and pricing","url":"https://www.cockroachlabs.com/blog/byoc-cockroach-continuum/"}],"url":"https://launchinyourcloud.com/directory/cockroachdb-byoc/","website":"https://www.cockroachlabs.com/"},{"advisories":[{"action":"Confirm purchase eligibility, migration timing and any written exception before evaluation.","conditions":"Existing-customer status and the purchased product determine eligibility.","effectiveDate":"2029-03-28","id":"atlassian-data-center-retirement","listingIds":["jira-software-data-center","jira-service-management-data-center","confluence-data-center"],"reviewed":"2026-11-16","scope":"Jira Software, Jira Service Management and Confluence Data Center. Bitbucket is excluded from this retirement; exceptional extensions require Atlassian agreement.","source":"https://www.atlassian.com/licensing/data-center-end-of-life","summary":"Affected subscriptions become read-only on March 28, 2029. New customers lost purchase eligibility on March 30, 2026; existing customers have a different expansion window.","title":"Data Center purchase restrictions and 2029 retirement","type":"lifecycle"},{"action":"Patch every affected installation to its fixed supported branch. If delayed, restrict internet access and apply the vendor WAF or product-specific rewrite mitigation to all relevant nodes.","conditions":"An attacker needs the exact file name and path; directory enumeration is not provided. Sensitive files in the application root change the risk.","id":"atlassian-cve-2026-21589","listingIds":["jira-software-data-center","jira-service-management-data-center","confluence-data-center","bitbucket-data-center"],"reviewed":"2026-11-17","scope":"Jira Software: 9.12.40/10.3.26/11.3.12; JSM: 5.12.40/10.3.26/11.3.12; Confluence: 9.2.26/10.2.19; Bitbucket: 9.4.26/10.2.8/10.5.1. Versions before the appropriate branch fix are affected.","source":"https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html","summary":"CVE-2026-21589 allows access to specifically named files under the web application root; Atlassian assigns critical severity.","title":"Atlassian Data Center unauthenticated file access","type":"security-advisory"},{"action":"Install a fixed supported release, or disable Remote API and verify HTTP 403 from the documented SOAP Axis endpoint.","conditions":"Requires Remote API (XML-RPC and SOAP). Disabling it can break scripts, automation and add-ons.","id":"confluence-cve-2026-90436","listingIds":["confluence-data-center"],"reviewed":"2026-11-17","scope":"Confluence Data Center 1.x–9.x before the applicable fix; 9.2.28 is the listed fixed LTS release. Confluence 10.x and later are unaffected.","source":"https://confluence.atlassian.com/security/cve-2026-90436-remote-code-execution-in-confluence-data-center-1874560038.html","summary":"CVE-2026-90436 is an unauthenticated code-execution issue when the affected Remote API is enabled.","title":"Confluence Remote API code-execution advisory","type":"security-advisory"},{"action":"Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility.","conditions":"Installed product, branch, bundled dependency, and Marketplace app compatibility determine applicability.","id":"atlassian-data-center-november-17-2026-bulletin","listingIds":["jira-software-data-center","confluence-data-center","bitbucket-data-center","jira-service-management-data-center"],"reviewed":"2026-11-18","scope":"Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.","source":"https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html","summary":"Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context.","title":"Atlassian Data Center November 17, 2026 bulletin","type":"security-advisory"}],"architecture":"Single-node or clustered Confluence and optional Synchrony services with an external database, load balancer, shared home and local indexes","categories":["collaboration","content-management"],"category":"Collaboration","categoryFit":{"collaboration":"Provides self-managed team workspaces, collaborative authoring and enterprise knowledge sharing.","content-management":"Manages structured spaces, pages, attachments, templates and governed enterprise knowledge content."},"cloudEvidence":[{"applicableVersions":["11.0; use the current compatibility matrix for other releases"],"clouds":["aws","azure","gcp"],"notes":"Atlassian documents Confluence Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments. The linked page applies to Confluence Data Center 11.0; select a Helm chart compatible with the installed product release.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Confluence Data Center on EKS, AKS or GKE","url":"https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html","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 self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.","diligence":{"compliance":{"reviewed":"2026-11-16","scope":"Vendor reports versus this self-managed Data Center installation","source":"https://www.atlassian.com/trust/compliance/resources/soc2","status":"inconclusive","summary":"Atlassian’s public SOC 2 page points to product reports, but does not establish the customer-operated Data Center boundary or report validity. Review the actual report before claiming coverage."},"footprint":{"reviewed":"2026-11-16","scope":"Clustered Confluence Data Center node guideline; not an installation-wide total","source":"https://confluence.atlassian.com/enterprise/confluence-data-center-technical-overview-612959401.html","status":"documented","summary":"The Data Center technical overview recommends at least 10 GB RAM per Confluence node, including operating-system, JVM, external-process and Synchrony allocations. Database, shared storage, node count and any separate Synchrony cluster require additional planning."},"iac":{"artifactRef":"main (moving branch; select product-compatible chart and application release)","artifactUrl":"https://github.com/atlassian/data-center-helm-charts","reviewed":"2026-11-16","scope":"Confluence Data Center; existing-customer eligibility and lifecycle conditions apply","source":"https://confluence.atlassian.com/doc/installing-confluence-data-center-203603.html","status":"documented","summary":"Atlassian publishes product-specific Data Center Helm charts. Select a chart and application version supported for this product and configure its database, persistent storage, ingress and license; one product’s chart does not establish compatibility for another."},"licensePricing":{"reviewed":"2026-11-16","scope":"Confluence Data Center: software license terms; infrastructure and operating costs are separate","source":"https://www.atlassian.com/licensing/data-center","status":"documented","summary":"New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies.","supportingSources":[{"title":"Edition and license conditions","url":"https://www.atlassian.com/licensing/data-center-end-of-life"}]},"release":{"releasePublishedOn":"2026-11-03","releaseTag":"11.0.1","reviewed":"2026-11-16","scope":"Vendor current-download feed; publication day only, with no invented release time","source":"https://my.atlassian.com/download/feeds/current/confluence.json","status":"documented","summary":"Atlassian’s current-download feed lists 11.0.1, released 2026-11-03. This is the reviewed download snapshot, not a guarantee that every other release branch, Helm chart, app or upgrade path is compatible. Existing-customer and lifecycle restrictions still apply.","supportingSources":[{"title":"Vendor release notes","url":"https://confluence.atlassian.com/display/DOC/Confluence+11.0+Release+Notes"}]},"scim":{"reviewed":"2026-11-16","scope":"Native Data Center cloud-IdP integration described by Atlassian; not an assessment of every Marketplace add-on","source":"https://confluence.atlassian.com/enterprise/manage-users-between-cloud-and-data-center-products-1085188069.html","status":"documented","summary":"Atlassian’s native cloud-IdP scenario uses login-time JIT provisioning for Data Center, without regular synchronization or de-provisioning. Its cloud SCIM path is different; third-party Data Center provisioning apps require separate review."},"securityControls":{"reviewed":"2026-11-18","scope":"Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.","source":"https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html","status":"documented","summary":"Current advisory review: Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility.","supportingSources":[]},"sso":{"availability":"available","reviewed":"2026-11-16","scope":"Confluence 7.12+ Data Center SSO feature baseline; existing-customer lifecycle restrictions remain","source":"https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html","status":"documented","summary":"Atlassian documents SAML 2.0 and OIDC through its Data Center SSO app. Match app compatibility to Confluence 7.12+; authentication does not assign application access or permissions.","supportingSources":[{"title":"OIDC product/version scope","url":"https://confluence.atlassian.com/enterprise/openid-connect-for-atlassian-data-center-applications-987142159.html"}]}},"id":"confluence-data-center","infrastructure":["servers"],"infrastructureNotes":"Confluence Data Center runs persistent application and collaborative-editing services with durable database, shared-home and local-index storage.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://confluence.atlassian.com/doc/installing-confluence-data-center-203603.html","https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html"],"install":"Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based single-node and clustered installation","installMethods":["helm","kubernetes","package"],"kind":"product","license":"Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029.","licenseModel":"commercial-only","licenseModelNotes":"New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies.","licenseModelSources":["https://www.atlassian.com/licensing/data-center","https://www.atlassian.com/licensing/data-center-end-of-life"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"Confluence Data Center","notes":"This entry covers Confluence Data Center, not Confluence Cloud. Atlassian supports its Kubernetes Helm chart and documents EKS, AKS and GKE as managed cluster options. The older AWS Quick Start and Azure Resource Manager templates are no longer supported or maintained. Atlassian states that affected Data Center subscriptions and associated Marketplace apps expire on March 28, 2029, after which the applications become read-only; evaluate the migration timeline before a new deployment. New customers cannot purchase this Data Center subscription after March 30, 2026. The remaining purchase/expansion window through March 30, 2028 is for existing Data Center customers; do not treat this listing as an unrestricted new-customer offering. Atlassian rates CVE-2026-21589 critical (9.3). Upgrade to Confluence 9.2.26, 10.2.19, or a later fixed release to prevent unauthenticated access to specifically named files under the web application root. Separately, CVE-2026-90436 is a critical unauthenticated remote-code-execution issue in Confluence 1.x–9.x when Remote API (XML-RPC and SOAP) is enabled. Upgrade to 9.2.28 or a later fixed release, or disable the remote API and verify that the Axis endpoint returns HTTP 403; Confluence 10.x and later are unaffected by the RCE. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.","operations":"Customer manages Kubernetes or hosts, the database, shared and local storage, Synchrony, load balancing, networking, TLS, identity, Marketplace apps, backups, monitoring and upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Install Confluence Data Center 11.0","url":"https://confluence.atlassian.com/doc/installing-confluence-data-center-203603.html"},{"title":"Run Confluence Data Center on Kubernetes","url":"https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html"},{"title":"Confluence Data Center supported platforms","url":"https://confluence.atlassian.com/doc/supported-platforms-207488198.html"},{"title":"Atlassian Data Center licensing and end of life","url":"https://www.atlassian.com/licensing/data-center"},{"title":"Atlassian product-specific end-of-life and purchase eligibility","url":"https://www.atlassian.com/licensing/data-center-end-of-life"},{"title":"Atlassian CVE-2026-21589 critical file-access advisory","url":"https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html"},{"title":"Atlassian CVE-2026-90436 Confluence RCE advisory","url":"https://confluence.atlassian.com/security/cve-2026-90436-remote-code-execution-in-confluence-data-center-1874560038.html"},{"title":"Atlassian security bulletin — November 17, 2026","url":"https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html"}],"url":"https://launchinyourcloud.com/directory/confluence-data-center/","website":"https://www.atlassian.com/software/confluence/enterprise"},{"advisories":[{"action":"Use each advisory to choose the patched branch and compatible CFK/components. Until patched, remove the separate Connect admin.listeners setting.","conditions":"Kafka Connect admin.listeners creates a separate affected administrative surface. ZooKeeper fixes apply only to the vendor-identified 7.x lines; do not transfer these claims to Confluent Cloud.","id":"confluent-november-2026-security-review","listingIds":["confluent-platform-self-managed"],"reviewed":"2026-11-17","scope":"Confluent Platform fixes: 7.6.15, 7.7.13, 7.8.12, 7.9.11, 8.0.9, 8.1.7, 8.2.5, 8.3.3 or 8.4.1, as applicable to each advisory. CFK/operator versions are separate.","source":"https://support.confluent.io/hc/en-us/sections/360008413952-Security-Advisories-and-Security-Release-Notes","summary":"Vendor advisories cover broker/Connect, CA trust, JWT, ZooKeeper and denial-of-service issues; component conditions vary.","supportingSources":[{"title":"Compromised CA trust remediation","url":"https://support.confluent.io/hc/en-us/articles/55611336006292-CONFSA-2026-33-CVE-2026-114820-CVE-2026-114406-Confluent-Platform-Compromised-eMudhra-Certificate-Authority-Roots-and-intermediates"},{"title":"Connect administrative listener mitigation","url":"https://support.confluent.io/hc/en-us/articles/55610452168340-CONFSA-2026-27-CVE-2026-115644-Confluent-Platform-Missing-Access-Control-Unauthenticated-Access-to-Kafka-Connect-Logging-API"}],"title":"Confluent Platform November security patches","type":"security-advisory"},{"action":"Apply -XX:-UseBASE64Intrinsics, restart and verify every affected Java process until a fixed vendor image or JDK is deployed.","conditions":"Package/archive installs inherit the customer JDK; Docker applicability depends on the image and tag.","disclosedOn":"2026-11-19","id":"confluent-confsa-2026-37-java4shell","listingIds":["confluent-platform-self-managed"],"reviewed":"2026-11-19","scope":"Confluent Platform 7.6.x–8.4.x, Control Center 2.0.x–2.7.x and the exact additional image ranges in the advisory.","source":"https://support.confluent.io/hc/en-us/articles/55810725278740-CONFSA-2026-37-CVE-2026-114938-Confluent-Cloud-and-Confluent-Platform-OpenJDK-vulnerability-Java4Shell","summary":"CONFSA-2026-37 covers CVE-2026-114938 in customer-JDK installs and multiple Confluent Docker-image ranges.","title":"Confluent CONFSA-2026-37 Java4Shell guidance","type":"security-advisory"}],"architecture":"CFK operator managing persistent Kafka, KRaft, Schema Registry, Connect, ksqlDB and other selected Confluent Platform services in a customer Kubernetes cluster","categories":["streaming"],"category":"Streaming","categoryFit":{"streaming":"Runs Apache Kafka brokers together with schema, connector and stream-processing services for customer-operated event streaming."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"The current CFK multi-region guide explicitly identifies Google Kubernetes Engine, Amazon Elastic Kubernetes Service and Azure Kubernetes Service for provider-specific configuration and validation. The CFK overview defines the product as managing self-managed Confluent Platform in the customer's own Kubernetes environment. This evidence does not include the separately operated Confluent Cloud service.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Confluent for Kubernetes guidance for EKS, AKS and GKE","url":"https://docs.confluent.io/operator/current/co-multi-region.html","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":"Self-managed event streaming platform deployed to customer-operated Kubernetes with Confluent for Kubernetes.","diligence":{"airGap":{"reviewed":"2026-11-16","scope":"CFK private-registry installation mechanics; full disconnected operation remains unresolved","source":"https://docs.confluent.io/operator/current/co-custom-registry.html","status":"inconclusive","summary":"CFK documents copying the required tagged Platform/operator/init-container images into a private registry and configuring pulls from it. This establishes private image delivery, but the reviewed guide does not establish end-to-end offline licensing, dependencies or updates for the selected stack."},"compliance":{"reviewed":"2026-11-16","scope":"Vendor security-controls report availability and deployment configuration; actual attestation scope unresolved","source":"https://docs.confluent.io/platform/current/security/compliance/overview.html","status":"inconclusive","summary":"The Platform guide says Confluent’s annual SOC 2 report is available on request. It does not supply the current report period or customer-environment scope; its separate FIPS configuration guidance must not be treated as a whole-deployment attestation."},"footprint":{"reviewed":"2026-11-16","scope":"CFK minimum cluster planning; not aggregate production sizing or pre-8.0 ZooKeeper guidance","source":"https://docs.confluent.io/operator/current/co-plan-sizing.html","status":"documented","summary":"The current CFK guide starts with three Kafka brokers and three KRaft controllers. Each broker’s minimum is 4 CPUs, 16 GB RAM and 1 TB disk; the production column is larger. Controllers and other components add resources."},"iac":{"artifactRef":"moving Helm repository index; select compatible chart version","artifactUrl":"https://packages.confluent.io/helm/index.yaml","reviewed":"2026-11-16","scope":"Confluent for Kubernetes deployment; commercial subscription applies","source":"https://docs.confluent.io/operator/current/co-deploy-operator.html","status":"documented","summary":"The CFK guide installs confluent-for-kubernetes from Confluent’s Helm repository, then manages Platform components through custom resources. The repository index moves; select a CFK/chart release compatible with the Platform components and Kubernetes version."},"licensePricing":{"reviewed":"2026-11-16","scope":"Confluent Platform Self-Managed: software license terms; infrastructure and operating costs are separate","source":"https://docs.confluent.io/platform/current/installation/license.html","status":"documented","summary":"This entry specifically covers deployment through Confluent for Kubernetes. Confluent states that deploying with CFK requires a subscription and applies licensing requirements to every Confluent Platform component in that cluster. Some components can use Apache 2.0 or Confluent Community licenses outside this CFK path, but that does not make the selected CFK deployment an open-source offering.","supportingSources":[]},"release":{"reviewed":"2026-11-16","scope":"CFK 3.4 release-line/support and component compatibility; not a claim about the newest Platform patch","source":"https://docs.confluent.io/operator/current/co-supported-environments.html","status":"documented","summary":"The reviewed compatibility matrix dates CFK 3.4.x to 2026-10-28, with standard support through 2028-10-28. It supports Platform 7.6.x–8.4.x and lists separate Control Center and Kubernetes ranges. The operator, init container and Platform have distinct versions; do not use a Platform patch number as the chart/operator version."},"securityControls":{"reviewed":"2026-11-19","scope":"Confluent Platform 7.6.x–8.4.x, Control Center 2.0.x–2.7.x and the exact Docker-image ranges in CONFSA-2026-37","source":"https://support.confluent.io/hc/en-us/articles/55810725278740-CONFSA-2026-37-CVE-2026-114938-Confluent-Cloud-and-Confluent-Platform-OpenJDK-vulnerability-Java4Shell","status":"documented","summary":"CFK telemetry is disabled by default; enabling Health+ sends service metadata to Confluent. The built-in JMX Prometheus exporter lacks authentication/encryption and cannot be disabled through CFK, so restrict access at the network boundary and configure other security surfaces separately. Current review: CONFSA-2026-37 covers CVE-2026-114938 in package/archive installs using affected customer JDKs and in the advisory's Platform, Control Center, CMF, Flink, operator, Gateway and CFK init-container image ranges. Fixed-runtime releases were still in preparation. Apply -XX:-UseBASE64Intrinsics, restart and verify every affected Java process until a fixed vendor image or JDK is deployed.","supportingSources":[{"title":"Prior security-controls source","url":"https://docs.confluent.io/operator/current/co-monitor-cp.html"}]},"sso":{"availability":"available","reviewed":"2026-11-16","scope":"Confluent Platform Control Center OIDC; requires the relevant licensed components","source":"https://docs.confluent.io/platform/current/security/authentication/sso-for-c3/overview.html","status":"documented","summary":"Control Center supports OIDC SSO and automated configuration through CFK. The guide says IdP refresh-token rotation must be disabled for this integration. This is self-managed Control Center authentication, distinct from Confluent Cloud SAML."}},"id":"confluent-platform-self-managed","infrastructure":["servers"],"infrastructureNotes":"CFK deploys long-running stateful brokers, controllers and supporting services on customer Kubernetes worker nodes with persistent storage. Using a managed Kubernetes control plane does not make the Confluent Platform application runtime serverless.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://docs.confluent.io/operator/current/overview.html","https://docs.confluent.io/operator/current/co-supported-environments.html","https://docs.confluent.io/operator/current/co-deploy-operator.html"],"install":"Install the Confluent for Kubernetes operator with Helm, then deploy Confluent Platform components through Kubernetes custom resources.","installMethods":["helm","kubernetes"],"kind":"product","license":"A commercial Confluent subscription is required for Confluent Platform components deployed with CFK; component licenses otherwise vary.","licenseModel":"commercial-only","licenseModelNotes":"This entry specifically covers deployment through Confluent for Kubernetes. Confluent states that deploying with CFK requires a subscription and applies licensing requirements to every Confluent Platform component in that cluster. Some components can use Apache 2.0 or Confluent Community licenses outside this CFK path, but that does not make the selected CFK deployment an open-source offering.","licenseModelSources":["https://docs.confluent.io/platform/current/installation/license.html"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"Confluent Platform Self-Managed","notes":"This entry covers self-managed Confluent Platform deployed with Confluent for Kubernetes, not Confluent Cloud. Current CFK guidance explicitly addresses Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine. Provider examples do not certify every Kubernetes, Confluent Platform or topology combination; use the current supported-environments matrix and validate cross-cluster networking, storage, security, version compatibility and subscription terms. Confluent's November 2026 security releases address multiple broker, Kafka Connect, ZooKeeper, TLS trust, JWT, file-read, and denial-of-service issues. Upgrade to the latest patched release for the deployed branch: 7.6.15, 7.7.13, 7.8.12, 7.9.11, 8.0.9, 8.1.7, 8.2.5, 8.3.3, or 8.4.1. Until patched, deployments using a separate Kafka Connect administrative listener should remove admin.listeners; the ZooKeeper fix applies to the affected 7.x lines identified by Confluent. CONFSA-2026-37 covers CVE-2026-114938 in Confluent Platform 7.6.x–8.4.x and Control Center 2.0.x–2.7.x when package/archive installs use affected customer JDKs, plus specified Docker-image ranges. Fixed-runtime releases were still being prepared at review time. Apply -XX:-UseBASE64Intrinsics to every affected Java process, restart and verify the flag until the applicable fixed image or runtime is available.","operations":"Customer manages Kubernetes clusters, node pools, persistent storage, load balancers, DNS and routing, identity and RBAC, secrets, backups, scaling and upgrades; CFK reconciles the declared Confluent application resources.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Confluent for Kubernetes overview","url":"https://docs.confluent.io/operator/current/overview.html"},{"title":"Deploy Confluent for Kubernetes","url":"https://docs.confluent.io/operator/current/co-deploy-operator.html"},{"title":"Supported environments and versions","url":"https://docs.confluent.io/operator/current/co-supported-environments.html"},{"title":"CFK multi-region deployment guidance","url":"https://docs.confluent.io/operator/current/co-multi-region.html"},{"title":"Confluent Platform licensing","url":"https://docs.confluent.io/platform/current/installation/license.html"},{"title":"Confluent November 2026 security advisories and patched releases","url":"https://support.confluent.io/hc/en-us/sections/360008413952-Security-Advisories-and-Security-Release-Notes"},{"title":"Confluent compromised CA trust advisory","url":"https://support.confluent.io/hc/en-us/articles/55611336006292-CONFSA-2026-33-CVE-2026-114820-CVE-2026-114406-Confluent-Platform-Compromised-eMudhra-Certificate-Authority-Roots-and-intermediates"},{"title":"Confluent Kafka Connect administrative-listener advisory","url":"https://support.confluent.io/hc/en-us/articles/55610452168340-CONFSA-2026-27-CVE-2026-115644-Confluent-Platform-Missing-Access-Control-Unauthenticated-Access-to-Kafka-Connect-Logging-API"},{"title":"CONFSA-2026-37 Java4Shell advisory","url":"https://support.confluent.io/hc/en-us/articles/55810725278740-CONFSA-2026-37-CVE-2026-114938-Confluent-Cloud-and-Confluent-Platform-OpenJDK-vulnerability-Java4Shell"}],"url":"https://launchinyourcloud.com/directory/confluent-platform-self-managed/","website":"https://www.confluent.io/product/confluent-platform/"},{"architecture":"Customer-operated Coroot server and agents. ClickHouse stores logs, traces and profiles, and metrics can use ClickHouse or Prometheus.","categories":["observability"],"category":"Observability","categoryFit":{"observability":"Node and cluster agents collect operational telemetry for application monitoring and troubleshooting."},"cloudEvidence":[{"clouds":["aws"],"notes":"The vendor explicitly names EKS as a supported Kubernetes environment. Use the linked Community Helm instructions to deploy the operator, server and agents. The vendor specifies basic support for Fargate.","reviewed":"2026-11-20","sourceType":"vendor-documentation","title":"Coroot on Amazon EKS","url":"https://docs.coroot.com/installation/requirements/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The vendor explicitly names AKS among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster, subject to privileges and Linux requirements.","reviewed":"2026-11-20","sourceType":"vendor-documentation","title":"Coroot on Azure AKS","url":"https://docs.coroot.com/installation/requirements/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The vendor explicitly names GKE among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster.","reviewed":"2026-11-20","sourceType":"vendor-documentation","title":"Coroot on Google GKE","url":"https://docs.coroot.com/installation/requirements/","vendorSupport":"not-assessed"},{"clouds":["oci"],"notes":"The vendor explicitly names OKE among supported Kubernetes environments. The Community Helm guide installs the server and agents on the customer's cluster.","reviewed":"2026-11-20","sourceType":"vendor-documentation","title":"Coroot on Oracle OKE","url":"https://docs.coroot.com/installation/requirements/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-20","clouds":["aws","azure","gcp","oci"],"communityAcceptance":{"reviewed":"2026-11-20","sources":[{"title":"Public contributor history","url":"https://github.com/coroot/coroot/graphs/contributors"},{"title":"Reviewed dated upstream release","url":"https://github.com/coroot/coroot/releases/tag/v1.29.4"}],"summary":"The upstream project has sustained public contributor history (including def, apetruhin, Split174) and a reviewed dated v1.29.4 release. This establishes maintenance/community participation rather than a production suitability, support 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"},{"boundary":"cloud-account","cloud":"oci","controlPlane":"not-assessed","evidence":[3],"operator":"customer"}],"description":"Self-hosted application observability with service maps, logs, metrics, traces and continuous profiling.","diligence":{"airGap":{"reviewed":"2026-11-20","scope":"Coroot Community Edition: reviewed customer-cloud deployment","source":"https://docs.coroot.com/installation/kubernetes/","status":"inconclusive","summary":"The reviewed sources do not establish a complete disconnected installation, update and licensing workflow. A telemetry opt-out alone does not establish air-gapped support; review registry, package, identity and optional external-service dependencies."},"commitments":{"reviewed":"2026-11-20","scope":"Coroot Community Edition: reviewed customer-cloud deployment","source":"https://docs.coroot.com/installation/kubernetes/","status":"inconclusive","summary":"No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately."},"compliance":{"reviewed":"2026-11-20","scope":"Coroot Community Edition: reviewed customer-cloud deployment","source":"https://docs.coroot.com/installation/kubernetes/","status":"inconclusive","summary":"No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities."},"cost":{"reviewed":"2026-11-20","scope":"Coroot Community Edition: reviewed customer-cloud deployment","source":"https://docs.coroot.com/installation/kubernetes/","status":"inconclusive","summary":"No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend."},"footprint":{"reviewed":"2026-11-20","scope":"Chart-specific storage and operator request baseline; server/agent/database sizing remains workload-dependent","source":"https://github.com/coroot/helm-charts/releases/download/coroot-ce-0.3.3/coroot-ce-0.3.3.tgz","status":"documented","summary":"The inspected Community chart defaults to 10 GiB Coroot storage, 10 GiB Prometheus storage and 100 GiB per ClickHouse instance. Its default ClickHouse layout is one shard/replica; the installation guide overrides this to two shards and two replicas. Operator requests are 100m CPU/64 MiB. These are component defaults, not total cluster CPU/RAM minima or an HA capacity guarantee.","supportingSources":[{"title":"Separate operator requests","url":"https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz"},{"title":"Installation layout and replica override","url":"https://docs.coroot.com/installation/kubernetes/"},{"title":"Kernel and orchestrator prerequisites","url":"https://docs.coroot.com/installation/requirements/"}]},"iac":{"artifactRef":"coroot-ce 0.3.3; sha256:e6213b27a4e73924d2fe03c12aa815ebd8ec806436c3a5ab9bd4a8801c18e6f3; operator chart 0.10.8 / operator 1.10.8","artifactUrl":"https://github.com/coroot/helm-charts/releases/download/coroot-ce-0.3.3/coroot-ce-0.3.3.tgz","availability":"available","reviewed":"2026-11-20","scope":"Community custom resource plus separately versioned operator and component images","source":"https://docs.coroot.com/installation/kubernetes/","status":"documented","summary":"The inspected coroot-ce 0.3.3 chart creates a Community custom resource and requires a separately installed operator; the reviewed operator chart is 0.10.8 (operator application 1.10.8). Neither chart version identifies the Coroot server release. Pin server, node-agent and cluster-agent images to prevent the documented automatic upgrades.","supportingSources":[{"title":"Operator package","url":"https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz"},{"title":"Published chart index","url":"https://coroot.github.io/helm-charts/index.yaml"}]},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream Community code; excludes Enterprise subscriptions","source":"https://github.com/coroot/coroot/blob/v1.29.4/LICENSE","status":"documented","summary":"Coroot Community v1.29.4 is licensed under Apache-2.0. This establishes the software licence rather than a per-seat subscription; Enterprise features/support, dependencies and infrastructure have separate costs."},"marketplace":{"reviewed":"2026-11-20","scope":"Coroot Community Edition: reviewed customer-cloud deployment","source":"https://docs.coroot.com/installation/kubernetes/","status":"inconclusive","summary":"The reviewed edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient."},"release":{"releasePublishedAt":"2026-11-18T17:14:42Z","releaseTag":"v1.29.4","reviewed":"2026-11-20","scope":"Upstream Community server release","source":"https://github.com/coroot/coroot/releases/tag/v1.29.4","status":"documented","summary":"The reviewed Coroot Community server snapshot is v1.29.4, published November 18, 2026. Operator, server, agents and charts are independently versioned; this snapshot does not guarantee support or pin the complete installation."},"scim":{"reviewed":"2026-11-20","scope":"Coroot Community Edition: reviewed customer-cloud deployment","source":"https://docs.coroot.com/installation/kubernetes/","status":"inconclusive","summary":"The reviewed sources do not establish a SCIM endpoint and supported user/group lifecycle for this edition. SSO and just-in-time account creation are not SCIM evidence."},"securityControls":{"reviewed":"2026-11-20","scope":"Configured Community access controls and privileged collector/operator boundary","source":"https://docs.coroot.com/configuration/authentication/","status":"documented","summary":"Community provides local-user authentication, three predefined roles and API-key service accounts. Set the initial admin password before exposure and review anonymous-mode settings. Node agents need privileged eBPF/host access; review the operator ClusterRole and its optional restriction on global secret access.","supportingSources":[{"title":"Node-agent privilege requirements","url":"https://docs.coroot.com/installation/kubernetes/"},{"title":"Inspected operator permissions/configuration","url":"https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz"}]},"sso":{"availability":"unavailable","reviewed":"2026-11-20","scope":"Native Coroot Community authentication; Enterprise is a separate edition","source":"https://docs.coroot.com/configuration/authentication/","status":"documented","summary":"The authentication guide explicitly reserves native SAML/OIDC single sign-on for Coroot Enterprise. Community has local users with Admin, Editor and Viewer roles. An external authentication proxy would be a separate configuration, not native Community SSO."}},"id":"coroot-community","infrastructure":["servers"],"infrastructureNotes":"Coroot and its agents run as Kubernetes workloads. Cluster node agents use eBPF and require compatible Linux kernels and privileged access.","infrastructureReviewed":"2026-11-20","infrastructureSources":["https://docs.coroot.com/installation/kubernetes/","https://docs.coroot.com/installation/architecture/"],"install":"Install the Coroot Operator and Community Edition Helm chart on the customer's Kubernetes cluster.","installMethods":["helm"],"kind":"product","license":"Apache License 2.0 for Coroot Community Edition. Enterprise Edition has separate subscription terms.","licenseModel":"open-source","licenseModelNotes":"Apache-2.0 applies to the published Community code. The Kubernetes guide identifies the separate licensed Enterprise chart.","licenseModelSources":["https://github.com/coroot/coroot/blob/main/LICENSE","https://docs.coroot.com/installation/kubernetes/"],"licenseReviewed":"2026-11-20","model":"Fully in your account","modelLabel":"Customer-operated","name":"Coroot Community Edition","notes":"The node agent requires privileged access for eBPF and host inspection, and upstream describes AWS Fargate support as basic. Anonymous usage statistics are enabled by default and can be disabled. The operator updates unpinned Coroot component images automatically. Native SAML/OIDC SSO is Enterprise-only. The Coroot server v1.29.4, Community chart 0.3.3 and operator chart 0.10.8 are separate version tracks; inspect and pin each required image.","operations":"The customer manages the operator, image versions, privileged node-agent permissions, storage capacity, telemetry retention, backup and recovery, and access to the UI.","publisher":false,"reviewed":"2026-11-20","sources":[{"title":"Community Helm installation and operating requirements","url":"https://docs.coroot.com/installation/kubernetes/"},{"title":"Supported orchestrators and Linux requirements","url":"https://docs.coroot.com/installation/requirements/"},{"title":"Coroot assembly and telemetry flow","url":"https://docs.coroot.com/installation/architecture/"},{"title":"ClickHouse storage and retention","url":"https://docs.coroot.com/configuration/clickhouse/"},{"title":"Apache-2.0 license","url":"https://github.com/coroot/coroot/blob/main/LICENSE"},{"title":"Upstream release history","url":"https://github.com/coroot/coroot/releases"},{"title":"Usage statistics and opt-out","url":"https://docs.coroot.com/misc/anonymous-usage-statistics/"},{"title":"Operator package","url":"https://github.com/coroot/helm-charts/releases/download/coroot-operator-0.10.8/coroot-operator-0.10.8.tgz"},{"title":"Published chart index","url":"https://coroot.github.io/helm-charts/index.yaml"},{"title":"Buyer evidence: sso","url":"https://docs.coroot.com/configuration/authentication/"},{"title":"Buyer evidence: footprint","url":"https://github.com/coroot/helm-charts/releases/download/coroot-ce-0.3.3/coroot-ce-0.3.3.tgz"},{"title":"Buyer evidence: licensePricing","url":"https://github.com/coroot/coroot/blob/v1.29.4/LICENSE"},{"title":"Buyer evidence: release","url":"https://github.com/coroot/coroot/releases/tag/v1.29.4"},{"title":"Public contributor history","url":"https://github.com/coroot/coroot/graphs/contributors"}],"url":"https://launchinyourcloud.com/directory/coroot-community/","website":"https://coroot.com/"},{"architecture":"Customer-operated Couchbase Server pods, Kubernetes Operator, services and persistent volumes","categories":["databases-vector"],"category":"Databases \u0026 vector","categoryFit":{"databases-vector":"Distributed NoSQL database deployed and lifecycle-managed in customer-controlled Kubernetes clusters."},"cloudEvidence":[{"applicableEdition":"Enterprise Edition","applicableVersions":["Server 7.2 through 8.0 in the reviewed compatibility matrix"],"clouds":["aws","azure","gcp"],"notes":"Couchbase states that the Operator deploys and manages Server Enterprise Edition and is certified for Amazon EKS, Microsoft AKS and Google GKE. Database pods, services and storage run in the customer's cluster; this is not Couchbase Capella.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Couchbase Server Enterprise on EKS, AKS and GKE","url":"https://docs.couchbase.com/operator/current/overview.html","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":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Self-managed distributed NoSQL database deployed in customer-controlled Kubernetes with the Couchbase Operator.","diligence":{"airGap":{"reviewed":"2026-11-19","scope":"Couchbase Server Enterprise Edition: selected customer-operated edition","source":"https://docs.couchbase.com/operator/current/overview.html","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":"Couchbase Server Enterprise Edition: selected customer-operated edition","source":"https://docs.couchbase.com/operator/current/overview.html","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":"Couchbase Server Enterprise Edition: selected customer-operated edition","source":"https://docs.couchbase.com/operator/current/overview.html","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":"Couchbase Server Enterprise Edition: selected customer-operated edition","source":"https://docs.couchbase.com/operator/current/overview.html","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-20","scope":"Couchbase Server 8.0 x86 per-node baseline; full service topology requires sizing","source":"https://docs.couchbase.com/server/current/install/pre-install.html","status":"documented","summary":"The current 8.0 x86 production floor is a 2-GHz two-core AVX2 CPU, 4 GiB physical RAM and 8 GiB block storage per node. The recommendation is four cores, at least 16 GiB RAM and SSDs. Each enabled service adds requirements; replicas, dataset/index size, backups and HA are additional."},"iac":{"artifactRef":"chart 2.94.0 / Operator 2.9.4; sha256:f08d9f62fa955964ab380129a5206a414a36495c370bcc245309607afcb38c2a","artifactUrl":"https://github.com/couchbase-partners/helm-charts/releases/download/couchbase-operator-2.94.0/couchbase-operator-2.94.0.tgz","availability":"available","reviewed":"2026-11-19","scope":"Public Helm deployment artifact for the Enterprise database; application licence and Server image remain separate","source":"https://docs.couchbase.com/operator/current/helm-setup-guide.html","status":"documented","summary":"The official Helm repository publishes couchbase-operator chart 2.94.0 for Operator 2.9.4. The downloaded chart matches its published SHA-256 digest. It can deploy the Operator, admission controller and a CouchbaseCluster; select a compatible licensed Server image and production values separately. Chart and Operator versions are not Couchbase Server release versions.","supportingSources":[{"title":"Official chart index and digest","url":"https://couchbase-partners.github.io/helm-charts/index.yaml"}]},"licensePricing":{"availability":"edition-dependent","reviewed":"2026-11-19","scope":"Couchbase Server Enterprise Edition: selected customer-operated edition","source":"https://production.docs.couchbase.com/server/current/introduction/editions.html","status":"documented","summary":"Couchbase Server Enterprise Edition requires a commercial subscription. Community Edition is a different product scope; obtain a quote covering the selected nodes, support and Operator use."},"marketplace":{"reviewed":"2026-11-19","scope":"Couchbase Server Enterprise Edition: selected customer-operated edition","source":"https://docs.couchbase.com/operator/current/overview.html","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":{"reviewed":"2026-11-19","scope":"Couchbase Server Enterprise Edition: selected customer-operated edition","source":"https://docs.couchbase.com/operator/current/prerequisite-and-setup.html","status":"documented","summary":"The current Operator compatibility material covers Couchbase Server Enterprise Edition 7.2 through 8.0. Compatibility is a matrix across Operator, Server and Kubernetes versions; pin the exact supported combination rather than treating the range as one release."},"scim":{"reviewed":"2026-11-19","scope":"Couchbase Server Enterprise Edition: selected customer-operated edition","source":"https://docs.couchbase.com/operator/current/overview.html","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":"Couchbase Server Enterprise Edition: selected customer-operated edition","source":"https://docs.couchbase.com/operator/current/prerequisite-and-setup.html","status":"documented","summary":"The Operator manages the Enterprise database inside the customer's Kubernetes boundary. The deployment still requires buyer configuration of TLS, authentication, network policy, storage encryption, backup and Kubernetes access controls."},"sso":{"availability":"available","reviewed":"2026-11-19","scope":"Couchbase Server Enterprise current 8.0-line Web Console; verify older Server and Operator combinations separately","source":"https://docs.couchbase.com/server/current/manage/manage-security/configure-saml.html","status":"documented","summary":"The current Enterprise Server Web Console supports SAML SSO, with tested Okta and Microsoft Azure AD/Entra ID integrations. Configure metadata, certificate validation, user/group/role mappings and NameID handling. This console authentication does not establish SAML authentication for application SDK or database data-plane clients."}},"id":"couchbase-server-enterprise","infrastructure":["servers"],"infrastructureNotes":"Couchbase Server runs as stateful pods with persistent volumes while the in-cluster Operator reconciles Couchbase resources and lifecycle actions.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://docs.couchbase.com/operator/current/concept-operator.html"],"install":"Couchbase Kubernetes Operator by Helm or downloaded package, then CouchbaseCluster resources for Enterprise Edition","installMethods":["helm","kubernetes"],"kind":"product","license":"Commercial subscription for Couchbase Server Enterprise Edition; Community Edition is separately licensed.","licenseModel":"commercial-only","licenseModelNotes":"This entry is limited to Enterprise Edition, which Couchbase documents as a commercial subscription. Community Edition is a separate licensing scope.","licenseModelSources":["https://production.docs.couchbase.com/server/current/introduction/editions.html"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Couchbase Server Enterprise Edition","notes":"The current Operator supports Couchbase Server Enterprise Edition 7.2 through 8.0 and is certified for Amazon EKS, Microsoft AKS and Google GKE. Couchbase Capella and Community Edition are outside this listing; verify the exact Operator, Server and Kubernetes compatibility matrix.","operations":"Customer manages Kubernetes, storage, networking, security, backups and upgrade policy; the Operator automates database lifecycle operations.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Couchbase Operator introduction and certified platforms","url":"https://docs.couchbase.com/operator/current/overview.html"},{"title":"Couchbase Operator prerequisites and supported versions","url":"https://docs.couchbase.com/operator/current/prerequisite-and-setup.html"},{"title":"Install Couchbase Operator on Kubernetes","url":"https://docs.couchbase.com/operator/current/install-kubernetes.html"},{"title":"Couchbase Server editions and licensing","url":"https://production.docs.couchbase.com/server/current/introduction/editions.html"},{"title":"Buyer evidence: sso","url":"https://docs.couchbase.com/server/current/manage/manage-security/configure-saml.html"},{"title":"Buyer evidence: iac","url":"https://docs.couchbase.com/operator/current/helm-setup-guide.html"},{"title":"Reviewed deployment artifact reference","url":"https://github.com/couchbase-partners/helm-charts/releases/download/couchbase-operator-2.94.0/couchbase-operator-2.94.0.tgz"},{"title":"Official chart index and digest","url":"https://couchbase-partners.github.io/helm-charts/index.yaml"}],"url":"https://launchinyourcloud.com/directory/couchbase-server-enterprise/","website":"https://www.couchbase.com/products/server/"},{"architecture":"Provider-specific CloudFormation or Terraform application stacks and evidence storage.","categories":["incident-investigation-management"],"category":"Incident \u0026 investigation management","categoryFit":{"incident-investigation-management":"Commercial customer-deployed cloud-forensics acquisition and investigation platform, formerly Cado Response."},"cloudEvidence":[{"clouds":["aws"],"notes":"Provider-specific CloudFormation or Terraform application stacks and evidence storage. Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"AWS CloudFormation","url":"https://docs.cadosecurity.com/cado/deploy/aws/cloudformation","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Provider-specific CloudFormation or Terraform application stacks and evidence storage. Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Azure Deploy","url":"https://docs.cadosecurity.com/cado/deploy/azure/azure-deploy","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Provider-specific CloudFormation or Terraform application stacks and evidence storage. Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"GCP Deploy","url":"https://docs.cadosecurity.com/cado/deploy/gcp/gcp-deploy","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 customer-deployed cloud-forensics acquisition and investigation platform, formerly Cado Response.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Customer-deployed Darktrace/Cado main-server recommendation; worker and evidence capacity separate","source":"https://docs.cadosecurity.com/cado/deploy/aws/cloudformation","status":"documented","summary":"The CloudFormation guide recommends m5.4xlarge as the enterprise minimum for the main EC2 server. Acquisition/processing workers, evidence volumes, network transfer and standby/recovery resources are additional. This is a vendor main-server recommendation, not a whole-system cost or HA workload guarantee."},"iac":{"artifactRef":"Current vendor CloudFormation guide reviewed on this date","artifactUrl":"https://docs.cadosecurity.com/cado/deploy/aws/cloudformation","reviewed":"2026-11-21","scope":"Vendor Cado/Darktrace customer-deployed AWS CloudFormation delivery","source":"https://docs.cadosecurity.com/cado/deploy/aws/cloudformation","status":"documented","summary":"The vendor supplies CloudFormation templates for public/private, existing-VPC and GovCloud deployment, with IAM/network parameters and sales/trial delivery access. Obtain the entitled template and licence, review permissions/TLS/storage, and choose the appropriate account/region topology."},"licensePricing":{"reviewed":"2026-11-19","scope":"Darktrace Forensic Acquisition and Investigation; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://docs.cadosecurity.com/cado/deploy/licenses","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-21","scope":"Darktrace customer-deployed Forensic Acquisition and Investigation; documented beta Okta SAML path","source":"https://docs.cadosecurity.com/cado/manage/users-authentication/sso/okta_saml","status":"documented","summary":"The customer-deployed guide documents an Okta SAML integration, explicitly marked beta, with application callback/audience and email/group mapping. It excludes SaaS deployments and points those to a different identity guide. Validate the selected release, beta suitability, IdP and administrator-group handling."}},"id":"cado-response","infrastructure":["servers"],"infrastructureNotes":"Provider-specific CloudFormation or Terraform application stacks and evidence storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://docs.cadosecurity.com/cado/deploy/aws/cloudformation","https://docs.cadosecurity.com/cado/deploy/azure/azure-deploy","https://docs.cadosecurity.com/cado/deploy/gcp/gcp-deploy"],"install":"CloudFormation; Terraform","installMethods":["cloudformation","terraform"],"kind":"product","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.cadosecurity.com/cado/deploy/licenses","https://www.darktrace.com/forensic-acquisition-investigation"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Darktrace Forensic Acquisition and Investigation","notes":"Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.","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 CloudFormation","url":"https://docs.cadosecurity.com/cado/deploy/aws/cloudformation"},{"title":"Azure Deploy","url":"https://docs.cadosecurity.com/cado/deploy/azure/azure-deploy"},{"title":"GCP Deploy","url":"https://docs.cadosecurity.com/cado/deploy/gcp/gcp-deploy"},{"title":"Licensing Docs","url":"https://docs.cadosecurity.com/cado/deploy/licenses"},{"title":"Product Page","url":"https://www.darktrace.com/forensic-acquisition-investigation"},{"title":"Darktrace News","url":"https://www.darktrace.com/news/darktrace-unveils-automated-forensics-capabilities-in-its-activeai-security-platform"}],"url":"https://launchinyourcloud.com/directory/cado-response/","website":"https://docs.cadosecurity.com/cado/deploy/aws/cloudformation"},{"architecture":"Vendor control plane; customer classic compute","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Data and AI platform with classic compute in your cloud environment."},"cloudEvidence":[{"clouds":["aws"],"notes":"The classic compute plane runs in the customer cloud account, subscription or project; Databricks operates its separate control plane. This badge describes classic compute, not serverless compute in a Databricks-managed account. Review the selected workspace networking, region and service terms.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Databricks classic compute architecture","url":"https://docs.databricks.com/aws/en/getting-started/high-level-architecture","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The classic compute plane runs in the customer cloud account, subscription or project; Databricks operates its separate control plane. This badge describes classic compute, not serverless compute in a Databricks-managed account. Review the selected workspace networking, region and service terms.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"Databricks classic compute architecture","url":"https://learn.microsoft.com/en-us/azure/databricks/getting-started/high-level-architecture","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The classic compute plane runs in the customer cloud account, subscription or project; Databricks operates its separate control plane. This badge describes classic compute, not serverless compute in a Databricks-managed account. Review the selected workspace networking, region and service terms.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Databricks classic compute architecture","url":"https://docs.databricks.com/gcp/en/security/network/concepts/architecture","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"vendor-hosted","evidence":[0],"operator":"shared"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"vendor-hosted","evidence":[1],"operator":"shared"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"vendor-hosted","evidence":[2],"operator":"shared"}],"description":"Data and AI platform with classic compute in your cloud environment.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Classic AWS compute sizing unresolved without workload and topology","source":"https://docs.databricks.com/aws/en/compute/configure","status":"inconclusive","summary":"The classic-compute guide requires selecting runtime, worker types, driver, autoscaling and policies for the workload. It does not establish one platform-wide CPU/RAM floor. Size the customer-account compute separately from Databricks-hosted control-plane and optional serverless services."},"iac":{"artifactRef":"Pin Databricks and cloud provider versions","artifactUrl":"https://github.com/databricks/terraform-provider-databricks","reviewed":"2026-11-20","scope":"Classic AWS workspace/infrastructure administration; serverless has a different boundary","source":"https://docs.databricks.com/aws/en/dev-tools/terraform/","status":"documented","summary":"The vendor-supported Terraform provider manages workspaces and administrative resources; AWS infrastructure is provisioned with the AWS provider. Databricks recommends Terraform for cloud/external resources and administrative actions, and Automation Bundles for jobs and pipelines. Select compatible provider versions and least-privilege credentials."},"licensePricing":{"reviewed":"2026-11-20","scope":"Databricks commercial usage model; no workload-specific quote or total cost","source":"https://www.databricks.com/product/pricing","status":"documented","summary":"Databricks publishes usage-based product pricing in DBUs with optional committed-use contracts. Rates depend on cloud, region, workload and product. Customer-account classic infrastructure can incur a separate cloud bill; obtain the selected product rate and contract rather than treating a starting DBU price as the whole deployment cost."},"scim":{"availability":"edition-dependent","reviewed":"2026-11-16","scope":"Databricks on AWS; Premium or above; not a statement about every cloud edition","source":"https://docs.databricks.com/aws/en/admin/users-groups/scim","status":"documented","summary":"Account-level SCIM user/group provisioning is documented with Premium or above. Identity federation is required for workspace assignment; workspace-level provisioning is legacy."},"sso":{"availability":"available","reviewed":"2026-11-14","scope":"Databricks AWS account/workspace identity; separate vendor-operated control plane","source":"https://docs.databricks.com/aws/en/security/auth/single-sign-on/","status":"documented","summary":"The AWS account/workspace login configuration supports SAML 2.0 or OpenID Connect. Unified-login and emergency-access settings must be planned for the account."}},"id":"databricks","infrastructure":["servers"],"infrastructureNotes":"Classic compute uses customer-cloud compute resources. Databricks serverless compute is a different vendor-managed deployment and is outside this listing.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.databricks.com/aws/en/compute/use-compute"],"install":"Cloud-specific workspace provisioning","installMethods":["vendor-assisted"],"kind":"platform","license":"Commercial","licenseModel":"commercial-only","licenseModelNotes":"This listing covers the commercially provided managed/BYOC service, not a separately licensed open-source engine or library.","licenseModelSources":["https://docs.databricks.com/aws/en/getting-started/high-level-architecture"],"licenseReviewed":"2026-11-10","model":"BYOC","modelLabel":"Shared operations · vendor control plane","name":"Databricks classic compute","notes":"This entry covers classic compute only. Serverless compute runs in a Databricks-managed environment and is outside this entry. Confirm the responsibility split and metadata flows for your cloud. Beginning November 18, 2026, new VARIANT tables created on Databricks Runtime 17.3 or later automatically use variantShredding. Databricks Runtime 15.4 cannot read or write those tables, so upgrade affected classic clusters to 16.4 or later before creating or accessing them.","operationReview":{"controlPlane":"vendor-hosted","modelLabel":"Shared operations · vendor control plane","operator":"shared","reviewed":"2026-11-20","source":"https://docs.databricks.com/aws/en/getting-started/high-level-architecture","summary":"Classic compute and workspace storage are in the customer cloud account. Databricks operates the separate management plane; the customer configures compute, networking and policy. Serverless compute is outside this listing."},"operations":"The vendor manages the control plane. Your team configures classic compute, cloud resources and policies.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"AWS architecture","url":"https://docs.databricks.com/aws/en/getting-started/high-level-architecture"},{"title":"Azure architecture","url":"https://learn.microsoft.com/en-us/azure/databricks/getting-started/high-level-architecture"},{"title":"Google Cloud architecture","url":"https://docs.databricks.com/gcp/en/security/network/concepts/architecture"},{"title":"Classic versus serverless compute","url":"https://docs.databricks.com/aws/en/compute/use-compute"},{"title":"Databricks upcoming behavior changes","url":"https://docs.databricks.com/aws/en/release-notes/whats-coming"}],"url":"https://launchinyourcloud.com/directory/databricks/","website":"https://www.databricks.com/"},{"advisories":[{"action":"Retain OrderedReady explicitly or follow the indexer StatefulSet migration. Keep gossip protocol 0 while older nodes remain, then apply the vendor-approved engine/Worker versions.","conditions":"Clusters running nodes older than engine v0.1.33 also need the documented gossip protocol compatibility setting during the transition.","id":"datadog-byoc-cloudprem-0-6-statefulset-migration","listingIds":["datadog-byoc-logs"],"reviewed":"2026-11-20","scope":"BYOC engine v0.1.36 packaged in cloudprem chart 0.6.0; chart and application versions are separate.","source":"https://docs.datadoghq.com/byoc-logs/release_notes/","summary":"Chart 0.6.0 defaults indexer podManagementPolicy to Parallel, an immutable StatefulSet field. Existing deployments need an override or the documented migration.","title":"Datadog BYOC chart 0.6.0 indexer policy transition","type":"lifecycle"}],"architecture":"Customer-operated Kubernetes engine and pipeline workers use object storage for log data and PostgreSQL for index metadata. Datadog hosts the UI and routes queries.","categories":["observability"],"category":"Observability","categoryFit":{"observability":"The customer-cloud Logs engine ingests, indexes, stores and queries operational logs. Datadog hosts the Log Explorer and pipeline configuration UI."},"cloudEvidence":[{"clouds":["aws"],"notes":"Vendor guide installs the engine in the customer's EKS cluster using S3 and PostgreSQL. Helm and the EKS-specific Datadog Operator are documented.","reviewed":"2026-11-20","sourceType":"vendor-documentation","title":"Datadog BYOC Logs on Amazon EKS","url":"https://docs.datadoghq.com/byoc-logs/install/aws_eks/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Vendor guide installs the engine into the customer's AKS cluster with Azure Blob Storage and PostgreSQL Flexible Server.","reviewed":"2026-11-20","sourceType":"vendor-documentation","title":"Datadog BYOC Logs on Azure AKS","url":"https://docs.datadoghq.com/byoc-logs/install/azure_aks/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Vendor guide installs the engine in the customer's Google Cloud project with GKE, Cloud Storage, PostgreSQL and Workload Identity.","reviewed":"2026-11-20","sourceType":"vendor-documentation","title":"Datadog BYOC Logs on Google GKE","url":"https://docs.datadoghq.com/byoc-logs/install/gcp_gke/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-20","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"vendor-hosted","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"vendor-hosted","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"vendor-hosted","evidence":[2],"operator":"customer"}],"description":"Datadog log processing, indexing and storage in the customer's cloud, with search through Datadog Log Explorer.","diligence":{"airGap":{"availability":"unavailable","reviewed":"2026-11-20","scope":"Complete documented Datadog BYOC Logs workflow, including hosted UI","source":"https://docs.datadoghq.com/byoc-logs/introduction/network/","status":"documented","summary":"The documented BYOC workflow depends on a connection to the hosted Datadog UI/control plane. Searchers maintain outbound connections by default, or Datadog connects through an optional ingress. This connected offering does not provide a documented fully disconnected mode."},"commitments":{"reviewed":"2026-11-20","scope":"Datadog BYOC Logs: reviewed customer-cloud deployment","source":"https://docs.datadoghq.com/byoc-logs/install/","status":"inconclusive","summary":"No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately."},"compliance":{"reviewed":"2026-11-20","scope":"Datadog BYOC Logs: reviewed customer-cloud deployment","source":"https://docs.datadoghq.com/byoc-logs/install/","status":"inconclusive","summary":"No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities."},"cost":{"reviewed":"2026-11-20","scope":"Datadog BYOC Logs: reviewed customer-cloud deployment","source":"https://docs.datadoghq.com/byoc-logs/install/","status":"inconclusive","summary":"No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend."},"footprint":{"reviewed":"2026-11-20","scope":"Vendor sizing model and assumptions; not a universal minimum or measured workload/cost estimate","source":"https://docs.datadoghq.com/byoc-logs/operate/sizing/","status":"documented","summary":"The sizing guide starts indexers at 2 vCPUs per TB/day, compactors at 1 vCPU per 2 TB/day and searchers near twice the indexer CPU, with query-driven adjustment. It separately sizes control services, Workers and PostgreSQL and recommends Multi-AZ database availability. Its 1 TB/day example assumes 30-day retention and roughly 6x compression; 1 TB stored is a different input."},"iac":{"artifactRef":"cloudprem 0.6.0 / engine v0.1.36; sha256:7cf894e6c9fd3dc4e28f120fd354847151ea414e7885b7724d73fe2f1babae73","artifactUrl":"https://github.com/DataDog/helm-charts/releases/download/cloudprem-0.6.0/cloudprem-0.6.0.tgz","availability":"available","reviewed":"2026-11-20","scope":"BYOC engine artifact plus separate Worker and cloud dependencies","source":"https://docs.datadoghq.com/byoc-logs/install/","status":"documented","summary":"The inspected cloudprem chart 0.6.0 packages engine v0.1.36. The separately indexed Worker chart is 2.26.0; observing both artifacts does not establish a validated engine/Worker pair. Select the vendor-approved combination. Chart 0.6.0 changes the indexer StatefulSet pod-management default; existing installations need the documented migration or an OrderedReady override.","supportingSources":[{"title":"Separate Worker artifact; not asserted to be a validated pair","url":"https://github.com/DataDog/helm-charts/releases/download/observability-pipelines-worker-2.26.0/observability-pipelines-worker-2.26.0.tgz"},{"title":"Vendor update/compatibility policy","url":"https://docs.datadoghq.com/byoc-logs/operate/updates/"},{"title":"Engine release and StatefulSet migration","url":"https://docs.datadoghq.com/byoc-logs/release_notes/"}]},"licensePricing":{"reviewed":"2026-11-20","scope":"Commercial activation/licensing boundary, not an operating-cost estimate","source":"https://docs.datadoghq.com/byoc-logs/install/","status":"documented","summary":"BYOC Logs is commercial Datadog software/service and requires activation through the account team. The reviewed materials do not establish an all-in public BYOC unit price or a customer quote; organization plan entitlements, engine/Worker billing and customer cloud charges must be confirmed separately.","supportingSources":[{"title":"Datadog EULA","url":"https://www.datadoghq.com/legal/eula/"}]},"marketplace":{"reviewed":"2026-11-20","scope":"Datadog BYOC Logs: reviewed customer-cloud deployment","source":"https://docs.datadoghq.com/byoc-logs/install/","status":"inconclusive","summary":"The reviewed edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient."},"release":{"releasePublishedOn":"2026-11-03","releaseTag":"v0.1.36","reviewed":"2026-11-20","scope":"BYOC engine snapshot and separately documented update policy","source":"https://docs.datadoghq.com/byoc-logs/release_notes/","status":"documented","summary":"The reviewed BYOC engine snapshot is v0.1.36, dated November 3, 2026 and bundled in cloudprem chart 0.6.0. Engine, Worker and charts have separate versions; use the vendor-validated combination. Datadog states an engine release cadence of at least monthly, which is a vendor policy rather than a support guarantee from this directory.","supportingSources":[{"title":"Vendor version-pair and update policy","url":"https://docs.datadoghq.com/byoc-logs/operate/updates/"}]},"scim":{"availability":"edition-dependent","reviewed":"2026-11-20","scope":"Plan-dependent hosted Datadog organization provisioning","source":"https://docs.datadoghq.com/account_management/scim/","status":"documented","summary":"Datadog documents SCIM user/team/role provisioning for Infrastructure Pro, Infrastructure Enterprise and Startup plans. Confirm the organization’s plan entitlement; BYOC Logs activation alone does not establish it. The endpoint manages hosted Datadog organization identities, not local engine users."},"securityControls":{"reviewed":"2026-11-20","scope":"BYOC query/control-plane connectivity and configurable customer-side controls","source":"https://docs.datadoghq.com/byoc-logs/introduction/network/","status":"documented","summary":"The default searcher-initiated reverse connection uses outbound HTTPS/WebSocket access to Datadog and carries queries, results and index-management messages without a public query ingress. The optional public ingress uses mTLS. Review API credentials, storage IAM, network restrictions and the resulting query-result egress."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Datadog hosted account/control-plane identity; not an independent engine login","source":"https://docs.datadoghq.com/account_management/saml/","status":"documented","summary":"The hosted Datadog organization used for Log Explorer supports SAML SSO with a configured identity provider. This authenticates users to Datadog’s hosted UI; the customer-side engine connection instead uses Datadog API credentials and the selected network configuration.","supportingSources":[{"title":"BYOC query and control-plane boundary","url":"https://docs.datadoghq.com/byoc-logs/introduction/architecture/"}]}},"id":"datadog-byoc-logs","infrastructure":["servers"],"infrastructureNotes":"Production workload uses Kubernetes, object storage and PostgreSQL. The listing's runtime describes the customer-operated engine and workers.","infrastructureReviewed":"2026-11-20","infrastructureSources":["https://docs.datadoghq.com/byoc-logs/install/","https://docs.datadoghq.com/byoc-logs/introduction/architecture/"],"install":"Install the BYOC Logs engine and Observability Pipelines Worker with Helm. An operator-managed installation is documented on Amazon EKS.","installMethods":["helm"],"kind":"product","license":"Commercial Datadog software and service. Confirm BYOC Logs activation and commercial terms with the account team.","licenseModel":"commercial-only","licenseModelNotes":"The offering requires a Datadog account and the vendor's terms. Account activation and the customer's applicable pricing and entitlement should be confirmed with Datadog.","licenseModelSources":["https://www.datadoghq.com/legal/eula/","https://docs.datadoghq.com/byoc-logs/configure/"],"licenseReviewed":"2026-11-20","model":"BYOC","modelLabel":"Customer-operated · vendor control plane","name":"Datadog BYOC Logs","notes":"Log ingestion, indexing and storage run in the customer's account. Matching query results travel to Datadog for display. The default connection is outbound from searcher pods to Datadog. Confirm service-site availability and account activation. A Docker path is documented for local evaluation. Docker is evaluation-only, and the Operator path is EKS-only. Engine v0.1.36/chart 0.6.0 needs the documented StatefulSet policy migration on existing clusters. Hosted Datadog SSO/SCIM and compliance boundaries remain distinct from the customer engine.","operationReview":{"controlPlane":"vendor-hosted","modelLabel":"Customer-operated · vendor control plane","operator":"customer","reviewed":"2026-11-20","source":"https://docs.datadoghq.com/byoc-logs/introduction.md","summary":"The customer installs and operates log processing, indexing and storage in its infrastructure. The Datadog-hosted UI submits queries and receives results; storing logs locally does not establish a disconnected or wholly customer-operated management plane.","supportingSources":[{"title":"Customer deployment and cluster configuration","url":"https://docs.datadoghq.com/byoc-logs/install.md"}]},"operations":"The customer provisions and sizes the cluster, manages storage, database, IAM and network connectivity, and applies validated engine and Worker version pairs. Datadog maintains the hosted UI.","publisher":false,"reviewed":"2026-11-20","sources":[{"title":"BYOC Logs install options and account activation","url":"https://docs.datadoghq.com/byoc-logs/install/"},{"title":"Architecture and query-result boundary","url":"https://docs.datadoghq.com/byoc-logs/introduction/architecture/"},{"title":"Connections and network data flow","url":"https://docs.datadoghq.com/byoc-logs/introduction/network/"},{"title":"Validated engine and worker updates","url":"https://docs.datadoghq.com/byoc-logs/operate/updates/"},{"title":"Datadog End-User License Agreement","url":"https://www.datadoghq.com/legal/eula/"},{"title":"BYOC Logs account configuration and activation","url":"https://docs.datadoghq.com/byoc-logs/configure/"},{"title":"Datadog BYOC Logs on Amazon EKS","url":"https://docs.datadoghq.com/byoc-logs/install/aws_eks/"},{"title":"Datadog BYOC Logs on Azure AKS","url":"https://docs.datadoghq.com/byoc-logs/install/azure_aks/"},{"title":"Datadog BYOC Logs on Google GKE","url":"https://docs.datadoghq.com/byoc-logs/install/gcp_gke/"},{"title":"Buyer evidence: scim","url":"https://docs.datadoghq.com/account_management/scim/"},{"title":"Separate Worker artifact; not asserted to be a validated pair","url":"https://github.com/DataDog/helm-charts/releases/download/observability-pipelines-worker-2.26.0/observability-pipelines-worker-2.26.0.tgz"},{"title":"Engine release and StatefulSet migration","url":"https://docs.datadoghq.com/byoc-logs/release_notes/"},{"title":"Buyer evidence: sso","url":"https://docs.datadoghq.com/account_management/saml/"},{"title":"Buyer evidence: footprint","url":"https://docs.datadoghq.com/byoc-logs/operate/sizing/"}],"url":"https://launchinyourcloud.com/directory/datadog-byoc-logs/","website":"https://docs.datadoghq.com/byoc-logs/"},{"advisories":[{"action":"Deploy fixed images for every DataHub service and restart them while retaining the v1.9.0 upgrade prerequisites.","conditions":"Affected image and CPU/JDK behavior determine exposure.","disclosedOn":"2026-11-19","id":"datahub-1-9-1-cve-2026-114938","listingIds":["datahub"],"reviewed":"2026-11-19","scope":"DataHub OSS GMS, frontend, MAE/MCE consumer, upgrade and actions images; fixes were also cherry-picked to the v1.9.0 hotfix branch.","source":"https://github.com/datahub-project/datahub/releases/tag/v1.9.1","summary":"DataHub v1.9.1 rebuilds service images on OpenJDK 25.0.5.1 for CVE-2026-114938 and removes cached Wolfi layers retaining the older JDK.","title":"DataHub v1.9.1 OpenJDK security rebuild","type":"security-advisory"}],"architecture":"Customer-operated application services with database, search, graph and event-stream dependencies","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Provides a metadata catalog, lineage graph, discovery and governance layer for connected data systems."},"cloudEvidence":[{"clouds":["aws"],"notes":"The official guide deploys DataHub to a customer EKS cluster and describes optional AWS managed services for stateful dependencies.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"DataHub on Amazon EKS","url":"https://docs.datahub.com/docs/deploy/aws","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The official guide deploys DataHub to a customer AKS cluster and documents the required infrastructure and Helm installation.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"DataHub on Azure Kubernetes Service","url":"https://docs.datahub.com/docs/deploy/azure","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The official guide deploys DataHub to a customer GKE cluster with Helm and provider-managed dependency options.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"DataHub on Google Kubernetes Engine","url":"https://docs.datahub.com/docs/deploy/gcp","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-14","clouds":["aws","azure","gcp"],"communityAcceptance":{"reviewed":"2026-11-16","sources":[{"title":"Reviewed maintenance release v1.9.0","url":"https://github.com/datahub-project/datahub/releases/tag/v1.9.0"},{"title":"Upstream contributor history","url":"https://github.com/datahub-project/datahub/graphs/contributors"},{"title":"Community profiles: Zynga fork and Farm Credit Canada deployment","url":"https://datahub.com/community/champions/"}],"summary":"The project community profiles identify Zynga running a customized DataHub fork and Farm Credit Canada hardening a Kubernetes deployment. Public contributor history shows sustained work by multiple participants, and release 1.9.0 on November 16, 2026 documents active maintenance, security updates, and significant upgrade requirements. These profiles establish project use without treating DataHub Cloud customers as proof of OSS deployment."},"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 data catalog and metadata platform for discovery, lineage and governance.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Local all-component deployment floor; production/HA capacity excluded","source":"https://docs.datahub.com/docs/deploy/kubernetes","status":"documented","summary":"The Kubernetes guide requires more than 7 GB RAM for a local Minikube deployment including dependencies. This is not a production minimum: application services, database, Kafka, search and any graph service require separate resource and availability sizing."},"iac":{"artifactRef":"Select compatible chart and application releases","artifactUrl":"https://github.com/acryldata/datahub-helm","reviewed":"2026-11-20","scope":"Official Kubernetes Helm deployment","source":"https://docs.datahub.com/docs/deploy/kubernetes","status":"documented","summary":"The official Helm repository provides separate DataHub and prerequisite charts, including external database, search and Kafka dependencies. The deployment guide includes example credentials that must be replaced. Pin compatible chart and application versions, and review whether to use managed or separately operated dependencies."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/datahub-project/datahub/master/LICENSE","status":"documented","summary":"The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate."},"release":{"releasePublishedAt":"2026-11-19T05:56:30Z","releaseTag":"v1.9.1","reviewed":"2026-11-19","scope":"Upstream DataHub OSS service images and hotfix branch; commercial editions and provider packages may differ","source":"https://github.com/datahub-project/datahub/releases/tag/v1.9.1","status":"documented","summary":"DataHub v1.9.1 was published November 19, 2026. It rebuilds service images on OpenJDK 25.0.5.1 for CVE-2026-114938 and fixes OpenSearch 2.x semantic search with multiple OR groups. Retain the v1.9.0 Elasticsearch/OpenSearch, CLI, Helm and breaking-change requirements.","supportingSources":[{"title":"Prior reviewed release context","url":"https://github.com/datahub-project/datahub/releases/tag/v1.9.0"}]},"securityControls":{"reviewed":"2026-11-19","scope":"DataHub OSS service images from the v1.9.1 release and its v1.9.0 hotfix branch","source":"https://github.com/datahub-project/datahub/releases/tag/v1.9.1","status":"documented","summary":"v1.9.1 rebuilds GMS, frontend, MAE/MCE consumer, upgrade and actions images on OpenJDK 25.0.5.1 to address CVE-2026-114938, and removes cached Wolfi layers that could retain the prior JDK. Upgrade every service image and restart."},"sso":{"availability":"available","reviewed":"2026-11-14","scope":"DataHub self-managed frontend OIDC configuration","source":"https://docs.datahub.com/docs/authentication/guides/sso/configure-oidc-react","status":"documented","summary":"The self-managed React application supports OIDC identity providers such as Okta, Google and Keycloak through its authentication configuration. This is separate from DataHub Cloud login setup."}},"id":"datahub","infrastructure":["servers"],"infrastructureNotes":"DataHub uses persistent application services and stateful database, search and event-stream components. Provider-managed dependencies do not remove application operations. DataHub v1.9.0 supports Elasticsearch 8.x or OpenSearch 2.x/3.x; GMS will not start with Elasticsearch 7.x or OpenSearch compatibility mode reporting 7.10.2.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://docs.datahub.com/docs/deploy/kubernetes","https://github.com/datahub-project/datahub/releases/tag/v1.9.0","https://docs.datahub.com/docs/how/breaking-changes#v190"],"install":"Official Helm deployment on EKS, AKS or GKE","installMethods":["helm"],"kind":"product","license":"Apache License 2.0.","licenseModel":"open-source","licenseModelNotes":"DataHub OSS is Apache-2.0 licensed. DataHub Cloud and associated enterprise services use separate commercial terms.","licenseModelSources":["https://github.com/datahub-project/datahub/blob/master/LICENSE"],"licenseReviewed":"2026-11-14","model":"Fully in your account","modelLabel":"Customer-operated","name":"DataHub OSS","notes":"This entry covers DataHub OSS, not DataHub Cloud. Production deployments require careful operation of the metadata database, search index, event streaming and upgrade jobs; managed provider services can replace some in-cluster dependencies. DataHub v1.9.0 removes Elasticsearch 7.x support and requires Elasticsearch 8.x or OpenSearch 2.x/3.x. Metrics are enabled by default; set METRICS_ENABLED=false to disable them. The release requires CLI/Python SDK 1.7.0.19 and Helm chart 1.1.10, and operators should review all documented breaking changes before rollout. DataHub v1.9.1 rebuilds service images on OpenJDK 25.0.5.1 for CVE-2026-114938 and removes cached Wolfi layers that retained the earlier JDK. It also fixes OpenSearch 2.x semantic search with multiple OR groups. Preserve the v1.9.0 breaking-change, search-backend, CLI and Helm upgrade requirements when applying the patch.","operations":"Customer manages Kubernetes, stateful dependencies, networking, secrets, backups, scaling, ingestion, and upgrades, including search-backend compatibility and per-version breaking-change actions.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Self-hosting on Kubernetes","url":"https://docs.datahub.com/docs/deploy/kubernetes"},{"title":"AWS deployment","url":"https://docs.datahub.com/docs/deploy/aws"},{"title":"Azure deployment","url":"https://docs.datahub.com/docs/deploy/azure"},{"title":"Google Cloud deployment","url":"https://docs.datahub.com/docs/deploy/gcp"},{"title":"Apache 2.0 license","url":"https://github.com/datahub-project/datahub/blob/master/LICENSE"},{"title":"DataHub v1.9.0 release and upgrade requirements","url":"https://github.com/datahub-project/datahub/releases/tag/v1.9.0"},{"title":"Upstream contributor history","url":"https://github.com/datahub-project/datahub/graphs/contributors"},{"title":"Community profiles: Zynga fork and Farm Credit Canada deployment","url":"https://datahub.com/community/champions/"},{"title":"DataHub v1.9.0 breaking changes","url":"https://docs.datahub.com/docs/how/breaking-changes#v190"},{"title":"DataHub v1.9.1 release","url":"https://github.com/datahub-project/datahub/releases/tag/v1.9.1"}],"url":"https://launchinyourcloud.com/directory/datahub/","website":"https://datahub.com/"},{"architecture":"Customer-hosted Fleet Manager provisioning VM-backed DSS instances and optional elastic Kubernetes compute in the customer's cloud tenant","categories":["data-analytics","ai-tools"],"category":"Data \u0026 analytics","categoryFit":{"ai-tools":"Provides customer-operated data science, machine-learning, generative-AI, model-deployment and AI-governance capabilities.","data-analytics":"Provides customer-operated data preparation, analytics, visual workflows, elastic computation and governed data projects."},"cloudEvidence":[{"clouds":["aws"],"notes":"Dataiku documents using an AWS CloudFormation template to deploy Fleet Manager into the customer's AWS account, then provisioning DSS nodes and optional EKS elastic-compute clusters.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Dataiku DSS Cloud Stacks on AWS","url":"https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/guided-setup-new-vpc-elastic-compute.html","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Dataiku documents deploying Fleet Manager and its supporting resources through an Azure ARM template, then provisioning DSS instances and optional AKS elastic compute in the customer's subscription.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Dataiku DSS Cloud Stacks on Azure","url":"https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/guided-setup-new-vnet-elastic-compute.html","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Dataiku documents deploying Fleet Manager through Google Cloud Infrastructure Manager using its supplied Terraform configuration, then provisioning DSS instances and optional GKE elastic compute in the customer's projects.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Dataiku DSS Cloud Stacks on Google Cloud","url":"https://doc.dataiku.com/dss/latest/installation/cloudstacks-gcp/guided-setup-new-vpc-elastic-compute.html","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":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Commercial Dataiku DSS deployment managed through Fleet Manager inside a customer AWS, Azure or Google Cloud tenant.","diligence":{"airGap":{"reviewed":"2026-11-16","scope":"Cloud Stacks/Fleet Manager boundary; an offline DSS feature does not establish a disconnected management stack","source":"https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/tenant-settings.html","status":"inconclusive","summary":"DSS 15 documents offline document-extraction resources, but Fleet Manager’s standard Cloud Stacks setup uses HTTP for image lists, license updates/verification and OIDC. The reviewed material does not establish an end-to-end disconnected Cloud Stacks procedure.","supportingSources":[{"title":"DSS 15 air-gapped extraction upgrade notes","url":"https://doc.dataiku.com/dss/latest/release_notes/15.html"}]},"compliance":{"reviewed":"2026-11-16","scope":"Dataiku Inc. ISO/IEC 27001:2022 and 27701:2019 organizational management systems; not a customer-deployment certificate","source":"https://downloads.dataiku.com/publicdocs/Dataiku_ISO_27001_Certificate_of_Registration.pdf","status":"documented","summary":"Dataiku’s published certificate 1850881-6 covers its organizational ISMS/PIMS supporting the Dataiku platform, including R\u0026D. It was issued 2026-04-30 and expires 2027-12-14, subject to surveillance. The certificate expressly does not authorize labeling products, processes or services as certified; it does not certify the customer’s Cloud Stacks environment.","supportingSources":[{"title":"Self-managed and SaaS account boundaries","url":"https://www.dataiku.com/legal/trust"}]},"footprint":{"reviewed":"2026-11-16","scope":"DSS 15 application requirements; not a complete Cloud Stacks architecture estimate","source":"https://doc.dataiku.com/dss/latest/installation/custom/requirements.html","status":"documented","summary":"DSS 15’s server requirements specify x86-64 Linux and at least 32 GB RAM, with more for in-memory data and additional users. This sizes the DSS application component only; Fleet Manager, execution infrastructure and cloud services add resources."},"iac":{"reviewed":"2026-11-16","scope":"Cloud Stacks Fleet Manager; provider-specific templates and permissions","source":"https://doc.dataiku.com/dss/latest/installation/cloudstacks-gcp/guided-setup-new-vpc-elastic-compute.html","status":"documented","summary":"The GCP guide deploys Fleet Manager with Infrastructure Manager and Terraform. It identifies gs://dataiku-cloudstacks/templates/fleet-manager/15.2.1/fleet-manager-instance.tf and a separate terraform.tfvars file. This is the guide’s versioned example, not a universal latest-version claim; AWS uses CloudFormation and Azure uses ARM templates.","supportingSources":[{"title":"AWS Cloud Stacks","url":"https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/index.html"},{"title":"Azure Cloud Stacks","url":"https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/concepts.html"}]},"licensePricing":{"reviewed":"2026-11-16","scope":"Dataiku DSS Cloud Stacks: software license terms; infrastructure and operating costs are separate","source":"https://doc.dataiku.com/dss/latest/operations/license.html","status":"documented","summary":"The listed fully featured Cloud Stacks deployment requires a Dataiku license or license token. Dataiku documents a separate DSS Free Edition, but that does not determine the licensing of the listed Cloud Stacks offering.","supportingSources":[{"title":"Edition and license conditions","url":"https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/tenant-settings.html"}]},"marketplace":{"reviewed":"2026-11-16","scope":"Trial AMI versus the listed commercial Cloud Stacks offering","source":"https://aws.amazon.com/marketplace/pp/prodview-hrcm5q34opptc","status":"inconclusive","summary":"The reviewed Dataiku Trial offer delivers an AWS AMI and uses an externally purchased license. That does not establish the current fully featured Cloud Stacks entitlement or a Fleet Manager deployment; confirm the selected contract and installer separately."},"release":{"releasePublishedOn":"2026-11-06","releaseTag":"15.2.2","reviewed":"2026-11-16","scope":"DSS application release; Fleet Manager templates and deployed instance versions may differ; source supplies a publication day, not a timestamp","source":"https://doc.dataiku.com/dss/latest/release_notes/15.html","status":"documented","summary":"The reviewed vendor release is 15.2.2, published 2026-11-06. This is a dated, scoped snapshot; it does not establish compatibility with another chart, cloud package or commercial edition."},"scim":{"reviewed":"2026-11-16","scope":"DSS 15 user suppliers and synchronization; not a claim that SCIM is unsupported","source":"https://doc.dataiku.com/dss/latest/security/authentication/","status":"inconclusive","summary":"DSS documents SSO/LDAP/Azure AD user suppliers, login-time provisioning and administrative synchronization. These mechanisms do not establish a SCIM protocol endpoint; the reviewed authentication manual leaves direct SCIM support unresolved."},"securityControls":{"reviewed":"2026-11-16","scope":"Fleet Manager AWS access, optional secret storage and outbound requirements","source":"https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/tenant-settings.html","status":"documented","summary":"For AWS Cloud Stacks, Fleet Manager recommends an IAM instance profile for cloud API calls. If it stores secrets, they are encrypted with an AWS KMS customer-managed key. HTTP access is used for image lists, license verification and OIDC."},"sso":{"availability":"available","reviewed":"2026-11-16","scope":"DSS instance authentication within Cloud Stacks; license and enabled features still govern entitlement","source":"https://doc.dataiku.com/dss/latest/security/sso.html","status":"documented","summary":"DSS 15 documents SAML and OpenID Connect SSO. Its SAML compatibility list includes Okta, Entra ID, ADFS, Auth0 and Keycloak; encrypted SAML assertions are explicitly unsupported. Configure the DSS instance and identity provider together.","supportingSources":[{"title":"DSS authentication mechanisms","url":"https://doc.dataiku.com/dss/latest/security/authentication/"}]}},"id":"dataiku-dss-cloud-stacks","infrastructure":["servers"],"infrastructureNotes":"Cloud Stacks deploys a persistent Fleet Manager and VM-backed DSS nodes in the customer tenant, with optional EKS, AKS or GKE elastic-compute clusters.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://doc.dataiku.com/dss/latest/installation/","https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/index.html","https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/concepts.html","https://doc.dataiku.com/dss/latest/installation/cloudstacks-gcp/index.html"],"install":"AWS CloudFormation, Azure ARM template or Google Cloud Infrastructure Manager with Terraform","installMethods":["cloudformation","terraform","other"],"kind":"product","license":"Commercial Dataiku license or license token required for the full Cloud Stacks capabilities.","licenseModel":"commercial-only","licenseModelNotes":"The listed fully featured Cloud Stacks deployment requires a Dataiku license or license token. Dataiku documents a separate DSS Free Edition, but that does not determine the licensing of the listed Cloud Stacks offering.","licenseModelSources":["https://doc.dataiku.com/dss/latest/operations/license.html","https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/tenant-settings.html"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"Dataiku DSS Cloud Stacks","notes":"This entry covers Dataiku Cloud Stacks, not vendor-hosted Dataiku Cloud. Dataiku states that Cloud Stacks resources run in the customer's organization or tenant and that Dataiku does not have access to customer data. Fleet Manager requires broad cloud permissions and outbound access for images, license validation and configured identity services. Dataiku DSS Free Edition is separate from the fully featured licensed Cloud Stacks deployment.","operations":"Customer manages cloud accounts, Fleet Manager, IAM identities, networking, VM and Kubernetes capacity, storage, TLS, backups, upgrades and license configuration.","publisher":false,"reviewed":"2026-11-16","sources":[{"title":"Dataiku DSS installation options","url":"https://doc.dataiku.com/dss/latest/installation/"},{"title":"Dataiku Cloud Stacks for AWS","url":"https://doc.dataiku.com/dss/latest/installation/cloudstacks-aws/index.html"},{"title":"Dataiku Cloud Stacks for Azure","url":"https://doc.dataiku.com/dss/latest/installation/cloudstacks-azure/index.html"},{"title":"Dataiku Cloud Stacks for Google Cloud","url":"https://doc.dataiku.com/dss/latest/installation/cloudstacks-gcp/index.html"},{"title":"Dataiku DSS licensing","url":"https://doc.dataiku.com/dss/latest/operations/license.html"}],"url":"https://launchinyourcloud.com/directory/dataiku-dss-cloud-stacks/","website":"https://www.dataiku.com/product/"},{"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"},{"architecture":"Persistent Docker server; the standalone template includes web, PostgreSQL and Redis services with host-mounted data volumes.","categories":["collaboration","customer-support"],"category":"Collaboration","categoryFit":{"collaboration":"Public or private discussion communities with searchable topics, chat and shared knowledge.","customer-support":"Customer and peer-support communities; this is a discussion platform rather than an agent-ticket helpdesk."},"cloudEvidence":[{"clouds":["aws","gcp","digitalocean","linode","vultr","hetzner"],"notes":"The official cloud installation guide explicitly names DigitalOcean, AWS EC2, Google Cloud, Linode/Akamai, Vultr and Hetzner as supported hosts, then provides a complete server installation workflow. This is provider compatibility for the customer-operated Discourse application, not its separate hosted SaaS; configure the supported OS, DNS, email, HTTPS and recovery.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Discourse supported cloud server installation","url":"https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","gcp","digitalocean","linode","vultr","hetzner"],"communityAcceptance":{"reviewed":"2026-11-14","sources":[{"title":"Named support-community adopters","url":"https://www.discourse.org/customers"},{"title":"Current releases and support timelines","url":"https://releases.discourse.org/"},{"title":"2026.10.1 security-maintenance changelog","url":"https://releases.discourse.org/changelog/v2026.10.1/"}],"summary":"The official customer directory identifies Docker, Elastic and GitLab support communities as Discourse users, without establishing their hosting model. The official release service records security-maintenance updates on November 10, 2026 for the latest, monthly and ESR channels; the supported 2026.10.1 release includes 38 security fixes."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"linode","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"vultr","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"hetzner","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Self-hosted discussion and community platform for workplace collaboration and customer support communities.","diligence":{"footprint":{"reviewed":"2026-11-14","scope":"Upstream standalone cloud install baseline","source":"https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md","status":"documented","summary":"The upstream cloud guide lists 1 CPU core, 1 GB RAM with swap and 10 GB disk as minima; 2+ cores, 2 GB+ RAM and 20 GB+ disk are recommended. Plugins, traffic and data growth change sizing."},"iac":{"artifactRef":"main (moving branch)","artifactUrl":"https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml","reviewed":"2026-11-20","scope":"Official self-hosted launcher and standalone container installation","source":"https://raw.githubusercontent.com/discourse/discourse_docker/main/README.md","status":"documented","summary":"The official discourse_docker repository supplies launcher scripts and a standalone configuration example with application, PostgreSQL and Redis templates. Configure mail, TLS, secrets, volumes and backups, and pin compatible releases; a standalone container is not a clustered HA topology.","supportingSources":[{"title":"Standalone configuration template","url":"https://raw.githubusercontent.com/discourse/discourse_docker/main/samples/standalone.yml"}]},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream self-hosted core license; hosted plan pricing is a different offering","source":"https://raw.githubusercontent.com/discourse/discourse/main/LICENSE.txt","status":"documented","summary":"The upstream Discourse software is GPL version 2. Hosted subscription prices on discourse.org are for separately operated hosting/services and should not be presented as the license cost of the self-hosted core. Infrastructure, implementation and optional services are separate."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Official DiscourseConnect self-hosted forum authentication","source":"https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045","status":"documented","summary":"DiscourseConnect is the official SSO protocol for connecting Discourse to an external identity provider through a signed shared-secret exchange. It is distinct from a generic SAML entitlement; configure account/email mapping and callback security for the actual identity service."}},"id":"discourse","infrastructure":["servers"],"infrastructureNotes":"The official installer requires a Linux server and Docker. Its standalone configuration mounts persistent host storage and includes PostgreSQL and Redis; this is a server workload.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md","https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml"],"install":"Official Docker installer on a Linux cloud or local server","installMethods":["docker","package"],"kind":"product","license":"GPL-2.0 core; review extensions separately","licenseModel":"open-source","licenseModelNotes":"The listed self-hosted core has a GNU GPL version 2 license. Official paid hosting is a separate service; review the licenses of selected extensions separately.","licenseModelSources":["https://raw.githubusercontent.com/discourse/discourse/main/LICENSE.txt","https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Discourse","notes":"This entry covers self-hosted Discourse. The official cloud installation guide explicitly lists AWS EC2 and Google Cloud as supported Docker hosts; customers provision the Linux server, rather than using a bundled cloud-specific infrastructure template. The installer offers an external Discourse ID login option when SMTP is skipped. Review authentication, email and other integrations for outbound data flows. Supported-series updates published November 10, 2026 include 2026.10.1 and 2026.7.5 ESR; the 2026.10.1 changelog records 38 security fixes. Self-hosted operators should upgrade on their selected supported release channel.","operations":"Customer maintains the Linux host, Docker deployment, backups, updates and configured messaging services; choose an actively supported release channel.","publisher":false,"reviewed":"2026-11-14","sources":[{"title":"Official self-hosting installation guide","url":"https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md"},{"title":"Official standalone Docker service and storage template","url":"https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml"},{"title":"Discussion, chat and administration features","url":"https://www.discourse.org/features"},{"title":"Discourse core license","url":"https://raw.githubusercontent.com/discourse/discourse/main/LICENSE.txt"},{"title":"Official releases and support timelines","url":"https://releases.discourse.org/"},{"title":"Official customer community directory","url":"https://www.discourse.org/customers"},{"title":"Discourse 2026.10.1 security-maintenance changelog","url":"https://releases.discourse.org/changelog/v2026.10.1/"}],"url":"https://launchinyourcloud.com/directory/discourse/","website":"https://www.discourse.org/"},{"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":"dotCMS Cloud Anywhere tenant with vendor Lighthouse management and customer cloud access roles.","categories":["content-management"],"category":"Content management \u0026 CMS","categoryFit":{"content-management":"Vendor-operated content platform deployed into a customer cloud account."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"dotCMS Cloud Anywhere tenant with vendor Lighthouse management and customer cloud access roles. The vendor operates the installation through its control plane and AWS role or GCP service account. Public core code and Cloud Anywhere service licensing are different; this is not a fully customer-operated instance.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Cloud Anywhere Quickstart","url":"https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"vendor"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0],"operator":"vendor"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"vendor"}],"description":"Vendor-operated content platform deployed into a customer cloud account.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Upstream standard-stack baseline; managed-service deployment sizing is separate","source":"https://dev.dotcms.com/docs/manage/installation-and-deployment/installation/requirements","status":"documented","summary":"The standard-stack requirements specify a multicore processor, dedicated 8+ GB RAM and 100 GB disk, with PostgreSQL and OpenSearch dependencies. These application-stack requirements do not size a contracted Cloud Anywhere topology or validate 100-user/1-TB HA capacity."},"iac":{"artifactRef":"Current reference examples; pin a supported application and backing-service release","artifactUrl":"https://dev.dotcms.com/docs/manage/installation-and-deployment/docker/getting-started-with-dotcms-in-docker-containers","reviewed":"2026-11-20","scope":"Upstream application container examples; selected managed deployment follows its separate contract","source":"https://dev.dotcms.com/docs/manage/installation-and-deployment/docker/getting-started-with-dotcms-in-docker-containers","status":"documented","summary":"Official container guidance provides Docker and multi-service Compose examples with persistent data volumes. The developer all-in-one image is for local evaluation; it is not the Cloud Anywhere managed-service architecture or a production HA baseline."},"licensePricing":{"reviewed":"2026-11-19","scope":"Selected self-managed application or customer-cloud service; contract confirmation required","source":"https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide","status":"inconclusive","summary":"The public core-code licence does not establish the Cloud Anywhere managed-service price, order or operating/support entitlements. Obtain the agreement for the customer-cloud service."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Current dotCMS application authentication; Cloud Anywhere service entitlement/version must be confirmed","source":"https://dev.dotcms.com/docs/manage/access-and-security/dotauth/dotauth-sso","status":"documented","summary":"The current dotAuth guide documents system/site SSO settings for OAuth2/OIDC and SAML, including separate redirects for site and administrator login. Validate the selected service plan, release and identity mapping; site inheritance is not the same as configuring every redirect at the IdP."}},"id":"dotcms","infrastructure":["servers"],"infrastructureNotes":"dotCMS Cloud Anywhere tenant with vendor Lighthouse management and customer cloud access roles. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide"],"install":"Cloud Anywhere onboarding and vendor management through customer-cloud access roles","installMethods":["vendor-assisted"],"kind":"product","license":"Commercial dotCMS Cloud Anywhere service terms; the public core-code licence does not grant service entitlements.","licenseModel":"commercial-only","licenseModelNotes":"Commercial dotCMS Cloud Anywhere service terms; the public core-code licence does not grant service entitlements.","licenseModelSources":["https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide","https://github.com/dotCMS/core/blob/master/LICENSE"],"licenseReviewed":"2026-11-19","model":"BYOC","modelLabel":"Vendor-operated BYOC","name":"dotCMS Cloud Anywhere","notes":"The vendor operates the installation through its control plane and AWS role or GCP service account. Public core code and Cloud Anywhere service licensing are different; this is not a fully customer-operated instance.","operationReview":{"controlPlane":"not-assessed","modelLabel":"Vendor-operated BYOC","operator":"vendor","reviewed":"2026-11-20","source":"https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide","summary":"dotCMS provisions and operates Cloud Anywhere through its automation and delegated access to a dedicated customer account, subscription or project. The separately customer-operated self-hosted edition is outside this listing."},"operations":"Vendor operates the Cloud Anywhere application through its management plane and scoped customer-cloud access; agree support access, logs, egress and exit procedures.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Cloud Anywhere Quickstart","url":"https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide"},{"title":"Azure Setup Guide","url":"https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-azure-setup-guide"},{"title":"BSL-1.1 LICENSE","url":"https://github.com/dotCMS/core/blob/master/LICENSE"},{"title":"Releases v26.11.18","url":"https://github.com/dotCMS/core/releases"}],"url":"https://launchinyourcloud.com/directory/dotcms/","website":"https://dev.dotcms.com/docs/manage/installation-and-deployment/cloud-anywhere/cloud-anywhere-quickstart-guide"},{"advisories":[{"action":"Review certificates and the linked bulletins, then apply the appropriate Enterprise patch and test connectivity.","conditions":"Services whose certificates chain only to the removed roots will fail validation. Brotli applicability depends on the affected component.","id":"dremio-26-1-13-security-review","listingIds":["dremio-self-managed"],"reviewed":"2026-11-17","scope":"Dremio Enterprise 26.1.13; this release does not establish the same fixes for Community Edition.","source":"https://docs.dremio.com/current/release-notes/version-260-release/#26113-november-2026-enterprise","summary":"Enterprise 26.1.13 removes compromised CA trust roots and patches the Brotli dependency in its Open Catalog service.","title":"Dremio Enterprise trust-store and Brotli update","type":"security-advisory"}],"architecture":"Customer-operated coordinator and executor services with metadata and distributed storage","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Provides distributed SQL queries, semantic modeling and lakehouse analytics over customer-controlled data sources."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Dremio identifies Community and Enterprise as self-managed on AWS, Azure and Google Cloud. Community supports Docker or Kubernetes; Enterprise self-managed uses Kubernetes. This is distinct from the fully managed Dremio Cloud service.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Dremio self-managed editions on AWS, Azure and Google Cloud","url":"https://docs.dremio.com/editions/","vendorSupport":"not-assessed"},{"clouds":["aws","azure","gcp"],"notes":"Dremio documents active testing against Amazon EKS, Azure AKS and Google GKE and provides provider recommendations. Customers operate the selected cluster and configure storage, identity and network access.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Dremio-tested EKS, AKS and GKE environments","url":"https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-13","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":"Self-managed distributed SQL and lakehouse analytics platform for customer-controlled data sources.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Current self-managed Kubernetes component floors; topology and query workload additional","source":"https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/","status":"documented","summary":"The current Kubernetes guide gives an 8-CPU/16-GB smallest production coordinator and executors with at least 64 GB memory. It recommends larger 32-CPU/64-GB coordinators and 128-GB executors. Catalog, search, messaging, storage and HA add substantial resources; these are component minima, not a complete cluster."},"iac":{"artifactRef":"oci://quay.io/dremio/dremio-helm; pin the selected v3 chart release","artifactUrl":"https://docs.dremio.com/current/deploy-dremio/deploy-on-kubernetes/","reviewed":"2026-11-20","scope":"Official Dremio 26+ self-managed OCI Helm distribution","source":"https://docs.dremio.com/current/deploy-dremio/deploy-on-kubernetes/","status":"documented","summary":"Current Dremio 26+ Kubernetes deployment uses the v3 OCI Helm chart at Quay; the older v2 chart is incompatible. Enterprise requires authorized registry access and a valid licence key. Configure chart values, object storage, cluster services and version compatibility before deployment."},"licensePricing":{"reviewed":"2026-11-20","scope":"Self-managed Enterprise quote; managed Cloud rates excluded","source":"https://www.dremio.com/pricing/","status":"documented","summary":"The vendor pricing page identifies Dremio Enterprise as self-hosted commercial software with pricing available from sales. Its displayed per-DCU Cloud price applies to the managed service, not this Enterprise licence. Agree capacity, term and support separately from the infrastructure bill."},"scim":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Dremio self-managed Enterprise 26.x","source":"https://docs.dremio.com/current/security/authentication/identity-providers/scim/","status":"documented","summary":"Enterprise documents SCIM 2.0 user/group provisioning with header authentication. Identity-provider configuration and the customer-accessible SCIM endpoint are required."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Dremio self-managed Enterprise 26.x; not Community or Dremio Cloud","source":"https://docs.dremio.com/current/security/authentication/identity-providers/oidc/","status":"documented","summary":"The current 26.x self-managed documentation marks OpenID Connect SSO as Enterprise. OIDC handles authentication; user and group memberships are provisioned separately through SCIM."}},"id":"dremio-self-managed","infrastructure":["servers"],"infrastructureNotes":"The self-managed platform runs distributed coordinator and executor services in containers or Kubernetes, with persistent metadata and distributed storage. It is a server/container workload even when managed cloud storage is used. Dremio Enterprise 26.1.13 adds configurable startup and liveness probes for Kubernetes executors.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://docs.dremio.com/current/deploy-dremio/","https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/","https://docs.dremio.com/current/release-notes/version-260-release/#26113-november-2026-enterprise"],"install":"Community on Docker or Kubernetes; Enterprise on Kubernetes using vendor-tested EKS, AKS or GKE environments.","installMethods":["docker"],"kind":"product","license":"Apache License 2.0 for Dremio Community; Dremio Enterprise uses separate commercial terms.","licenseModel":"open-source","licenseModelNotes":"Dremio Community is Apache-2.0 licensed; self-managed Dremio Enterprise is commercially licensed. This classification covers the platform family and requires edition-specific feature review.","licenseModelSources":["https://github.com/dremio/dremio-oss/blob/master/LICENSE","https://docs.dremio.com/editions/"],"licenseReviewed":"2026-11-13","model":"Fully in your account","modelLabel":"Customer-operated","name":"Dremio Self-Managed","notes":"This entry covers Dremio Community and self-managed Enterprise, not Dremio Cloud. Community and Enterprise feature, support and billing differences must be reviewed separately. Query engines require network and credential access to configured data sources. Dremio Enterprise 26.1.13 removes compromised eMudhra certificate roots, updates Brotli for CVE-2026-111497, fixes incorrect or missing query results, and addresses rare file deletion after a network partition. Certificates chaining only to the removed roots will fail after upgrading. These fixes are specific to the Enterprise release.","operations":"Customer manages Kubernetes or container capacity, storage, security, scaling, upgrades, backups and integration with data sources.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Dremio edition and deployment comparison","url":"https://docs.dremio.com/editions/"},{"title":"Vendor-tested Kubernetes environments","url":"https://docs.dremio.com/current/deploy-dremio/kubernetes-environments/"},{"title":"Dremio OSS Apache 2.0 license","url":"https://github.com/dremio/dremio-oss/blob/master/LICENSE"},{"title":"Dremio Enterprise 26.1.13 security and reliability fixes","url":"https://docs.dremio.com/current/release-notes/version-260-release/#26113-november-2026-enterprise"}],"url":"https://launchinyourcloud.com/directory/dremio-self-managed/","website":"https://www.dremio.com/"},{"advisories":[{"action":"Upgrade to 3.8.6, 4.2.1, or later; perform certificate cleanup where required; and review or revoke persistent role tokens.","conditions":"Several issues require particular platform roles, certificate rotation, persistent tokens, symlink paths, or Enterprise Search. Multiple advisories have no workaround.","id":"elastic-cloud-enterprise-3-8-6-4-2-1-security-update","listingIds":["elastic-cloud-enterprise"],"reviewed":"2026-11-18","scope":"Most issues affect releases through 3.8.5 and 4.2.0. ESA-2026-222 affects 4.1.0 through 4.2.0 when Enterprise Search is present. Fixed releases are 3.8.6 and 4.2.1.","source":"https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-216/391263","summary":"ESA-2026-211, 212, 215, 216, 218, 221, and 222 cover credential escalation, retained certificate credentials and CA keys, cross-deployment access through symlinks, role-token exposure, and platform-setting authorization.","supportingSources":[{"title":"ESA-2026-211","url":"https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-211/391260"},{"title":"ESA-2026-212","url":"https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-212/391261"},{"title":"ESA-2026-215","url":"https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-215/391262"},{"title":"ESA-2026-218","url":"https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-218/391264"},{"title":"ESA-2026-221","url":"https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-221/391265"},{"title":"ESA-2026-222","url":"https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-4-2-1-security-update-esa-2026-222/391266"}],"title":"Elastic Cloud Enterprise 3.8.6 and 4.2.1 security update","type":"security-advisory"},{"action":"Apply -XX:-UseBASE64Intrinsics, restart every deployment and follow Elastic's advisory until fixed ECE images are released and deployed.","conditions":"CPU features, JDK and deployed Elasticsearch version determine exposure.","disclosedOn":"2026-11-18","id":"elastic-ece-cve-2026-114938","listingIds":["elastic-cloud-enterprise"],"reviewed":"2026-11-19","scope":"ECE-hosted Elasticsearch 7.17.3 and later on affected hardware; planned ECE 4.2.2 and 3.8.7 were not yet released when reviewed.","source":"https://discuss.elastic.co/t/java4shell-remote-code-execution-rce-vulnerability-cve-2026-114938/391703","summary":"Elastic says affected Elasticsearch on x86-64 AVX512_VBMI CPUs can permit authenticated RCE and unauthenticated denial of service.","title":"Elastic Cloud Enterprise CVE-2026-114938 guidance","type":"security-advisory"}],"architecture":"Multi-host orchestration layer with coordinators, proxies, allocators and managed Elasticsearch and Kibana deployments","categories":["data-analytics","databases-vector","observability"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Orchestrates self-managed Elasticsearch and Kibana deployments for search, analytical and data-exploration workloads.","databases-vector":"Operates Elasticsearch clusters that provide document, full-text and vector search in customer infrastructure.","observability":"Operates Elastic Stack deployments used to ingest, search and analyze logs, metrics, traces and security telemetry."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Elastic's current ECE installation guide explicitly supports public-cloud hosts on AWS, Google Cloud and Microsoft Azure and installs ECE on customer-prepared virtual machines.","reviewed":"2026-11-15","sourceType":"vendor-documentation","title":"Elastic Cloud Enterprise on public cloud hosts","url":"https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-15","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 self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"ECE host-role requirements; hosted deployment capacity and HA additional","source":"https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/ece-hardware-prereq","status":"documented","summary":"ECE lists an 8-GB installation floor per host role, but recommends 128–256 GB for allocator hosts and distinct control/proxy sizing. HA needs at least three hosts across three availability zones. Fast SSDs, deployment memory/storage ratios and cluster workloads materially affect the footprint; the installer floor is not production capacity."},"iac":{"reviewed":"2026-11-16","scope":"Elastic Cloud Enterprise installation guide; orchestrator hosts, not Elastic Cloud Hosted","source":"https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install","status":"documented","summary":"ECE installation prepares supported Linux hosts, Docker or Podman, XFS quotas and mount points before installing the orchestrator. Follow the supported OS/container-engine matrix and deployment-specific prerequisites; generic cloud VMs alone are insufficient."},"licensePricing":{"reviewed":"2026-11-20","scope":"Commercial ECE platform/deployment licensing; numeric price requires a quote","source":"https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-ece","status":"documented","summary":"ECE requires an Elastic-issued licence; installation activates a 30-day trial. A full ECE licence enables managed deployments at the stated Enterprise subscription feature/support level for their stack version. The page does not quote a price; obtain ECE terms separately from hosted Elastic Cloud rates and infrastructure."},"release":{"releasePublishedOn":"2026-10-20","releaseTag":"4.2.1","reviewed":"2026-11-18","scope":"Elastic Cloud Enterprise 3.8 and 4.2 maintained lines","source":"https://www.elastic.co/docs/release-notes/cloud-enterprise","status":"documented","summary":"Elastic Cloud Enterprise 4.2.1 was released October 20, 2026; 3.8.6 is the parallel fixed release for that maintained line. The updates address multiple platform-role, credential, certificate, token, and cross-deployment issues."},"securityControls":{"reviewed":"2026-11-19","scope":"ECE-hosted Elasticsearch deployments on affected x86-64 AVX512_VBMI hardware; planned ECE versions are not recorded as released","source":"https://discuss.elastic.co/t/java4shell-remote-code-execution-rce-vulnerability-cve-2026-114938/391703","status":"documented","summary":"Current advisory review: ESA-2026-211, 212, 215, 216, 218, 221, and 222 cover credential escalation, retained certificate credentials and CA keys, cross-deployment access through symlinks, role-token exposure, and platform-setting authorization. Upgrade to 3.8.6, 4.2.1, or later; perform certificate cleanup where required; and review or revoke persistent role tokens. Current review: CVE-2026-114938 can affect Elasticsearch 7.17.3 and later on x86-64 AVX512_VBMI CPUs. Authenticated read access can permit RCE and unauthenticated access can cause denial of service. Elastic planned ECE 4.2.2 and 3.8.7 but had not released them when reviewed. Use -XX:-UseBASE64Intrinsics, restart every deployment and follow the vendor advisory until fixed ECE images are available.","supportingSources":[{"title":"Prior security-controls source","url":"https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-216/391263"},{"title":"ESA-2026-211","url":"https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-211/391260"},{"title":"ESA-2026-212","url":"https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-212/391261"},{"title":"ESA-2026-215","url":"https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-215/391262"},{"title":"ESA-2026-218","url":"https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-218/391264"},{"title":"ESA-2026-221","url":"https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-221/391265"},{"title":"ESA-2026-222","url":"https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-4-2-1-security-update-esa-2026-222/391266"}]},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Self-managed ECE orchestrator browser federation","source":"https://www.elastic.co/docs/deploy-manage/users-roles/cloud-enterprise-orchestrator/saml","status":"documented","summary":"ECE supports SAML 2.0 Web Browser SSO for the orchestrator/Cloud UI, with attribute and role mappings. It does not apply to ordinary API clients or automatically configure every hosted Elasticsearch/Kibana deployment; those access policies are separate."}},"id":"elastic-cloud-enterprise","infrastructure":["servers"],"infrastructureNotes":"ECE uses multiple persistent Linux hosts for orchestration, proxies and workload allocators and then runs Elastic Stack clusters on those hosts.","infrastructureReviewed":"2026-11-15","infrastructureSources":["https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install"],"install":"Official ECE installation script on prepared AWS, Azure or Google Cloud Linux hosts","installMethods":["other"],"kind":"product","license":"Commercial Elastic Cloud Enterprise license required after the trial.","licenseModel":"commercial-only","licenseModelNotes":"ECE starts with a 30-day trial and then requires a valid Elastic Cloud Enterprise orchestration license.","licenseModelSources":["https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-ece"],"licenseReviewed":"2026-11-15","model":"Fully in your account","modelLabel":"Customer-operated","name":"Elastic Cloud Enterprise","notes":"This entry covers Elastic Cloud Enterprise, not Elastic Cloud Hosted or Elastic Cloud Serverless. ECE requires supported Linux and container-engine combinations, dedicated storage planning and coordinated host maintenance; automatic cloud VM patching can disrupt the platform. Elastic Cloud Enterprise 3.8.6 and 4.2.1 fix seven platform-role, retained credential and CA key, cross-deployment symlink, role-token, and platform-setting issues. Certificate-rotation users must complete the documented cleanup after upgrade, and operators should review or revoke persistent role tokens. Elastic's CVE-2026-114938 advisory states Elasticsearch 7.17.3 and later can be affected on x86-64 AVX512_VBMI CPUs. Authenticated read access can permit RCE and unauthenticated access can cause denial of service. Planned ECE 4.2.2 and 3.8.7 were not yet released at review time; until fixed images are available, apply -XX:-UseBASE64Intrinsics, restart every deployment and follow Elastic's rollout guidance.","operations":"Customer manages cloud instances, Linux and container runtime compatibility, XFS storage, networking, DNS, certificates, host maintenance, capacity, backups, upgrades and licensing.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Install Elastic Cloud Enterprise","url":"https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/install"},{"title":"Elastic Cloud Enterprise overview","url":"https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise"},{"title":"Manage an Elastic Cloud Enterprise license","url":"https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-ece"},{"title":"Elastic Cloud Enterprise release notes","url":"https://www.elastic.co/docs/release-notes/cloud-enterprise"},{"title":"Elastic Cloud Enterprise 4.2.1 security update ESA-2026-216","url":"https://discuss.elastic.co/t/elastic-cloud-enterprise-ece-3-8-6-and-4-2-1-security-update-esa-2026-216/391263"},{"title":"Elastic Java4Shell advisory for ECE","url":"https://discuss.elastic.co/t/java4shell-remote-code-execution-rce-vulnerability-cve-2026-114938/391703"}],"url":"https://launchinyourcloud.com/directory/elastic-cloud-enterprise/","website":"https://www.elastic.co/cloud/cloud-enterprise"},{"advisories":[{"action":"Upgrade to ECK 3.5.0 or later and rotate the service token where directed.","conditions":"Namespace boundaries, service tokens, and managed resource lifecycle determine exposure. CVE-2026-72648 has no workaround.","id":"elastic-cloud-on-kubernetes-3-5-0-security-update","listingIds":["elastic-cloud-on-kubernetes"],"reviewed":"2026-11-18","scope":"Affected ECK releases before 3.5.0; exact component and configuration ranges follow the three advisories.","source":"https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493","summary":"ESA-2026-113, 145, and 146 fix service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials.","supportingSources":[{"title":"ESA-2026-145","url":"https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-145/390105"},{"title":"ESA-2026-146","url":"https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-146/390106"}],"title":"Elastic Cloud on Kubernetes 3.5.0 security update","type":"security-advisory"}],"architecture":"Customer-operated Kubernetes operator and Elastic Stack stateful workloads with persistent storage.","categories":["databases-vector","observability","data-analytics","ai-tools"],"category":"Databases \u0026 vector","categoryFit":{"ai-tools":"Vector search and licensed machine-learning capabilities support retrieval and AI-oriented workloads.","data-analytics":"Search, aggregations and Kibana visualizations support interactive analysis of indexed data.","databases-vector":"Elasticsearch provides distributed document storage, full-text search and vector search in a customer cluster.","observability":"Elastic Stack collects and analyzes logs, metrics and traces; exact integrations and features depend on the selected license."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Elastic documents ECK for managed Kubernetes services including Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine. The customer owns and operates the cluster and persistent storage.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Elastic Cloud on Kubernetes on EKS, AKS and GKE","url":"https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s","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":"Elastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.","diligence":{"airGap":{"availability":"available","reviewed":"2026-11-17","scope":"ECK isolated deployment with all selected dependencies staged","source":"https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/air-gapped-install","status":"documented","summary":"ECK documents offline operation with locally mirrored operator and Elastic Stack images. Integrations also need local package, artifact and endpoint repositories; mirroring the operator alone is insufficient.","supportingSources":[{"title":"Additional offline dependency repositories","url":"https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/eck-gdch"}]},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Elastic Cloud on Kubernetes; unresolved within this edition/deployment","source":"https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/eck-gdch","status":"inconclusive","summary":"A GDC air-gapped BYOL Marketplace route does not establish AWS Marketplace commitment treatment for a self-managed ECK Enterprise subscription."},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck","status":"inconclusive","summary":"The reviewed Elastic Cloud on Kubernetes 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":{"estimate":{"currency":"USD","exclusions":["Software licence and support","Operating labor","Backups and recovery testing","Load balancing, NAT/endpoints, IPv4 and all data transfer","Monitoring, mail and other services","Taxes and discounts","Additional ingest/ML nodes, snapshots and licences","Index expansion beyond the assumed primary-data size"],"kind":"partial-infrastructure","period":"month","region":"AWS us-east-1","rows":[{"description":"3 Linux r6i.2xlarge VMs × 730 hours; capacity is an editorial planning choice, not a vendor 100-user benchmark","id":"compute","quantity":2190,"rate":0.504},{"description":"3150 GB provisioned gp3 capacity, including stated boot/data allowance; base IOPS/throughput only","id":"storage","quantity":3150,"rate":0.08},{"description":"One EKS cluster on standard version support; Auto Mode, paid add-ons and observability excluded","id":"external","quantity":730,"rate":0.1},{"description":"Unpriced; include if required by the selected topology","id":"database","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"backup","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"network","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"license","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"labor","quantity":1,"rate":""}],"workload":"100 internal users; 1 TB (1,000 GB) logical data; HA target; average usage unmeasured; 730 h/month. See reviewed scope for topology, replication, retention and sizing assumptions."},"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":"Editorial ECK scenario; load/ingest rate and indexed-data expansion must be measured. Separate shard/zone placement and failure testing are required. No Savings Plans, Spot or credits.","source":"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","status":"inconclusive","summary":"Illustrative priced infrastructure subtotal: USD 1,428.76/month. Three 8-vCPU/64-GiB workers across three AZs host three master/data nodes and two Kibana replicas. The storage assumption is 1,000 GB primary indexed data plus one replica, with 3,000 GB total data capacity and 150 GB boot capacity. This is not a complete operating-cost estimate or a validated capacity/SLA claim.","supportingSources":[{"title":"Product topology/sizing basis","url":"https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/nodes-orchestration"},{"title":"Current AWS documentation: us-east-1 gp3 capacity example","url":"https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html"},{"title":"EBS performance and charging qualifications","url":"https://aws.amazon.com/ebs/pricing/"},{"title":"EKS standard versus extended support pricing","url":"https://aws.amazon.com/eks/pricing/"}]},"footprint":{"reviewed":"2026-11-17","scope":"ECK availability topology, not benchmarked resource sizing","source":"https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/nodes-orchestration","status":"documented","summary":"HA guidance calls for three master-eligible nodes, multiple nodes per data tier and at least one index replica. CPU, memory, shard layout and disk headroom depend on indexing/search workload; no universal 100-user minimum is established."},"iac":{"reviewed":"2026-11-17","scope":"Self-managed ECK operator installation","source":"https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/install","status":"documented","summary":"Elastic supplies ECK installation through Helm or Kubernetes manifests. Pin the operator and compatible Elastic application versions and configure persistent storage and RBAC; the operator is not a vendor-operated service."},"licensePricing":{"reviewed":"2026-11-17","scope":"Elastic Cloud on Kubernetes: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-eck","status":"documented","summary":"The ECK and Elastic Stack distribution is governed by Elastic License 2.0 rather than an OSI-approved open-source license. A free Basic tier is available; Enterprise features and support require a subscription."},"marketplace":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"ECK in GDC air-gapped Marketplace; separate from hosted Elastic procurement","source":"https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/eck-gdch","status":"documented","summary":"Elastic documents an ECK BYOL offering inside Google Distributed Cloud air-gapped Marketplace. This is a specific isolated GDC deployment route, not proof that an Elastic Cloud Hosted marketplace subscription delivers ECK in a customer AWS account."},"release":{"reviewed":"2026-11-18","scope":"ECK operator 3.5.0 security update","source":"https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493","status":"documented","summary":"Elastic Cloud on Kubernetes 3.5.0 fixes service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. Rotate the service token after upgrade where ESA-2026-113 requires it."},"scim":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Elastic Cloud on Kubernetes; unresolved within this edition/deployment","source":"https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck","status":"inconclusive","summary":"ECK documents external realms and native/file user management, but a native ECK application SCIM provisioning endpoint was not established. Ingesting another product’s SCIM audit logs is not SCIM support."},"securityControls":{"reviewed":"2026-11-18","scope":"ECK managed credentials and external realms Affected ECK releases before 3.5.0; exact component and configuration ranges follow the three advisories.","source":"https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493","status":"documented","summary":"ECK manages credentials in Kubernetes secrets and supports rotation and disabling the default elastic superuser when using external identity. Restrict secret/RBAC access and configure application roles. Current advisory review: ESA-2026-113, 145, and 146 fix service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. Upgrade to ECK 3.5.0 or later and rotate the service token where directed.","supportingSources":[{"title":"Prior security-controls source","url":"https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck"},{"title":"ESA-2026-145","url":"https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-145/390105"},{"title":"ESA-2026-146","url":"https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-146/390106"}]},"sso":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"ECK application authentication; subscription eligibility must be checked","source":"https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/managed-credentials-eck","status":"documented","summary":"ECK deployments can configure Elasticsearch/Kibana external SAML or OIDC realms, with the applicable self-managed subscription. Elastic Cloud organization SSO is a separate control plane.","supportingSources":[{"title":"Self-managed subscription feature matrix","url":"https://www.elastic.co/pricing/self-managed"}]}},"id":"elastic-cloud-on-kubernetes","infrastructure":["servers"],"infrastructureNotes":"ECK manages persistent Elasticsearch and related container workloads on customer Kubernetes with durable volumes and operator reconciliation.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s","https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/install"],"install":"Official ECK Helm chart or Kubernetes manifests on EKS, AKS or GKE","installMethods":["helm","kubernetes"],"kind":"platform","license":"Elastic License 2.0 distribution with free Basic capabilities; Enterprise licensing unlocks additional features and support.","licenseModel":"source-available","licenseModelNotes":"The ECK and Elastic Stack distribution is governed by Elastic License 2.0 rather than an OSI-approved open-source license. A free Basic tier is available; Enterprise features and support require a subscription.","licenseModelSources":["https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-eck","https://www.elastic.co/pricing/self-managed"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"Elastic Cloud on Kubernetes","notes":"This entry covers self-managed Elastic Cloud on Kubernetes, not Elastic Cloud Hosted or Elastic Cloud Enterprise. ECK automates application lifecycle but does not transfer cluster, storage, backup or upgrade responsibility to Elastic. The free Basic license and paid Enterprise feature set differ; optional Cloud Connect services create separate external dependencies. ECK 3.5.0 fixes service-token exposure, cross-namespace certificate injection, and retained cross-namespace credentials. CVE-2026-72648 has no workaround; after upgrading, rotate the affected service token as Elastic directs.","operations":"Customer manages Kubernetes, storage, resource sizing, security, snapshots, upgrades and availability; Elastic licensing controls advanced features and support.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Deploy Elastic Cloud on Kubernetes","url":"https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s"},{"title":"Install ECK with Helm or manifests","url":"https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/install"},{"title":"Manage the ECK license","url":"https://www.elastic.co/docs/deploy-manage/license/manage-your-license-in-eck"},{"title":"Self-managed Elastic pricing and editions","url":"https://www.elastic.co/pricing/self-managed"},{"title":"ECK 3.5.0 security update ESA-2026-113","url":"https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-113/389493"},{"title":"ECK 3.5.0 security update ESA-2026-145","url":"https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-145/390105"},{"title":"ECK 3.5.0 security update ESA-2026-146","url":"https://discuss.elastic.co/t/elastic-cloud-on-kubernetes-3-5-0-security-update-esa-2026-146/390106"}],"url":"https://launchinyourcloud.com/directory/elastic-cloud-on-kubernetes/","website":"https://www.elastic.co/elastic-cloud-kubernetes"},{"architecture":"Dedicated customer-cloud instances run task brokers and reactors. Estuary's control plane starts connectors and applies task configurations.","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Captures, transforms, and delivers data to analytical destinations through managed connectors."},"cloudEvidence":[{"clouds":["aws"],"notes":"The documented cross-account IAM role uses an external ID and grants AmazonEC2FullAccess.","reviewed":"2026-11-21","sourceType":"vendor-documentation","title":"Estuary BYOC on AWS","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The guide adds Estuary's deployment application and grants a role scoped to the customer's subscription.","reviewed":"2026-11-21","sourceType":"vendor-documentation","title":"Estuary BYOC on Azure","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The guide asks for project-level Editor access for Estuary's controller principal.","reviewed":"2026-11-21","sourceType":"vendor-documentation","title":"Estuary BYOC on Google Cloud","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-21","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"vendor-hosted","evidence":[0],"operator":"vendor"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"vendor-hosted","evidence":[1],"operator":"vendor"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"vendor-hosted","evidence":[2],"operator":"vendor"}],"description":"Managed data capture, transformation, and delivery with a dedicated data plane in the customer's cloud account.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Dedicated Enterprise BYOC data plane; quantitative production sizing unresolved.","source":"https://docs.estuary.dev/private-byoc/networking/","status":"inconclusive","summary":"The networking guide identifies broker/reactor instances, coordination and management access, but does not publish a quantitative CPU/RAM/storage baseline or HA topology. Estuary sizes the managed data plane during onboarding. Obtain connector counts, data rates, retention, replay and recovery requirements before selecting resources; 100 users and 1 TB alone do not size a streaming pipeline."},"iac":{"reviewed":"2026-11-21","scope":"Estuary-managed BYOC runtime deployment artifact unresolved.","source":"https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/","status":"inconclusive","summary":"The provider guides document permissions and vendor-assisted provisioning. The AWS example creates a delegated IAM role with an external ID and AmazonEC2FullAccess; it does not expose a reviewed, versioned data-plane deployment template. Obtain the actual provisioning artifact, permission scope and rollback procedure from Estuary. An IAM policy example alone does not establish a reusable runtime installer.","supportingSources":[{"title":"Azure onboarding permissions","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/"},{"title":"Google Cloud onboarding permissions","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/"}]},"licensePricing":{"reviewed":"2026-11-21","scope":"Enterprise managed BYOC commercial terms and separate cloud bill; request a quote.","source":"https://docs.estuary.dev/getting-started/pricing/","status":"documented","summary":"BYOC is available on annual or multi-year Enterprise contracts with custom pricing based on data volume, connector instances, deployment model, term and support. The customer pays the cloud provider directly for infrastructure. Public Cloud-plan per-GB/task-hour examples do not quote the BYOC contract."},"scim":{"availability":"unavailable","reviewed":"2026-11-21","scope":"Documented Estuary dashboard provisioning flow for Enterprise BYOC.","source":"https://docs.estuary.dev/getting-started/sso-setup/","status":"documented","summary":"Estuary explicitly documents just-in-time SSO account creation rather than SCIM. Tenant administrators invite users and assign access after the SSO account is created. SAML support does not establish SCIM lifecycle provisioning."},"sso":{"availability":"available","reviewed":"2026-11-21","scope":"Enterprise BYOC dashboard SSO; coordinate domain and IdP configuration with Estuary.","source":"https://docs.estuary.dev/getting-started/sso-setup/","status":"documented","summary":"Enterprise plans, including BYOC, include SSO. Estuary documents support-assisted SAML 2.0 configuration for its hosted dashboard, with domain metadata and just-in-time account creation. This is control-plane user identity, separate from connector credentials and data-plane authentication.","supportingSources":[{"title":"Enterprise BYOC and SSO entitlement","url":"https://docs.estuary.dev/getting-started/pricing/"}]}},"id":"estuary-byoc","infrastructure":["servers"],"infrastructureNotes":"Dedicated customer-cloud instances run task brokers and reactors. Estuary's control plane starts connectors and applies task configurations.","infrastructureReviewed":"2026-11-21","infrastructureSources":["https://docs.estuary.dev/private-byoc/networking/"],"install":"Arrange Enterprise BYOC onboarding and grant the documented permissions in a separate AWS account, Azure subscription, or Google Cloud project.","installMethods":["vendor-assisted"],"kind":"platform","license":"Commercial BYOC under an annual Enterprise agreement with custom pricing.","licenseModel":"commercial-only","licenseModelNotes":"Commercial BYOC under an annual Enterprise agreement with custom pricing.","licenseModelSources":["https://docs.estuary.dev/getting-started/pricing/"],"licenseReviewed":"2026-11-21","model":"BYOC","modelLabel":"Vendor-operated BYOC","name":"Estuary BYOC","notes":"The data plane accepts connections from Estuary's control plane and authorized users. Pipeline specifications can be pulled with flowctl. Confirm storage export and account teardown with Estuary.","operationReview":{"controlPlane":"vendor-hosted","modelLabel":"Vendor-operated BYOC","operator":"vendor","reviewed":"2026-11-21","source":"https://docs.estuary.dev/private-byoc/byoc-deployments/","summary":"Estuary provisions, patches, scales and removes the customer-account data plane. Its vendor-operated control plane starts connectors and applies task configuration; the customer governs the surrounding cloud account, permissions and network policies.","supportingSources":[{"title":"Control-plane and management connectivity","url":"https://docs.estuary.dev/private-byoc/networking/"}]},"operations":"Estuary provisions and manages data-plane resources, including patching, scaling, and deletion. The customer owns the cloud environment and manages its surrounding firewall, routing, and policies.","publisher":false,"reviewed":"2026-11-21","sources":[{"title":"BYOC operating model","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/"},{"title":"Data-plane network requirements","url":"https://docs.estuary.dev/private-byoc/networking/"},{"title":"Enterprise BYOC pricing","url":"https://docs.estuary.dev/getting-started/pricing/"},{"title":"Pull published specifications","url":"https://docs.estuary.dev/guides/flowctl/edit-specification-locally/"},{"title":"Estuary BYOC on AWS","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/aws-byoc/"},{"title":"Estuary BYOC on Azure","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/azure-byoc/"},{"title":"Estuary BYOC on Google Cloud","url":"https://docs.estuary.dev/private-byoc/byoc-deployments/gcp-byoc/"}],"url":"https://launchinyourcloud.com/directory/estuary-byoc/","website":"https://estuary.dev/"},{"architecture":"Ever Gauzy application/API, database and required workers using provider-specific deployment recipes.","categories":["project-management","hr-employee-records-management"],"category":"Project management","categoryFit":{"hr-employee-records-management":"Open-source business operations platform for people, projects, time and financial records.","project-management":"Open-source business operations platform for people, projects, time and financial records."},"cloudEvidence":[{"clouds":["aws"],"notes":"Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"AWS Guide","url":"https://docs.gauzy.co/deployment/cloud/aws-deployment/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Azure Guide","url":"https://docs.gauzy.co/deployment/cloud/azure-deployment/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"GCP Guide","url":"https://docs.gauzy.co/deployment/cloud/gcp-deployment/","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"DO Guide","url":"https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/","vendorSupport":"not-assessed"},{"clouds":["heroku"],"notes":"Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Heroku Guide","url":"https://docs.gauzy.co/deployment/cloud/heroku-deployment/","vendorSupport":"not-assessed"},{"clouds":["fly"],"notes":"Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Fly.io Guide","url":"https://docs.gauzy.co/deployment/cloud/flyio-deployment/","vendorSupport":"not-assessed"},{"clouds":["railway"],"notes":"Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.","reviewed":"2026-11-19","sourceType":"community-template","title":"Railway","url":"https://railway.com/deploy/ever-gauzy","vendorSupport":"not-assessed"},{"clouds":["render"],"notes":"Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Render Guide","url":"https://docs.gauzy.co/deployment/cloud/render-deployment/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","azure","gcp","digitalocean","heroku","fly","railway","render"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/ever-co/ever-gauzy/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/ever-co/ever-gauzy"}],"summary":"The reviewed upstream contributor history includes evereq, rahul-rocket, adkif, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-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"},{"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":"platform-workspace","cloud":"fly","controlPlane":"not-assessed","evidence":[5],"operator":"customer"},{"boundary":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[6],"operator":"customer"},{"boundary":"platform-workspace","cloud":"render","controlPlane":"not-assessed","evidence":[7],"operator":"customer"}],"description":"Open-source business operations platform for people, projects, time and financial records.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Published AWS example allocations, not a 100-user/1-TB HA minimum or current operating-cost estimate","source":"https://docs.gauzy.co/deployment/cloud/aws-deployment/","status":"documented","summary":"The AWS guide illustrates two Fargate tasks at 1 vCPU/2 GB each, a db.t3.medium database with a 50-GB provisioning example and cache.t3.micro Redis. These are example service sizes from the guide, with file storage and load balancing additional; its advertised cost table is not a reference-workload quote."},"iac":{"reviewed":"2026-11-21","scope":"Vendor-documented customer AWS deployment recipe; complete production configuration and version alignment require review","source":"https://docs.gauzy.co/deployment/cloud/aws-deployment/","status":"documented","summary":"The official AWS guide provides service architecture, CLI provisioning and ECS task configuration for the application, PostgreSQL, Redis and S3. Configure images, task resources, secrets, networking and persistence for production; the illustrative commands are not a supplied complete CloudFormation stack."},"licensePricing":{"reviewed":"2026-11-19","scope":"Ever Gauzy; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://github.com/ever-co/ever-gauzy/blob/develop/LICENSE","status":"documented","summary":"GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"sso":{"availability":"available","reviewed":"2026-11-21","scope":"Upstream application-user social OAuth configuration; not proof of arbitrary enterprise SAML or SCIM support","source":"https://docs.gauzy.co/authentication/social-auth/","status":"documented","summary":"The vendor documents application-user OAuth login with Google, GitHub, Facebook, Twitter, LinkedIn and Microsoft, including registered clients and instance callback settings. Provider login and the application JWT session/API mechanism are distinct configuration layers."}},"id":"ever-gauzy","infrastructure":["servers"],"infrastructureNotes":"Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://docs.gauzy.co/deployment/cloud/aws-deployment/","https://docs.gauzy.co/deployment/cloud/azure-deployment/","https://docs.gauzy.co/deployment/cloud/gcp-deployment/","https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/","https://docs.gauzy.co/deployment/cloud/heroku-deployment/","https://docs.gauzy.co/deployment/cloud/flyio-deployment/","https://railway.com/deploy/ever-gauzy","https://docs.gauzy.co/deployment/cloud/render-deployment/"],"install":"Application platform deployment","installMethods":["platform-template"],"kind":"product","license":"GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://github.com/ever-co/ever-gauzy/blob/develop/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Ever Gauzy","notes":"The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.","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 Guide","url":"https://docs.gauzy.co/deployment/cloud/aws-deployment/"},{"title":"Azure Guide","url":"https://docs.gauzy.co/deployment/cloud/azure-deployment/"},{"title":"GCP Guide","url":"https://docs.gauzy.co/deployment/cloud/gcp-deployment/"},{"title":"DO Guide","url":"https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/"},{"title":"Heroku Guide","url":"https://docs.gauzy.co/deployment/cloud/heroku-deployment/"},{"title":"Fly.io Guide","url":"https://docs.gauzy.co/deployment/cloud/flyio-deployment/"},{"title":"Railway","url":"https://railway.com/deploy/ever-gauzy"},{"title":"Render Guide","url":"https://docs.gauzy.co/deployment/cloud/render-deployment/"},{"title":"AGPL-3.0 LICENSE","url":"https://github.com/ever-co/ever-gauzy/blob/develop/LICENSE"},{"title":"Releases v111.250.0","url":"https://github.com/ever-co/ever-gauzy/releases"}],"url":"https://launchinyourcloud.com/directory/ever-gauzy/","website":"https://gauzy.co"},{"advisories":[{"action":"Upgrade to v2.292.0 or later, configure the SSRF allowlist, and retest nested writes.","conditions":"Applicability depends on outbound request configuration, nested-resource writes, and the affected dependency.","id":"flagsmith-2-292-0-security-hardening","listingIds":["flagsmith"],"reviewed":"2026-11-18","scope":"Upstream v2.292.0 release notes; no consolidated affected-version range is asserted.","source":"https://github.com/Flagsmith/flagsmith/releases/tag/v2.292.0","summary":"Flagsmith v2.292.0 adds SSRF allowlisting, corrects nested-write authorization scope, and updates a security dependency.","title":"Flagsmith 2.292.0 request and authorization hardening","type":"security-advisory"}],"architecture":"Customer-operated dashboard and Django API with PostgreSQL persistence and optional processing services","categories":["feature-management"],"category":"Feature management","categoryFit":{"feature-management":"Feature flags, remote configuration, user targeting, segments and multivariate release control; advanced edition features are separate."},"cloudEvidence":[{"clouds":["aws","azure","gcp","digitalocean"],"deploymentBoundaries":{"digitalocean":"not-assessed"},"notes":"The vendor explicitly names AWS, Google Cloud, Azure and DigitalOcean for team-managed Docker or Kubernetes deployments. This is a self-hosted application compatibility statement, distinct from managed Flagsmith SaaS; configure the backing services, security and edition-specific entitlements.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Flagsmith self-hosted platform architecture","url":"https://docs.flagsmith.com/flagsmith-concepts/platform-architecture","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp","digitalocean"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Current releases","url":"https://github.com/Flagsmith/flagsmith/releases"},{"title":"Open-source development and core scope","url":"https://www.flagsmith.com/open-source"},{"title":"Named production adoption","url":"https://www.flagsmith.com/case-studies/wistia"}],"summary":"The project publishes frequent 2026 releases and a documented public development model. Its named Wistia case study describes production feature-flag adoption; the case study alone does not certify a self-hosted deployment boundary."},"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"}],"description":"Feature management platform for targeted rollouts and remotely configured application behavior.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Official per-pod allocation guidance; database/warehouse and HA resources are separate","source":"https://docs.flagsmith.com/deployment-self-hosting/hosting-guides/kubernetes-openshift","status":"documented","summary":"The Kubernetes guide leaves resource requests/limits unset by default and recommends limits of 1 vCPU and 2 GB RAM per pod, subject to workload. PostgreSQL, evaluation/SSE traffic, replicas and any experimentation warehouse need separate capacity. These are pod limits, not a whole-host or HA minimum."},"iac":{"artifactRef":"main (moving branch)","artifactUrl":"https://raw.githubusercontent.com/Flagsmith/flagsmith/main/docker-compose.yml","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://docs.flagsmith.com/deployment-self-hosting/hosting-guides/docker","status":"documented","summary":"The official Docker guide downloads an upstream Compose environment for dashboard/API and supporting services. It is a local setup starting point; configure production secrets, network access, database persistence and edition requirements."},"licensePricing":{"reviewed":"2026-11-20","scope":"Published OSS core terms; commercial features and infrastructure are separate","source":"https://github.com/Flagsmith/flagsmith/blob/v2.292.0/LICENSE.md","status":"documented","summary":"The published v2.292.0 core uses BSD 3-Clause terms. This does not include every Enterprise authentication, support or on-premises entitlement; choose the edition and agreement separately. Application/database hosting, SDK evaluation traffic, experimentation storage and operations have separate costs."},"release":{"releasePublishedAt":"2026-11-17T17:14:04Z","releaseTag":"v2.292.0","reviewed":"2026-11-18","scope":"Upstream Flagsmith self-hosted release","source":"https://github.com/Flagsmith/flagsmith/releases/tag/v2.292.0","status":"documented","summary":"Flagsmith v2.292.0 was published November 17, 2026. It adds SSRF allowlisting, corrects nested-write scope, adds organization audit-log UI, and updates dnspython for security."},"securityControls":{"reviewed":"2026-11-18","scope":"Upstream v2.292.0 release notes; no consolidated affected-version range is asserted.","source":"https://github.com/Flagsmith/flagsmith/releases/tag/v2.292.0","status":"documented","summary":"Current advisory review: Flagsmith v2.292.0 adds SSRF allowlisting, corrects nested-write authorization scope, and updates a security dependency. Upgrade to v2.292.0 or later, configure the SSRF allowlist, and retest nested writes."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Enterprise self-hosted/on-premises features","source":"https://docs.flagsmith.com/flagsmith-concepts/platform-architecture","status":"documented","summary":"The platform architecture identifies advanced authentication including Okta, LDAP, SAML and ADFS in Enterprise on-premises deployments. Confirm the licensed integration and protocol configuration for the chosen package."}},"id":"flagsmith","infrastructure":["servers"],"infrastructureNotes":"Customer-operated dashboard and Django API with PostgreSQL persistence and optional processing services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.flagsmith.com/deployment-self-hosting/hosting-guides/docker"],"install":"Deploy the official Docker Compose environment and configure the dashboard/API, PostgreSQL and application SDK endpoints.","installMethods":["docker"],"kind":"product","license":"BSD-3-Clause for upstream core functionality; supported Enterprise editions and commercial features have separate terms.","licenseModel":"open-source","licenseModelNotes":"BSD-3-Clause for upstream core functionality; supported Enterprise editions and commercial features have separate terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.","licenseModelSources":["https://raw.githubusercontent.com/Flagsmith/flagsmith/main/LICENSE.md"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Flagsmith Self-Hosted","notes":"The local Compose guide is an evaluation path requiring production hardening. Point SDKs to the self-hosted endpoint; experimentation can add warehouse and ingestion services with separate operational requirements. Flagsmith v2.291.0 fixes existing authentication tokens remaining valid after a password change or reset, an identities search that could bring down the database, a security update to oauthlib, and trust in compromised eMudhra certificate authorities. Self-hosted operators should upgrade so password changes invalidate existing dashboard tokens and the database-search safeguards are present. Flagsmith v2.292.0 adds SSRF allowlisting, scopes nested writes correctly, exposes organization audit logs, and updates dnspython for security. Review outbound destinations and nested-resource authorization after upgrading.","operations":"Customer manages flag API availability, SDK endpoints, database, permissions, secrets, backups and upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Official installation and runtime","url":"https://docs.flagsmith.com/deployment-self-hosting/hosting-guides/docker"},{"title":"Upstream project and capabilities","url":"https://github.com/Flagsmith/flagsmith"},{"title":"Current upstream license","url":"https://raw.githubusercontent.com/Flagsmith/flagsmith/main/LICENSE.md"},{"title":"Flagsmith v2.291.0 security and reliability fixes","url":"https://github.com/Flagsmith/flagsmith/releases/tag/v2.291.0"},{"title":"Password-change token revocation security issue","url":"https://github.com/Flagsmith/flagsmith/issues/8651"},{"title":"Flagsmith v2.292.0 release","url":"https://github.com/Flagsmith/flagsmith/releases/tag/v2.292.0"}],"url":"https://launchinyourcloud.com/directory/flagsmith/","website":"https://www.flagsmith.com/"},{"advisories":[{"action":"Remove fragments from registered redirects before upgrading, test SAML integrations and explicitly configure the paid rate limit if required. Recheck older provider packages.","conditions":"Exposure depends on SAML/redirect configuration. The new Enterprise rate limit is disabled by default and applies to the documented FormField strategy.","id":"fusionauth-1-71-0-security-review","listingIds":["fusionauth-self-hosted"],"reviewed":"2026-11-18","scope":"FusionAuth 1.71.0 release notes; the vendor does not establish a complete affected-version range or CVE for every change.","source":"https://fusionauth.io/docs/release-notes","summary":"The release hardens SAML parsing and rejects redirect URLs containing fragments. It also adds an optional Enterprise passwordless-code rate limit.","title":"FusionAuth 1.71.0 security and redirect configuration review","type":"security-advisory"}],"architecture":"FusionAuth application instances with a customer database and optional search, deployed on cloud Kubernetes or as a customer Render web service and PostgreSQL database.","categories":["identity-access-management"],"category":"Identity \u0026 access management","categoryFit":{"identity-access-management":"Provides customer-operated authentication, authorization, user management and federation for applications."},"cloudEvidence":[{"clouds":["aws"],"notes":"FusionAuth documents provisioning the cluster, database and full application in customer AWS infrastructure.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"FusionAuth on Amazon EKS","url":"https://fusionauth.io/docs/deploy/production/kubernetes/eks","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"FusionAuth documents the full application on a customer AKS cluster and Azure database resources.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"FusionAuth on Azure AKS","url":"https://fusionauth.io/docs/deploy/production/kubernetes/aks","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"FusionAuth documents the full application on customer GKE and Google Cloud database resources.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"FusionAuth on Google GKE","url":"https://fusionauth.io/docs/deploy/production/kubernetes/gke","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"The vendor and provider document a full FusionAuth 1-Click Kubernetes application. The provider catalog packages 1.53.3, older than the reviewed upstream release; validate upgrades and production database/HA design.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"FusionAuth in customer DigitalOcean Kubernetes","url":"https://fusionauth.io/docs/deploy/production/marketplaces/digitalocean","vendorSupport":"not-assessed"},{"clouds":["render"],"notes":"FusionAuth provides a Render blueprint deploying the full application and PostgreSQL in the customer’s account/project. Production needs paid resource capacity and a deliberate database/backup design.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"FusionAuth and PostgreSQL in customer Render","url":"https://fusionauth.io/docs/deploy/production/marketplaces/render","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-18","clouds":["aws","azure","gcp","digitalocean","render"],"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":"render","controlPlane":"not-assessed","evidence":[4],"operator":"customer"}],"description":"Proprietary identity platform with documented customer-account EKS, AKS, GKE, DigitalOcean and Render application/database deployments.","diligence":{"airGap":{"availability":"edition-dependent","reviewed":"2026-11-18","scope":"FusionAuth Self-Hosted: selected customer-operated edition","source":"https://fusionauth.io/docs/deploy/production/install/air-gapping","status":"documented","summary":"Enterprise documents an air-gapped licence, offline key activation and an expiry without a grace period; network-backed features and update feeds need separate handling. The requirements also state Community can block outbound access without a paid licence. Choose the plan and disable or supply reachable dependencies explicitly.","supportingSources":[{"title":"Community versus paid-plan network requirements","url":"https://fusionauth.io/docs/deploy/production/system-requirements"}]},"commitments":{"reviewed":"2026-11-18","scope":"FusionAuth Self-Hosted: selected customer-operated edition","source":"https://fusionauth.io/docs/deploy/production/marketplaces/aws","status":"inconclusive","summary":"The vendor’s AWS Marketplace subscription is FusionAuth Cloud. Its procurement terms do not establish commitment credit for a self-hosted licence. Confirm the selected self-hosted Enterprise order and buyer agreement separately.","supportingSources":[{"title":"AWS commitment qualification is product/agreement-specific","url":"https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html"}]},"compliance":{"reviewed":"2026-11-18","scope":"FusionAuth Self-Hosted: selected customer-operated edition","source":"https://trust.fusionauth.io/?format=html","status":"inconclusive","summary":"FusionAuth’s August 2025 announcement identifies AssurancePoint as its ISO 27001:2022 auditor. The current certificate/SOA and SOC 2 report remain request-gated, so their validity and self-hosted system boundary were not independently checked here. Its licence FAQ limits report access and requires Enterprise plus HA hosting for a BAA. Assess the actual report/customer controls; FIPS mode is explicitly not FIPS certification.","supportingSources":[{"title":"Licence and assurance FAQ","url":"https://fusionauth.io/license-faq"},{"title":"FIPS mode versus certification","url":"https://fusionauth.io/docs/security/compliance/"},{"title":"Named auditor and original announcement","url":"https://fusionauth.io/blog/fusionauth-iso27001-2025"}]},"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://fusionauth.io/docs/deploy/production/system-requirements","status":"inconclusive","summary":"Define monthly active users, peak logins/token operations, password-hash settings, identity/audit retention, database/search HA and selected paid features. One hundred internal users need not equal billable MAU, and 1 TB needs a database/log retention split. Include licences, backups, egress and operations.","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":"FusionAuth Self-Hosted: selected customer-operated edition","source":"https://fusionauth.io/docs/deploy/production/system-requirements","status":"documented","summary":"The application minimum is 512 MB RAM with 10–50 GB disk for application/log needs; database, operating system and optional search are additional. CPU depends on login rate and password hashing. Current releases bundle Java 25 and recommend tested PostgreSQL versions. Multiple app replicas and HA database/search require separate sizing."},"iac":{"artifactRef":"Moving repository default branch; reviewed 2026-11-18","artifactUrl":"https://github.com/FusionAuth/fusionauth-render-blueprint","reviewed":"2026-11-18","scope":"FusionAuth Self-Hosted: selected customer-operated edition","source":"https://fusionauth.io/docs/deploy/production/marketplaces/render","status":"documented","summary":"The vendor’s Render blueprint deploys FusionAuth and PostgreSQL into the customer’s Render account. The repository is a moving source, not an immutable image lockfile; fork/review it and select production capacity. EKS/AKS/GKE have separate production guides.","supportingSources":[{"title":"EKS deployment","url":"https://fusionauth.io/docs/deploy/production/kubernetes/eks"}]},"licensePricing":{"reviewed":"2026-11-18","scope":"FusionAuth Self-Hosted: selected customer-operated edition","source":"https://fusionauth.io/license","status":"documented","summary":"FusionAuth uses its proprietary Customer Licence Agreement, including the no-cost Community plan. Paid plan/MAU terms are separate; SCIM and the documented paid air-gap licence require Enterprise. Free Community is not an open-source software licence.","supportingSources":[{"title":"Self-hosting plan comparison","url":"https://fusionauth.io/pricing?hosting=self-hosting\u0026step=plan"},{"title":"SCIM Enterprise entitlement","url":"https://fusionauth.io/docs/users/provision/scim"}]},"marketplace":{"availability":"edition-dependent","offers":[{"cloud":"digitalocean","delivery":"Kubernetes 1-Click application","id":"fusionauth","publisher":"FusionAuth","url":"https://marketplace.digitalocean.com/apps/fusionauth","version":"1.53.3"}],"reviewed":"2026-11-18","scope":"FusionAuth Self-Hosted: selected customer-operated edition","source":"https://docs.digitalocean.com/products/marketplace/catalog/fusionauth/","status":"documented","summary":"DigitalOcean documents a FusionAuth Kubernetes 1-Click application, currently packaged as 1.53.3. That older package must not be presented as upstream 1.71.0. FusionAuth’s AWS Marketplace guide instead describes FusionAuth Cloud hosting; it is not the self-hosted EKS product.","supportingSources":[{"title":"AWS offer is hosted FusionAuth Cloud","url":"https://fusionauth.io/docs/deploy/production/marketplaces/aws"},{"title":"Vendor DigitalOcean package guide","url":"https://fusionauth.io/docs/deploy/production/marketplaces/digitalocean"}]},"release":{"releasePublishedOn":"2026-11-17","releaseTag":"1.71.0","reviewed":"2026-11-18","scope":"FusionAuth Self-Hosted: selected customer-operated edition","source":"https://fusionauth.io/docs/release-notes","status":"documented","summary":"FusionAuth 1.71.0 was released November 17, 2026. It includes security changes and rejects authorized redirect URLs containing fragments; test SAML and redirect configurations during upgrade. The DigitalOcean package remains 1.53.3 in the reviewed catalog.","supportingSources":[{"title":"Separate DigitalOcean package version","url":"https://docs.digitalocean.com/products/marketplace/catalog/fusionauth/"}]},"scim":{"availability":"edition-dependent","reviewed":"2026-11-18","scope":"FusionAuth Self-Hosted: selected customer-operated edition","source":"https://fusionauth.io/docs/users/provision/scim","status":"documented","summary":"SCIM 2.0 is an Enterprise-plan feature available from 1.36.0. FusionAuth acts as an inbound SCIM server for users/groups, with OAuth client credentials and configurable mappings. It is not a SCIM client provisioning other services; application registration remains separate."},"securityControls":{"reviewed":"2026-11-18","scope":"FusionAuth Self-Hosted: selected customer-operated edition","source":"https://fusionauth.io/docs/security/compliance/","status":"documented","summary":"Enterprise self-hosted FIPS mode is available from 1.62.0 only for new installations and requires every node in the cluster to use that mode, with separately compliant database/search components. This is a scoped configuration feature, not FIPS certification. SSO, token and provisioning controls require explicit configuration.","supportingSources":[{"title":"SCIM access control","url":"https://fusionauth.io/docs/users/provision/scim"},{"title":"Application SSO/session behavior","url":"https://fusionauth.io/docs/authentication/sessions/single-sign-on"}]},"sso":{"availability":"available","reviewed":"2026-11-18","scope":"FusionAuth Self-Hosted: selected customer-operated edition","source":"https://fusionauth.io/docs/authentication/sessions/single-sign-on","status":"documented","summary":"Self-hosted FusionAuth provides SSO between applications through its own login/session system and OIDC/SAML integration. Distinguish FusionAuth acting as the application identity provider from connecting an external IdP, and confirm the selected plan’s optional features."}},"id":"fusionauth-self-hosted","infrastructure":["servers"],"infrastructureNotes":"FusionAuth uses provisioned application capacity and persistent database state. Kubernetes and Render have different platform-operation boundaries; the customer selects and configures the application and database deployment.","infrastructureReviewed":"2026-11-18","infrastructureSources":["https://fusionauth.io/docs/deploy/production/kubernetes/"],"install":"Vendor Kubernetes/Helm guides, DigitalOcean Kubernetes 1-Click package, or Render application/PostgreSQL blueprint; versions and production topology differ","installMethods":["helm","kubernetes","platform-template"],"kind":"product","license":"FusionAuth Customer License Agreement; Community and paid plans are proprietary, with feature and support limits by plan.","licenseModel":"commercial-only","licenseModelNotes":"FusionAuth is proprietary under its Customer License Agreement, including the no-cost Community plan; paid plan capabilities require corresponding entitlements.","licenseModelSources":["https://fusionauth.io/license","https://fusionauth.io/docs/concepts/plans-and-limits/plans-features"],"licenseReviewed":"2026-11-18","model":"Fully in your account","modelLabel":"Customer-operated","name":"FusionAuth Self-Hosted","notes":"This is self-hosted FusionAuth, not FusionAuth Cloud. The AWS Marketplace guide sells hosted Cloud service; EKS remains a separately documented customer-hosted path. DigitalOcean’s 1-Click package is 1.53.3, distinct from upstream 1.71.0. SCIM and paid air-gap/FIPS options have Enterprise conditions; Render uses a customer-owned application/database blueprint.","operations":"Customer configures application releases, plan features, database/search, networking, TLS, secrets, backups and capacity. Kubernetes operations apply to cluster deployments; Render operates its platform while the customer configures the web service and managed database.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"FusionAuth on Kubernetes","url":"https://fusionauth.io/docs/deploy/production/kubernetes/"},{"title":"FusionAuth on Amazon EKS","url":"https://fusionauth.io/docs/deploy/production/kubernetes/eks"},{"title":"FusionAuth on Azure AKS","url":"https://fusionauth.io/docs/deploy/production/kubernetes/aks"},{"title":"FusionAuth on Google GKE","url":"https://fusionauth.io/docs/deploy/production/kubernetes/gke"},{"title":"FusionAuth license","url":"https://fusionauth.io/license"},{"title":"FusionAuth in customer DigitalOcean Kubernetes","url":"https://fusionauth.io/docs/deploy/production/marketplaces/digitalocean"},{"title":"FusionAuth and PostgreSQL in customer Render","url":"https://fusionauth.io/docs/deploy/production/marketplaces/render"}],"url":"https://launchinyourcloud.com/directory/fusionauth-self-hosted/","website":"https://fusionauth.io/"},{"advisories":[{"action":"Install a patched supported appliance release, follow the upgrade sequence and reapply custom firewall rules where required.","conditions":"Appliance component and network exposure determine applicability. The release notes also identify dependency updates that are only partial remediations.","id":"ghes-3-22-4-security-review","listingIds":["github-enterprise-server"],"reviewed":"2026-11-17","scope":"GitHub Enterprise Server 3.22.4 security release; other supported lines need their own branch-specific patch guidance.","source":"https://docs.github.com/en/enterprise-server@3.22/admin/release-notes","summary":"GHES 3.22.4 patches Active Storage file-read/code-execution, Git and Brotli vulnerabilities.","title":"GitHub Enterprise Server appliance security patch","type":"security-advisory"}],"architecture":"Customer-operated appliance VM with persistent data storage and optional high-availability nodes","categories":["devops"],"category":"DevOps","categoryFit":{"devops":"Provides customer-operated source control, pull requests, collaboration and software delivery workflows as a licensed virtual appliance."},"cloudEvidence":[{"clouds":["aws"],"notes":"GitHub documents launching its published appliance image on EC2 and attaching an EBS data volume in the customer's AWS account.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"GitHub Enterprise Server on AWS","url":"https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"GitHub documents deploying the appliance to a supported Azure VM with premium storage in the customer's subscription.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"GitHub Enterprise Server on Azure","url":"https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"GitHub documents deploying its appliance image to a supported Compute Engine VM with persistent disks in the customer's project.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"GitHub Enterprise Server on Google Cloud","url":"https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform","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":"Customer-operated GitHub software-development platform deployed as a licensed virtual appliance.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"GHES 3.21 AWS sizing by licensed users; feature and HA overhead additional","source":"https://docs.github.com/en/enterprise-server%403.21/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws","status":"documented","summary":"The GHES 3.21 AWS guide recommends 8 x86-64 vCPUs, 48 GB RAM, 400 GB root and 500 GB data disk at 3,000 IOPS for up to 1,000 user licences. Its 4-vCPU/32-GB tier is trial/demo or ten light users. Actions, code security, growth and HA replicas require extra resources."},"iac":{"artifactRef":"Release-specific regional image; choose a supported GHES version","artifactUrl":"https://enterprise.github.com/releases","reviewed":"2026-11-20","scope":"Official GHES 3.21 AWS appliance installation","source":"https://docs.github.com/en/enterprise-server%403.21/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws","status":"documented","summary":"The official AWS guide deploys the GitHub Enterprise Server appliance AMI into a customer VPC with configured instance, storage and security groups. Select the release-specific regional AMI and supply the Enterprise licence; this is a vendor appliance deployment guide rather than a public Terraform module."},"licensePricing":{"reviewed":"2026-11-20","scope":"GitHub Enterprise licensing across Server/Cloud; infrastructure additional","source":"https://docs.github.com/en/enterprise-server@3.21/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise","status":"documented","summary":"A GitHub Enterprise account can include both Server and Cloud under enterprise licensing, with unique users counted across deployments when usage is synchronized. The appliance requires a licence file; agree seats, billing model and optional security products. This is not a hosting or runner-cost quote."},"release":{"releasePublishedOn":"2026-11-17","releaseTag":"3.22.5","reviewed":"2026-11-18","scope":"GitHub Enterprise Server 3.22 appliance line","source":"https://docs.github.com/en/enterprise-server@3.22/admin/release-notes","status":"documented","summary":"GitHub Enterprise Server 3.22.5 was released November 17, 2026. It adds support-bundle and backup metrics, defaults new AWS roots to gp3, updates system packages for security, and fixes operational issues."},"sso":{"availability":"available","reviewed":"2026-11-14","scope":"GitHub Enterprise Server 3.22 appliance; not GitHub.com Enterprise Cloud","source":"https://docs.github.com/en/enterprise-server@3.22/admin/overview/about-github-enterprise-server","status":"documented","summary":"The versioned appliance overview documents external authentication with CAS, LDAP or SAML. Authentication, identity-provider reachability and account lifecycle need configuration."}},"id":"github-enterprise-server","infrastructure":["servers"],"infrastructureNotes":"The platform runs as one or more persistent virtual-machine appliances with attached data storage. Customer-cloud placement does not remove appliance sizing, backup, upgrade or availability responsibilities. GHES upgrades remove custom firewall rules; reapply any custom rules after upgrading.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance","https://docs.github.com/en/enterprise-server@latest/admin/overview/about-github-enterprise-server","https://docs.github.com/en/enterprise-server@3.22/admin/release-notes"],"install":"Official virtual-machine image on AWS, Azure or Google Cloud","installMethods":["vm-image"],"kind":"product","license":"Commercial GitHub Enterprise license required.","licenseModel":"commercial-only","licenseModelNotes":"GitHub Enterprise Server requires a purchased GitHub Enterprise license file that controls access and licensed users.","licenseModelSources":["https://docs.github.com/en/enterprise-server@latest/billing/concepts/enterprise-billing/ghes-license-files"],"licenseReviewed":"2026-11-14","model":"Fully in your account","modelLabel":"Customer-operated","name":"GitHub Enterprise Server","notes":"This entry covers GitHub Enterprise Server, not GitHub Enterprise Cloud. A valid license file is required. Review supported instance types, storage, backup utilities, upgrade paths and version support before deployment. GitHub Enterprise Server 3.22.4 fixes critical Active Storage file-read and remote-code-execution CVE-2026-66066, several high-severity Git vulnerabilities, and Brotli CVE-2026-111497. Upgrade to 3.22.4 or a later supported patch. GitHub Enterprise Server 3.22.5 adds support-bundle and backup metrics, defaults new AWS roots to gp3, updates system packages for security, and fixes operational issues. Follow the documented upgrade path and reapply custom firewall rules when required.","operations":"Customer provisions infrastructure and manages networking, storage, backups, upgrades, monitoring and high availability.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"GitHub Enterprise Server overview","url":"https://docs.github.com/en/enterprise-server@latest/admin/overview/about-github-enterprise-server"},{"title":"AWS installation","url":"https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws"},{"title":"Azure installation","url":"https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure"},{"title":"Google Cloud installation","url":"https://docs.github.com/en/enterprise-server@latest/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform"},{"title":"Enterprise Server license files","url":"https://docs.github.com/en/enterprise-server@latest/billing/concepts/enterprise-billing/ghes-license-files"},{"title":"GitHub Enterprise Server 3.22 release notes","url":"https://docs.github.com/en/enterprise-server@3.22/admin/release-notes"}],"url":"https://launchinyourcloud.com/directory/github-enterprise-server/","website":"https://github.com/enterprise"},{"advisories":[{"action":"Install the patched release for the deployed branch. Rebuild the required Git binaries for source installations, or use a distribution fix for the CVE.","conditions":"All installation types are covered unless the vendor identifies an exception. Source builds need both Gitaly-embedded Git and git.bin_path checked.","id":"gitlab-cve-2026-105437","listingIds":["gitlab"],"reviewed":"2026-11-17","scope":"GitLab CE/EE 16.2 to before 19.3.8, 19.4 to before 19.4.6, and 19.5 to before 19.5.4.","source":"https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/","summary":"CVE-2026-105437 concerns a Git heap-write flaw that can reach command execution inside Gitaly.","title":"GitLab bundled Git command-execution advisory","type":"security-advisory"},{"action":"Upgrade to 19.5.6, 19.4.8, or 19.3.9 for the deployed branch, or a later supported patch.","conditions":"Impact depends on enabled features, user roles, and exposed endpoints. This record does not replace the separate bundled-Git CVE review.","id":"gitlab-19-5-6-security-update","listingIds":["gitlab"],"reviewed":"2026-11-18","scope":"GitLab CE/EE patch lines 19.3, 19.4, and 19.5; consult the vendor table for the affected versions.","source":"https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/","summary":"GitLab 19.5.6, 19.4.8, and 19.3.9 fix a high-severity cross-site scripting issue and authorization weaknesses in CI/CD and workspaces.","title":"GitLab 19.5.6 security update","type":"security-advisory"},{"action":"Upgrade to 19.6.1, 19.5.8, or 19.4.10 as appropriate. For source builds, rebuild GitLab’s Ruby with 3.3.14, 3.4.13, or a later patch in the same minor series.","conditions":"Official Linux packages and container images carry the fixed Ruby. Self-compiled installations manage Ruby separately.","id":"gitlab-cve-2026-132825","listingIds":["gitlab"],"reviewed":"2026-11-20","scope":"Self-managed GitLab CE/EE releases before 19.4.10, 19.5 releases before 19.5.8, and 19.6 releases before 19.6.1, per GitLab.","source":"https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1","summary":"GitLab updated bundled Ruby for CVE-2026-132825 and related upstream Ruby security issues.","supportingSources":[{"title":"Upstream Ruby security advisory","url":"https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/"}],"title":"GitLab critical bundled Ruby security update","type":"security-advisory"}],"architecture":"Customer-operated application and storage","categories":["devops"],"category":"DevOps","categoryFit":{"devops":"Source control and CI/CD on infrastructure you operate."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"The upstream installation index links full GitLab Self-Managed deployment on AWS, Azure and Google Cloud. Choose the Linux package, chart or reference architecture appropriate to the selected edition, scale and supported release; a GitLab Runner alone is not the GitLab application.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"GitLab Self-Managed cloud installation guides","url":"https://docs.gitlab.com/install/cloud_providers/","vendorSupport":"not-assessed"},{"clouds":["alibaba"],"notes":"Alibaba documents GitLab Community Edition Docker deployment on Alibaba Cloud Linux 3 ECS as well as older package-based examples. Use the Community Edition path for this listing; JiHu GitLab is a separately distributed edition and old CentOS examples are not a current production recommendation.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"GitLab Community Edition on Alibaba Cloud ECS","url":"https://www.alibabacloud.com/help/en/ecs/user-guide/deploy-and-use-gitlab","vendorSupport":"not-assessed"},{"clouds":["oci"],"notes":"Oracle explicitly documents the GitLab application VM, customer tenancy, region, compartment, compute and VCN configuration, and administrator login. This confirms the provider deployment model. Its linked quick-start architecture has been retired, so these instructions do not establish a currently maintained one-click stack; validate the installer and supported GitLab release before using the legacy automation.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"Oracle GitLab application deployment in an OCI tenancy","url":"https://docs.oracle.com/cd/G26828_02/books/DeploySCM/c-installing-gitlab.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp","oci","alibaba"],"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":"cloud-account","cloud":"oci","controlPlane":"not-assessed","evidence":[2],"operator":"customer"},{"boundary":"cloud-account","cloud":"alibaba","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Source control and CI/CD on infrastructure you operate.","diligence":{"airGap":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Documented offline Self-Managed configuration, not default online installation","source":"https://docs.gitlab.com/topics/offline/","status":"documented","summary":"Self-Managed Free, Premium and Ultimate have an offline installation workflow. Transfer the correct packages/images and handle scanners, AI and update dependencies separately."},"commitments":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Vendor procurement statement; actual provider commitment terms govern eligibility","source":"https://about.gitlab.com/cloud-partner-marketplaces/","status":"documented","summary":"GitLab states eligible cloud-marketplace purchases can count toward committed spend on AWS or Google Cloud. Confirm the specific offer, billing account and buyer agreement; this is not an unconditional credit guarantee."},"footprint":{"reviewed":"2026-11-14","scope":"Self-Managed single-node baseline; not a total production cost estimate","source":"https://docs.gitlab.com/install/requirements/","status":"documented","summary":"The single-node baseline is 8 vCPU and 16 GB RAM. A memory-constrained configuration can use at least 8 GB; distributed sizing is component- and workload-specific."},"iac":{"artifactRef":"Select explicit version-ce.0 or version-ee.0 image tag","artifactUrl":"https://docs.gitlab.com/install/docker/installation/#install-gitlab-by-using-docker-compose","reviewed":"2026-11-20","scope":"Official self-managed Docker/Compose installation","source":"https://docs.gitlab.com/install/docker/installation/","status":"documented","summary":"The official self-managed guide publishes Compose YAML for versioned Community or Enterprise images with persistent configuration, logs and data. It warns against placing the all-in-one Docker image in Kubernetes; use the Helm chart/operator there. Configure hostname, TLS, secrets, backups and runner capacity separately."},"licensePricing":{"reviewed":"2026-11-20","scope":"GitLab Self-Managed instance-wide commercial tiers","source":"https://docs.gitlab.com/subscriptions/choosing_subscription/","status":"documented","summary":"GitLab Self-Managed offers tier-based subscriptions applying to the whole instance; all instance users share the selected features. A GitLab.com subscription cannot be transferred to Self-Managed. Select the required tier, seats and add-ons; this does not establish a complete hosting/support cost."},"marketplace":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Premium/Ultimate subscription procurement; self-hosting and SaaS offers must be distinguished","source":"https://about.gitlab.com/cloud-partner-marketplaces/","status":"documented","summary":"GitLab documents AWS Marketplace self-service/private offers and Google Cloud Marketplace private offers for paid subscriptions. Delivery/billing does not by itself change where a selected GitLab installation runs."},"release":{"releasePublishedOn":"2026-11-20","releaseTag":"19.6.1","reviewed":"2026-11-20","scope":"GitLab Self-Managed Community and Enterprise editions","source":"https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1","status":"documented","summary":"GitLab published 19.6.1 on November 20, 2026, with parallel Ruby security patches 19.5.8 and 19.4.10."},"scim":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"GitLab Self-Managed / Dedicated, Premium and Ultimate","source":"https://docs.gitlab.com/administration/settings/scim_setup/","status":"documented","summary":"SCIM is documented for Self-Managed Premium and Ultimate, with SAML configured. The API implements part of RFC7644; verify the supported identity provider and operations."},"securityControls":{"reviewed":"2026-11-20","scope":"GitLab Self-Managed CE/EE, including Linux packages, containers and self-compiled installations. The separate bundled Git fix has its own requirements.","source":"https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1","status":"documented","summary":"On November 20, GitLab issued CE/EE patches 19.6.1, 19.5.8, and 19.4.10 for CVE-2026-132825 and related Ruby flaws. GitLab recommends upgrading affected self-managed installations immediately. Official Linux packages and container images include patched Ruby. Source builds must rebuild the Ruby used by GitLab with 3.3.14 or 3.4.13, or a later patch in the same minor series.","supportingSources":[{"title":"Upstream Ruby security advisory","url":"https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/"}]},"sso":{"availability":"available","reviewed":"2026-11-14","scope":"GitLab Self-Managed instance authentication; not GitLab.com group SSO","source":"https://docs.gitlab.com/integration/saml/","status":"documented","summary":"Instance-wide SAML SSO is documented for Self-Managed Free, Premium and Ultimate. Group SAML and advanced group mapping have separate tier requirements."}},"id":"gitlab","infrastructure":["servers"],"infrastructureNotes":"The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://docs.gitlab.com/install/cloud_providers/","https://www.alibabacloud.com/help/en/ecs/user-guide/deploy-and-use-gitlab","https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/"],"install":"Linux package, container or Helm chart","installMethods":["helm","package","docker"],"kind":"platform","license":"Free and paid tiers","licenseModel":"open-source","licenseModelNotes":"Community Edition uses MIT terms; Enterprise Edition adds components under a more restrictive commercial license.","licenseModelSources":["https://docs.gitlab.com/development/licensing/"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"GitLab Self-Managed","notes":"GitLab documents AWS, Azure and Google Cloud installations. Oracle and Alibaba Cloud also publish deployment guides. These are documented deployment paths, not a promise of identical support or feature availability. Check operating system, edition and region requirements. GitLab 19.5.4, 19.4.6, and 19.3.8 patch critical CVE-2026-105437 in the bundled Git. Affected self-managed versions are 16.2 through versions before 19.3.8, 19.4 before 19.4.6, and 19.5 before 19.5.4. Upgrade immediately. Self-compiled deployments must also rebuild the Git binaries embedded in Gitaly and the Git installation referenced by git.bin_path, or use a distribution-patched Git 2.56.1 or later. GitLab 19.5.6, 19.4.8, and 19.3.9 address a high-severity cross-site scripting issue plus CI/CD and workspace authorization flaws. On November 20, GitLab issued CE/EE patches 19.6.1, 19.5.8, and 19.4.10 for CVE-2026-132825 and related Ruby flaws. GitLab recommends upgrading affected self-managed installations immediately. Official Linux packages and container images include patched Ruby. Source builds must rebuild the Ruby used by GitLab with 3.3.14 or 3.4.13, or a later patch in the same minor series.","operations":"Your team operates, upgrades and backs up the installation.","publisher":false,"reviewed":"2026-11-20","sources":[{"title":"GitLab cloud installation","url":"https://docs.gitlab.com/install/cloud_providers/"},{"title":"Alibaba Cloud deployment","url":"https://www.alibabacloud.com/help/en/ecs/user-guide/deploy-and-use-gitlab"},{"title":"Licensing and edition terms","url":"https://docs.gitlab.com/development/licensing/"},{"title":"Oracle GitLab application deployment in an OCI tenancy","url":"https://docs.oracle.com/cd/G26828_02/books/DeploySCM/c-installing-gitlab.html"},{"title":"GitLab critical patch release for CVE-2026-105437","url":"https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/"},{"title":"GitLab 19.5.6 security patch release","url":"https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-6-released/"},{"title":"GitLab 19.6.1 critical Ruby patch announcement","url":"https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-6-1-released/?nav=19.6.1"},{"title":"Upstream Ruby security advisory","url":"https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/"}],"url":"https://launchinyourcloud.com/directory/gitlab/","website":"https://about.gitlab.com/"},{"architecture":"Self-hosted management API and user interfaces, API gateways, MongoDB and Elasticsearch, with optional Redis, PostgreSQL and enterprise services","categories":["backend-platforms"],"category":"Backend platforms","categoryFit":{"backend-platforms":"Provides a self-hosted API gateway, management control plane, developer portal, policy engine and API lifecycle tooling."},"cloudEvidence":[{"applicableVersions":["4.10"],"clouds":["aws","azure","gcp"],"notes":"Gravitee's current self-hosted guide lists AWS EKS, Azure AKS and Google GKE as Kubernetes deployment methods and states that the customer manages both the control plane and data plane. Provider quick starts are development guidance rather than production architecture commitments.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Gravitee APIM self-hosted deployment on EKS, AKS or GKE","url":"https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-16","clouds":["aws","azure","gcp"],"communityAcceptance":{"reviewed":"2026-11-16","sources":[{"title":"Gravitee APIM releases","url":"https://github.com/gravitee-io/gravitee-api-management/releases"},{"title":"Gravitee APIM contributor history","url":"https://github.com/gravitee-io/gravitee-api-management/graphs/contributors"}],"summary":"Gravitee maintains public releases and contributor history for its Apache-licensed API Management project. This evidence establishes continuing upstream activity, not Enterprise support or production support for a particular cloud configuration."},"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":"Open-source and commercial self-hosted API management platform with documented EKS, AKS and GKE deployment paths.","diligence":{"compliance":{"reviewed":"2026-11-16","scope":"Published certificate-scope mismatch; current self-hosted APIM assurance remains unresolved","source":"https://www.gravitee.io/security-at-gravitee","status":"inconclusive","summary":"The security page’s printed certificate scope describes a marketing platform rather than APIM. That mismatch does not establish assurance for this listing; obtain a current certificate/report identifying the APIM organization, product boundary and validity dates."},"footprint":{"reviewed":"2026-11-16","scope":"Self-hosted component baselines, not the total platform footprint or guaranteed throughput","source":"https://documentation.gravitee.io/apim/4.10/prepare-a-production-environment/gateway-resource-sizing-guidelines","status":"documented","summary":"The APIM 4.10 guide gives the combined Portal/Console/REST API a baseline of 2 vCPU, 4 GB RAM and 20 GB disk. Gateways, analytics and configuration databases are additional; production HA recommends multiple nodes and traffic-dependent sizing."},"iac":{"artifactRef":"master (moving branch; select a chart compatible with APIM 4.10)","artifactUrl":"https://github.com/gravitee-io/gravitee-api-management/tree/master/helm","reviewed":"2026-11-16","scope":"Self-hosted APIM 4.10 installation guidance; chart repository moves independently","source":"https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides/kubernetes","status":"documented","summary":"The current APIM chart source is in the API Management repository; the older standalone helm-charts repository points there. Use the versioned installation guide and a compatible chart release, database and search backend.","supportingSources":[{"title":"APIM chart relocation","url":"https://github.com/gravitee-io/helm-charts"}]},"licensePricing":{"reviewed":"2026-11-16","scope":"Gravitee API Management Self-Hosted: software license terms; infrastructure and operating costs are separate","source":"https://github.com/gravitee-io/gravitee-api-management/blob/master/LICENSE.txt","status":"documented","summary":"Gravitee APIM Community Edition is Apache-2.0 licensed. Enterprise Edition capabilities require a separate commercial license.","supportingSources":[{"title":"Edition and license conditions","url":"https://documentation.gravitee.io/apim/4.10/readme/enterprise-edition"}]},"release":{"releasePublishedOn":"2026-11-13","releaseTag":"4.10.36","reviewed":"2026-11-18","scope":"Gravitee APIM self-hosted 4.10 branch, with 4.13 support and migration context","source":"https://documentation.gravitee.io/apim/4.10/release-information/changelog/apim-4.10.x","status":"documented","summary":"Gravitee APIM 4.10.36 and supported 4.13.4 were released November 13, 2026. Plan separately for v2 API removal in October 2027 and the 2027 Alpine-to-Debian image transition.","supportingSources":[{"title":"4.13.4 changelog","url":"https://documentation.gravitee.io/apim/4.13/release-information/changelog/apim-4.13.x"}]},"securityControls":{"reviewed":"2026-11-16","scope":"APIM 4.10 production authentication configuration","source":"https://documentation.gravitee.io/apim/4.10/prepare-a-production-environment/production-best-practices/authentication","status":"documented","summary":"Production guidance recommends external identity, least-privilege roles/groups and signed session cookies. Operators must replace example JWT/cookie secrets and scope cookies to the correct environment. These are configuration requirements, not a compliance attestation."},"sso":{"availability":"available","reviewed":"2026-11-16","scope":"Self-hosted APIM 4.10 Console/Portal; not a blanket entitlement to the separate Access Management product","source":"https://documentation.gravitee.io/apim/4.10/prepare-a-production-environment/production-best-practices/authentication","status":"documented","summary":"APIM documents delegating Console and Portal authentication to a corporate OAuth2/OIDC provider or LDAP, with role/group mapping. The New Developer Portal has its own SSO configuration and requires APIM 4.10+.","supportingSources":[{"title":"New Portal SSO setup","url":"https://documentation.gravitee.io/apim/4.10/developer-portal/new-developer-portal/configure-authentication/configure-authentication-with-sso"}]}},"id":"gravitee-apim-self-hosted","infrastructure":["servers"],"infrastructureNotes":"Gravitee APIM runs persistent management, gateway, portal, database and analytics services on customer hosts or Kubernetes.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides","https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides/kubernetes/azure-aks"],"install":"Official Helm chart, Docker deployment or Linux packages on customer infrastructure","installMethods":["helm","docker","package"],"kind":"product","license":"Apache License 2.0 Community Edition; Enterprise Edition requires a commercial license.","licenseModel":"open-source","licenseModelNotes":"Gravitee APIM Community Edition is Apache-2.0 licensed. Enterprise Edition capabilities require a separate commercial license.","licenseModelSources":["https://github.com/gravitee-io/gravitee-api-management/blob/master/LICENSE.txt","https://documentation.gravitee.io/apim/4.10/readme/enterprise-edition"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"Gravitee API Management Self-Hosted","notes":"This entry covers Gravitee APIM with both control and data planes self-hosted. Gravitee recommends its cloud option for new installations, and multi-environment self-hosted configuration requires a connection to Gravitee Cloud. The provider-specific Kubernetes guides are development and quick-start material, not production reference architectures. Gravitee APIM 4.10.36 fixes Kafka OAUTHBEARER reauthentication, subscription metadata deletion, dead-letter-queue failure handling, and health-check POST bodies. Supported 4.13.4 also fixes upgrade and Redis-cache behavior; v2 APIs are scheduled for removal in October 2027, and unqualified images move from Alpine to Debian in March 2027 before Alpine images stop in June 2027.","operations":"Customer manages Kubernetes or hosts, databases, search, networking, ingress, TLS, identity, secrets, monitoring, backups, scaling, upgrades and any Enterprise license.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Gravitee APIM self-hosted installation guides","url":"https://documentation.gravitee.io/apim/4.10/self-hosted-installation-guides"},{"title":"Gravitee APIM Enterprise Edition","url":"https://documentation.gravitee.io/apim/4.10/readme/enterprise-edition"},{"title":"Gravitee APIM editions","url":"https://documentation.gravitee.io/apim/4.10/getting-started"},{"title":"Gravitee APIM Apache 2.0 license","url":"https://github.com/gravitee-io/gravitee-api-management/blob/master/LICENSE.txt"},{"title":"Gravitee APIM releases","url":"https://github.com/gravitee-io/gravitee-api-management/releases"},{"title":"Gravitee APIM contributor history","url":"https://github.com/gravitee-io/gravitee-api-management/graphs/contributors"},{"title":"Gravitee APIM 4.10 changelog","url":"https://documentation.gravitee.io/apim/4.10/release-information/changelog/apim-4.10.x"},{"title":"Gravitee APIM 4.13 changelog","url":"https://documentation.gravitee.io/apim/4.13/release-information/changelog/apim-4.13.x"},{"title":"Gravitee APIM support model","url":"https://documentation.gravitee.io/apim/release-information/support-model"},{"title":"Gravitee APIM 4.13 release notes","url":"https://github.com/gravitee-io/gravitee-platform-docs/blob/main/docs/gamma/4.13/platform-management/gamma-release-notes.md"}],"url":"https://launchinyourcloud.com/directory/gravitee-apim-self-hosted/","website":"https://www.gravitee.io/platform/api-management"},{"advisories":[{"action":"Upgrade to the applicable fixed or later Enterprise build and restrict credential-store egress.","conditions":"Requires the affected Vault credential-store path and reachable network targets.","disclosedOn":"2026-10-29","id":"hashicorp-boundary-cve-2026-13303","listingIds":["hashicorp-boundary-enterprise"],"reviewed":"2026-11-18","scope":"Fixed in Boundary Enterprise 1.0.2 and 0.21.6.","source":"https://discuss.hashicorp.com/t/hcsec-2026-54-boundary-vulnerable-to-server-side-request-forgery-in-vault-credential-store/77932","summary":"HCSEC-2026-54 covers CVE-2026-13303, a server-side request forgery issue in the Vault credential store.","title":"HashiCorp Boundary Vault credential-store SSRF","type":"security-advisory"}],"architecture":"Customer-operated Boundary controllers and workers with external PostgreSQL, KMS or HSM integration and PKI.","categories":["identity-access-management"],"category":"Identity \u0026 access management","categoryFit":{"identity-access-management":"Provides identity-aware, policy-controlled access to infrastructure targets without exposing long-lived network credentials."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"HashiCorp documents self-managed Boundary Enterprise architectures and Terraform deployments in customer AWS, Azure and Google Cloud environments. Customers operate controllers, workers, PostgreSQL and key management.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Boundary Enterprise validated self-managed deployment on AWS, Azure and Google Cloud","url":"https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment","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":"Commercial identity-aware remote-access platform deployed as controllers and workers in a customer cloud account.","diligence":{"airGap":{"reviewed":"2026-11-17","scope":"Self-managed Boundary Enterprise reporting; not blanket isolation of integrations","source":"https://developer.hashicorp.com/boundary/docs/enterprise/automated-license-reporting","status":"inconclusive","summary":"The Enterprise licence-reporting guide explicitly allows manual utilization reporting for isolated installations. This resolves the reporting dependency, but the complete offline licence-renewal, identity, package and upgrade procedure for the selected deployment still needs confirmation."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HashiCorp Boundary Enterprise; unresolved within this edition/deployment","source":"https://www.hashicorp.com/en/products/boundary/pricing","status":"inconclusive","summary":"Boundary Enterprise pricing did not establish eligible software charges under the buyer’s cloud commitment agreement."},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment","status":"inconclusive","summary":"The reviewed HashiCorp Boundary Enterprise material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage."},"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://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment","status":"inconclusive","summary":"Specify concurrent sessions, recording retention, controller/worker topology, HA PostgreSQL and KMS. Data transfer/session volume and commercial entitlements remain unpriced. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"Boundary Enterprise architecture; workload capacity requires session metrics","source":"https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment","status":"documented","summary":"Controllers, workers, PostgreSQL and KMS are separate components. Session concurrency and recording/egress requirements determine worker and storage capacity; 100 identities alone do not establish an HA sizing model."},"iac":{"reviewed":"2026-11-17","scope":"Self-managed Boundary Enterprise validated design","source":"https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment","status":"documented","summary":"The validated design provides Terraform deployment of Boundary controllers and workers in AWS, Azure or Google Cloud. PostgreSQL, key management and network configuration are required; this is not HCP Boundary."},"licensePricing":{"reviewed":"2026-11-17","scope":"HashiCorp Boundary Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://www.hashicorp.com/en/products/boundary/pricing","status":"documented","summary":"Boundary Enterprise is proprietary commercial software. HCP Boundary is a separate managed service, and any community distribution does not grant Enterprise features."},"marketplace":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HashiCorp Boundary Enterprise; unresolved within this edition/deployment","source":"https://www.hashicorp.com/en/products/boundary/pricing","status":"inconclusive","summary":"Self-managed Enterprise deployment and pricing do not establish a current Marketplace offer matching this edition. HCP Boundary is a different operating model."},"release":{"reviewed":"2026-11-17","scope":"Enterprise-filtered release API snapshot; community and HCP releases excluded","source":"https://api.releases.hashicorp.com/v1/releases/boundary/latest?license_class=enterprise","status":"documented","summary":"The vendor release API identifies 1.1.1+ent as a supported, non-prerelease Enterprise build. Its record was created 2026-11-05. This is the API record-creation date, not a separately established publication date; verify the licensed release/support path before upgrading.","supportingSources":[{"title":"Versioned Enterprise binaries and checksums","url":"https://releases.hashicorp.com/boundary/1.1.1+ent/"}]},"scim":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HashiCorp Boundary Enterprise; unresolved within this edition/deployment","source":"https://developer.hashicorp.com/boundary/docs/authentication","status":"inconclusive","summary":"Boundary documents OIDC/LDAP and first-login account creation, but a self-managed Enterprise SCIM endpoint and deprovisioning semantics were not established. HCP SCIM is separate."},"securityControls":{"reviewed":"2026-11-18","scope":"Boundary Enterprise deployment security Fixed in Boundary Enterprise 1.0.2 and 0.21.6.","source":"https://discuss.hashicorp.com/t/hcsec-2026-54-boundary-vulnerable-to-server-side-request-forgery-in-vault-credential-store/77932","status":"documented","summary":"The deployment design separates controller and worker paths with database and key-management dependencies. Configure TLS, network access and recovery, and protect credentials used for provisioning. Current advisory review: HCSEC-2026-54 covers CVE-2026-13303, a server-side request forgery issue in the Vault credential store. Upgrade to the applicable fixed or later Enterprise build and restrict credential-store egress.","supportingSources":[{"title":"Prior security-controls source","url":"https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment"}]},"sso":{"availability":"available","reviewed":"2026-11-17","scope":"Self-managed Boundary identity methods","source":"https://developer.hashicorp.com/boundary/docs/authentication","status":"documented","summary":"Boundary supports OIDC through external providers such as Okta and Entra ID, plus separate password/LDAP methods. A primary auth method can create users on first login; this is not evidence of SCIM lifecycle synchronization."}},"id":"hashicorp-boundary-enterprise","infrastructure":["servers"],"infrastructureNotes":"Boundary Enterprise runs persistent controller and worker services on customer virtual machines and depends on external PostgreSQL, key management and TLS infrastructure.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://developer.hashicorp.com/boundary/docs/deploy/self-managed","https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment"],"install":"HashiCorp Validated Design Terraform architectures plus supported apt, yum or binary packages","installMethods":["terraform","package"],"kind":"platform","license":"Commercial Boundary Enterprise license required; HCP Boundary is a separate hosted service.","licenseModel":"commercial-only","licenseModelNotes":"Boundary Enterprise is proprietary commercial software. HCP Boundary is a separate managed service, and any community distribution does not grant Enterprise features.","licenseModelSources":["https://www.hashicorp.com/en/products/boundary/pricing"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"HashiCorp Boundary Enterprise","notes":"This entry covers self-managed Boundary Enterprise, not HCP Boundary. Production deployment requires multiple controllers and workers, an external PostgreSQL database, KMS or HSM-backed key management, TLS and a deliberate worker topology. Validate provider modules, identity integrations and recovery procedures before rollout. HCSEC-2026-54 covers CVE-2026-13303, a Vault credential-store SSRF issue. Fixed Enterprise builds are 1.0.2 and 0.21.6; upgrade the installed maintained branch and restrict credential-store network reachability.","operations":"Customer manages controllers, workers, PostgreSQL, KMS, PKI, networking, identity integrations, backups, upgrades and availability.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Boundary self-managed deployment","url":"https://developer.hashicorp.com/boundary/docs/deploy/self-managed"},{"title":"Boundary Validated Design deployment","url":"https://developer.hashicorp.com/validated-designs/boundary/installation-guide/deployment"},{"title":"Boundary pricing and editions","url":"https://www.hashicorp.com/en/products/boundary/pricing"},{"title":"HCSEC-2026-54","url":"https://discuss.hashicorp.com/t/hcsec-2026-54-boundary-vulnerable-to-server-side-request-forgery-in-vault-credential-store/77932"}],"url":"https://launchinyourcloud.com/directory/hashicorp-boundary-enterprise/","website":"https://www.hashicorp.com/en/products/boundary"},{"advisories":[{"action":"Upgrade Consul Enterprise and consul-k8s to the applicable fixed or later builds.","conditions":"Health-check registration permissions and Kubernetes component ACL binding rules determine exposure.","disclosedOn":"2026-10-29","id":"hashicorp-consul-hcsec-2026-49-50","listingIds":["hashicorp-consul-enterprise"],"reviewed":"2026-11-18","scope":"Fixed in Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18.","source":"https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914","summary":"HCSEC-2026-49 and 50 cover health-check registration and consul-k8s cross-namespace authorization bypasses.","supportingSources":[{"title":"HCSEC-2026-50","url":"https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915"}],"title":"HashiCorp Consul authorization-bypass updates","type":"security-advisory"}],"architecture":"Customer-operated Consul server quorum and clients with provider load balancers, KMS, secrets and snapshot storage.","categories":["backend-platforms","devops"],"category":"Backend platforms","categoryFit":{"backend-platforms":"Provides service discovery, configuration, connectivity and service-mesh control for distributed application platforms.","devops":"Automates service networking, health discovery and policy across deployment environments."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"HashiCorp provides validated Terraform deployment paths for Consul Enterprise in customer AWS, Azure and Google Cloud environments. Customers manage the deployed cluster, security material and backups.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Consul Enterprise Terraform deployments on AWS, Azure and Google Cloud","url":"https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform","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":"Commercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.","diligence":{"airGap":{"reviewed":"2026-11-17","scope":"Self-managed Consul Enterprise reporting; not blanket isolation of integrations","source":"https://developer.hashicorp.com/consul/docs/enterprise/license/reporting","status":"inconclusive","summary":"The Enterprise licence-reporting guide explicitly allows manual utilization reporting for isolated installations. This resolves the reporting dependency, but the complete offline licence-renewal, identity, package and upgrade procedure for the selected deployment still needs confirmation."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment","source":"https://www.hashicorp.com/en/products/consul/pricing","status":"inconclusive","summary":"Consul Enterprise price/edition material did not establish qualifying Marketplace charges and commitment treatment for the buyer agreement."},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform","status":"inconclusive","summary":"The reviewed HashiCorp Consul Enterprise material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage."},"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://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform","status":"inconclusive","summary":"Specify service/agent count, mesh traffic, gateways and Enterprise server topology. Human users and 1 TB application data do not size a Consul service mesh. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"Consul topology and workload boundary","source":"https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform","status":"documented","summary":"The design deploys a fault-tolerant Consul server cluster; service count, agent placement, traffic, mesh gateways and availability requirements determine total capacity. Human-user count does not size the service mesh."},"iac":{"reviewed":"2026-11-17","scope":"Self-managed Enterprise validated Terraform deployment","source":"https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform","status":"documented","summary":"The validated design provides provider-specific Terraform deployment for Consul Enterprise on AWS, Azure and Google Cloud. Configure the licence, secrets, network access and snapshot storage before production use."},"licensePricing":{"reviewed":"2026-11-17","scope":"HashiCorp Consul Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://www.hashicorp.com/en/products/consul/pricing","status":"documented","summary":"Consul Enterprise is proprietary commercial software. The separate Community Edition and HCP service do not determine this entry's entitlement."},"marketplace":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment","source":"https://www.hashicorp.com/en/products/consul/pricing","status":"inconclusive","summary":"The reviewed Enterprise pricing and Terraform deployment establish the licensed product, but not a current Consul Enterprise-specific Marketplace offer. HCP procurement is separate."},"release":{"reviewed":"2026-11-17","scope":"Enterprise-filtered release API snapshot; community and HCP releases excluded","source":"https://api.releases.hashicorp.com/v1/releases/consul/latest?license_class=enterprise","status":"documented","summary":"The vendor release API identifies 2.1.0+ent as a supported, non-prerelease Enterprise build. Its record was created 2026-10-22. This is the API record-creation date, not a separately established publication date; verify the licensed release/support path before upgrading.","supportingSources":[{"title":"Versioned Enterprise binaries and checksums","url":"https://releases.hashicorp.com/consul/2.1.0+ent/"}]},"scim":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment","source":"https://developer.hashicorp.com/consul/docs/secure/acl/auth-method/oidc","status":"inconclusive","summary":"Enterprise OIDC exchanges claims for ACL tokens; it does not establish a SCIM user/group lifecycle endpoint. HCP account SCIM was excluded."},"securityControls":{"reviewed":"2026-11-18","scope":"Consul Enterprise deployment controls Fixed in Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18.","source":"https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914","status":"documented","summary":"The Enterprise Terraform workflow configures cluster secrets and cloud permissions. Apply ACL, TLS/gossip, backup and key-management requirements rather than treating provisioning completion as a security review. Current advisory review: HCSEC-2026-49 and 50 cover health-check registration and consul-k8s cross-namespace authorization bypasses. Upgrade Consul Enterprise and consul-k8s to the applicable fixed or later builds.","supportingSources":[{"title":"Prior security-controls source","url":"https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform"},{"title":"HCSEC-2026-50","url":"https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915"}]},"sso":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"Self-managed Consul Enterprise, not HCP account SSO","source":"https://developer.hashicorp.com/consul/docs/secure/acl/auth-method/oidc","status":"documented","summary":"The OIDC authentication method requires self-managed Consul Enterprise 1.8.0+. It supports browser-based UI/CLI login through a configured IdP, with ACL tokens and claim mappings."}},"id":"hashicorp-consul-enterprise","infrastructure":["servers"],"infrastructureNotes":"Consul Enterprise runs persistent server and client agents on customer infrastructure with consensus state, snapshots and network dependencies.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform"],"install":"HashiCorp Validated Design Terraform modules for AWS, Azure or Google Cloud","installMethods":["terraform","package"],"kind":"platform","license":"Commercial Consul Enterprise license required for the selected validated design.","licenseModel":"commercial-only","licenseModelNotes":"Consul Enterprise is proprietary commercial software. The separate Community Edition and HCP service do not determine this entry's entitlement.","licenseModelSources":["https://www.hashicorp.com/en/products/consul/pricing"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"HashiCorp Consul Enterprise","notes":"This entry covers Consul Enterprise, not HCP Consul and not the separately licensed Community Edition. The validated designs require a commercial license and production security material, including TLS certificates, ACL configuration and gossip encryption. Protect bootstrap tokens and snapshot storage and validate the selected module release before deployment. HCSEC-2026-49 and 50 cover a health-check registration authorization bypass and a consul-k8s cross-namespace ACL binding-rule bypass. Fixed builds are Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18.","operations":"Customer manages cluster nodes, TLS, ACLs, gossip keys, secret handling, snapshots, upgrades, service integrations and availability.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Deploy Consul Enterprise using Terraform on AWS, Azure and Google Cloud","url":"https://developer.hashicorp.com/validated-designs/consul/installation-guide/deploying-consul-using-terraform"},{"title":"Consul pricing and editions","url":"https://www.hashicorp.com/en/products/consul/pricing"},{"title":"HCSEC-2026-49","url":"https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914"},{"title":"HCSEC-2026-50","url":"https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915"}],"url":"https://launchinyourcloud.com/directory/hashicorp-consul-enterprise/","website":"https://www.hashicorp.com/en/products/consul"},{"advisories":[{"action":"Upgrade the installed maintained Enterprise branch to the listed fixed or later build.","conditions":"Namespace permissions, dispatch payload writes, allocation migration, and symlink handling determine exposure.","disclosedOn":"2026-10-29","id":"hashicorp-nomad-hcsec-2026-51-53","listingIds":["hashicorp-nomad-enterprise"],"reviewed":"2026-11-18","scope":"Fixed in Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18.","source":"https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929","summary":"HCSEC-2026-51 through 53 cover cross-namespace information disclosure and two symlink-based host or allocation escalation paths.","supportingSources":[{"title":"HCSEC-2026-52","url":"https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930"},{"title":"HCSEC-2026-53","url":"https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931"}],"title":"HashiCorp Nomad Enterprise October 2026 security updates","type":"security-advisory"}],"architecture":"Customer-operated Nomad server quorum and client nodes with persistent state, networking and workload drivers.","categories":["devops","workflow-orchestration"],"category":"DevOps","categoryFit":{"devops":"Schedules and operates application, batch and system workloads across customer infrastructure.","workflow-orchestration":"Coordinates long-running services, batch jobs and parameterized workload execution through declarative job specifications."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"HashiCorp's Validated Design documents production Nomad deployment on customer AWS, Azure and Google Cloud infrastructure. The operator supplies the Enterprise license and manages the resulting cluster.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Nomad Enterprise validated cloud deployment on AWS, Azure and Google Cloud","url":"https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment","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":"Commercial workload scheduler and orchestrator deployed as a multi-node cluster on customer cloud virtual machines.","diligence":{"airGap":{"reviewed":"2026-11-17","scope":"Self-managed Nomad Enterprise reporting; not blanket isolation of integrations","source":"https://developer.hashicorp.com/nomad/docs/enterprise/license/utilization-reporting","status":"inconclusive","summary":"The Enterprise licence-reporting guide explicitly allows manual utilization reporting for isolated installations. This resolves the reporting dependency, but the complete offline licence-renewal, identity, package and upgrade procedure for the selected deployment still needs confirmation."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment","source":"https://www.hashicorp.com/en/products/nomad/pricing","status":"inconclusive","summary":"Nomad Enterprise pricing did not establish offer-specific eligible charges against the buyer cloud agreement; infrastructure discounts are separate."},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment","status":"inconclusive","summary":"The reviewed HashiCorp Nomad Enterprise material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage."},"cost":{"estimate":{"currency":"USD","exclusions":["Software licence and support","Operating labor","Backups and recovery testing","Load balancing, NAT/endpoints, IPv4 and all data transfer","Monitoring, mail and other services","Taxes and discounts","All workload/client compute and the requested 1 TB workload data","Optional Consul/Vault and storage/network plugins"],"kind":"partial-infrastructure","period":"month","region":"AWS us-east-1","rows":[{"description":"6 Linux m5.xlarge VMs × 730 hours; capacity is an editorial planning choice, not a vendor 100-user benchmark","id":"compute","quantity":4380,"rate":0.192},{"description":"300 GB provisioned gp3 capacity, including stated boot/data allowance; base IOPS/throughput only","id":"storage","quantity":300,"rate":0.08},{"description":"Unpriced; include if required by the selected topology","id":"database","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"backup","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"network","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"license","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"labor","quantity":1,"rate":""}],"workload":"100 internal users; 1 TB (1,000 GB) logical data; HA target; average usage unmeasured; 730 h/month. Nomad control plane only; workload clients and data unpriced."},"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":"Nomad Enterprise server control-plane subtotal; 100 identities do not size jobs, task concurrency or workload clients. Price applications and replicated workload storage separately.","source":"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","status":"inconclusive","summary":"Illustrative priced infrastructure subtotal: USD 864.96/month. Six 4-vCPU/16-GiB server VMs follow the validated three-voting/three-non-voting design, with 50 GB gp3 each. This prices the control plane only; workload clients and their 1 TB data are unpriced. This is not a complete operating-cost estimate or a validated capacity/SLA claim.","supportingSources":[{"title":"Product topology/sizing basis","url":"https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment"},{"title":"Current AWS documentation: us-east-1 gp3 capacity example","url":"https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html"},{"title":"EBS performance and charging qualifications","url":"https://aws.amazon.com/ebs/pricing/"}]},"footprint":{"reviewed":"2026-11-17","scope":"Nomad cluster topology versus workload capacity","source":"https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment","status":"documented","summary":"The cloud design separates voting/non-voting servers from workload clients across availability zones. Server count alone does not size user jobs, 1 TB application data, storage plugins or client failover capacity."},"iac":{"reviewed":"2026-11-17","scope":"Self-managed Enterprise validated cloud design","source":"https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment","status":"documented","summary":"The validated design documents customer-cloud Nomad installation on AWS, Azure and Google Cloud with servers, clients, networking and enterprise licensing. Review the design and pin the chosen deployment tooling before applying it."},"licensePricing":{"reviewed":"2026-11-17","scope":"HashiCorp Nomad Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://www.hashicorp.com/en/products/nomad/pricing","status":"documented","summary":"Nomad Enterprise is proprietary commercial software. Nomad Community Edition is separately distributed under source-available terms and does not grant Enterprise features or support."},"marketplace":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment","source":"https://www.hashicorp.com/en/products/nomad/pricing","status":"inconclusive","summary":"The Enterprise pricing and deployment material establishes licensed self-management, but not a current Nomad Enterprise-specific Marketplace offer. HCP/Vault offers were excluded."},"release":{"reviewed":"2026-11-17","scope":"Enterprise-filtered release API snapshot; community and HCP releases excluded","source":"https://api.releases.hashicorp.com/v1/releases/nomad/latest?license_class=enterprise","status":"documented","summary":"The vendor release API identifies 2.1.1+ent as a supported, non-prerelease Enterprise build. Its record was created 2026-10-29. This is the API record-creation date, not a separately established publication date; verify the licensed release/support path before upgrading.","supportingSources":[{"title":"Versioned Enterprise binaries and checksums","url":"https://releases.hashicorp.com/nomad/2.1.1+ent/"}]},"scim":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment","source":"https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management","status":"inconclusive","summary":"Nomad OIDC maps identity claims to short-lived ACL tokens. A Nomad Enterprise SCIM lifecycle service was not established; HCP Terraform SCIM is a different product."},"securityControls":{"reviewed":"2026-11-18","scope":"Nomad customer-managed cluster controls Fixed in Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18.","source":"https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929","status":"documented","summary":"The validated identity design requires appropriate ACL policies and mapped roles. Protect management tokens, configure TLS/gossip and snapshot recovery, and isolate workload client permissions from server administration. Current advisory review: HCSEC-2026-51 through 53 cover cross-namespace information disclosure and two symlink-based host or allocation escalation paths. Upgrade the installed maintained Enterprise branch to the listed fixed or later build.","supportingSources":[{"title":"Identity and access management","url":"https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management"},{"title":"Prior security-controls source","url":"https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment"},{"title":"HCSEC-2026-52","url":"https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930"},{"title":"HCSEC-2026-53","url":"https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931"}]},"sso":{"availability":"available","reviewed":"2026-11-17","scope":"Self-managed Nomad Enterprise identity design","source":"https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management","status":"documented","summary":"Nomad documents OIDC SSO through external IdPs with ACL policies, roles and binding rules. Human and machine authentication are different flows; short-lived ACL tokens replace distributing static tokens."}},"id":"hashicorp-nomad-enterprise","infrastructure":["servers"],"infrastructureNotes":"Production Nomad uses persistent server nodes for consensus and state plus client nodes that execute workloads on customer virtual machines.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment"],"install":"HashiCorp Validated Design Terraform modules where available or manual package and binary installation","installMethods":["terraform","package"],"kind":"platform","license":"Commercial Nomad Enterprise license required for the selected edition; Community Edition uses separate source-available terms.","licenseModel":"commercial-only","licenseModelNotes":"Nomad Enterprise is proprietary commercial software. Nomad Community Edition is separately distributed under source-available terms and does not grant Enterprise features or support.","licenseModelSources":["https://www.hashicorp.com/en/products/nomad/pricing"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"HashiCorp Nomad Enterprise","notes":"This entry scopes Nomad Enterprise rather than the separately licensed Community Edition. HashiCorp's validated cloud design requires a production multi-node topology, enterprise license, TLS and gossip encryption, protected snapshots and provider-specific infrastructure. Confirm the current validated module release and supported operating systems before deployment. HCSEC-2026-51, 52, and 53 cover cross-namespace information disclosure plus symlink-based allocation-directory escape and host permission modification. Fixed Enterprise builds are 2.1.0, 1.11.12, and 1.10.18.","operations":"Customer manages servers and clients, TLS, gossip encryption, ACLs, snapshots, networking, workload drivers, upgrades and availability.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Nomad validated cloud deployment","url":"https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment"},{"title":"Nomad pricing and editions","url":"https://www.hashicorp.com/en/products/nomad/pricing"},{"title":"HCSEC-2026-51","url":"https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929"},{"title":"HCSEC-2026-52","url":"https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930"},{"title":"HCSEC-2026-53","url":"https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931"}],"url":"https://launchinyourcloud.com/directory/hashicorp-nomad-enterprise/","website":"https://www.hashicorp.com/en/products/nomad"},{"architecture":"Customer-operated API engine with PostgreSQL metadata database and connected data sources","categories":["backend-platforms"],"category":"Backend platforms","categoryFit":{"backend-platforms":"Database-backed GraphQL API layer with authorization, subscriptions and configured remote actions. It does not supply a complete standalone application database or identity provider."},"cloudEvidence":[{"clouds":["azure"],"notes":"The v2 project documentation deploys the GraphQL Engine container on Azure Container Instances with PostgreSQL. Review secrets, database access and production hardening; Hasura Cloud regions are not used as evidence.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Hasura GraphQL Engine on Azure Container Instances","url":"https://hasura.io/docs/2.0/deployment/deployment-guides/azure-container-instances-postgres/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The v2 project documentation deploys the GraphQL Engine on GKE with Cloud SQL. This establishes application hosting in the customer project, not just connectivity to a Google-hosted database.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Hasura GraphQL Engine on Google Kubernetes Engine","url":"https://hasura.io/docs/2.0/deployment/deployment-guides/google-kubernetes-engine-cloud-sql/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["azure","gcp"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Current GraphQL Engine release maintenance","url":"https://github.com/hasura/graphql-engine/releases"},{"title":"Public developer community and calls","url":"https://hasura.io/help/"},{"title":"GraphQL Engine contribution history","url":"https://hasura.io/blog/call-for-open-source-contributions"}],"summary":"The upstream v2 release stream includes current security maintenance. Hasura documents a long-running developer community, public community calls and community contributions around GraphQL Engine."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"GraphQL API engine that exposes connected databases through permission-aware application APIs.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Hasura v2 production and tuning guidance; current workload-specific compute/storage sizing remains unconfirmed","source":"https://hasura.io/docs/2.0/deployment/production-checklist/","status":"inconclusive","summary":"The v2 production checklist and subscription-tuning guide require database connection/concurrency planning and CPU/memory monitoring, but do not establish a numeric whole-stack minimum. Query complexity, live subscriptions, metadata/source databases and replicas determine capacity. Old tutorial VM allocations or Cloud auto-scaling are not a current 100-user, 1 TB HA sizing guarantee.","supportingSources":[{"title":"v2 subscription saturation and performance tuning","url":"https://hasura.io/docs/2.0/subscriptions/observability-and-performance/"}]},"iac":{"artifactRef":"master v2 example (moving)","artifactUrl":"https://raw.githubusercontent.com/hasura/graphql-engine/master/install-manifests/docker-compose/docker-compose.yaml","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://hasura.io/docs/2.0/deployment/deployment-guides/docker/","status":"documented","summary":"The v2 guide links an upstream Compose manifest with PostgreSQL metadata storage. Select the appropriate community/commercial image and set administrator/database credentials rather than exposing the defaults."},"licensePricing":{"reviewed":"2026-11-20","scope":"GraphQL Engine v2 CE versus commercial image/features; not Hasura v3 DDN","source":"https://github.com/hasura/graphql-engine/blob/v2.51.6/LICENSE","status":"documented","summary":"The v2.51.6 open-source GraphQL Engine core is Apache-2.0 licensed. Hasura v2 Enterprise has separate commercial entitlements; the official image distribution distinguishes the -ce variant from images that include Enterprise components. Enterprise Console SSO is not granted by the CE licence, and DDN/Cloud pricing is not a self-hosted v2 quote.","supportingSources":[{"title":"Official image and CE variant distinction","url":"https://hub.docker.com/r/hasura/graphql-engine/"},{"title":"Self-Hosted Enterprise v2 scope","url":"https://hasura.io/docs/2.0/enterprise/overview/"}]},"release":{"releasePublishedAt":"2026-11-11T00:28:51Z","releaseTag":"v2.51.6","reviewed":"2026-11-14","scope":"Upstream hasura/graphql-engine release record; commercial editions and deployment packages may differ","source":"https://github.com/hasura/graphql-engine/releases/tag/v2.51.6","status":"documented","summary":"The publisher-designated GitHub release checked was v2.51.6, published 2026-11-11. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Hasura v2 Enterprise administrative Console, not every API client","source":"https://hasura.io/docs/2.0/enterprise/sso/adfs/","status":"documented","summary":"Self-hosted Enterprise Console can integrate ADFS SAML through Dex from v2.25.0, with a valid license key. Console authentication is separate from GraphQL API JWT/webhook authorization and is not a CE entitlement."}},"id":"hasura-graphql-engine","infrastructure":["servers"],"infrastructureNotes":"Customer-operated API engine with PostgreSQL metadata database and connected data sources. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. Coordinate PostgreSQL patch upgrades with the GraphQL Engine version. Older engines can break source-catalog initialization or logical replication after upgrading to PostgreSQL 15.15, 16.11, 17.7, or 18 and later.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://hasura.io/docs/2.0/deployment/deployment-guides/docker/","https://github.com/hasura/graphql-engine/releases/tag/v2.51.6","https://github.com/hasura/graphql-engine/releases/tag/v2.50.9"],"install":"Deploy the documented v2 Docker Compose setup; select the versioned -ce image when only open-source components are required.","installMethods":["docker","source"],"kind":"product","license":"Apache License 2.0 for upstream open-source GraphQL Engine components. Default distributions can include separately licensed enterprise components; -ce images contain open-source components.","licenseModel":"open-source","licenseModelNotes":"Apache License 2.0 for upstream open-source GraphQL Engine components. Default distributions can include separately licensed enterprise components; -ce images contain open-source components. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.","licenseModelSources":["https://raw.githubusercontent.com/hasura/graphql-engine/master/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Hasura GraphQL Engine v2","notes":"This listing is specifically for the self-operated v2 engine, not Hasura Cloud or DDN. Authentication webhooks, remote schemas, event handlers and database destinations can cross account boundaries. GraphQL Engine v2.51.6 and v2.50.9 fix source-catalog initialization and upgrades when PostgreSQL 15.15, 16.11, 17.7, or 18 and later enforce replica identity for INSERT ... ON CONFLICT DO UPDATE in a logical-replication publication. Upgrade GraphQL Engine before PostgreSQL. For older engine versions, the documented workaround is ALTER TABLE hdb_catalog.hdb_source_catalog_version REPLICA IDENTITY FULL on every data source, repeated whenever a new source is added.","operations":"Customer manages engine and metadata storage, database access, admin secrets, authorization, TLS, and coordinated engine/database upgrades.","publisher":false,"reviewed":"2026-11-16","sources":[{"title":"Official installation and runtime","url":"https://hasura.io/docs/2.0/deployment/deployment-guides/docker/"},{"title":"Upstream project and capabilities","url":"https://github.com/hasura/graphql-engine"},{"title":"Current upstream license","url":"https://raw.githubusercontent.com/hasura/graphql-engine/master/LICENSE"},{"title":"Official image and -ce licensing distinction","url":"https://hub.docker.com/r/hasura/graphql-engine/"},{"title":"v2 capabilities and Community Edition","url":"https://hasura.io/docs/2.0/index/"},{"title":"Hasura v2.51.6 PostgreSQL upgrade-order fix","url":"https://github.com/hasura/graphql-engine/releases/tag/v2.51.6"},{"title":"Hasura v2.50.9 PostgreSQL upgrade-order fix","url":"https://github.com/hasura/graphql-engine/releases/tag/v2.50.9"}],"url":"https://launchinyourcloud.com/directory/hasura-graphql-engine/","website":"https://hasura.io/"},{"architecture":"Customer-operated Kubernetes deployment with persistent application, content and asset services plus external platform dependencies.","categories":["content-management","digital-asset-management"],"category":"Content management \u0026 CMS","categoryFit":{"content-management":"A web content management system with authoring, presentation templates, headless APIs and publishing workflows.","digital-asset-management":"Integrated digital asset management organizes, controls and reuses images, video and other web-ready assets."},"cloudEvidence":[{"clouds":["aws"],"notes":"HCL documents deploying the entitled DX Helm chart to Amazon-managed Kubernetes in the customer's AWS environment.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"HCL Digital Experience on Amazon EKS","url":"https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"HCL's current support matrix explicitly lists Microsoft Azure AKS as a tested and supported full-container platform.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"HCL Digital Experience on Microsoft Azure AKS","url":"https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"HCL's current support matrix explicitly lists Google GKE as a tested and supported full-container platform.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"HCL Digital Experience on Google GKE","url":"https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/","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":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Commercial web content and digital asset management platform deployed by Helm to customer-operated Kubernetes.","diligence":{"airGap":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HCL Digital Experience Cloud Native 9.5; unresolved within this edition/deployment","source":"https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/","status":"inconclusive","summary":"The Helm installation requires entitled images and chart configuration; a supported complete offline licence, image/dependency transfer and update workflow was not established."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HCL Digital Experience Cloud Native 9.5; unresolved within this edition/deployment","source":"https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/","status":"inconclusive","summary":"The AWS Marketplace installation guide does not establish qualifying fees or commitment treatment for the selected DX offer and buyer agreement."},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/","status":"inconclusive","summary":"The reviewed HCL Digital Experience Cloud Native 9.5 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://help.hcl-software.com/digital-experience/9.5/CF239/get_started/plan_deployment/container_deployment/limitations_requirements/","status":"inconclusive","summary":"Confirm Portal, content/asset components, cumulative-fix images, database/search/persistence and session-licence unit. A generic EKS fleet would omit required services and the HA design. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"DX cloud-native CF239 requirements; topology-specific sizing","source":"https://help.hcl-software.com/digital-experience/9.5/CF239/get_started/plan_deployment/container_deployment/limitations_requirements/","status":"documented","summary":"The container requirements distinguish supported Kubernetes platforms, CPU architecture, persistence and component limitations. Size Portal, content and asset services separately for the selected cumulative fix."},"iac":{"reviewed":"2026-11-17","scope":"HCL DX 9.5 CF239 Helm installation","source":"https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/","status":"documented","summary":"The Marketplace installation uses the HCL Helm chart with configured values, container images and persistent volumes. Review the matching CF requirements; the former Operator path is not the current Helm workflow."},"licensePricing":{"reviewed":"2026-11-17","scope":"HCL Digital Experience Cloud Native 9.5: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://www.hcl-software.com/resources/license-agreements/user-session-licensing","status":"documented","summary":"Current HCL Digital Experience Cloud Native entitlements are commercial subscriptions. The User Session metric includes an associated production virtual-processing-capacity allowance; exact rights follow the order and License Information document."},"marketplace":{"availability":"available","reviewed":"2026-11-17","scope":"HCL DX 9.5 AWS Marketplace Helm route","source":"https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/","status":"documented","summary":"HCL documents DX 9.5 Helm deployment through AWS Marketplace. Obtain the matching subscription and container access; licensing and image versions must match the selected cumulative fix."},"release":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HCL Digital Experience Cloud Native 9.5; unresolved within this edition/deployment","source":"https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/","status":"inconclusive","summary":"CF239-scoped deployment documentation and a separately resolved current compatibility matrix were reviewed. The latest entitled CF/chart/image bundle and precise release date require confirmation."},"scim":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HCL Digital Experience Cloud Native 9.5; unresolved within this edition/deployment","source":"https://help.hcl-software.com/digital-experience/9.5/CF239/extend_dx/integration/people_service/limitations/","status":"inconclusive","summary":"People Service documents LDAP synchronization limitations, not a DX-wide SCIM service. A supported SCIM endpoint and licence scope for the selected cumulative fix were not established."},"securityControls":{"reviewed":"2026-11-17","scope":"DX Helm deployment access; not an attestation","source":"https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/","status":"documented","summary":"The Helm workflow requires image access, configured credentials and persistent service configuration. Restrict Kubernetes and registry permissions and use the matching deployment security guidance."},"sso":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for HCL Digital Experience Cloud Native 9.5; unresolved within this edition/deployment","source":"https://help.hcl-software.com/digital-experience/9.5/CF239/extend_dx/integration/people_service/deployment/configuration/oidc_configuration/","status":"inconclusive","summary":"The CF239 docs establish People Service OIDC and a DX/Leap SSO integration, but the complete primary DX authentication configuration and entitlement for this deployment were not established."}},"id":"hcl-digital-experience-cloud-native","infrastructure":["servers"],"infrastructureNotes":"The supported deployment runs persistent HCL DX containers on customer Kubernetes with persistent volumes and supporting stateful services. Helm is supported for CF200 and later.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/","https://help.hcl-software.com/digital-experience/9.5/CF239/get_started/plan_deployment/container_deployment/limitations_requirements/"],"install":"Official HCL Digital Experience Helm chart on customer Amazon EKS, Microsoft AKS or Google GKE","installMethods":["helm","kubernetes"],"kind":"platform","license":"Commercial HCL Digital Experience Cloud Native subscription measured by user sessions and associated production processing capacity.","licenseModel":"commercial-only","licenseModelNotes":"Current HCL Digital Experience Cloud Native entitlements are commercial subscriptions. The User Session metric includes an associated production virtual-processing-capacity allowance; exact rights follow the order and License Information document.","licenseModelSources":["https://www.hcl-software.com/resources/license-agreements/user-session-licensing"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"HCL Digital Experience Cloud Native 9.5","notes":"Beginning with HCL DX 9.5 CF200, operator-based deployments are discontinued and Helm is the supported container method. Supported cloud Kubernetes deployments require x86-64 hardware, compatible Kubernetes and Helm versions, persistent storage and production sizing. HCL tests Amazon EKS, Microsoft AKS and Google GKE; exact storage and version support must be checked for the selected release.","operations":"Customer manages Kubernetes, storage, databases and integrations, ingress, certificates, capacity, backups, upgrades and version compatibility.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Current Kubernetes runtime and cloud support matrix","url":"https://help.hcl-software.com/digital-experience/9.5/latest/get_started/system_requirements/kubernetes/kubernetes-runtime/"},{"title":"AWS Marketplace Helm deployment","url":"https://help.hcl-software.com/digital-experience/9.5/CF239/deployment/install/container/helm_deployment/aws_marketplace_helm_deployment/"},{"title":"Azure Kubernetes Service Helm deployment","url":"https://help.hcl-software.com/digital-experience/9.5/CF238/guide_me/howto/install/DeployOnAzure/"},{"title":"Container deployment requirements and limitations","url":"https://help.hcl-software.com/digital-experience/9.5/CF239/get_started/plan_deployment/container_deployment/limitations_requirements/"},{"title":"HCL DX content management","url":"https://www.help.hcl-software.com/digital-experience/9.5/CF239/get_started/product_overview/content_management/"},{"title":"HCL DX digital asset management","url":"https://www.help.hcl-software.com/digital-experience/9.5/CF239/get_started/product_overview/asset_management/"},{"title":"User Session licensing","url":"https://www.hcl-software.com/resources/license-agreements/user-session-licensing"}],"url":"https://launchinyourcloud.com/directory/hcl-digital-experience-cloud-native/","website":"https://www.hcl-software.com/digital-experience"},{"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":"Apply the fix for the installed Hypercell line and follow the documented sequential upgrades or temporary workarounds.","conditions":"PDF decoding is an additional path in v42–v44; earlier listed versions have configured HTTP-response exposure. SaaS patching does not patch customer installations.","id":"2026-11-19-hypercell-brotli","listingIds":["hyperscience"],"reviewed":"2026-11-19","scope":"Hypercell v33.0–v44.0; the vendor lists fixes 44.0.2, 43.2.5, 42.3.19, 42.0.27, 41.0.39 and 40.0.39. Other or archived lines need an agreed upgrade path.","source":"https://help.hyperscience.ai/docs/security-advisory","summary":"The vendor documents CVE-2026-111497 and version-dependent PDF/HTTP response exposure.","title":"Hypercell Brotli decoder remediation","type":"security-advisory"}],"architecture":"Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard.","categories":["correspondence-management","ai-tools"],"category":"Correspondence management","categoryFit":{"ai-tools":"Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.","correspondence-management":"Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure."},"cloudEvidence":[{"clouds":["aws","gcp"],"notes":"Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard. The Helm guide supplies complete AWS and GCP values, including application storage permissions. Registry integration alone is not a hosting badge. Hypercell application versions, Helm charts and Kubernetes support dates are separate. The October 2026 decoder advisory and the current v44 flow/block upgrade instructions must be checked before exposing document processing; hosted FedRAMP claims do not transfer to this installation. The vendor Azure reference diagram depicts the complete platform, Blob storage and PostgreSQL; its namespace label still says GKE, so validate the Azure-specific values with the vendor.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Helm Chart (AWS/GCP)","url":"https://help.hyperscience.ai/deployment/docs/helm-chart","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard. The Helm guide supplies complete AWS and GCP values, including application storage permissions. Registry integration alone is not a hosting badge. Hypercell application versions, Helm charts and Kubernetes support dates are separate. The October 2026 decoder advisory and the current v44 flow/block upgrade instructions must be checked before exposing document processing; hosted FedRAMP claims do not transfer to this installation. The vendor Azure reference diagram depicts the complete platform, Blob storage and PostgreSQL; its namespace label still says GKE, so validate the Azure-specific values with the vendor.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Kubernetes Installation Overview","url":"https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview","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":[0],"operator":"customer"}],"description":"Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"VM baseline documented; selected Kubernetes production footprint unresolved","source":"https://help.hyperscience.ai/deployment/docs/infrastructure-requirements.md","status":"inconclusive","summary":"The VM guide requires at least 8 logical cores with a 1:4 CPU-to-GB-RAM ratio and documents throughput examples. These VM numbers do not establish the complete Helm/Kubernetes namespace, trainer, database and object-store footprint. Obtain current chart resource values and workload/HA sizing; ORCA GPU requirements are separate.","supportingSources":[{"title":"Kubernetes dependencies and deployment boundary","url":"https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview.md"}]},"iac":{"artifactRef":"Vendor-provided HS_HELM_CHART; choose compatible application/chart releases","artifactUrl":"https://help.hyperscience.ai/deployment/docs/artifacts-management-and-hsk8s-hyperscience-kubernetes-cli","reviewed":"2026-11-20","scope":"Commercial Hypercell Kubernetes distribution; entitled artifacts required","source":"https://help.hyperscience.ai/deployment/docs/helm-chart","status":"documented","summary":"The vendor supplies an entitled Helm chart and hsk8s tooling, with AWS/GCP values examples and separate application-image delivery. Pin chart and application versions independently; configure external secrets, database, storage and worker/GPU tiers. Sample image tags do not establish the current supported release."},"licensePricing":{"reviewed":"2026-11-19","scope":"Hyperscience Hypercell; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://www.hyperscience.ai/legal-documents/eula/","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":"Private-cloud/on-premises Hyperscience identity configuration","source":"https://help.hyperscience.ai/deployment/docs/saml.md","status":"documented","summary":"The private-cloud deployment guide documents SP-initiated SAML federation using IdP metadata, attribute mapping and signed/encrypted assertion settings. Only one of SAML, OIDC, LDAP or Google authentication can be enabled. Confirm the application/chart version and licensed integration before rollout."}},"id":"hyperscience","infrastructure":["servers"],"infrastructureNotes":"Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://help.hyperscience.ai/deployment/docs/helm-chart","https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview"],"install":"Helm / Kubernetes operator; Kubernetes manifests","installMethods":["helm","kubernetes"],"kind":"product","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.hyperscience.ai/legal-documents/eula/"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Hyperscience Hypercell","notes":"The Helm guide supplies complete AWS and GCP values, including application storage permissions. Registry integration alone is not a hosting badge. Hypercell application versions, Helm charts and Kubernetes support dates are separate. The October 2026 decoder advisory and the current v44 flow/block upgrade instructions must be checked before exposing document processing; hosted FedRAMP claims do not transfer to this installation. The vendor Azure reference diagram depicts the complete platform, Blob storage and PostgreSQL; its namespace label still says GKE, so validate the Azure-specific values with the vendor. Apply the fix for the installed Hypercell line and follow the documented sequential upgrades or temporary workarounds.","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":"Helm Chart (AWS/GCP)","url":"https://help.hyperscience.ai/deployment/docs/helm-chart"},{"title":"Kubernetes Installation Overview","url":"https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview"},{"title":"hsk8s CLI (ECR/GAR)","url":"https://help.hyperscience.ai/deployment/docs/artifacts-management-and-hsk8s-hyperscience-kubernetes-cli"},{"title":"Gov Mailrooms \u0026 Correspondence","url":"https://www.hyperscience.ai/blog/the-trusted-ai-infrastructure-behind-modern-government/"},{"title":"Hyperscience EULA","url":"https://www.hyperscience.ai/legal-documents/eula/"},{"title":"V44 Release Notes (2026-11-18)","url":"https://help.hyperscience.ai/docs/v44-release-notes"},{"title":"Security Advisory (2026-10-30)","url":"https://help.hyperscience.ai/docs/security-advisory"},{"title":"Helm Releases","url":"https://help.hyperscience.ai/deployment/docs/news-and-release-notes"},{"title":"Hypercell Brotli decoder remediation","url":"https://help.hyperscience.ai/docs/security-advisory"}],"url":"https://launchinyourcloud.com/directory/hyperscience/","website":"https://help.hyperscience.ai/deployment/docs/helm-chart"},{"advisories":[{"action":"Check the installed container version and current IBM bulletins. For affected 12.1.0 deployments, obtain the designated fixed or later supported bundle and follow the vendor upgrade procedure.","conditions":"Exposure depends on the affected components and CVE-specific prerequisites in the bulletin. The reviewed record does not establish the current entitled container bundle.","disclosedOn":"2025-11-07","id":"ibm-cognos-certified-containers-12-1-0-fixes","listingIds":["ibm-cognos-analytics-certified-containers"],"reviewed":"2026-11-17","scope":"IBM bulletin published 2025-11-07 for Certified Containers 12.1.0; not a claim that every newer Cognos release or deployment is affected.","source":"https://www.ibm.com/support/pages/node/7250395","summary":"IBM bulletin 7250395 identifies PostgreSQL JDBC and information-disclosure vulnerabilities in Certified Containers 12.1.0, with 12.1.1 named as the fix.","title":"Cognos Certified Containers 12.1.0 fixes available","type":"security-advisory"}],"architecture":"Customer-operated Kubernetes cluster running IBM Cognos containers with external databases, authentication, storage and ingress.","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Enterprise reporting, dashboards, governed analytics and data exploration delivered by customer-managed Cognos containers."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"IBM documents the certified Cognos containers on Amazon EKS, Microsoft AKS and Google GKE. Non-OpenShift support is narrower than the OpenShift delivery model.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Cognos Certified Containers on EKS, AKS and GKE","url":"https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models","vendorSupport":"not-assessed"},{"clouds":["ibm"],"notes":"IBM's Cognos ingress framework explicitly names IBM Cloud Kubernetes Service alongside EKS, AKS and GKE. The customer operates the cluster and external dependencies.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Cognos Certified Containers on IBM Cloud Kubernetes Service","url":"https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=files-ingress-cognos-analytics-framework-configuration","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-17","clouds":["aws","azure","gcp","ibm"],"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":"cloud-account","cloud":"ibm","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Customer-managed enterprise reporting and analytics deployed by Helm to a Kubernetes cluster in the customer's cloud.","diligence":{"airGap":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment","source":"https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers","status":"inconclusive","summary":"Registry entitlement and Helm deployment alone do not establish the complete offline image, licence, dependency and update workflow for Certified Containers."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment","source":"https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers","status":"inconclusive","summary":"Container entitlement and registry access do not establish qualifying Marketplace spend or contract-specific cloud credit eligibility."},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://www.ibm.com/support/pages/node/7250395","status":"inconclusive","summary":"The reviewed IBM Cognos Analytics Certified Containers 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://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers","status":"inconclusive","summary":"Obtain the current entitled container bundle, report concurrency, HA services, content-store database, storage and licence metric. User count and data volume do not size reporting/AI dependencies. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"Certified Containers sizing; desktop/agent-only requirements excluded","source":"https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers","status":"inconclusive","summary":"The reviewed container installation requires cluster, storage and deployment configuration, but did not establish a complete numerical HA sizing model for 100 users/1 TB, including reporting concurrency and auxiliary services."},"iac":{"reviewed":"2026-11-17","scope":"Cognos Analytics 12.1.x Certified Containers","source":"https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers","status":"documented","summary":"IBM supplies entitled container images and Helm deployment for Certified Containers. Obtain the registry entitlement and configure ingress, persistent storage and the selected cluster; OpenShift and other Kubernetes platforms have different support boundaries."},"licensePricing":{"reviewed":"2026-11-17","scope":"IBM Cognos Analytics Certified Containers: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=cognos-analytics-offerings","status":"documented","summary":"Certified Containers are a separately licensed IBM product. Installation retrieves entitled images and Helm artifacts with an IBM entitlement key."},"marketplace":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment","source":"https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers","status":"inconclusive","summary":"Entitled registry images and Helm installation are documented; a current Marketplace offer for this Certified Containers edition was not established. Cognos hosted offerings are separate."},"release":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment","source":"https://www.ibm.com/support/pages/node/7250395","status":"inconclusive","summary":"IBM identifies container release-specific fixes, including 12.1.0 to 12.1.1 remediation, but the reviewed public records did not establish the latest entitled container/chart bundle and publication date."},"scim":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for IBM Cognos Analytics Certified Containers; unresolved within this edition/deployment","source":"https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=providers-creating-dynamic-namespace-in-manage-component","status":"inconclusive","summary":"The reviewed 12.1.x namespace guide supports LDAP/OIDC providers, but does not establish a Certified Containers SCIM endpoint and lifecycle operations."},"securityControls":{"reviewed":"2026-11-17","scope":"Certified Containers 12.1.0-specific security bulletin; historical affected/fixed scope","source":"https://www.ibm.com/support/pages/node/7250395","status":"documented","summary":"IBM bulletin 7250395 identifies Certified Containers 12.1.0 vulnerabilities and names 12.1.1 as the fix. Check the deployed container release against current bulletins; this historical fix is not a claim that newer releases have no vulnerabilities."},"sso":{"availability":"available","reviewed":"2026-11-17","scope":"Cognos 12.1.x identity configuration; not a Cloud-only entitlement","source":"https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=providers-creating-dynamic-namespace-in-manage-component","status":"documented","summary":"Cognos 12.1.x documents dynamic OpenID Connect namespaces with a configured supported IdP and administrative capabilities. Confirm the namespace/provider settings for the selected container deployment."}},"id":"ibm-cognos-analytics-certified-containers","infrastructure":["servers"],"infrastructureNotes":"The product runs as persistent containerized services on a customer Kubernetes cluster and requires external stateful services, ingress and production capacity planning.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=containers-overview","https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers"],"install":"Install IBM's entitled Cognos Analytics Helm chart on customer-managed Kubernetes","installMethods":["helm","kubernetes"],"kind":"product","license":"Commercial, separately licensed Cognos Analytics Certified Containers entitlement.","licenseModel":"commercial-only","licenseModelNotes":"Certified Containers are a separately licensed IBM product. Installation retrieves entitled images and Helm artifacts with an IBM entitlement key.","licenseModelSources":["https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=cognos-analytics-offerings","https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"IBM Cognos Analytics Certified Containers","notes":"This entry covers Cognos Analytics Certified Containers, not IBM-hosted or on-demand Cognos offerings. Installation requires an IBM entitlement key and registry access. Support on EKS, AKS, GKE and other non-OpenShift platforms is narrower than on Red Hat OpenShift and is focused on the Cognos software, certified images, Helm orchestration, deployment and updates.","operations":"Customer manages Kubernetes, databases, authentication, storage, ingress, capacity, backups and upgrades; IBM support scope varies by platform.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Cognos Analytics offerings","url":"https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=cognos-analytics-offerings"},{"title":"Certified Containers overview","url":"https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=containers-overview"},{"title":"Container delivery support policy","url":"https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=overview-support-policy-container-delivery-models"},{"title":"Ingress configuration for named Kubernetes services","url":"https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=files-ingress-cognos-analytics-framework-configuration"},{"title":"Installing and deploying Certified Containers","url":"https://www.ibm.com/docs/en/cognos-analytics/12.1.x?topic=installing-deploying-cognos-analytics-certified-containers"}],"url":"https://launchinyourcloud.com/directory/ibm-cognos-analytics-certified-containers/","website":"https://www.ibm.com/products/cognos-analytics"},{"architecture":"Planning Analytics cartridge on IBM Software Hub and a supported customer OpenShift cluster with persistent TM1 and Workspace storage.","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Licensed self-managed planning, budgeting and multidimensional analytics cartridge."},"cloudEvidence":[{"clouds":["ibm","aws","azure","gcp"],"notes":"Planning Analytics cartridge on IBM Software Hub and a supported customer OpenShift cluster with persistent TM1 and Workspace storage. Current Software Hub 5.4 guidance provides an application-specific install-components workflow and explicitly supports IBM Cloud, AWS, Azure and Google Cloud platform installations. Keep the platform/cartridge release aligned and verify permitted storage. The older Azure PDF is historical background; Local, SaaS, TM1 and cartridge versions and licences are separate.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Application deployment guidance","url":"https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["ibm","aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"ibm","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"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":"Licensed self-managed planning, budgeting and multidimensional analytics cartridge.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Planning Analytics cartridge current full production sizing remains unconfirmed","source":"https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing","status":"inconclusive","summary":"Software Hub/OpenShift platform requirements are additional to the Planning Analytics cartridge and model/data resources. A complete current cartridge-specific CPU/RAM/storage and HA baseline was not verified from accessible material; standalone/TM1 or vendor-hosted sizing must not be substituted."},"iac":{"artifactRef":"master (moving CASE package index)","artifactUrl":"https://github.com/IBM/cloud-pak/blob/master/repo/case/ibm-planning-analytics/index.yaml","reviewed":"2026-11-19","scope":"Planning Analytics CASE package metadata; select a compatible release and licensed image source","source":"https://github.com/IBM/cloud-pak/blob/master/repo/case/ibm-planning-analytics/index.yaml","status":"documented","summary":"IBM publishes a CASE package index for Planning Analytics, separate from Local and SaaS releases. Use the application-specific install-components workflow and keep the cartridge and Software Hub refresh aligned."},"licensePricing":{"reviewed":"2026-11-19","scope":"IBM Planning Analytics Cartridge; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://www.ibm.com/products/planning-analytics/pricing","status":"documented","summary":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation."},"sso":{"reviewed":"2026-11-21","scope":"Planning Analytics cartridge on Software Hub; selected-edition user federation remains unconfirmed","source":"https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing","status":"inconclusive","summary":"The reviewed Software Hub cartridge installation context does not establish its exact user SSO configuration. Separate Planning Analytics Cloud IBMid and Advanced Certified Containers OIDC guides apply to different offerings; confirm the cartridge release, platform/user mapping and configured provider before transferring those claims."}},"id":"ibm-planning-analytics","infrastructure":["servers"],"infrastructureNotes":"Planning Analytics cartridge on IBM Software Hub and a supported customer OpenShift cluster with persistent TM1 and Workspace storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing"],"install":"Kubernetes manifests","installMethods":["kubernetes"],"kind":"product","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.ibm.com/products/planning-analytics/pricing"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"IBM Planning Analytics Cartridge","notes":"Current Software Hub 5.4 guidance provides an application-specific install-components workflow and explicitly supports IBM Cloud, AWS, Azure and Google Cloud platform installations. Keep the platform/cartridge release aligned and verify permitted storage. The older Azure PDF is historical background; Local, SaaS, TM1 and cartridge versions and licences are separate.","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":"Additional reviewed source","url":"https://www.ibm.com/docs/en/software-hub/5.4.x?topic=pa-installing"},{"title":"IBM Cloud CP4D Services","url":"https://github.com/ibm-cloud-docs/cloud-pak-data/blob/master/install-services.md"},{"title":"Azure ARO PA Guide (PDF)","url":"https://cp4dazuremarketplacedoc.blob.core.windows.net/ibmcp4dazuremarketplace/CP4D_MS_ARO_Deployment_Guide.pdf"},{"title":"PA Pricing \u0026 CP4D Cartridge","url":"https://www.ibm.com/products/planning-analytics/pricing"},{"title":"CP4D Docs Commits","url":"https://github.com/ibm-cloud-docs/cloud-pak-data/commits/master"},{"title":"PA CASE Index (v5.4.5)","url":"https://github.com/IBM/cloud-pak/blob/master/repo/case/ibm-planning-analytics/index.yaml"},{"title":"PA CASE Commits","url":"https://github.com/IBM/cloud-pak/commits/master/repo/case/ibm-planning-analytics"},{"title":"Current Software Hub cloud installation environments","url":"https://www.ibm.com/docs/en/software-hub/5.4.x?topic=cluster-installing-red-hat-openshift"},{"title":"License information for IBM Software Hub 5.4 and related services","url":"https://www.ibm.com/support/pages/node/7275162/"}],"url":"https://launchinyourcloud.com/directory/ibm-planning-analytics/","website":"https://github.com/ibm-cloud-docs/cloud-pak-data"},{"advisories":[{"action":"Upgrade to v0.167.13 or later and retest least-privilege delegated automation.","conditions":"Scope-narrowed delegated tokens and automation using administration or workspace-list operations are affected; some calls may newly return 403.","disclosedOn":"2026-11-19","id":"infisical-0-167-13-delegated-token-authorization","listingIds":["infisical-self-hosted"],"reviewed":"2026-11-19","scope":"Delegated OAuth tokens and workspace listing; no complete affected-version range was published.","source":"https://github.com/Infisical/infisical/pull/9607","summary":"Infisical now enforces delegated OAuth-token scopes ahead of role-only administration checks and denies approval, rejection and bypass operations.","supportingSources":[{"title":"v0.167.13 release","url":"https://github.com/Infisical/infisical/releases/tag/v0.167.13"}],"title":"Infisical v0.167.13 delegated-token authorization hardening","type":"security-advisory"}],"architecture":"Persistent application containers with PostgreSQL, Redis and cloud networking/secrets services","categories":["identity-access-management"],"category":"Identity \u0026 access management","categoryFit":{"identity-access-management":"Centralizes application secrets and related access/configuration workflows. Certificate, privileged-access and enterprise features depend on the licensed edition and selected components."},"cloudEvidence":[{"clouds":["aws"],"notes":"Includes application task definition and service creation, RDS PostgreSQL, ElastiCache, load balancing, IAM/secrets and upgrade steps. The optional Terraform/CloudFormation summaries are incomplete examples. Use current pinned application versions and review networking, database transport and credentials.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Vendor ECS/Fargate installation in the customer AWS account","url":"https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/aws-native.mdx","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Provisions GKE, Cloud SQL and Memorystore and installs the application Helm release in the operator project. Review supported chart/image versions, VPC access, TLS, key backup and database migrations. This is an application deployment, distinct from connecting Infisical to Google secrets APIs.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Vendor GKE installation in the customer Google Cloud project","url":"https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/gcp-native.mdx","vendorSupport":"not-assessed"},{"clouds":["vultr"],"notes":"Provider instructions install the application, PostgreSQL, Redis and TLS proxy on an operator-controlled Ubuntu server. Customer manages OS, application updates and data/key recovery; generic cloud integrations are not additional hosting evidence.","reviewed":"2026-11-13","sourceType":"provider-guide","title":"Vultr application deployment with Docker Compose","url":"https://docs.vultr.com/how-to-deploy-infisical-secrets-management-platform","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-13","clouds":["aws","gcp","vultr"],"communityAcceptance":{"reviewed":"2026-11-13","sources":[{"title":"Reviewed application release","url":"https://github.com/Infisical/infisical/releases/tag/v0.167.10"},{"title":"Contributor history","url":"https://github.com/Infisical/infisical/graphs/contributors"}],"summary":"Upstream has sustained participation from multiple substantive contributors and frequent maintained releases, including 0.167.10 on the review date. This is a maintained community/commercial project, not a configuration-only Terraform provider."},"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":"cloud-account","cloud":"vultr","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Self-hosted secrets-management platform with application and machine-identity access workflows.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Current self-hosted application, PostgreSQL and Redis resource guidance; not a total operating-cost estimate","source":"https://infisical.com/docs/self-hosting/configuration/requirements","status":"documented","summary":"The small-deployment guide specifies at least two application instances, each 2 CPU cores/4 GB RAM, plus PostgreSQL at 2 vCPU/8 GB/100 GB disk and Redis at 2 vCPU/4 GB/30 GB SSD. Redis is a persistent required datastore, not a disposable cache. These component baselines need additional replication/storage planning for your throughput, audit retention and HA targets."},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://infisical.com/docs/self-hosting/deployment-options/docker-compose","status":"documented","summary":"The official self-hosting guide documents Compose with PostgreSQL and Redis. Configure the required encryption/authentication secrets, persistence and HTTPS; commercial features require their own license entitlement."},"licensePricing":{"reviewed":"2026-11-14","scope":"Vendor self-hosted pricing policy; no infrastructure or labor estimate","source":"https://infisical.com/pricing","status":"documented","summary":"The pricing FAQ explicitly says self-hosted pricing differs from Infisical Cloud and directs buyers to contact the vendor. Public Cloud per-identity prices must not be used as a self-hosted quote."},"release":{"releasePublishedAt":"2026-11-19T07:55:56Z","releaseTag":"v0.167.13","reviewed":"2026-11-19","scope":"Upstream Infisical self-hosted release; cloud packages and commercial editions may differ","source":"https://github.com/Infisical/infisical/releases/tag/v0.167.13","status":"documented","summary":"Infisical v0.167.13 was published November 19, 2026. It tightens delegated OAuth-token authorization and may cause formerly accepted scope-narrowed administration calls to return 403.","supportingSources":[{"title":"Prior reviewed release context","url":"https://github.com/Infisical/infisical/releases/tag/v0.167.10"},{"title":"Authorization change","url":"https://github.com/Infisical/infisical/pull/9607"}]},"scim":{"reviewed":"2026-11-14","scope":"Self-hosted commercial scope unresolved; Cloud tier names are not a substitute","source":"https://infisical.com/pricing","status":"inconclusive","summary":"The pricing page advertises Enterprise SCIM, but explicitly separates self-hosted pricing from Cloud. This pass did not establish the exact self-hosted license and provisioning entitlement; obtain the deployment-specific matrix."},"securityControls":{"reviewed":"2026-11-19","scope":"Infisical delegated OAuth tokens; the vendor did not publish a complete affected-version range","source":"https://github.com/Infisical/infisical/pull/9607","status":"documented","summary":"v0.167.13 denies delegated OAuth-token approval, rejection and bypass operations, enforces scope checks ahead of role-only administration checks and adds an organization-permission check to workspace listing. Retest delegated automation.","supportingSources":[{"title":"v0.167.13 release","url":"https://github.com/Infisical/infisical/releases/tag/v0.167.13"}]},"sso":{"availability":"edition-dependent","reviewed":"2026-11-20","scope":"Explicit self-hosted protocol/edition boundary; resolves the earlier Cloud-matrix-only question","source":"https://infisical.com/docs/documentation/platform/sso/overview","status":"documented","summary":"The detailed SSO guide explicitly includes free Google/GitHub login on self-hosted instances. SAML and OIDC require a self-hosted Enterprise licence, with organization email-domain verification and provider configuration. The Enterprise guide explains licence activation; Cloud Pro prices do not establish a self-hosted quote or SCIM entitlement.","supportingSources":[{"title":"Published v0.167.13 SSO guide","url":"https://github.com/Infisical/infisical/blob/v0.167.13/docs/documentation/platform/sso/overview.mdx"},{"title":"Self-hosted Enterprise licence activation","url":"https://github.com/Infisical/infisical/blob/v0.167.13/docs/self-hosting/ee.mdx"}]}},"id":"infisical-self-hosted","infrastructure":["servers"],"infrastructureNotes":"Persistent application containers with PostgreSQL, Redis and cloud networking/secrets services. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements.","infrastructureReviewed":"2026-11-13","infrastructureSources":["https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/aws-native.mdx","https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/gcp-native.mdx","https://docs.vultr.com/how-to-deploy-infisical-secrets-management-platform"],"install":"Official AWS ECS/Fargate and Google GKE deployment guides, or a Vultr Docker Compose guide; configure PostgreSQL, Redis, TLS and encryption keys.","installMethods":["docker"],"kind":"product","license":"MIT core outside enterprise directories; enterprise features and third-party components have separate terms.","licenseModel":"open-source","licenseModelNotes":"The repository licenses code outside ee directories under MIT, enterprise directories under their own license and incorporated third-party components under their original terms. Paid enterprise entitlements must be checked separately.","licenseModelSources":["https://github.com/Infisical/infisical/blob/main/LICENSE"],"licenseReviewed":"2026-11-13","model":"Fully in your account","modelLabel":"Customer-operated","name":"Infisical Self-Hosted","notes":"Review used upstream 0.167.10. Vendor AWS/GCP examples contain older version placeholders; pin a current compatible image/chart and use the complete installation steps, not the abbreviated infrastructure snippets alone. Preserve encryption keys independently of database backups. Configure telemetry, mail and external secret/infrastructure connections for the intended boundary. Infisical Cloud and agent-only integrations are separate. Infisical v0.167.13 tightens delegated OAuth-token authorization: scope-narrowed tokens no longer pass role-only administration checks, approval/rejection/bypass operations are denied, and workspace listing checks organization permission. Previously accepted delegated-token calls may return 403; retest automation with least-privilege scopes.","operations":"Customer owns the AWS account, Google project or Vultr instance and manages application identity, encryption keys, database recovery and upgrades. Providers operate selected managed infrastructure services.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Official AWS application deployment source","url":"https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/aws-native.mdx"},{"title":"Official GKE application deployment source","url":"https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/gcp-native.mdx"},{"title":"Standalone runtime requirements","url":"https://github.com/Infisical/infisical/blob/main/docs/self-hosting/deployment-options/standalone-infisical.mdx"},{"title":"Vultr application deployment with Docker Compose","url":"https://docs.vultr.com/how-to-deploy-infisical-secrets-management-platform"},{"title":"Exact upstream license boundaries","url":"https://github.com/Infisical/infisical/blob/main/LICENSE"},{"title":"Reviewed application release","url":"https://github.com/Infisical/infisical/releases/tag/v0.167.10"},{"title":"Contributor history","url":"https://github.com/Infisical/infisical/graphs/contributors"},{"title":"Infisical v0.167.13 release","url":"https://github.com/Infisical/infisical/releases/tag/v0.167.13"},{"title":"Delegated-token authorization hardening","url":"https://github.com/Infisical/infisical/pull/9607"}],"url":"https://launchinyourcloud.com/directory/infisical-self-hosted/","website":"https://infisical.com/"},{"architecture":"Persistent Docker server deployment with mounted application data, configuration, logs and backup directories.","categories":["project-management"],"category":"Project management","categoryFit":{"project-management":"Task and issue tracking with Scrum/Kanban boards, planning and progress reporting for project teams."},"cloudEvidence":[{"clouds":["aws","azure","gcp","oci"],"notes":"JetBrains names Amazon EKS, Azure Kubernetes Service, Oracle Container Engine for Kubernetes and Google Kubernetes Engine for YouTrack Server, with a worked GKE deployment. The instructions deploy a single YouTrack node with persistent volumes; multi-node application installations are not supported. Check the current image, license, storage and backup requirements rather than treating Kubernetes as application clustering.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"YouTrack Server Kubernetes deployment on named cloud services","url":"https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp","oci"],"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":"cloud-account","cloud":"oci","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Customer-hosted project and issue management application from JetBrains.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Upstream Server sizing guidelines; issue and attachment workload are material","source":"https://www.jetbrains.com/help/youtrack/server/youtrack-supported-environments.html","status":"documented","summary":"The Server 2026.2 guide states 1.5 GB minimum RAM with JVM minimums of 1,024 MB heap and 250 MB Metaspace. Storage guidance is roughly 1 GB per 5,000 issues before attachment variation. Database growth and transactions drive sizing; this is not a 1-TB HA topology."},"iac":{"artifactRef":"versioned image tag must be selected","artifactUrl":"https://hub.docker.com/r/jetbrains/youtrack","reviewed":"2026-11-14","scope":"YouTrack Server 2026.2 installation guide","source":"https://www.jetbrains.com/help/youtrack/server/youtrack-docker-installation.html","status":"documented","summary":"JetBrains distributes YouTrack Server as an official Docker image for evaluation and production. Configure persistent data/conf/log/backup directories and use a selected versioned image."},"licensePricing":{"reviewed":"2026-11-20","scope":"Current Server licensing; historical perpetual-license and Cloud pricing are separate","source":"https://www.jetbrains.com/help/youtrack/server/manage-youtrack-server-license.html","status":"documented","summary":"The current Server license guide grants free use for up to ten users and three helpdesk agents. New commercial purchases from June 23, 2026 use annual user-pack subscriptions; earlier perpetual licenses have different terms. Each installation needs its own license; confirm the current pack price and renewal terms."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"YouTrack Server 2026.2 user authentication, not a Cloud-only claim","source":"https://www.jetbrains.com/help/youtrack/server/saml-authentication-module.html","status":"documented","summary":"The Server SAML 2.0 module configures YouTrack as a service provider for an external identity provider. Configure metadata, certificate trust and callback URLs; login-time user/group updates differ from separately configured SCIM provisioning."}},"id":"youtrack-server","infrastructure":["servers"],"infrastructureNotes":"Persistent Docker server deployment with mounted application data, configuration, logs and backup directories.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://www.jetbrains.com/help/youtrack/server/installation-and-upgrade.html","https://www.jetbrains.com/help/youtrack/server/youtrack-docker-installation.html"],"install":"Official YouTrack Docker image and Server installation documentation","installMethods":["docker","package"],"kind":"product","license":"Proprietary YouTrack Server subscription; a limited free-user tier is available","licenseModel":"commercial-only","licenseModelNotes":"YouTrack Server is proprietary subscription software, including when used within its free-user allowance. The Server agreement and selected plan determine install rights, updates and user/agent entitlements.","licenseModelSources":["https://www.jetbrains.com/legal/docs/youtrack/subscription/","https://www.jetbrains.com/youtrack/buy/?section=server\u0026with-helpdesk=true"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"JetBrains YouTrack Server","notes":"This entry selects YouTrack Server. Free user allowances do not make the application open source, and each installation requires its own license. Review optional integrations and AI services separately from the self-hosted project-tracking deployment.","operations":"Customer manages Docker/server resources, persistent data, backups, TLS/network configuration and upgrades.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Official server installation and updates","url":"https://www.jetbrains.com/help/youtrack/server/installation-and-upgrade.html"},{"title":"Docker deployment and persistent directories","url":"https://www.jetbrains.com/help/youtrack/server/youtrack-docker-installation.html"},{"title":"Project-management functionality","url":"https://www.jetbrains.com/youtrack/features/agile_project_management.html"},{"title":"Server software subscription agreement","url":"https://www.jetbrains.com/legal/docs/youtrack/subscription/"},{"title":"Server/free-tier license scope","url":"https://www.jetbrains.com/youtrack/buy/?section=server\u0026with-helpdesk=true"}],"url":"https://launchinyourcloud.com/directory/youtrack-server/","website":"https://www.jetbrains.com/youtrack/"},{"advisories":[{"action":"Upgrade to the fixed or later supported build for the installed branch and review administrative access.","conditions":"The vendor identifies default configuration as affected; exact branch applicability follows the advisory matrix.","disclosedOn":"2026-08-28","id":"jfrog-artifactory-cve-2026-82329","listingIds":["jfrog-artifactory-self-hosted"],"reviewed":"2026-11-18","scope":"JFrog lists fixed builds 7.161.20, 7.146.38, 7.133.29, 7.125.20, 7.117.28, and 7.111.21 across maintained branches.","source":"https://docs.jfrog.com/releases/docs/jfrog-security-advisories","summary":"CVE-2026-82329 is a critical unauthenticated authentication bypass affecting default-configured Artifactory deployments.","title":"JFrog Artifactory unauthenticated authentication bypass","type":"security-advisory"}],"architecture":"Customer-operated Artifactory service with persistent filestore and database.","categories":["devops"],"category":"DevOps","categoryFit":{"devops":"Artifact, package and container registry for software delivery pipelines."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"JFrog's current Artifactory Helm guide explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as cluster types and documents installation into the customer's cluster. Provider storage, database, ingress and support details vary by edition.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Artifactory Helm installation on EKS, AKS and GKE","url":"https://docs.jfrog.com/installation/docs/helm-charts","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":"Universal artifact repository installed on Kubernetes clusters or servers you operate.","diligence":{"airGap":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"Licensed self-managed air-gap configuration","source":"https://docs.jfrog.com/installation/docs/configure-jfrog-platform-in-an-air-gapped-environment","status":"documented","summary":"Artifactory 7.77+ documents an air-gap setting and offline entitlement-file workflow. Obtain and renew the correct entitlement files and stage all dependencies; the 14-day license grace period can end in service disruption."},"commitments":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"JFrog Marketplace purchasing; provider contract and selected offer govern","source":"https://jfrog.com/cloud/","status":"documented","summary":"JFrog states approved cloud Marketplace purchases can draw down committed spend. Obtain confirmation for the self-hosted offer and buyer agreement; this is a conditional procurement statement, not universal credit eligibility.","supportingSources":[{"title":"Self-hosted Marketplace contracting","url":"https://jfrog.com/self-hosted-terms-and-conditions-10-01-2024/"}]},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds","status":"inconclusive","summary":"The reviewed JFrog Artifactory 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.jfrog.com/installation/docs/hardware-sizing-matrix","status":"inconclusive","summary":"Determine active artifact clients, package traffic, HA edition, database/filestore design and whether Xray/Workers are included. A 100-person headcount does not determine concurrent repository clients or scanning load. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"Artifactory active-client matrix; users are not necessarily simultaneous clients","source":"https://docs.jfrog.com/installation/docs/hardware-sizing-matrix","status":"documented","summary":"Artifactory sizing is based on active clients: the baseline starts at 4 cores/6 GB RAM for up to 20 clients, rising to 8 cores/18 GB for 101–200 clients. Database, HA, Xray and storage are additional sizing decisions."},"iac":{"reviewed":"2026-11-17","scope":"Self-managed Artifactory Helm installation","source":"https://docs.jfrog.com/installation/docs/helm-charts","status":"documented","summary":"JFrog supplies Helm installation paths for EKS, AKS and GKE. Configure master/join keys, persistent storage and the database, and pin compatible chart/application versions rather than treating Helm defaults as production sizing."},"licensePricing":{"reviewed":"2026-11-17","scope":"JFrog Artifactory Self-Hosted: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://jfrog.com/community/open-source/","status":"documented","summary":"JFrog publishes Artifactory OSS as an open-source edition and separately sells proprietary self-managed Pro X, Enterprise X and Enterprise+ subscriptions. Other community editions have different capability limits."},"marketplace":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"Self-hosted subscription procurement","source":"https://jfrog.com/self-hosted-terms-and-conditions-10-01-2024/","status":"documented","summary":"The self-hosted subscription agreement explicitly permits procurement through supported cloud marketplaces, with fees and terms in the offer/order form. This is software procurement, not proof that a SaaS offer deploys in the buyer account."},"release":{"reviewed":"2026-11-18","scope":"JFrog Artifactory self-managed release notes","source":"https://docs.jfrog.com/releases/docs/artifactory-release-notes","status":"documented","summary":"The reviewed current self-managed Artifactory release is 7.173.21. Older maintained branches have separate CVE-2026-82329 fixed builds; verify the selected branch before upgrading.","supportingSources":[{"title":"Self-managed lifecycle policy","url":"https://docs.jfrog.com/releases/docs/artifactory-end-of-life"}]},"scim":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"Self-managed Enterprise X / Enterprise+","source":"https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds","status":"documented","summary":"SCIM identity management is included in Enterprise X and Enterprise+, and excluded from Pro X and non-commercial editions. The API uses the Access SCIM v2 endpoint and a restricted identity-management token.","supportingSources":[{"title":"SCIM endpoint and token permissions","url":"https://docs.jfrog.com/administration/docs/scim"}]},"securityControls":{"reviewed":"2026-11-18","scope":"Self-managed component and feature entitlements; not an attestation JFrog lists fixed builds 7.161.20, 7.146.38, 7.133.29, 7.125.20, 7.117.28, and 7.111.21 across maintained branches.","source":"https://docs.jfrog.com/releases/docs/jfrog-security-advisories","status":"documented","summary":"The edition matrix distinguishes LDAP/RBAC from paid SAML, identity management, HA and scanning features. Xray and Advanced Security are separately entitled capabilities; do not assume the free Artifactory distribution includes them. Current advisory review: CVE-2026-82329 is a critical unauthenticated authentication bypass affecting default-configured Artifactory deployments. Upgrade to the fixed or later supported build for the installed branch and review administrative access.","supportingSources":[{"title":"Prior security-controls source","url":"https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds"}]},"sso":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"Self-managed Artifactory edition matrix","source":"https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds","status":"documented","summary":"SAML SSO is included from Pro X, including Enterprise X and Enterprise+; it is excluded from the non-commercial editions in the reviewed matrix.","supportingSources":[{"title":"SAML configuration","url":"https://docs.jfrog.com/administration/docs/saml-sso"}]}},"id":"jfrog-artifactory-self-hosted","infrastructure":["servers"],"infrastructureNotes":"Artifactory runs as server or container workloads with persistent database and filestore dependencies; the listed Helm path uses customer-operated Kubernetes infrastructure.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://docs.jfrog.com/installation/docs/helm-charts","https://docs.jfrog.com/installation/docs/installing-artifactory"],"install":"Helm chart, Docker or Docker Compose, or native OS package or archive","installMethods":["helm","kubernetes","docker","package"],"kind":"platform","license":"Open-source Artifactory OSS; commercial Pro X, Enterprise X and Enterprise+ editions.","licenseModel":"open-source","licenseModelNotes":"JFrog publishes Artifactory OSS as an open-source edition and separately sells proprietary self-managed Pro X, Enterprise X and Enterprise+ subscriptions. Other community editions have different capability limits.","licenseModelSources":["https://jfrog.com/community/open-source/","https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"JFrog Artifactory Self-Hosted","notes":"This entry covers self-hosted Artifactory, not JFrog SaaS. Edition capabilities differ substantially: Artifactory OSS is limited and does not include cloud object storage, while high availability and broader repository, security and platform capabilities require the applicable commercial entitlement. Production deployments should use an external PostgreSQL database and durable filestore. The separate Amazon ECS path is single-node, limited to 16 vCPUs and cannot connect to Xray or Distribution. CVE-2026-82329 is a critical unauthenticated authentication bypass under default configuration. JFrog lists fixed builds across maintained branches, including 7.161.20, 7.146.38, 7.133.29, 7.125.20, 7.117.28, and 7.111.21; move to a fixed or later supported build.","operations":"Customer operates the cluster or servers, database, filestore, backups, upgrades and availability configuration.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Artifactory installation with Helm charts","url":"https://docs.jfrog.com/installation/docs/helm-charts"},{"title":"Artifactory installation methods and Amazon ECS limits","url":"https://docs.jfrog.com/installation/docs/installing-artifactory"},{"title":"Self-managed edition feature comparison","url":"https://docs.jfrog.com/installation/docs/feature-comparison-matrix-for-self-mangaged-jpds"},{"title":"JFrog open-source offerings","url":"https://jfrog.com/community/open-source/"},{"title":"JFrog security advisories","url":"https://docs.jfrog.com/releases/docs/jfrog-security-advisories"},{"title":"Artifactory release notes","url":"https://docs.jfrog.com/releases/docs/artifactory-release-notes"}],"url":"https://launchinyourcloud.com/directory/jfrog-artifactory-self-hosted/","website":"https://jfrog.com/artifactory/"},{"advisories":[{"action":"Confirm purchase eligibility, migration timing and any written exception before evaluation.","conditions":"Existing-customer status and the purchased product determine eligibility.","effectiveDate":"2029-03-28","id":"atlassian-data-center-retirement","listingIds":["jira-software-data-center","jira-service-management-data-center","confluence-data-center"],"reviewed":"2026-11-16","scope":"Jira Software, Jira Service Management and Confluence Data Center. Bitbucket is excluded from this retirement; exceptional extensions require Atlassian agreement.","source":"https://www.atlassian.com/licensing/data-center-end-of-life","summary":"Affected subscriptions become read-only on March 28, 2029. New customers lost purchase eligibility on March 30, 2026; existing customers have a different expansion window.","title":"Data Center purchase restrictions and 2029 retirement","type":"lifecycle"},{"action":"Patch every affected installation to its fixed supported branch. If delayed, restrict internet access and apply the vendor WAF or product-specific rewrite mitigation to all relevant nodes.","conditions":"An attacker needs the exact file name and path; directory enumeration is not provided. Sensitive files in the application root change the risk.","id":"atlassian-cve-2026-21589","listingIds":["jira-software-data-center","jira-service-management-data-center","confluence-data-center","bitbucket-data-center"],"reviewed":"2026-11-17","scope":"Jira Software: 9.12.40/10.3.26/11.3.12; JSM: 5.12.40/10.3.26/11.3.12; Confluence: 9.2.26/10.2.19; Bitbucket: 9.4.26/10.2.8/10.5.1. Versions before the appropriate branch fix are affected.","source":"https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html","summary":"CVE-2026-21589 allows access to specifically named files under the web application root; Atlassian assigns critical severity.","title":"Atlassian Data Center unauthenticated file access","type":"security-advisory"},{"action":"Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility.","conditions":"Installed product, branch, bundled dependency, and Marketplace app compatibility determine applicability.","id":"atlassian-data-center-november-17-2026-bulletin","listingIds":["jira-software-data-center","confluence-data-center","bitbucket-data-center","jira-service-management-data-center"],"reviewed":"2026-11-18","scope":"Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.","source":"https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html","summary":"Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context.","title":"Atlassian Data Center November 17, 2026 bulletin","type":"security-advisory"}],"architecture":"Single-node or clustered Jira Service Management application nodes with an external database, load balancer, shared home, indexes and optional dedicated nodes","categories":["customer-support","devops"],"category":"Customer support","categoryFit":{"customer-support":"Provides self-managed service desks, request portals, queues, knowledge integration and service-management workflows.","devops":"Supports IT service management, incident response, change coordination and development-to-operations workflows."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Atlassian documents Jira Service Management Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Jira Service Management Data Center on EKS, AKS or GKE","url":"https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html","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 self-managed IT service management platform deployed on customer-operated infrastructure. New Data Center subscriptions are restricted to eligible existing Atlassian customers.","diligence":{"compliance":{"reviewed":"2026-11-16","scope":"Vendor reports versus this self-managed Data Center installation","source":"https://www.atlassian.com/trust/compliance/resources/soc2","status":"inconclusive","summary":"Atlassian’s public SOC 2 page points to product reports, but does not establish the customer-operated Data Center boundary or report validity. Review the actual report before claiming coverage."},"footprint":{"reviewed":"2026-11-16","scope":"JSM 11.3.x extra-large benchmark; representative workload sizing remains necessary","source":"https://confluence.atlassian.com/servicemanagement/jira-service-management-11-3-x-long-term-support-release-performance-report-1689289059.html","status":"documented","summary":"The vendor’s 11.3.x extra-large benchmark uses three r5.8xlarge application nodes, 30 GB Java heap per node and a separate db.m6i.4xlarge PostgreSQL 16.9 database in AWS ap-southeast-2. Its dataset includes about 3.1 million issues and 6,471 agents. This is a test configuration, not a universal minimum or a performance/cost guarantee."},"iac":{"artifactRef":"main (moving branch; select product-compatible chart and application release)","artifactUrl":"https://github.com/atlassian/data-center-helm-charts","reviewed":"2026-11-16","scope":"Jira Service Management Data Center; existing-customer eligibility and lifecycle conditions apply","source":"https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html","status":"documented","summary":"Atlassian publishes product-specific Data Center Helm charts. Select a chart and application version supported for this product and configure its database, persistent storage, ingress and license; one product’s chart does not establish compatibility for another."},"licensePricing":{"reviewed":"2026-11-16","scope":"Jira Service Management Data Center: software license terms; infrastructure and operating costs are separate","source":"https://www.atlassian.com/licensing/data-center","status":"documented","summary":"New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies.","supportingSources":[{"title":"Edition and license conditions","url":"https://www.atlassian.com/licensing/data-center-end-of-life"}]},"release":{"releasePublishedOn":"2026-11-05","releaseTag":"11.3.13","reviewed":"2026-11-16","scope":"Vendor current-download feed; publication day only, with no invented release time","source":"https://my.atlassian.com/download/feeds/current/jira-servicedesk.json","status":"documented","summary":"Atlassian’s current-download feed lists 11.3.13, released 2026-11-05. This is the reviewed download snapshot, not a guarantee that every other release branch, Helm chart, app or upgrade path is compatible. Existing-customer and lifecycle restrictions still apply.","supportingSources":[{"title":"Vendor release notes","url":"https://confluence.atlassian.com/display/SERVICEDESK/JIRA+Service+Management+11.3.x+release+notes"}]},"scim":{"reviewed":"2026-11-16","scope":"Native Data Center cloud-IdP integration described by Atlassian; not an assessment of every Marketplace add-on","source":"https://confluence.atlassian.com/enterprise/manage-users-between-cloud-and-data-center-products-1085188069.html","status":"documented","summary":"Atlassian’s native cloud-IdP scenario uses login-time JIT provisioning for Data Center, without regular synchronization or de-provisioning. Its cloud SCIM path is different; third-party Data Center provisioning apps require separate review."},"securityControls":{"reviewed":"2026-11-18","scope":"Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.","source":"https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html","status":"documented","summary":"Current advisory review: Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility.","supportingSources":[]},"sso":{"availability":"available","reviewed":"2026-11-16","scope":"Jira Service Management Data Center 5.15+; not Atlassian Guard cloud customer provisioning","source":"https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html","status":"documented","summary":"The Data Center SSO guide explicitly covers Jira Service Management 5.15+. SAML login can include customer-portal logins when enabled; application access remains separately configured."}},"id":"jira-service-management-data-center","infrastructure":["servers"],"infrastructureNotes":"Jira Service Management Data Center runs persistent Jira application services with durable database, shared-home and local-index storage.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html","https://confluence.atlassian.com/security/jira-service-management-data-center-architecture-and-infrastructure-options-1409093042.html"],"install":"Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based Jira Data Center installation","installMethods":["helm","kubernetes","package"],"kind":"product","license":"Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029.","licenseModel":"commercial-only","licenseModelNotes":"New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies.","licenseModelSources":["https://www.atlassian.com/licensing/data-center","https://www.atlassian.com/licensing/data-center-end-of-life"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"Jira Service Management Data Center","notes":"This entry covers Jira Service Management Data Center, not Atlassian Cloud. Atlassian supports its Kubernetes Helm chart and documents EKS, AKS and GKE as managed cluster options. The older AWS Quick Start and Azure Resource Manager templates are no longer supported or maintained. Atlassian states that affected Data Center subscriptions and associated Marketplace apps expire on March 28, 2029, after which the applications become read-only; evaluate the migration timeline before a new deployment. New customers cannot purchase this Data Center subscription after March 30, 2026. The remaining purchase/expansion window through March 30, 2028 is for existing Data Center customers; do not treat this listing as an unrestricted new-customer offering. Atlassian rates CVE-2026-21589 critical (9.3). All Jira Service Management Data Center versions before the fixed 5.12.40, 10.3.26, or 11.3.12 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Tomcat rewrite mitigation. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.","operations":"Customer manages Kubernetes or hosts, the database, shared and local storage, load balancing, networking, TLS, identity, email, Marketplace apps, backups, monitoring and upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Install Jira Data Center","url":"https://confluence.atlassian.com/security/installing-jira-data-center-1409092898.html"},{"title":"Run Jira Service Management Data Center on Kubernetes","url":"https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html"},{"title":"Jira Service Management Data Center architecture","url":"https://confluence.atlassian.com/security/jira-service-management-data-center-architecture-and-infrastructure-options-1409093042.html"},{"title":"Atlassian Data Center licensing and end of life","url":"https://www.atlassian.com/licensing/data-center"},{"title":"Atlassian product-specific end-of-life and purchase eligibility","url":"https://www.atlassian.com/licensing/data-center-end-of-life"},{"title":"Atlassian CVE-2026-21589 critical file-access advisory","url":"https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html"},{"title":"Atlassian security bulletin — November 17, 2026","url":"https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html"}],"url":"https://launchinyourcloud.com/directory/jira-service-management-data-center/","website":"https://www.atlassian.com/software/jira/service-management/enterprise"},{"advisories":[{"action":"Confirm purchase eligibility, migration timing and any written exception before evaluation.","conditions":"Existing-customer status and the purchased product determine eligibility.","effectiveDate":"2029-03-28","id":"atlassian-data-center-retirement","listingIds":["jira-software-data-center","jira-service-management-data-center","confluence-data-center"],"reviewed":"2026-11-16","scope":"Jira Software, Jira Service Management and Confluence Data Center. Bitbucket is excluded from this retirement; exceptional extensions require Atlassian agreement.","source":"https://www.atlassian.com/licensing/data-center-end-of-life","summary":"Affected subscriptions become read-only on March 28, 2029. New customers lost purchase eligibility on March 30, 2026; existing customers have a different expansion window.","title":"Data Center purchase restrictions and 2029 retirement","type":"lifecycle"},{"action":"Patch every affected installation to its fixed supported branch. If delayed, restrict internet access and apply the vendor WAF or product-specific rewrite mitigation to all relevant nodes.","conditions":"An attacker needs the exact file name and path; directory enumeration is not provided. Sensitive files in the application root change the risk.","id":"atlassian-cve-2026-21589","listingIds":["jira-software-data-center","jira-service-management-data-center","confluence-data-center","bitbucket-data-center"],"reviewed":"2026-11-17","scope":"Jira Software: 9.12.40/10.3.26/11.3.12; JSM: 5.12.40/10.3.26/11.3.12; Confluence: 9.2.26/10.2.19; Bitbucket: 9.4.26/10.2.8/10.5.1. Versions before the appropriate branch fix are affected.","source":"https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html","summary":"CVE-2026-21589 allows access to specifically named files under the web application root; Atlassian assigns critical severity.","title":"Atlassian Data Center unauthenticated file access","type":"security-advisory"},{"action":"Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility.","conditions":"Installed product, branch, bundled dependency, and Marketplace app compatibility determine applicability.","id":"atlassian-data-center-november-17-2026-bulletin","listingIds":["jira-software-data-center","confluence-data-center","bitbucket-data-center","jira-service-management-data-center"],"reviewed":"2026-11-18","scope":"Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.","source":"https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html","summary":"Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context.","title":"Atlassian Data Center November 17, 2026 bulletin","type":"security-advisory"}],"architecture":"Single-node or clustered Jira application nodes with an external database, load balancer, shared home, local indexes and optional dedicated nodes","categories":["project-management","devops"],"category":"Project management","categoryFit":{"devops":"Supports software-delivery planning, issue tracking, release coordination and integrations with development toolchains.","project-management":"Provides self-managed issue, project, planning and work-tracking capabilities for enterprise teams."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Atlassian documents Jira Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments. Atlassian supports the product and Helm chart, but not the underlying Kubernetes platform.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Jira Data Center on EKS, AKS or GKE","url":"https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html","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 self-managed Jira Software edition deployed on customer-operated cloud or Kubernetes infrastructure. New Data Center subscriptions are restricted to eligible existing Atlassian customers.","diligence":{"compliance":{"reviewed":"2026-11-16","scope":"Vendor reports versus this self-managed Data Center installation","source":"https://www.atlassian.com/trust/compliance/resources/soc2","status":"inconclusive","summary":"Atlassian’s public SOC 2 page points to product reports, but does not establish the customer-operated Data Center boundary or report validity. Review the actual report before claiming coverage."},"footprint":{"reviewed":"2026-11-16","scope":"Legacy small-installation example; not a current Data Center production sizing recommendation","source":"https://confluence.atlassian.com/adminjiraserver/jira-applications-installation-requirements-938846826.html","status":"documented","summary":"The installation guide, last modified in 2021, gives a multicore server with 8 GB available RAM for 100 projects, 1,000–5,000 issues and 100–200 users. This is a legacy small-installation example, not a current Data Center cluster minimum; size production nodes, supported database and storage separately."},"iac":{"artifactRef":"main (moving branch; select product-compatible chart and application release)","artifactUrl":"https://github.com/atlassian/data-center-helm-charts","reviewed":"2026-11-16","scope":"Jira Software Data Center; existing-customer eligibility and lifecycle conditions apply","source":"https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html","status":"documented","summary":"Atlassian publishes product-specific Data Center Helm charts. Select a chart and application version supported for this product and configure its database, persistent storage, ingress and license; one product’s chart does not establish compatibility for another."},"licensePricing":{"reviewed":"2026-11-16","scope":"Jira Software Data Center: software license terms; infrastructure and operating costs are separate","source":"https://www.atlassian.com/licensing/data-center","status":"documented","summary":"New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies.","supportingSources":[{"title":"Edition and license conditions","url":"https://www.atlassian.com/licensing/data-center-end-of-life"}]},"release":{"releasePublishedOn":"2026-11-05","releaseTag":"11.3.13","reviewed":"2026-11-16","scope":"Vendor current-download feed; publication day only, with no invented release time","source":"https://my.atlassian.com/download/feeds/current/jira-software.json","status":"documented","summary":"Atlassian’s current-download feed lists 11.3.13, released 2026-11-05. This is the reviewed download snapshot, not a guarantee that every other release branch, Helm chart, app or upgrade path is compatible. Existing-customer and lifecycle restrictions still apply.","supportingSources":[{"title":"Vendor release notes","url":"https://confluence.atlassian.com/display/JIRASOFTWARE/JIRA+Software+11.3.x+release+notes"}]},"scim":{"reviewed":"2026-11-16","scope":"Native Data Center cloud-IdP integration described by Atlassian; not an assessment of every Marketplace add-on","source":"https://confluence.atlassian.com/enterprise/manage-users-between-cloud-and-data-center-products-1085188069.html","status":"documented","summary":"Atlassian’s native cloud-IdP scenario uses login-time JIT provisioning for Data Center, without regular synchronization or de-provisioning. Its cloud SCIM path is different; third-party Data Center provisioning apps require separate review."},"securityControls":{"reviewed":"2026-11-18","scope":"Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.","source":"https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html","status":"documented","summary":"Current advisory review: Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility.","supportingSources":[]},"sso":{"availability":"available","reviewed":"2026-11-16","scope":"Jira Software 8.15+ Data Center SSO feature baseline; existing-customer lifecycle restrictions remain","source":"https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html","status":"documented","summary":"Atlassian documents SAML 2.0 and OIDC through its Data Center SSO app. Match app compatibility to Jira Software 8.15+; authentication does not assign application access or permissions.","supportingSources":[{"title":"OIDC product/version scope","url":"https://confluence.atlassian.com/enterprise/openid-connect-for-atlassian-data-center-applications-987142159.html"}]}},"id":"jira-software-data-center","infrastructure":["servers"],"infrastructureNotes":"Jira Data Center runs persistent application nodes with durable database, shared-home and index storage; managed Kubernetes supplies the cluster control plane but not a serverless application runtime.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html","https://confluence.atlassian.com/security/jira-data-center-architecture-and-infrastructure-options-1409092890.html"],"install":"Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based single-node and clustered installation","installMethods":["helm","kubernetes","package"],"kind":"product","license":"Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029.","licenseModel":"commercial-only","licenseModelNotes":"New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies.","licenseModelSources":["https://www.atlassian.com/licensing/data-center","https://www.atlassian.com/licensing/data-center-end-of-life"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"Jira Software Data Center","notes":"This entry covers Jira Software Data Center, not Jira Cloud. Atlassian supports its Kubernetes Helm chart and documents EKS, AKS and GKE as managed cluster options. The older AWS Quick Start and Azure Resource Manager templates are no longer supported or maintained, so they are not listed as current install methods. Atlassian states that affected Data Center subscriptions and associated Marketplace apps expire on March 28, 2029, after which the applications become read-only; evaluate the migration timeline before a new deployment. New customers cannot purchase this Data Center subscription after March 30, 2026. The remaining purchase/expansion window through March 30, 2028 is for existing Data Center customers; do not treat this listing as an unrestricted new-customer offering. Atlassian rates CVE-2026-21589 critical (9.3). All Jira Software Data Center versions before the fixed 9.12.40, 10.3.26, or 11.3.12 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Tomcat rewrite mitigation. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.","operations":"Customer manages Kubernetes or hosts, the database, shared and local storage, load balancing, networking, TLS, identity, Marketplace apps, backups, monitoring and upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Install Jira Data Center","url":"https://confluence.atlassian.com/security/installing-jira-data-center-1409092898.html"},{"title":"Run Jira Data Center on Kubernetes","url":"https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html"},{"title":"Jira Data Center architecture and infrastructure","url":"https://confluence.atlassian.com/security/jira-data-center-architecture-and-infrastructure-options-1409092890.html"},{"title":"Atlassian Data Center licensing and end of life","url":"https://www.atlassian.com/licensing/data-center"},{"title":"Atlassian product-specific end-of-life and purchase eligibility","url":"https://www.atlassian.com/licensing/data-center-end-of-life"},{"title":"Atlassian CVE-2026-21589 critical file-access advisory","url":"https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html"},{"title":"Atlassian security bulletin — November 17, 2026","url":"https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html"}],"url":"https://launchinyourcloud.com/directory/jira-software-data-center/","website":"https://www.atlassian.com/software/jira/enterprise"},{"advisories":[{"action":"Upgrade to v2.0.11 or later and retest browser and API authentication flows.","conditions":"Browser behavior changes when Basic authentication is used; dependency exposure depends on the deployed components.","id":"kestra-2-0-11-security-update","listingIds":["kestra"],"reviewed":"2026-11-18","scope":"Upstream v2.0.11 release; consult the dependency advisories for component-specific ranges.","source":"https://github.com/kestra-io/kestra/releases/tag/v2.0.11","summary":"Kestra v2.0.11 updates dependencies for CVE-2026-45292 and enforces CSRF tokens for Basic-auth browser requests.","title":"Kestra 2.0.11 dependency and CSRF update","type":"security-advisory"}],"architecture":"Customer-operated Kestra server and workers with PostgreSQL queue/repository state and object storage","categories":["workflow-orchestration"],"category":"Workflow orchestration","categoryFit":{"workflow-orchestration":"Orchestrates scheduled and event-driven data, infrastructure, business and AI workflows with customer-operated execution workers."},"cloudEvidence":[{"clouds":["aws"],"notes":"The vendor documents deploying Kestra on a customer EC2 instance and moving database and internal storage to customer RDS PostgreSQL and S3. Secure the application endpoint and replace example broad credentials with least-privilege IAM.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Kestra on Amazon EC2 with RDS and S3","url":"https://kestra.io/docs/installation/aws-ec2","vendorSupport":"not-assessed"},{"clouds":["aws"],"notes":"The vendor documents a distributed Helm deployment on customer EKS with RDS PostgreSQL, S3 storage and an AWS load balancer. Review cluster sizing, ingress, workload identity, backups and high-availability configuration.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Kestra on Amazon EKS with RDS and S3","url":"https://kestra.io/docs/installation/kubernetes-aws-eks","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The vendor documents creating a GKE cluster, installing the Kestra Helm chart, configuring Cloud SQL PostgreSQL and Cloud Storage, and using Workload Identity. The operator manages the application and cluster configuration, access, persistence and availability.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Kestra on Google GKE with Cloud SQL and Cloud Storage","url":"https://kestra.io/docs/installation/kubernetes-gcp-gke","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The vendor documents installing Kestra with Helm on a customer AKS cluster and configuring Azure Database for PostgreSQL, Blob Storage and ingress. Configure identities, secrets, network access and production availability for the selected deployment.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Kestra on Azure AKS with PostgreSQL and Blob Storage","url":"https://kestra.io/docs/installation/kubernetes-azure-aks","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"The vendor documents creating a customer Droplet, installing Docker and Kestra, and connecting DigitalOcean Managed PostgreSQL and Spaces storage. The customer operates the application and configures network access, credentials, persistent storage and backups.","reviewed":"2026-11-13","sourceType":"vendor-documentation","title":"Kestra on DigitalOcean Droplets with Managed Database and Spaces","url":"https://kestra.io/docs/installation/digitalocean-droplet","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-13","clouds":["aws","azure","gcp","digitalocean"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0,1],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[3],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"},{"boundary":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[4],"operator":"customer"}],"description":"Self-hosted orchestration platform for scheduled and event-driven workflows across data, infrastructure and applications.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Official AWS application starting point with separately configured database and object storage","source":"https://kestra.io/docs/installation/aws-ec2","status":"documented","summary":"The official EC2 guide starts Kestra at 2 vCPUs and 4 GiB RAM, suggesting t3.medium for its example. PostgreSQL, object storage, task execution and redundancy are separate capacities. Validate workflow/task concurrency and data movement; the example host is not a complete 1 TB HA production design."},"iac":{"artifactRef":"develop (moving branch); development example","artifactUrl":"https://raw.githubusercontent.com/kestra-io/kestra/develop/docker-compose.yml","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://kestra.io/docs/installation/docker-compose","status":"documented","summary":"The Compose guide provides a standalone server with PostgreSQL and a moving develop-branch recipe. Its root user and Docker socket example is for development; production hardening and licensed images are separate."},"licensePricing":{"reviewed":"2026-11-20","scope":"Published Kestra OSS core versus self-hosted Enterprise features","source":"https://github.com/kestra-io/kestra/blob/v2.0.11/LICENSE","status":"documented","summary":"The published v2.0.11 core is Apache-2.0 licensed. Enterprise authentication and other commercial features require their own edition agreement and are not granted by the OSS licence. Infrastructure, database/object storage, task execution and support costs are separate from software licensing.","supportingSources":[{"title":"Self-managed Enterprise SSO scope","url":"https://kestra.io/docs/enterprise/auth/sso"}]},"release":{"releasePublishedAt":"2026-11-17T14:26:39Z","releaseTag":"v2.0.11","reviewed":"2026-11-18","scope":"Upstream Kestra 2.0 release","source":"https://github.com/kestra-io/kestra/releases/tag/v2.0.11","status":"documented","summary":"Kestra v2.0.11 was published November 17, 2026. It updates dependencies for CVE-2026-45292 and other vulnerable libraries and enforces CSRF tokens on Basic-auth browser requests."},"securityControls":{"reviewed":"2026-11-18","scope":"Upstream v2.0.11 release; consult the dependency advisories for component-specific ranges.","source":"https://github.com/kestra-io/kestra/releases/tag/v2.0.11","status":"documented","summary":"Current advisory review: Kestra v2.0.11 updates dependencies for CVE-2026-45292 and enforces CSRF tokens for Basic-auth browser requests. Upgrade to v2.0.11 or later and retest browser and API authentication flows."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Self-managed Kestra Enterprise","source":"https://kestra.io/docs/enterprise/auth/sso","status":"documented","summary":"The Enterprise authentication guide documents OIDC single sign-on with providers such as Google, Microsoft, Okta and Keycloak. This does not establish SSO in the OSS edition."}},"id":"kestra","infrastructure":["servers"],"infrastructureNotes":"Kestra runs long-lived server and worker processes backed by PostgreSQL and object storage. The documented cloud paths use customer-configured compute or Kubernetes and managed database/storage services.","infrastructureReviewed":"2026-11-13","infrastructureSources":["https://kestra.io/docs/installation/aws-ec2","https://kestra.io/docs/installation/kubernetes-aws-eks","https://kestra.io/docs/installation/kubernetes-gcp-gke","https://kestra.io/docs/installation/kubernetes-azure-aks","https://kestra.io/docs/installation/digitalocean-droplet"],"install":"Docker on AWS EC2 or DigitalOcean Droplets, or Helm on AWS EKS, Google GKE or Azure AKS, with documented database and object storage services.","installMethods":["helm","docker"],"kind":"product","license":"Apache License 2.0 for the open-source Kestra platform; commercial Enterprise features and support are separate.","licenseModel":"open-source","licenseModelNotes":"The reviewed Kestra platform is Apache-2.0 licensed. Commercial Enterprise features and support are separately licensed and do not change the upstream open-source classification.","licenseModelSources":["https://github.com/kestra-io/kestra/blob/develop/LICENSE"],"licenseReviewed":"2026-11-13","model":"Fully in your account","modelLabel":"Customer-operated","name":"Kestra Self-Hosted","notes":"Vendor guides cover AWS, Azure, Google Cloud and DigitalOcean deployments, including single-VM starting points and distributed Kubernetes installations. Customers operate the application, database and storage configuration; production ingress, authentication, credentials and high availability depend on the selected topology. Enterprise features and support are separately licensed. Kestra v2.0.11 updates dependencies for CVE-2026-45292 and other vulnerable libraries and adds CSRF tokens to Basic-auth browser requests. Recheck browser automation and authenticated API clients after upgrading.","operations":"Customer manages server and worker capacity, PostgreSQL, object storage, plugins, credentials, network access, backups and upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"AWS EC2 deployment with RDS and S3","url":"https://kestra.io/docs/installation/aws-ec2"},{"title":"AWS EKS deployment with RDS and S3","url":"https://kestra.io/docs/installation/kubernetes-aws-eks"},{"title":"Apache 2.0 project license","url":"https://github.com/kestra-io/kestra/blob/develop/LICENSE"},{"title":"Kestra on Google GKE with Cloud SQL and Cloud Storage","url":"https://kestra.io/docs/installation/kubernetes-gcp-gke"},{"title":"Kestra on Azure AKS with PostgreSQL and Blob Storage","url":"https://kestra.io/docs/installation/kubernetes-azure-aks"},{"title":"Kestra on DigitalOcean Droplets with Managed Database and Spaces","url":"https://kestra.io/docs/installation/digitalocean-droplet"},{"title":"Kestra v2.0.11 release","url":"https://github.com/kestra-io/kestra/releases/tag/v2.0.11"}],"url":"https://launchinyourcloud.com/directory/kestra/","website":"https://kestra.io/"},{"architecture":"Single Marketplace virtual machine containing KNIME Business Hub services and execution infrastructure with persistent customer storage","categories":["data-analytics","ai-tools"],"category":"Data \u0026 analytics","categoryFit":{"ai-tools":"Provides customer-operated execution and governance for data-science, machine-learning and generative-AI workflows.","data-analytics":"Provides governed collaboration, automation, execution and deployment for analytical workflows and data applications."},"cloudEvidence":[{"clouds":["aws"],"notes":"KNIME documents launching Business Hub from an AWS Marketplace AMI into the customer's AWS account, with Marketplace or BYOL software licensing.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"KNIME Business Hub on AWS Marketplace","url":"https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"KNIME documents launching Business Hub from an Azure Marketplace single-VM image into the customer's Azure subscription.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"KNIME Business Hub on Azure Marketplace","url":"https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"KNIME documents launching Business Hub through Google Cloud Marketplace using a Google Compute VM image in the customer's project.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"KNIME Business Hub on Google Cloud Marketplace","url":"https://docs.knime.com/hub/latest/gc_marketplace_business_hub_guide/","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":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Commercial workflow collaboration and automation platform launched from AWS, Azure or Google Cloud Marketplace VM images.","diligence":{"airGap":{"availability":"edition-dependent","reviewed":"2026-11-16","scope":"Customer-managed Argo CD installation; not an automatic entitlement or procedure for every Marketplace VM","source":"https://docs.knime.com/hub/latest/business_hub_argocd_installation_guide/prerequisites","status":"documented","summary":"The customer-managed Argo CD guide supplies an airgap bundle containing images and Helm charts. Obtain the target-version bundle from KNIME, import it into private registries and apply registry overrides. The guide requires Self Hosted Premium for the covered on-premises installation."},"compliance":{"reviewed":"2026-11-16","scope":"Knime-managed service documentation versus customer-managed Business Hub","source":"https://docs.knime.com/admin/security/","status":"inconclusive","summary":"The reviewed security manual explicitly describes a Knime-managed AWS/Azure account. Its ISO and encryption statements therefore do not establish a current attestation for this customer-managed Business Hub installation; obtain the applicable report/certificate scope."},"footprint":{"reviewed":"2026-11-16","scope":"AWS Marketplace single-VM starting configuration; not a cost or HA estimate","source":"https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/","status":"documented","summary":"The AWS AMI guide recommends m5.4xlarge and one 512 GiB EBS volume as the starting minimum. Workflow load, backup and failover needs can require more."},"iac":{"reviewed":"2026-11-16","scope":"Marketplace VM delivery, not a multi-node reference architecture","source":"https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/","status":"documented","summary":"KNIME documents single-VM Marketplace images for AWS, Azure and Google Cloud. These contain a local Kubernetes installation; custom infrastructure follows a separate installation path. Select an offer and region matching the intended edition and license.","supportingSources":[{"title":"Azure VM image deployment","url":"https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/"},{"title":"Google Cloud VM image deployment","url":"https://docs.knime.com/hub/latest/gc_marketplace_business_hub_guide/"}]},"licensePricing":{"reviewed":"2026-11-16","scope":"KNIME Business Hub: software license terms; infrastructure and operating costs are separate","source":"https://www.knime.com/knime-hub-pricing","status":"documented","summary":"KNIME Business Hub Basic, Standard and Enterprise are commercial offerings. Marketplace software pricing or a separately obtained BYOL license applies, depending on the selected image.","supportingSources":[{"title":"Edition and license conditions","url":"https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/"}]},"marketplace":{"availability":"edition-dependent","offers":[{"cloud":"aws","delivery":"Single-instance AMI; Basic PAYG","id":"prodview-nzgqreu746eq2","publisher":"KNIME","url":"https://aws.amazon.com/marketplace/pp/prodview-nzgqreu746eq2"},{"cloud":"aws","delivery":"Single-instance AMI; Standard PAYG","id":"prodview-cd3xzq7m5fqjg","publisher":"KNIME","url":"https://aws.amazon.com/marketplace/pp/prodview-cd3xzq7m5fqjg"},{"cloud":"aws","delivery":"Single-instance AMI; BYOL","id":"prodview-gwty5knsn4bp2","publisher":"KNIME","url":"https://aws.amazon.com/marketplace/pp/prodview-gwty5knsn4bp2"},{"cloud":"azure","delivery":"Virtual-machine image; Basic","id":"knime.knime-business-hub-basic","publisher":"KNIME","url":"https://azuremarketplace.microsoft.com/en-us/marketplace/apps/knime.knime-business-hub-basic?tab=Overview"},{"cloud":"azure","delivery":"Virtual-machine image; Standard","id":"knime.knime-business-hub-standard","publisher":"KNIME","url":"https://azuremarketplace.microsoft.com/en-us/marketplace/apps/knime.knime-business-hub-standard?tab=Overview"},{"cloud":"azure","delivery":"Virtual-machine image; BYOL","id":"knime.knime-business-hub-byol","publisher":"KNIME","url":"https://azuremarketplace.microsoft.com/en-us/marketplace/apps/knime.knime-business-hub-byol?tab=Overview"}],"reviewed":"2026-11-16","scope":"Vendor-linked AWS/Azure VM offers; region, edition and agreement govern purchase","source":"https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/","status":"documented","summary":"The official AWS and Azure guides link Basic, Standard and BYOL VM offers. PAYG software charges or a separate BYOL entitlement apply; cloud infrastructure charges are additional. Availability does not establish cloud-commitment eligibility.","supportingSources":[{"title":"Azure Marketplace offer links","url":"https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/"}]},"release":{"releasePublishedOn":"2026-09-03","releaseTag":"1.19.0","reviewed":"2026-11-16","scope":"Business Hub application release; Marketplace VM and installation-package versions require separate checks; source supplies a publication day, not a timestamp","source":"https://docs.knime.com/hub/latest/business_hub_release_notes/1.19/","status":"documented","summary":"The reviewed vendor release is 1.19.0, published 2026-09-03. This is a dated, scoped snapshot; it does not establish compatibility with another chart, cloud package or commercial edition."},"scim":{"availability":"edition-dependent","reviewed":"2026-11-16","scope":"Business Hub Standard/Enterprise; excludes Basic","source":"https://docs.knime.com/hub/latest/business_hub_advanced_admin_guide/","status":"documented","summary":"Standard and Enterprise document SCIM user/group provisioning, tested with Okta and Microsoft Entra ID. An administrator creates an application password/token; align usernames with the SSO mappings. Other SCIM clients are not covered by the stated test matrix."},"securityControls":{"reviewed":"2026-11-16","scope":"AWS Marketplace guide defaults; deployment configuration remains the customer’s responsibility","source":"https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/","status":"documented","summary":"The AWS guide says its default security group exposes application and administration ports to all IPs, and its default EBS volume is unencrypted. Restrict administrative access and configure encryption before production use."},"sso":{"availability":"available","reviewed":"2026-11-16","scope":"Customer-managed Business Hub identity setup; not the Knime-managed SaaS setup","source":"https://docs.knime.com/hub/latest/business_hub_installation_guide/","status":"documented","summary":"The customer-managed installation uses Keycloak and can federate to an external identity provider through SAML 2.0, OIDC or OAuth 2.0. Map required username, email and name attributes in the knime realm."}},"id":"knime-business-hub","infrastructure":["servers"],"infrastructureNotes":"The reviewed Marketplace paths run KNIME Business Hub and its execution services on a persistent virtual machine in the customer's cloud account.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/","https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/","https://docs.knime.com/hub/latest/gc_marketplace_business_hub_guide/"],"install":"Official AWS, Azure or Google Cloud Marketplace virtual-machine image","installMethods":["vm-image"],"kind":"product","license":"Commercial KNIME Business Hub license or Marketplace software subscription required.","licenseModel":"commercial-only","licenseModelNotes":"KNIME Business Hub Basic, Standard and Enterprise are commercial offerings. Marketplace software pricing or a separately obtained BYOL license applies, depending on the selected image.","licenseModelSources":["https://www.knime.com/knime-hub-pricing","https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"KNIME Business Hub","notes":"This entry covers customer-hosted KNIME Business Hub, not the open-source KNIME Analytics Platform or KNIME's managed Hub offering. Marketplace deployments use single VM images; production capacity, availability and recovery requirements must be assessed separately. Customer-provisioned Kubernetes installation requires the applicable Self Hosted Premium package. Cloud infrastructure charges are separate from KNIME software pricing.","operations":"Customer manages the cloud account, virtual machine, networking, DNS, TLS, identity, storage, backups, capacity, upgrades and Business Hub license.","publisher":false,"reviewed":"2026-11-16","sources":[{"title":"KNIME Business Hub on AWS Marketplace","url":"https://docs.knime.com/hub/latest/aws_marketplace_business_hub_guide/"},{"title":"KNIME Business Hub on Azure Marketplace","url":"https://docs.knime.com/hub/latest/azure_marketplace_business_hub_guide/"},{"title":"KNIME Business Hub on Google Cloud Marketplace","url":"https://docs.knime.com/hub/latest/gc_marketplace_business_hub_guide/"},{"title":"KNIME Business Hub installation guide","url":"https://docs.knime.com/hub/latest/business_hub_installation_guide/"},{"title":"KNIME Business Hub pricing and licensing","url":"https://www.knime.com/knime-hub-pricing"}],"url":"https://launchinyourcloud.com/directory/knime-business-hub/","website":"https://www.knime.com/knime-hub"},{"advisories":[{"action":"Upgrade Enterprise deployments to 3.16.0.2 or later and retest exact SAML Audience and issuer matching.","conditions":"Applicability depends on the enabled Enterprise authentication, cache, SAML, RBAC, forwarded-path, and LLM plugins.","disclosedOn":"2026-11-10","id":"kong-gateway-enterprise-3-16-0-2-security-update","listingIds":["kong-gateway"],"reviewed":"2026-11-18","scope":"Kong Gateway Enterprise plugins and features; the listing's separate community/core release snapshot is not replaced by this Enterprise build.","source":"https://developer.konghq.com/gateway/changelog/","summary":"Enterprise 3.16.0.2 fixes cache leakage across authentication contexts, request-callout cache keys, SAML audience validation, Admin API RBAC bypass, unsafe forwarded paths, and LLM usage-counter SQL injection.","title":"Kong Gateway Enterprise 3.16.0.2 security patch","type":"security-advisory"},{"action":"Upgrade the applicable maintained core branch and separately follow Enterprise guidance for the installed edition.","conditions":"HTTP/2 exposure and the exact bundled nginx build determine applicability.","disclosedOn":"2026-11-19","id":"kong-gateway-3-9-5-nginx-http2-fixes","listingIds":["kong-gateway"],"reviewed":"2026-11-19","scope":"Kong Gateway community/core 3.9 line with affected nginx HTTP/2 code; Enterprise and other branches are separately versioned.","source":"https://github.com/Kong/kong/blob/release/3.9.x/CHANGELOG.md#395","summary":"Kong Gateway community/core 3.9.5 applies nginx patches for CVE-2026-123007 and CVE-2026-123633.","supportingSources":[{"title":"Kong Gateway 3.9.5","url":"https://github.com/Kong/kong/releases/tag/3.9.5"},{"title":"nginx security advisories","url":"https://nginx.org/en/security_advisories.html"}],"title":"Kong Gateway 3.9.5 nginx HTTP/2 fixes","type":"security-advisory"}],"architecture":"Gateway proxy and administration services in database-backed, database-less or hybrid topologies on customer compute or Kubernetes","categories":["backend-platforms"],"category":"Backend platforms","categoryFit":{"backend-platforms":"Provides a self-managed API gateway for routing, authentication, traffic control, transformation, observability and extensible API policies."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Kong lists supported self-managed deployment platforms including Amazon EKS, ECS and Fargate; Azure AKS, Container Instances and Container Apps; and Google GKE, GKE Autopilot and Cloud Run. Edition-specific support entitlements should be confirmed separately.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Kong Gateway supported public-cloud deployment platforms","url":"https://developer.konghq.com/gateway/version-support-policy/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-16","clouds":["aws","azure","gcp"],"communityAcceptance":{"reviewed":"2026-11-16","sources":[{"title":"Kong Gateway releases","url":"https://github.com/Kong/kong/releases"},{"title":"Kong Gateway contributor history","url":"https://github.com/Kong/kong/graphs/contributors"}],"summary":"Kong maintains public upstream releases and contributor history for the Apache-licensed Kong Gateway core. This evidence establishes continuing project activity, not Enterprise support or support for every listed cloud topology."},"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":"Open-source and commercial self-managed API gateway with supported AWS, Azure and Google Cloud deployment platforms.","diligence":{"airGap":{"reviewed":"2026-11-16","scope":"Enterprise offline license validation only; not Konnect or blanket end-to-end air-gap certification","source":"https://developer.konghq.com/gateway/entities/license/","status":"documented","summary":"Self-managed Enterprise license validation does not require network connectivity: each node reads a supplied license at startup. This resolves offline license validation, but does not certify every plugin, integration, image source or update workflow as disconnected."},"compliance":{"reviewed":"2026-11-16","scope":"Vendor-stated product-versus-module validation boundary; not an assessment of other certifications","source":"https://developer.konghq.com/gateway/fips-support/","status":"documented","summary":"Kong explicitly says the Gateway FIPS package has not itself been submitted to a NIST testing lab for product validation. Its use of a validated cryptographic provider must not be presented as a certificate for the entire customer deployment."},"footprint":{"reviewed":"2026-11-16","scope":"Self-managed Gateway sizing guidelines, v3.4+; example resources are not throughput guarantees","source":"https://developer.konghq.com/gateway/resource-sizing-guidelines/","status":"documented","summary":"Kong publishes workload-based sizing rather than a fixed universal minimum. Its small per-node starting example is 1–2 CPU cores and 2–4 GB RAM; database/Redis, enabled plugins, configuration size and traffic must be sized separately."},"iac":{"artifactRef":"main (moving branch)","artifactUrl":"https://github.com/Kong/charts/tree/main/charts/kong","reviewed":"2026-11-16","scope":"Kong Gateway chart; open-source and Enterprise image entitlements differ","source":"https://developer.konghq.com/gateway/install/","status":"documented","summary":"The upstream Kong Helm chart deploys Gateway on Kubernetes. Select compatible chart, image and database settings; an Enterprise image/license does not follow automatically from installing the chart."},"licensePricing":{"reviewed":"2026-11-16","scope":"Kong Gateway Self-Managed: software license terms; infrastructure and operating costs are separate","source":"https://github.com/Kong/kong/blob/master/LICENSE","status":"documented","summary":"Kong Gateway's upstream core is Apache-2.0 licensed. Kong Gateway Enterprise adds separately licensed proprietary features and commercial support.","supportingSources":[{"title":"Edition and license conditions","url":"https://www.konghq.com/products/kong-gateway"}]},"marketplace":{"reviewed":"2026-11-16","scope":"Vendor Marketplace availability statement; exact self-managed offer records remain unverified","source":"https://developer.konghq.com/gateway/version-support-policy/","status":"inconclusive","summary":"Kong’s Gateway policy names AWS, Azure and Google Cloud marketplaces. The reviewed policy does not identify exact offers, publishers, delivery types or packaged versions. Confirm those records and the Gateway entitlement before treating a Konnect or third-party offer as the self-managed product."},"release":{"releasePublishedAt":"2026-11-19T10:33:35Z","releaseTag":"3.9.5","reviewed":"2026-11-19","scope":"Upstream Kong Gateway community/core 3.9 line; Enterprise and deployment packages may differ","source":"https://github.com/Kong/kong/releases/tag/3.9.5","status":"documented","summary":"Kong Gateway community/core 3.9.5 was published November 19, 2026. It applies nginx patches for CVE-2026-123007 and CVE-2026-123633. Enterprise releases, plugins and cloud packages remain separately versioned.","supportingSources":[{"title":"Prior reviewed release context","url":"https://github.com/Kong/kong/releases/tag/3.9.4"},{"title":"3.9.5 changelog","url":"https://github.com/Kong/kong/blob/release/3.9.x/CHANGELOG.md#395"}]},"securityControls":{"availability":"edition-dependent","reviewed":"2026-11-19","scope":"Kong Gateway community/core 3.9 line with affected nginx HTTP/2 code","source":"https://github.com/Kong/kong/blob/release/3.9.x/CHANGELOG.md#395","status":"documented","summary":"Enterprise v3.14+ offers an AMD64 FIPS 140-3 package using approved algorithms and an OpenSSL FIPS provider. Kong explicitly distinguishes its compliant package from a product submitted for NIST validation; configure the supported distribution and FIPS mode. Current advisory review: Enterprise 3.16.0.2 fixes cache leakage across authentication contexts, request-callout cache keys, SAML audience validation, Admin API RBAC bypass, unsafe forwarded paths, and LLM usage-counter SQL injection. Upgrade Enterprise deployments to 3.16.0.2 or later and retest exact SAML Audience and issuer matching. Current review: Community/core 3.9.5 applies nginx fixes for CVE-2026-123007 and CVE-2026-123633, HTTP/2 memory-corruption and use-after-free vulnerabilities. Upgrade the applicable maintained branch; do not substitute the 3.9 core tag for separately versioned Enterprise guidance.","supportingSources":[{"title":"Prior security-controls source","url":"https://developer.konghq.com/gateway/changelog/"},{"title":"Prior security-controls source","url":"https://developer.konghq.com/gateway/fips-support/"},{"title":"3.9.5 release","url":"https://github.com/Kong/kong/releases/tag/3.9.5"},{"title":"nginx advisories","url":"https://nginx.org/en/security_advisories.html"}]},"sso":{"availability":"edition-dependent","reviewed":"2026-11-16","scope":"Kong Gateway Enterprise Manager, v3.6+; not the Apache-licensed core alone","source":"https://developer.konghq.com/gateway/kong-manager/openid-connect/","status":"documented","summary":"Self-managed Kong Manager can authenticate administrators through OIDC using the Enterprise-only OpenID Connect plugin. The v3.6+ procedure uses kong.conf and differs from Konnect SSO and from authenticating API consumers.","supportingSources":[{"title":"Enterprise-only OIDC plugin","url":"https://developer.konghq.com/plugins/openid-connect/"}]}},"id":"kong-gateway","infrastructure":["servers"],"infrastructureNotes":"Kong Gateway runs persistent proxy and administration processes on Linux, Docker or Kubernetes, with an optional customer-managed datastore and control-plane services.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://developer.konghq.com/gateway/install/","https://developer.konghq.com/gateway/version-support-policy/"],"install":"Official Linux packages, Docker images, Helm chart or Kubernetes Operator","installMethods":["helm","docker","package"],"kind":"product","license":"Apache License 2.0 for the open-source core; Enterprise features use separate commercial licensing.","licenseModel":"open-source","licenseModelNotes":"Kong Gateway's upstream core is Apache-2.0 licensed. Kong Gateway Enterprise adds separately licensed proprietary features and commercial support.","licenseModelSources":["https://github.com/Kong/kong/blob/master/LICENSE","https://www.konghq.com/products/kong-gateway"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"Kong Gateway Self-Managed","notes":"This entry covers self-managed Kong Gateway, not Kong Konnect or Kong-managed cloud gateways. The open-source core and Enterprise distribution have different features and support entitlements. Validate the selected topology, package version, datastore mode and cloud-platform compatibility before deployment. Kong Gateway Enterprise 3.16.0.2 fixes authentication-context cache leakage, request-callout cache keys, SAML audience validation, Admin API RBAC self-protection, unsafe forwarded paths, and LLM usage-counter SQL injection. This Enterprise plugin guidance is separate from the listing's community/core 3.9.4 snapshot; exact SAML Audience and issuer matching may require configuration changes. Kong Gateway community/core 3.9.5 applies nginx patches for CVE-2026-123007 and CVE-2026-123633, HTTP/2 memory-corruption and use-after-free vulnerabilities. Upgrade the applicable maintained core line and separately follow Enterprise guidance for the installed edition.","operations":"Customer manages compute or Kubernetes, datastore topology, networking, TLS, plugins, secrets, configuration, monitoring, backups, scaling and upgrades. Enterprise users also manage subscription and license configuration.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Install Kong Gateway","url":"https://developer.konghq.com/gateway/install/"},{"title":"Kong Gateway public-cloud platform support","url":"https://developer.konghq.com/gateway/version-support-policy/"},{"title":"Kong Gateway edition comparison","url":"https://www.konghq.com/products/kong-gateway"},{"title":"Kong Gateway Apache 2.0 license","url":"https://github.com/Kong/kong/blob/master/LICENSE"},{"title":"Kong Gateway releases","url":"https://github.com/Kong/kong/releases"},{"title":"Kong Gateway contributor history","url":"https://github.com/Kong/kong/graphs/contributors"},{"title":"Kong Gateway Enterprise changelog","url":"https://developer.konghq.com/gateway/changelog/"},{"title":"Kong Gateway 3.9.5 release","url":"https://github.com/Kong/kong/releases/tag/3.9.5"},{"title":"Kong Gateway 3.9.5 changelog","url":"https://github.com/Kong/kong/blob/release/3.9.x/CHANGELOG.md#395"},{"title":"nginx security advisories","url":"https://nginx.org/en/security_advisories.html"}],"url":"https://launchinyourcloud.com/directory/kong-gateway/","website":"https://www.konghq.com/products/kong-gateway"},{"advisories":[{"action":"Upgrade to 1.13.3 or later and retest component policy and session revocation.","conditions":"Applicability depends on custom components, workflow execution mode, and native authentication.","id":"langflow-1-13-3-security-hardening","listingIds":["langflow"],"reviewed":"2026-11-18","scope":"Upstream 1.13.3 release notes; no consolidated affected-version range is asserted.","source":"https://github.com/langflow-ai/langflow/releases/tag/v1.13.3","summary":"Langflow 1.13.3 extends custom-component policy enforcement to background workflows and invalidates native sessions after password changes.","title":"Langflow 1.13.3 policy and session hardening","type":"security-advisory"}],"architecture":"Customer-operated flow application with persistent database and configured model/tool endpoints","categories":["ai-applications-rag","ai-tools"],"category":"AI applications \u0026 RAG","categoryFit":{"ai-applications-rag":"Visual builder and runtime for AI flows, agents and model integrations. Local model endpoints are configurable; a flow can also call externally hosted providers.","ai-tools":"Visual AI workflow and agent builder with Docker and persistent PostgreSQL deployment."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"The project explicitly identifies EKS, AKS and GKE for its Helm deployment. Separate the development IDE from the production runtime, and review PostgreSQL, model endpoints and external vector stores.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Langflow Kubernetes deployment architecture","url":"https://docs.langflow.org/deployment-architecture","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","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":"Visual AI workflow and agent builder with Docker and persistent PostgreSQL deployment.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Langflow OSS application baseline; model and production topology excluded","source":"https://docs.langflow.org/get-started-installation","status":"documented","summary":"Langflow OSS lists a dual-core CPU and 2 GB RAM minimum, recommending a multi-core CPU and at least 4 GB. This covers the Python application; external databases, model inference, workflow concurrency and HA are additional."},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://docs.langflow.org/deployment-docker","status":"documented","summary":"The Docker guide provides an official image and Compose with persistent PostgreSQL, plus custom-image options. Preserve database/flow data and configure secrets, access controls and model-provider credentials."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/langflow-ai/langflow/main/LICENSE","status":"documented","summary":"The reviewed upstream core is MIT licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Model weights and external model APIs require their own review."},"release":{"releasePublishedAt":"2026-11-17T21:22:27Z","releaseTag":"v1.13.3","reviewed":"2026-11-18","scope":"Upstream Langflow self-hosted release","source":"https://github.com/langflow-ai/langflow/releases/tag/v1.13.3","status":"documented","summary":"Langflow v1.13.3 was published November 17, 2026. It applies custom-component policy to background workflows, invalidates native sessions after password changes, updates security dependencies, and aligns Docker and wheel packaging."},"securityControls":{"reviewed":"2026-11-18","scope":"Upstream 1.13.3 release notes; no consolidated affected-version range is asserted.","source":"https://github.com/langflow-ai/langflow/releases/tag/v1.13.3","status":"documented","summary":"Current advisory review: Langflow 1.13.3 extends custom-component policy enforcement to background workflows and invalidates native sessions after password changes. Upgrade to 1.13.3 or later and retest component policy and session revocation."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Langflow 1.13 external-token validation with a separately operated SSO gateway","source":"https://docs.langflow.org/external-authentication","status":"documented","summary":"Current 1.13 documentation supports an upstream OIDC proxy/SSO gateway forwarding tokens that Langflow validates using issuer, audience and JWKS. It can provision a local user; built-in credentials remain a separate path. Configure the gateway and validation explicitly and replace development identity-provider examples."}},"id":"langflow","infrastructure":["servers"],"infrastructureNotes":"Official images run the application on a Docker host; the Compose deployment adds persistent PostgreSQL storage. Model-serving hardware is a separate requirement if inference is also self-hosted.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.langflow.org/deployment-docker"],"install":"Official Docker image or Docker Compose; Python installation and Kubernetes options are also documented.","installMethods":["docker","source"],"kind":"product","license":"MIT for the upstream project; connected models, providers and bundles have their own terms.","licenseModel":"open-source","licenseModelNotes":"The reviewed upstream Langflow project uses the MIT license. This classification covers that project; connected model weights, provider services and third-party components have their own terms.","licenseModelSources":["https://github.com/langflow-ai/langflow/blob/main/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Langflow Self-Hosted","notes":"The reviewed model-component docs support Ollama and configurable OpenAI-compatible endpoints as well as commercial providers. External models, embeddings, tools or custom components can move data beyond the host. Hosting Langflow is distinct from hosting those dependencies and from any vendor-managed service. Langflow 1.13.3 enforces custom-component policy in background workflows, invalidates native sessions after password changes, updates security dependencies, and aligns Docker and wheel packaging. Recheck custom components and session behavior after upgrading.","operations":"Customer manages the application, database, access controls, installed components, backups and version upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Docker and Docker Compose deployment","url":"https://docs.langflow.org/deployment-docker"},{"title":"Model components and local endpoints","url":"https://docs.langflow.org/components-models"},{"title":"Upstream MIT license","url":"https://github.com/langflow-ai/langflow/blob/main/LICENSE"},{"title":"Langflow 1.13.3 release","url":"https://github.com/langflow-ai/langflow/releases/tag/v1.13.3"}],"url":"https://launchinyourcloud.com/directory/langflow/","website":"https://www.langflow.org/"},{"advisories":[{"action":"Upgrade to v4.82.0 or later and restrict outbound SSO connectivity.","conditions":"Requires the affected GitHub Enterprise SSO configuration and a reachable outbound target.","id":"langfuse-4-82-0-github-enterprise-sso-ssrf","listingIds":["langfuse"],"reviewed":"2026-11-18","scope":"Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note.","source":"https://github.com/langfuse/langfuse/releases/tag/v4.82.0","summary":"Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO.","title":"Langfuse GitHub Enterprise SSO SSRF fix","type":"security-advisory"}],"architecture":"Application and worker containers with PostgreSQL, ClickHouse, Redis/Valkey and object storage","categories":["ai-observability","ai-tools","observability"],"category":"AI observability \u0026 LLMOps","categoryFit":{"ai-observability":"LLM/agent tracing, evaluation and prompt management deployed with customer-controlled storage. Evaluation and optional gateway providers must be scoped independently.","ai-tools":"Self-hosted LLM observability, evaluations and prompt-management platform.","observability":"Application/model traces and experiment visibility for AI workloads. Infrastructure metrics and broader application monitoring require separately selected tooling."},"cloudEvidence":[{"clouds":["aws"],"notes":"The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Langfuse customer cloud deployment on AWS","url":"https://langfuse.com/self-hosting/deployment/aws","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Langfuse customer cloud deployment on Azure","url":"https://langfuse.com/self-hosting/deployment/azure","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Langfuse customer cloud deployment on Google Cloud","url":"https://langfuse.com/self-hosting/deployment/gcp","vendorSupport":"not-assessed"},{"clouds":["railway"],"notes":"The vendor documents a community-maintained Railway template for the complete Langfuse v3 stack. This establishes that version-specific application deployment; the same page explicitly distinguishes the v4 alternatives. The vendor does not systematically test the community template. Review the template services, image tags, database timezones and upgrade path.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Langfuse v3 community Railway deployment","url":"https://langfuse.com/self-hosting/deployment/railway","vendorSupport":"not-assessed"},{"clouds":["render"],"notes":"The vendor documents a community-maintained v4 Blueprint with separate web and worker services, PostgreSQL, Key Value, ClickHouse and MinIO. It creates the full application in the customer Render workspace. Review service plans, persistent disks, object-storage exposure and recovery procedures; community support is best-effort.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Langfuse v4 community Render Blueprint","url":"https://langfuse.com/self-hosting/deployment/render","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","cloudScope":"Documented provider-specific deployment","clouds":["aws","azure","gcp","railway","render"],"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":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[3],"operator":"customer"},{"boundary":"platform-workspace","cloud":"render","controlPlane":"not-assessed","evidence":[4],"operator":"customer"}],"description":"Self-hosted LLM observability, evaluations and prompt-management platform.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Langfuse Web/Worker resource recommendation; backing services additional","source":"https://langfuse.com/self-hosting/deployment/infrastructure/containers","status":"documented","summary":"The vendor recommends at least 2 CPUs and 4 GB RAM for application containers and at least two Web instances for HA. Worker, ClickHouse, PostgreSQL, Redis and blob storage capacity are additional. Confirm per-container resources and retention/ingestion volume rather than treating this as the whole-stack footprint."},"iac":{"artifactRef":"main (moving branch)","artifactUrl":"https://github.com/langfuse/langfuse/blob/main/docker-compose.yml","reviewed":"2026-11-14","scope":"Upstream Compose recipe; supporting-service operations remain customer responsibilities","source":"https://github.com/langfuse/langfuse/blob/main/docker-compose.yml","status":"documented","summary":"The upstream Compose recipe defines application services and backing data services. Pin a compatible Langfuse release and review credentials, persistent storage and exposed ports."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/langfuse/langfuse/main/LICENSE","status":"documented","summary":"Core code is MIT licensed, while ee directories, including application and worker enterprise paths, use a separate enterprise licence. Optional commercial features and support need separate terms; underlying databases, object storage and model services are additional."},"release":{"releasePublishedAt":"2026-11-17T14:28:42Z","releaseTag":"v4.82.0","reviewed":"2026-11-18","scope":"Upstream Langfuse self-hosted release","source":"https://github.com/langfuse/langfuse/releases/tag/v4.82.0","status":"documented","summary":"Langfuse v4.82.0 was published November 17, 2026. It fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse."},"securityControls":{"reviewed":"2026-11-18","scope":"Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note.","source":"https://github.com/langfuse/langfuse/releases/tag/v4.82.0","status":"documented","summary":"Current advisory review: Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO. Upgrade to v4.82.0 or later and restrict outbound SSO connectivity."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Self-hosted OAuth/OIDC sign-in","source":"https://langfuse.com/self-hosting/security/authentication-and-sso","status":"documented","summary":"The self-hosted guide documents OAuth/OIDC providers including Keycloak, Okta, Entra ID and a custom issuer. Configure account linking, email verification and access policy; SCIM and separately licensed enterprise features require their own review."}},"id":"langfuse","infrastructure":["servers"],"infrastructureNotes":"The documented deployment uses application/worker containers and persistent database, cache and object-storage services. Host/cluster capacity and database operations remain part of the self-hosted system.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://langfuse.com/self-hosting/deployment/docker-compose","https://langfuse.com/self-hosting/deployment/aws","https://langfuse.com/self-hosting/deployment/azure","https://langfuse.com/self-hosting/deployment/gcp"],"install":"Docker Compose for a single VM; Helm/Kubernetes and official AWS, Azure and Google Cloud Terraform modules.","installMethods":["terraform","helm","docker"],"kind":"product","license":"MIT core; designated enterprise directories and add-on capabilities use separate license terms or keys.","licenseModel":"open-source","licenseModelNotes":"The main codebase uses MIT terms outside designated enterprise directories. Enterprise code requires a separate valid license, so the directory treats the combined product as open-core.","licenseModelSources":["https://github.com/langfuse/langfuse/blob/main/LICENSE","https://github.com/langfuse/langfuse/blob/main/ee/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Langfuse Self-Hosted","notes":"Traces can contain prompts, outputs and other sensitive application data, so configure capture and retention deliberately. Self-hosted trace storage does not move the underlying application model into the same account. Optional model-based evaluators or the gateway use configured providers, which may be external. The single-VM Compose example does not provide production high availability or backups. Langfuse v4.82.0 fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Review outbound SSO connectivity and audit-log storage during upgrade.","operations":"Customer operates the deployment, persistence, access policies, retention, backups and scaling.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Docker Compose on a VM","url":"https://langfuse.com/self-hosting/deployment/docker-compose"},{"title":"Self-hosting architecture and provider dependencies","url":"https://langfuse.com/self-hosting"},{"title":"AWS account Terraform deployment","url":"https://langfuse.com/self-hosting/deployment/aws"},{"title":"Azure account Terraform deployment","url":"https://langfuse.com/self-hosting/deployment/azure"},{"title":"Google Cloud account Terraform deployment","url":"https://langfuse.com/self-hosting/deployment/gcp"},{"title":"Core and enterprise licensing","url":"https://github.com/langfuse/langfuse/blob/main/LICENSE"},{"title":"Licensing and edition terms","url":"https://github.com/langfuse/langfuse/blob/main/ee/LICENSE"},{"title":"Langfuse v3 community Railway deployment","url":"https://langfuse.com/self-hosting/deployment/railway"},{"title":"Langfuse v4 community Render Blueprint","url":"https://langfuse.com/self-hosting/deployment/render"},{"title":"Langfuse v4.82.0 release","url":"https://github.com/langfuse/langfuse/releases/tag/v4.82.0"}],"url":"https://launchinyourcloud.com/directory/langfuse/","website":"https://langfuse.com/"},{"architecture":"Customer-operated EKS, AKS or GKE deployment integrated with provider database, object storage and search services.","categories":["content-management","digital-asset-management"],"category":"Content management \u0026 CMS","categoryFit":{"content-management":"Liferay DXP provides web and headless content authoring, publishing, sites and digital-experience delivery on customer infrastructure.","digital-asset-management":"The DXP includes digital asset management for organizing and reusing documents and media; exact entitlement follows the selected subscription."},"cloudEvidence":[{"clouds":["aws"],"notes":"Liferay documents automated deployment in the customer's AWS account with EKS, RDS, S3 and OpenSearch. Enterprise Subscription entitlement and customer cloud permissions are required.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Liferay DXP Cloud Native Experience AWS Ready","url":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Liferay documents Terraform, Argo CD and Kubernetes provisioning in the customer's Azure subscription, including AKS and managed data services.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Liferay DXP Cloud Native Experience Azure Ready","url":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-azure-ready","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Liferay documents Terraform, Argo CD and Kubernetes provisioning in the customer's Google Cloud environment, including GKE and managed data services.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Liferay DXP Cloud Native Experience GCP Ready","url":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-gcp-ready","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":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Commercial digital experience, content management and digital asset platform deployed into customer cloud infrastructure with Liferay's Cloud Native Experience toolkit.","diligence":{"airGap":{"reviewed":"2026-11-17","scope":"Path/version-specific offline licensing, not unconditional air-gap support","source":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/automatic-environment-licensing/licensing-an-offline-environment","status":"inconclusive","summary":"CNE documents offline activation bundles for AWS/GCP Ready, but Azure Ready 0.3.0 lacks the required Marketplace volume. This establishes offline licensing for selected paths; complete dependency mirroring, updates and integrations still need validation."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Liferay DXP Cloud Native Experience; unresolved within this edition/deployment","source":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/setting-up-liferay/activating-liferay-dxp","status":"inconclusive","summary":"DXP Enterprise activation and add-on delivery do not establish cloud-provider Marketplace commitment treatment."},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready","status":"inconclusive","summary":"The reviewed Liferay DXP Cloud Native Experience 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://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-kubernetes-ready/architecture-sizing-and-support-model","status":"inconclusive","summary":"The Small tier supplies app/search/HA-database starting requirements, but the complete provider bill of materials, DXP entitlement and measured content/search workload still need confirmation. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"Kubernetes Ready Small production starting tier; AWS Ready infrastructure defaults may differ","source":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-kubernetes-ready/architecture-sizing-and-support-model","status":"documented","summary":"The Kubernetes Ready Small tier uses two Liferay replicas, each requesting 2 CPU/12 GiB (limits 4 CPU/16 GiB), 20 GiB PVC per pod, an HA database, three search nodes and object storage. It targets up to 500 concurrent users but requires workload load testing."},"iac":{"artifactRef":"master (moving branch; select a compatible chart/image release)","artifactUrl":"https://github.com/liferay/liferay-portal/tree/master/cloud/helm/default","reviewed":"2026-11-17","scope":"Official Helm artifact for customer Kubernetes","source":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-kubernetes-ready","status":"documented","summary":"CNE Kubernetes Ready supplies the liferay-default Helm chart; supporting Kubernetes, database, search and object storage are customer-managed. This complements provider-specific Ready automation. Pin a chart compatible with the chosen DXP release."},"licensePricing":{"reviewed":"2026-11-17","scope":"Liferay DXP Cloud Native Experience: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/setting-up-liferay/activating-liferay-dxp","status":"documented","summary":"This entry is scoped to commercial Liferay DXP Cloud Native Experience, not Liferay Portal Community Edition. Provider-ready capabilities require Enterprise Subscription entitlement and DXP requires an activation key."},"marketplace":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Liferay DXP Cloud Native Experience; unresolved within this edition/deployment","source":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/automatic-environment-licensing","status":"inconclusive","summary":"CNE licensing refers to Liferay Marketplace add-ons, not a provider billing offer. A current cloud Marketplace offer for the selected CNE Enterprise path was not established."},"release":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Liferay DXP Cloud Native Experience; unresolved within this edition/deployment","source":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience","status":"inconclusive","summary":"CNE supports DXP 2024.Q1+ and provider tooling has independent revisions. The complete latest supported DXP/chart/operator/provider-Ready combination and publication dates were not established."},"scim":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"DXP subscription/version-specific provisioning","source":"https://learn.liferay.com/es/w/dxp/security-and-administration/security/system-for-cross-domain-identity-management-scim","status":"documented","summary":"DXP SCIM was introduced behind a flag in 2024.Q1, moved to a release flag in 2024.Q4 and became GA in 2025.Q1. Verify the deployed release and supported RFC operations; it does not implement arbitrary vendor schema extensions."},"securityControls":{"reviewed":"2026-11-17","scope":"AWS Ready deployment access and secrets","source":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready","status":"documented","summary":"The CNE deployment requires controlled GitOps access, cloud credentials and activation keys. Configure secrets, network boundaries and the certified identity/runtime components rather than treating cloud provisioning as hardening."},"sso":{"availability":"available","reviewed":"2026-11-17","scope":"Self-hosted DXP identity compatibility; reviewed 2025.Q2 matrix","source":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/reference/compatibility-matrices/liferay-dxp-2025-q2-compatibility-matrix","status":"documented","summary":"The DXP compatibility matrix documents SAML 2.0 and OIDC provider standards. Match the IdP and certified runtime components to the actual DXP release used by CNE."}},"id":"liferay-dxp-cloud-native-experience","infrastructure":["servers"],"infrastructureNotes":"Provider-ready CNE provisions managed Kubernetes and supporting stateful services in the customer's cloud. Liferay runs as persistent workloads managed through Helm and Argo CD.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience","https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready"],"install":"Provider-ready Terraform bootstrap with Kubernetes, Helm and Argo CD GitOps deployment","installMethods":["terraform","helm","kubernetes"],"kind":"platform","license":"Commercial Liferay DXP subscription; Cloud Native Experience provider-ready capabilities require Enterprise Subscription entitlement.","licenseModel":"commercial-only","licenseModelNotes":"This entry is scoped to commercial Liferay DXP Cloud Native Experience, not Liferay Portal Community Edition. Provider-ready capabilities require Enterprise Subscription entitlement and DXP requires an activation key.","licenseModelSources":["https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/setting-up-liferay/activating-liferay-dxp","https://learn.liferay.com/w/updates/release-notes/liferay-dxp/2026.q3/features/cloud-native-gcp-ready"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"Liferay DXP Cloud Native Experience","notes":"Cloud Native Experience supports Liferay DXP 2024.Q1 and later. Provider architectures differ: AWS Ready integrates RDS, S3 and OpenSearch; Azure Ready uses AKS, Azure PostgreSQL Flexible Server, Blob Storage and Elasticsearch through ECK; GCP Ready uses GKE, Cloud SQL, Cloud Storage and ECK. The customer must provide cloud permissions, a Git repository, secret storage, compatible tools and a valid activation key. Starting with DXP 2026.Q1, all installations require an activation key.","operations":"Customer manages the cloud account, GitOps repository, Kubernetes platform, secrets, domains, certificates, capacity, backups, upgrades and application customizations.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Cloud Native Experience overview","url":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience"},{"title":"AWS Ready deployment","url":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-aws-ready"},{"title":"Azure Ready deployment","url":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-azure-ready"},{"title":"GCP Ready deployment","url":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/cloud-native-experience/cne-cloud-provider-ready/cne-gcp-ready"},{"title":"Liferay DXP activation and subscription keys","url":"https://learn.liferay.com/w/dxp/self-hosted-installation-and-upgrades/setting-up-liferay/activating-liferay-dxp"},{"title":"AWS Ready Enterprise Subscription requirement","url":"https://learn.liferay.com/w/updates/release-notes/liferay-dxp/2026.q2/features/cloud-native-aws-ready-2026-q2-2"},{"title":"GCP Ready Enterprise Subscription requirement","url":"https://learn.liferay.com/w/updates/release-notes/liferay-dxp/2026.q3/features/cloud-native-gcp-ready"}],"url":"https://launchinyourcloud.com/directory/liferay-dxp-cloud-native-experience/","website":"https://www.liferay.com/products/dxp"},{"advisories":[{"action":"Upgrade the selected release line and recheck guardrail output and proxy-administrator permissions.","conditions":"Applicability depends on Bedrock guardrails and team-setting permissions.","id":"litellm-1-108-11-lts-security-fixes","listingIds":["litellm"],"reviewed":"2026-11-18","scope":"LiteLLM 1.108 LTS line; standard-line deployments should use their corresponding maintained release.","source":"https://github.com/BerriAI/litellm/releases/tag/v1.108.11","summary":"LiteLLM 1.108.11 LTS fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators.","title":"LiteLLM LTS proxy security fixes","type":"security-advisory"},{"action":"Upgrade the maintained LTS line to 1.108.12 or later and retest tool-policy enforcement.","conditions":"The request must use a blocked tool name longer than 64 characters.","disclosedOn":"2026-11-19","id":"litellm-1-108-12-tool-policy-bypass","listingIds":["litellm"],"reviewed":"2026-11-19","scope":"LiteLLM 1.108 LTS /v1/messages tool-policy enforcement.","source":"https://github.com/BerriAI/litellm/releases/tag/v1.108.12","summary":"LiteLLM 1.108.12 LTS prevents blocked tool names longer than 64 characters from bypassing tool_policy on /v1/messages.","title":"LiteLLM 1.108.12 LTS tool-policy fix","type":"security-advisory"}],"architecture":"Customer-operated gateway with optional PostgreSQL persistence and configured model endpoints","categories":["ai-inference-gateways","ai-tools"],"category":"AI inference \u0026 gateways","categoryFit":{"ai-inference-gateways":"Self-hosted model API gateway for routing, virtual keys, spend tracking and policy enforcement. It routes inference requests; it is not an inference engine for all supported models.","ai-tools":"Self-hosted AI API gateway providing model routing, access controls and usage tracking."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Official production guidance covers EKS, AKS and GKE with Helm, plus Terraform on AWS and Google Cloud. The proxy, database and Redis deployment is separate from the model services it calls.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"LiteLLM production deployment","url":"https://docs.litellm.ai/docs/proxy/deploy","vendorSupport":"not-assessed"},{"clouds":["railway","render"],"notes":"The current upstream deployment guide supplies Railway and Render deployment buttons in addition to its EKS/AKS/GKE instructions, followed by readiness and Admin UI verification. These are customer application deployments on managed platforms; configure persistent data, secrets and external model-provider endpoints separately.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"LiteLLM Railway and Render deployment options","url":"https://docs.litellm.ai/docs/proxy/deploy","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp","railway","render"],"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":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"platform-workspace","cloud":"render","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Self-hosted AI API gateway providing model routing, access controls and usage tracking.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Gateway per-worker load-test starting point; backing services and inference excluded","source":"https://docs.litellm.ai/docs/proxy/prod","status":"documented","summary":"The current production guide starts load testing at 1 vCPU and 4 GiB per worker, preferably one worker per Kubernetes pod. Memory depends on queued requests, payloads, stream duration and logging. PostgreSQL, Redis for multiple workers/instances, HA and model inference are additional."},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://docs.litellm.ai/docs/proxy/deploy/helm","status":"documented","summary":"The official Helm guide documents Kubernetes installation and configurable database/secret settings. Select matching chart/image versions and review the separate scaling and production-readiness guidance."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/BerriAI/litellm/main/LICENSE","status":"documented","summary":"Core code outside litellm/enterprise is MIT licensed; the enterprise directory has separate terms. Enterprise features and support need separate entitlement and pricing. Upstream model APIs, infrastructure and operating labour are additional."},"release":{"releasePublishedAt":"2026-11-19T05:05:03Z","releaseTag":"v1.110.1","reviewed":"2026-11-19","scope":"Upstream LiteLLM standard release; select and maintain either the standard or LTS line","source":"https://github.com/BerriAI/litellm/releases/tag/v1.110.1","status":"documented","summary":"LiteLLM v1.110.1 was published November 19, 2026. It refreshes the Wolfi base and changes the UI image to slim nginx, removing curl. The maintained v1.108.12 LTS line fixes a tool_policy bypass for blocked tool names longer than 64 characters.","supportingSources":[{"title":"Prior reviewed release context","url":"https://github.com/BerriAI/litellm/releases/tag/v1.110.0"},{"title":"LiteLLM v1.108.11 LTS","url":"https://github.com/BerriAI/litellm/releases/tag/v1.108.11"},{"title":"v1.108.12 LTS security fix","url":"https://github.com/BerriAI/litellm/releases/tag/v1.108.12"}]},"securityControls":{"reviewed":"2026-11-19","scope":"LiteLLM 1.108 LTS /v1/messages tool_policy; standard and other maintained lines require their own release review","source":"https://github.com/BerriAI/litellm/releases/tag/v1.108.12","status":"documented","summary":"Release images and Helm charts use keyless Cosign from v1.111.0-dev.3; verify the documented workflow identity and issuer. Earlier releases use historical keys. The October 21 v1.107.0 compromise also affected mutable image tags; compare digests and exposure windows because affected images had valid historical signatures. Follow the incident remediation guidance for executed artifacts. Current advisory review: LiteLLM 1.108.11 LTS fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators. Upgrade the selected release line and recheck guardrail output and proxy-administrator permissions. Current review: v1.108.12 LTS fixes tool_policy allowing a /v1/messages request through when a blocked tool name exceeded 64 characters. Upgrade the maintained LTS line and retest tool-policy enforcement.","supportingSources":[{"title":"Prior security-controls source","url":"https://github.com/BerriAI/litellm/releases/tag/v1.108.11"},{"title":"Canonical incident investigation","url":"https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chain"},{"title":"Prior security-controls source","url":"https://docs.litellm.ai/blog/security-incident-oct-21-2026"}]},"sso":{"availability":"edition-dependent","reviewed":"2026-11-20","scope":"LiteLLM Admin UI OIDC; user-count/Enterprise entitlement applies","source":"https://docs.litellm.ai/docs/proxy/admin_ui_sso","status":"documented","summary":"The Admin UI documents OIDC SSO. From 1.76.0, it is free for up to five users; larger deployments require an Enterprise licence. Configure issuer, callbacks, roles and database/master-key prerequisites. This is Admin UI identity, distinct from model API virtual keys."}},"id":"litellm","infrastructure":["servers"],"infrastructureNotes":"The gateway runs as provisioned application containers or Kubernetes workloads; persistent key/spend storage can use PostgreSQL. Inference compute is a separate dependency rather than included in the gateway.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.litellm.ai/docs/proxy/deploy"],"install":"Official container image, Docker Compose or Kubernetes deployment; production infrastructure examples are documented.","installMethods":["docker"],"kind":"product","license":"MIT outside the enterprise directory; enterprise code and features have separate license terms.","licenseModel":"open-source","licenseModelNotes":"The gateway has an MIT-licensed base and separately licensed enterprise features. The enterprise documentation describes a license key enabling restricted capabilities in the gateway, beyond paid hosting or support alone.","licenseModelSources":["https://github.com/BerriAI/litellm/blob/main/LICENSE","https://docs.litellm.ai/docs/enterprise"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"LiteLLM Proxy Self-Hosted","notes":"The gateway forwards each request to its configured model provider. Self-hosting the proxy does not ensure prompts stay inside the account: external model APIs, guardrail services and logging integrations can receive data. Use appropriate self-hosted inference endpoints and explicitly review outbound integrations when required. For release integrity, release images and the Helm chart starting with v1.111.0-dev.3 use keyless Cosign signatures bound to LiteLLM's release workflow; earlier releases require the documented historical public keys. The October 21 incident affected PyPI v1.107.0 and Docker Hub/GHCR v1.107.0 plus mutable latest, main-latest and main-stable tags during the documented exposure windows. Check the incident's artifact digests and remediation instructions; the compromised images carried valid historical signatures, so signature verification alone does not establish safety. LiteLLM v1.110.0 changes authentication, guardrail, accounting, and S3 behavior. The 1.108.11 LTS patch also fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators; review both the selected release line and existing incident-response or image-signing guidance. LiteLLM v1.108.12 LTS fixes tool_policy allowing blocked /v1/messages tool names longer than 64 characters. The standard v1.110.1 UI image changes to slim nginx and removes curl while retaining wget and nc, so retest health probes and scripts that assume curl.","operations":"Customer manages gateway availability, credentials, database, access policies, logs and upgrades, including pinning versions and verifying release artifacts with the documented version-appropriate Cosign method; model providers remain separate services.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Production deployment","url":"https://docs.litellm.ai/docs/proxy/deploy"},{"title":"Gateway request flow and functionality","url":"https://docs.litellm.ai/docs/simple_proxy"},{"title":"MIT core and enterprise exception","url":"https://github.com/BerriAI/litellm/blob/main/LICENSE"},{"title":"Licensing and edition terms","url":"https://docs.litellm.ai/docs/enterprise"},{"title":"Supply-chain incident and Cosign verification guidance","url":"https://docs.litellm.ai/blog/security-incident-oct-21-2026"},{"title":"Canonical LiteLLM incident investigation","url":"https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chain"},{"title":"LiteLLM v1.110.0 release","url":"https://github.com/BerriAI/litellm/releases/tag/v1.110.0"},{"title":"LiteLLM v1.108.11 LTS release","url":"https://github.com/BerriAI/litellm/releases/tag/v1.108.11"},{"title":"LiteLLM v1.110.1","url":"https://github.com/BerriAI/litellm/releases/tag/v1.110.1"},{"title":"LiteLLM v1.108.12 LTS","url":"https://github.com/BerriAI/litellm/releases/tag/v1.108.12"}],"url":"https://launchinyourcloud.com/directory/litellm/","website":"https://www.litellm.ai/"},{"architecture":"Persistent application with relational metadata database, document file storage and search services; selected components depend on edition.","categories":["document-management","vendor-supplier-document-management"],"category":"Document management","categoryFit":{"document-management":"Searchable repository, metadata, versioning and configurable document workflows in a commercial on-premises deployment.","vendor-supplier-document-management":"Supplier certificate storage, expiry tracking and configured reports, documented in the Lesepidado implementation."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"The vendor explicitly offers private-cloud installation on AWS, Azure and Google Cloud, separately from its managed LogicalDOC Cloud service. Confirm the commercial edition, system requirements and support agreement.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"LogicalDOC private-cloud deployment options","url":"https://www.logicaldoc.com/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","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":"Customer-hosted commercial document platform for controlled business files and supplier documentation.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Current vendor commercial-server requirements; verify against selected release","source":"https://www.logicaldoc.com/resources/system-requirements","status":"documented","summary":"The current vendor matrix specifies a dedicated 64-bit 2.5-GHz eight-core server, 24 GB memory and 512 GB fast disk for application deployment. It lists JDK 25 and current OS baselines. Concurrency, repository data, configuration and HA require additional sizing; older installation guides show different minima."},"iac":{"artifactRef":"Select a vendor-supported immutable image; catalog entry date is not a current release","artifactUrl":"https://hub.docker.com/r/logicaldoc/logicaldoc/","reviewed":"2026-11-20","scope":"Vendor commercial Docker distribution; current supported artifact version must be confirmed","source":"https://www.logicaldoc.com/download/docker-images","status":"documented","summary":"The vendor publishes a logicaldoc/logicaldoc image and links its Docker distribution source. A licence activation code is required, including for evaluation. The catalog entry is dated 2018; confirm a currently supported image tag and matching database/Java requirements before adopting it."},"licensePricing":{"reviewed":"2026-11-20","scope":"Commercial on-premises offer; quoted licence terms, not Community pricing","source":"https://www.logicaldoc.com/product/on-premise-dms","status":"documented","summary":"The on-premises offer requires commercial licences and directs buyers to request a quote. No numeric price is established by the reviewed product page. Agree user counts, edition, term and maintenance separately from hosting and operating costs."},"scim":{"reviewed":"2026-11-14","scope":"SAML/JIT documentation checked; SCIM remains unresolved","source":"https://docs.logicaldoc.com/en/access-control/saml-single-sign-on","status":"inconclusive","summary":"The SAML guide describes user creation at first login. It does not establish a SCIM provisioning/deprovisioning API or licensed entitlement; login-time account creation must not be labeled SCIM."},"sso":{"reviewed":"2026-11-14","scope":"Commercial LogicalDOC documentation; edition/contract entitlement not established","source":"https://docs.logicaldoc.com/en/access-control/saml-single-sign-on","status":"documented","summary":"The commercial administration guide documents SAML 2.0 service-provider integration, login-time account creation and optional single logout. It does not establish that every Business/Enterprise license includes the feature; confirm licensed features and test the identity provider."}},"id":"logicaldoc-commercial","infrastructure":["servers"],"infrastructureNotes":"Persistent application with relational metadata database, document file storage and search services; selected components depend on edition.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://www.logicaldoc.com/product/on-premise-dms","https://www.logicaldoc.com/product/architecture"],"install":"Licensed on-premises server installation","installMethods":["package"],"kind":"product","license":"Commercial edition under LogicalDOC EULA; separate Community Edition exists","licenseModel":"commercial-only","licenseModelNotes":"The selected licensed commercial edition follows LogicalDOC EULA restrictions. This classification does not cover the separate open-source Community Edition.","licenseModelSources":["https://www.logicaldoc.com/eula"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"LogicalDOC Commercial On-Premise","notes":"Scope is a licensed commercial on-premises edition, not Community Edition feature parity. The supplier-document example uses configured metadata, expiry dates and periodic reports; it is a document process rather than a supplier-assessment service.","operations":"Customer manages application, database, document storage, backups and upgrades; agree support scope and required commercial capabilities.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"On-premises deployment","url":"https://www.logicaldoc.com/product/on-premise-dms"},{"title":"Application and storage architecture","url":"https://www.logicaldoc.com/product/architecture"},{"title":"On-premises supplier certificate implementation","url":"https://www.logicaldoc.com/blog/660-lesepidado-logicaldoc-case-study"},{"title":"Commercial end-user license","url":"https://www.logicaldoc.com/eula"}],"url":"https://launchinyourcloud.com/directory/logicaldoc-commercial/","website":"https://www.logicaldoc.com/"},{"architecture":"Persistent customer-operated M-Files Server and vault/database infrastructure on Windows Server.","categories":["document-management","records-management","policy-procedure-management"],"category":"Document management","categoryFit":{"document-management":"Metadata-driven document vaults with controlled access, document relationships and workflows.","policy-procedure-management":"Configured SOP, compliance and training workflows supported by metadata, permissions and document lifecycle controls; not a separately verified turnkey policy module.","records-management":"Configurable records retention and disposition rules with document history and audit trails."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"The vendor documents customer-managed Windows Server virtual machines on AWS, Azure and Google Cloud as the same server deployment model used on-premises. This is distinct from M-Files Cloud; confirm server, vault/database and licensing requirements.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"M-Files self-managed cloud deployment","url":"https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","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":"Customer-operated document vault and information-governance platform with metadata-driven workflows.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Vendor single-server guidelines; application storage and HA excluded","source":"https://userguide.m-files.com/user-guide/latest/eng/hardware_guidelines_for_single_server_environments.html","status":"documented","summary":"The single-server guide lists 2 CPU cores, 1 GB RAM and 300 MB for M-Files Server itself. Its examples scale to 4 cores/4 GB for 50,000 objects and 8 cores/16 GB plus SQL Server for one million. File storage, database, backups and HA need separate sizing; these are object-count examples, not a 100-user guarantee."},"iac":{"artifactRef":"Vendor latest-download portal; authenticated or entitled access may be required","artifactUrl":"https://product.m-files.com/downloads/","reviewed":"2026-11-20","scope":"Current on-premises Windows installer distribution","source":"https://www.userguide.m-files.com/user-guide/latest/eng/Installing_the_software.html","status":"documented","summary":"The vendor supplies an installation package containing Server, Admin and optional desktop components. The guide links the latest package through the vendor download portal and documents advanced installation options. Package access and entitlements must be obtained; this is not a public infrastructure template."},"licensePricing":{"reviewed":"2026-11-20","scope":"On-premises server subscription and licence automation","source":"https://userguide.m-files.com/user-guide/latest/eng/?contextId=133304","status":"documented","summary":"The on-premises server is linked to a customer subscription using an initial licence from M-Files Manage. Automated renewal needs outbound licensing endpoints. This establishes subscription/licence delivery, not a published per-user price or infrastructure cost."},"scim":{"availability":"edition-dependent","reviewed":"2026-11-16","scope":"M-Files on-premises provisioning; Manage connection, method and client limitations differ","source":"https://userguide.m-files.com/user-guide/latest/eng/user_synchronization_entra_id.html","status":"documented","summary":"The guide documents subscription-level SCIM for on-premises servers joined to M-Files Manage. A separate vault-level Entra SCIM method requires Entra ID Premium and limits Entra authentication to Desktop; on-premises plugin-based synchronization is also documented."},"sso":{"availability":"available","reviewed":"2026-11-14","scope":"M-Files document-vault authentication; not Hubshare or automatic cloud login setup","source":"https://userguide.m-files.com/user-guide/latest/eng/document_vault_authentication.html","status":"documented","summary":"The vault authentication guide explicitly links on-premises Microsoft Entra configuration and OAuth 2.0/OIDC providers for any environment. Client/web-add-in configuration and licensed implementation requirements remain separate."}},"id":"m-files-on-premises","infrastructure":["servers"],"infrastructureNotes":"Persistent customer-operated M-Files Server and vault/database infrastructure on Windows Server.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html"],"install":"Licensed Windows Server installation; vendor implementation planning","installMethods":["package","vendor-assisted"],"kind":"platform","license":"Commercial subscription software; on-premises and support entitlements follow the order","licenseModel":"commercial-only","licenseModelNotes":"Commercial M-Files server subscription software. The EULA covers ordered on-premises or cloud software and associated licenses/support; this entry selects on-premises operation.","licenseModelSources":["https://empower.m-files.com/sfc/servlet.shepherd/version/download/068QA00000Y5dQGYAZ"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"M-Files On-Premises","notes":"Only customer-operated M-Files deployment is listed. The documented SOP and records patterns require configuration and possibly selected components. Confirm the available edition, deployment scope and integrations rather than assuming that every separately packaged cloud solution is included.","operations":"Customer maintains server infrastructure, vault backups and upgrades; review server requirements and the contracted support and licensing connections.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Customer-operated deployment options","url":"https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html"},{"title":"Records retention and disposition","url":"https://www.m-files.com/supplemental/records-management/"},{"title":"SOP, training and governance application patterns","url":"https://www.m-files.com/wp-content/uploads/2023/07/How-M-Files-Mitigates-Risks-for-Accounting-Firms.pdf"},{"title":"Software subscription license agreement","url":"https://empower.m-files.com/sfc/servlet.shepherd/version/download/068QA00000Y5dQGYAZ"}],"url":"https://launchinyourcloud.com/directory/m-files-on-premises/","website":"https://www.m-files.com/"},{"architecture":"Customer-operated analytics application and MySQL/MariaDB database with scheduled report processing","categories":["web-analytics","data-analytics"],"category":"Web analytics","categoryFit":{"data-analytics":"Website analytics and reporting over collected visitor and event data; scope is web measurement rather than a general data warehouse.","web-analytics":"Website traffic, campaign and behavior analytics on customer-controlled servers; premium analytics plugins have separate commercial licensing."},"cloudEvidence":[{"clouds":["aws","azure","gcp","alibaba"],"notes":"The vendor explicitly confirms Matomo On-Premise compatibility with AWS, Azure, Google Cloud and Alibaba Cloud, and links its installation requirements. This is a compatibility statement, not a cloud-provider certification or a managed Matomo Cloud offering.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Matomo named-cloud compatibility FAQ","url":"https://matomo.org/faq/how-to-install/faq_31411/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp","alibaba"],"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":"cloud-account","cloud":"alibaba","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Self-hosted web analytics with visitor, campaign and website reporting on customer servers.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"On-premises traffic-tier recommendations; not a benchmark or total operating-cost estimate","source":"https://matomo.org/faq/on-premise/matomo-requirements/","status":"documented","summary":"For up to 100k monthly page views the vendor suggests one server with 2 CPUs, 2 GB RAM and 50 GB SSD; at 1 million, 4 CPUs, 8 GB and 250 GB SSD. Larger workloads separate database and application roles. Tracking requests, segments and retention govern sizing; 100 internal users and 1 TB alone do not define an HA analytics workload."},"iac":{"artifactRef":"repository default branch (moving; select matching application release)","artifactUrl":"https://github.com/matomo-org/docker","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://github.com/matomo-org/docker","status":"documented","summary":"The Matomo-maintained Docker repository supplies application/web-server and database examples. Persistent data, TLS, scheduled archiving and plugin/edition choices require deployment-specific configuration."},"licensePricing":{"reviewed":"2026-11-20","scope":"Core versus commercial plugin software terms; excludes Matomo Cloud and infrastructure","source":"https://matomo.org/faq/general/matomo-analytics-licences-for-core-tracker-and-plugins/","status":"documented","summary":"The On-Premise core is free to download under GPLv3; premium plugins and support have separate commercial terms. The paid LoginSAML feature is not implied by the free core. Select the plugin/site entitlements and current quote separately from server and operations costs.","supportingSources":[{"title":"On-Premise product and free core","url":"https://matomo.org/matomo-on-premise/"}]},"release":{"releasePublishedAt":"2026-10-22T02:49:53Z","releaseTag":"5.14.2","reviewed":"2026-11-14","scope":"Upstream matomo-org/matomo release record; commercial editions and deployment packages may differ","source":"https://github.com/matomo-org/matomo/releases/tag/5.14.2","status":"documented","summary":"The publisher-designated GitHub release checked was 5.14.2, published 2026-10-22. 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 Matomo with LoginSAML premium feature","source":"https://matomo.org/faq/general/set-up-login-with-saml-authentication/","status":"documented","summary":"On-premises SAML uses the paid LoginSAML premium feature from Matomo Marketplace. Provider setup and user provisioning options require configuration; this is separate from a Matomo Cloud subscription."}},"id":"matomo","infrastructure":["servers"],"infrastructureNotes":"Official installation runs on a web/shared/dedicated server with a database, or using the official Docker image. Higher-volume reporting uses a scheduled cron task rather than an event-driven application runtime.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://matomo.org/faq/on-premise/installing-matomo/"],"install":"PHP web-server installation or official Docker image","installMethods":["docker","package"],"kind":"product","license":"GPLv3-or-later core; premium plugins use separate commercial EULA and subscription terms","licenseModel":"open-source","licenseModelNotes":"Matomo On-Premise combines a GPLv3 core and open-source plugins with separately licensed commercial premium plugins. Premium plugin source and redistribution rights are governed by the InnoCraft EULA rather than the core GPL license.","licenseModelSources":["https://matomo.org/faq/general/matomo-analytics-licences-for-core-tracker-and-plugins/","https://matomo.org/faq/general/faq_22573/","https://raw.githubusercontent.com/matomo-org/matomo/5.x-dev/LEGALNOTICE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Matomo On-Premise","notes":"This entry covers Matomo On-Premise rather than Matomo Cloud. Core analytics can be self-hosted, while premium capabilities and support may require separate purchases. Configure collection, consent and retention deliberately rather than treating the deployment model as a privacy-compliance guarantee.","operations":"Customer manages hosting, upgrades, security, backups, tracking configuration and scheduled report processing.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"On-Premise product scope","url":"https://matomo.org/matomo-on-premise/"},{"title":"Official installation instructions","url":"https://matomo.org/faq/on-premise/installing-matomo/"},{"title":"Core and premium plugin licenses","url":"https://matomo.org/faq/general/matomo-analytics-licences-for-core-tracker-and-plugins/"},{"title":"Core legal notice","url":"https://raw.githubusercontent.com/matomo-org/matomo/5.x-dev/LEGALNOTICE"},{"title":"Licensing and edition terms","url":"https://matomo.org/faq/general/faq_22573/"}],"url":"https://launchinyourcloud.com/directory/matomo/","website":"https://matomo.org/"},{"advisories":[{"action":"Use the appropriate maintained-line patch. For v12, review plugin compatibility, glibc 2.34+, PostgreSQL 15+ and OpenSearch 2.x+ where used.","conditions":"Individual vulnerability details follow the vendor disclosure schedule; plugins, PostgreSQL and optional search integrations have separate compatibility requirements.","id":"mattermost-12-security-review","listingIds":["mattermost"],"reviewed":"2026-11-17","scope":"Mattermost 12.0.2 and the maintained 11.x patches identified in the November 5 security notice.","source":"https://docs.mattermost.com/product-overview/mattermost-v12-changelog","summary":"The v12 changelog records medium/high security fixes and important runtime and plugin compatibility changes.","title":"Mattermost maintained-line security review","type":"security-advisory"}],"architecture":"Customer-operated application with PostgreSQL and file/object storage","categories":["collaboration"],"category":"Collaboration","categoryFit":{"collaboration":"Team channels, messaging, file sharing and collaborative operational workflows; production scale, identity and governance capabilities depend on edition."},"cloudEvidence":[{"clouds":["azure"],"notes":"The vendor documents the full Mattermost application in the customer Azure subscription or OCI tenancy. The OKE Marketplace option uses Enterprise Edition; Kubernetes/Operator and enterprise features require their applicable plan, separate from Team Edition and the evaluation-only Compose example.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Mattermost customer cloud deployment on Azure","url":"https://docs.mattermost.com/deployment-guide/server/linux/deploy-azure-native-vm","vendorSupport":"not-assessed"},{"clouds":["oci"],"notes":"The vendor documents the full Mattermost application in the customer Azure subscription or OCI tenancy. The OKE Marketplace option uses Enterprise Edition; Kubernetes/Operator and enterprise features require their applicable plan, separate from Team Edition and the evaluation-only Compose example.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Mattermost customer cloud deployment on Oracle Cloud","url":"https://docs.mattermost.com/deployment-guide/server/kubernetes/deploy-k8s-oke","vendorSupport":"not-assessed"},{"clouds":["aws","gcp"],"notes":"The vendor architecture builder explicitly includes AWS and Google Cloud hosting for the self-hosted application, with separate VM and Kubernetes deployment options and linked installation instructions. These are application hosting architectures, not Mattermost Cloud residency or storage adapters. Provider SKU suggestions are illustrative; size and validate the selected deployment and edition.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Mattermost self-hosted provider architecture and sizing","url":"https://docs.mattermost.com/deployment-guide/deployment-architecture","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","cloudScope":"Official customer-subscription Azure VM and customer-tenancy Oracle OKE guides establish these paths; unreviewed provider badges are omitted.","clouds":["azure","oci","aws","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"oci","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[2],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Self-hosted team messaging and collaborative operational workflows on customer infrastructure.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Upstream small/medium single-server baseline; enterprise multi-server sizing is separate","source":"https://docs.mattermost.com/deployment-guide/software-hardware-requirements.html","status":"documented","summary":"The upstream traditional-deployment guide gives a small-team baseline of 1 vCPU and 2 GB RAM for 1–1,000 registered users. Activity, peak file sharing, database/storage and multi-server HA alter sizing; this is not a complete 1-TB HA design."},"iac":{"artifactRef":"Moving deployment repository; pin supported server and PostgreSQL versions","artifactUrl":"https://github.com/mattermost/docker","reviewed":"2026-11-20","scope":"Self-managed Docker deployment; HA architecture is a separate design","source":"https://docs.mattermost.com/deployment-guide/server/deploy-containers.html","status":"documented","summary":"The official container guide uses the mattermost/docker Compose repository with application and PostgreSQL containers and an optional NGINX proxy. Configure secrets, persistent paths, domain and TLS; the quick-start Compose stack is not automatically a clustered production deployment."},"licensePricing":{"reviewed":"2026-11-20","scope":"Current self-hosted Entry/Enterprise offerings; do not reuse historical Team Edition or SaaS pricing","source":"https://docs.mattermost.com/product-overview/editions-and-offerings.html","status":"documented","summary":"The current offerings guide distinguishes commercial self-hosted Enterprise Edition from its free Entry mode and paid subscriptions. Entry has server-wide feature/usage limits; advanced entitlements require a trial or subscription. Exact paid-plan pricing and infrastructure costs remain separate."},"scim":{"availability":"unavailable","reviewed":"2026-11-14","scope":"Current SAML user-lifecycle documentation; recheck for the selected release","source":"https://docs.mattermost.com/administration-guide/onboard/sso-saml-entraid","status":"documented","summary":"The SAML provisioning FAQ explicitly states SCIM is not supported and refers administrators to AD/LDAP for provisioning/deactivation. This is a documented limitation, rather than an unanswered field."},"sso":{"availability":"available","reviewed":"2026-11-14","scope":"Current Mattermost commercial distribution plan names; not a blanket Team Edition entitlement","source":"https://docs.mattermost.com/onboard/sso-saml","status":"documented","summary":"The current SAML documentation lists Entry, Professional, Enterprise and Enterprise Advanced. It distinguishes tested Okta, OneLogin and ADFS integrations from custom identity providers that require validation."}},"id":"mattermost","infrastructure":["servers"],"infrastructureNotes":"Production documentation uses persistent Linux application hosts or Kubernetes, PostgreSQL and file storage. Azure provisions a VM scale set; the OCI option provisions OKE and managed database/storage components. Mattermost 12 drops RHEL 7 and 8, requires glibc 2.34 or later, PostgreSQL 15 or later, and OpenSearch 2.x or later.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://docs.mattermost.com/deployment-guide/server/deploy-linux","https://docs.mattermost.com/deployment-guide/server/deploy-kubernetes","https://docs.mattermost.com/product-overview/mattermost-v12-changelog"],"install":"Linux binary/packages or Mattermost Kubernetes Operator; provider architectures and Azure/OCI Marketplace guides","installMethods":["helm","package"],"kind":"product","license":"MIT Team Edition; commercial Enterprise offerings and separately licensed components; inspect the selected edition","licenseModel":"open-source","licenseModelNotes":"The listed self-hosted family includes MIT Team Edition and commercial Enterprise offerings with proprietary capabilities and feature entitlements. The license of a public core, community build or plugin must not be applied to the complete Enterprise distribution.","licenseModelSources":["https://docs.mattermost.com/product-overview/editions-and-offerings","https://docs.mattermost.com/product-overview/faq-license","https://docs.mattermost.com/developers/integrate/plugins/source-available-license"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Mattermost Self-Hosted","notes":"Team Edition is intended for small teams and lacks the commercial governance and enterprise identity capabilities. Enterprise Entry has limits; paid features require the applicable subscription. The current Docker Compose guide is for evaluation/testing and is not recommended for production/HA. The vendor provides AWS and Google Cloud self-hosted architectures alongside Azure VM and OCI OKE deployment guides. Mattermost 12.0.2 and the November 5 patches for maintained 11.x branches contain medium-to-high severity security fixes. For v12 upgrades, verify community and custom plugin compatibility.","operations":"Customer maintains the deployment, database, storage, upgrades and availability; subscriptions govern supported enterprise capabilities.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Editions and feature restrictions","url":"https://docs.mattermost.com/product-overview/editions-and-offerings"},{"title":"Business and licensing","url":"https://docs.mattermost.com/product-overview/faq-license"},{"title":"Linux deployment","url":"https://docs.mattermost.com/deployment-guide/server/deploy-linux"},{"title":"Kubernetes deployment","url":"https://docs.mattermost.com/deployment-guide/server/deploy-kubernetes"},{"title":"Container deployment caveats","url":"https://docs.mattermost.com/deployment-guide/server/deploy-containers"},{"title":"Azure Native VM deployment","url":"https://docs.mattermost.com/deployment-guide/server/linux/deploy-azure-native-vm"},{"title":"Oracle OKE deployment","url":"https://docs.mattermost.com/deployment-guide/server/kubernetes/deploy-k8s-oke"},{"title":"Licensing and edition terms","url":"https://docs.mattermost.com/developers/integrate/plugins/source-available-license"},{"title":"Mattermost self-hosted provider architecture and sizing","url":"https://docs.mattermost.com/deployment-guide/deployment-architecture"},{"title":"Mattermost v12 security and upgrade changelog","url":"https://docs.mattermost.com/product-overview/mattermost-v12-changelog"}],"url":"https://launchinyourcloud.com/directory/mattermost/","website":"https://mattermost.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/"},{"advisories":[{"action":"Upgrade to 1.57.0 or a later supported release, or the applicable fixed patch for a maintained branch.","conditions":"Applicability depends on the installed branch and the fixes listed in its release notes.","id":"meilisearch-november-2026-security-maintenance","listingIds":["meilisearch-community"],"reviewed":"2026-11-18","scope":"Upstream 1.55 and 1.56 maintenance lines; the release notes do not provide one consolidated affected-version range.","source":"https://github.com/meilisearch/meilisearch/releases/tag/v1.56.1","summary":"Meilisearch 1.56.1 and 1.55.1 identify important security fixes and urge affected users to upgrade; 1.57.0 includes those fixes.","supportingSources":[{"title":"v1.55.1 security release","url":"https://github.com/meilisearch/meilisearch/releases/tag/v1.55.1"},{"title":"v1.57.0","url":"https://github.com/meilisearch/meilisearch/releases/tag/v1.57.0"}],"title":"Meilisearch November 2026 security maintenance","type":"security-advisory"}],"architecture":"Customer-operated search server with persistent index storage and optional external embedding or language-model integrations","categories":["databases-vector"],"category":"Databases \u0026 vector","categoryFit":{"databases-vector":"Application search engine with typo-tolerant full-text search and semantic or hybrid retrieval over vector embeddings."},"cloudEvidence":[{"clouds":["aws"],"notes":"The vendor documents a production-oriented installation on a customer AWS EC2 instance, including the official binary installer, dedicated service account, persistent data directory, systemd service and network security. The customer operates the VM and search service; this is separate from Meilisearch Cloud.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Meilisearch Community Edition on Amazon EC2","url":"https://www.meilisearch.com/docs/resources/self_hosting/deployment/aws","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The vendor documents a production-oriented installation on a customer Google Compute Engine VM with billing enabled, including the official binary installer, dedicated service account, persistent data directory, systemd service and firewall configuration. The customer operates the VM and search service.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Meilisearch Community Edition on Google Compute Engine","url":"https://www.meilisearch.com/docs/resources/self_hosting/deployment/gcp","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"The vendor documents installation on a customer DigitalOcean Droplet using its official binary installer, persistent service configuration and production security steps. This is a customer-operated Droplet, not a managed Meilisearch Cloud deployment.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Meilisearch Community Edition on a DigitalOcean Droplet","url":"https://www.meilisearch.com/docs/resources/self_hosting/deployment/digitalocean","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-16","clouds":["aws","gcp","digitalocean"],"communityAcceptance":{"reviewed":"2026-11-16","sources":[{"title":"Upstream project and contribution workflow","url":"https://github.com/meilisearch/meilisearch"},{"title":"Current upstream releases","url":"https://github.com/meilisearch/meilisearch/releases"},{"title":"Official open-source project catalog","url":"https://www.meilisearch.com/open-source"}],"summary":"The official repository publishes continuing versioned releases and public contribution workflows, while the vendor maintains a broader catalog of open-source integrations and deployment components."},"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":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Self-hosted search engine for typo-tolerant full-text, semantic and hybrid retrieval.","diligence":{"compliance":{"reviewed":"2026-11-16","scope":"Vendor SOC 2 offering versus customer-operated Community engine; not a claim that an operator cannot obtain its own attestation","source":"https://www.meilisearch.com/oss-to-cloud","status":"documented","summary":"The vendor comparison explicitly excludes the vendor’s SOC 2 Type II offering from self-hosted open source. Hosted-service assurance does not transfer to a customer-operated Community installation; assess the operator’s environment separately."},"footprint":{"reviewed":"2026-11-16","scope":"Self-hosted indexing workload guidance; capacity requires representative data and benchmarks","source":"https://www.meilisearch.com/blog/indexing-optimization-guide","status":"inconclusive","summary":"The indexing guide ties memory and disk use to document fields, payload sizes and batch size. It warns that large payloads can exhaust RAM. The reviewed guide provides tuning guidance, not a universal production CPU/RAM minimum."},"iac":{"reviewed":"2026-11-16","scope":"Community Edition VM installation; not Meilisearch Cloud or Enterprise","source":"https://www.meilisearch.com/docs/resources/self_hosting/deployment/aws","status":"documented","summary":"The VM guides install an upstream binary, dedicated system user and systemd service, with persistent data and HTTPS/reverse-proxy configuration. Release assets are versioned separately from any cloud image; choose a platform-compatible Community Edition asset.","supportingSources":[{"title":"Versioned upstream release assets","url":"https://github.com/meilisearch/meilisearch/releases/tag/v1.57.0"}]},"licensePricing":{"reviewed":"2026-11-16","scope":"Meilisearch Community Edition: software license terms; infrastructure and operating costs are separate","source":"https://github.com/meilisearch/meilisearch/blob/main/LICENSE","status":"documented","summary":"This listing is scoped specifically to the MIT-licensed Community Edition. The separately available Enterprise Edition uses a BUSL license, cannot be used freely in production and reserves sharding as its exclusive feature.","supportingSources":[{"title":"Edition and license conditions","url":"https://www.meilisearch.com/docs/resources/self_hosting/enterprise_edition"}]},"release":{"releasePublishedOn":"2026-11-16","releaseTag":"v1.57.0","reviewed":"2026-11-18","scope":"Upstream Meilisearch Community release","source":"https://github.com/meilisearch/meilisearch/releases/tag/v1.57.0","status":"documented","summary":"Meilisearch v1.57.0 was published November 16, 2026, and includes the fixes from the 1.56.1 and 1.55.1 security maintenance releases.","supportingSources":[{"title":"v1.56.1 security release","url":"https://github.com/meilisearch/meilisearch/releases/tag/v1.56.1"},{"title":"v1.55.1 security release","url":"https://github.com/meilisearch/meilisearch/releases/tag/v1.55.1"}]},"securityControls":{"reviewed":"2026-11-18","scope":"Self-hosted search engine API authorization; not Meilisearch Cloud account SSO Upstream 1.55 and 1.56 maintenance lines; the release notes do not provide one consolidated affected-version range.","source":"https://github.com/meilisearch/meilisearch/releases/tag/v1.56.1","status":"documented","summary":"Self-hosted Meilisearch uses a master key of at least 16 bytes and scoped API keys for requests. Keep master/admin keys off public frontends and use a search-scoped key where appropriate. This API authorization does not establish SSO or SCIM. Current advisory review: Meilisearch 1.56.1 and 1.55.1 identify important security fixes and urge affected users to upgrade; 1.57.0 includes those fixes. Upgrade to 1.57.0 or a later supported release, or the applicable fixed patch for a maintained branch.","supportingSources":[{"title":"Prior security-controls source","url":"https://www.meilisearch.com/docs/resources/self_hosting/security/basic_security"},{"title":"v1.55.1 security release","url":"https://github.com/meilisearch/meilisearch/releases/tag/v1.55.1"},{"title":"v1.57.0","url":"https://github.com/meilisearch/meilisearch/releases/tag/v1.57.0"}]},"sso":{"availability":"unavailable","reviewed":"2026-11-16","scope":"Self-hosted open-source/Community tier in the vendor comparison","source":"https://www.meilisearch.com/oss-to-cloud","status":"documented","summary":"The vendor comparison explicitly excludes SAML/OIDC SSO from self-hosted open source and places it in Enterprise. The Community engine’s API keys and tenant tokens are not an organization SSO integration."}},"id":"meilisearch-community","infrastructure":["servers"],"infrastructureNotes":"Each reviewed cloud guide runs Meilisearch as a persistent Linux service on a customer-owned VM. The customer provisions and sizes the server and storage; these paths are neither serverless nor vendor-managed.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://www.meilisearch.com/docs/resources/self_hosting/deployment/aws","https://www.meilisearch.com/docs/resources/self_hosting/deployment/gcp","https://www.meilisearch.com/docs/resources/self_hosting/deployment/digitalocean"],"install":"Install the official binary on an AWS EC2 instance, Google Compute Engine VM or DigitalOcean Droplet, then configure a dedicated system user, systemd service, persistent data directory, reverse proxy and HTTPS.","installMethods":["package"],"kind":"product","license":"MIT License for Community Edition. Enterprise Edition uses a BUSL license, cannot be freely used in production and requires a commercial agreement for production self-hosting.","licenseModel":"open-source","licenseModelNotes":"This listing is scoped specifically to the MIT-licensed Community Edition. The separately available Enterprise Edition uses a BUSL license, cannot be used freely in production and reserves sharding as its exclusive feature.","licenseModelSources":["https://github.com/meilisearch/meilisearch/blob/main/LICENSE","https://www.meilisearch.com/docs/resources/self_hosting/enterprise_edition"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"Meilisearch Community Edition","notes":"The reviewed provider guides deploy a customer-operated server rather than a managed Meilisearch service. Meilisearch Cloud is the vendor-recommended production option, but the Community Edition is explicitly available for independent hosting. Community Edition does not include Enterprise-only sharding, so the documented VM paths do not establish a highly available or horizontally sharded topology. Configured remote embedders or LLM providers can receive indexed or query content; user-provided vectors and customer-selected local endpoints can produce a different data boundary. Meilisearch 1.56.1 and 1.55.1 were security maintenance releases; current 1.57.0 includes those fixes. Affected deployments should move to 1.57.0 or an appropriate later supported patch and review the vendor's branch guidance.","operations":"Customer manages the VM, operating system, network rules, master key, TLS, persistent indexes, backups, monitoring, capacity and version upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"AWS EC2 deployment","url":"https://www.meilisearch.com/docs/resources/self_hosting/deployment/aws"},{"title":"Google Compute Engine deployment","url":"https://www.meilisearch.com/docs/resources/self_hosting/deployment/gcp"},{"title":"DigitalOcean Droplet deployment","url":"https://www.meilisearch.com/docs/resources/self_hosting/deployment/digitalocean"},{"title":"Production self-hosting guidance","url":"https://www.meilisearch.com/docs/resources/self_hosting/deployment/running_production"},{"title":"Full-text, semantic, hybrid and vector-search capabilities","url":"https://www.meilisearch.com/docs/getting_started/features"},{"title":"Community and Enterprise edition boundaries","url":"https://www.meilisearch.com/docs/resources/self_hosting/enterprise_edition"},{"title":"Community Edition MIT license","url":"https://github.com/meilisearch/meilisearch/blob/main/LICENSE"},{"title":"Meilisearch v1.57.0 release","url":"https://github.com/meilisearch/meilisearch/releases/tag/v1.57.0"},{"title":"Meilisearch v1.56.1 security release","url":"https://github.com/meilisearch/meilisearch/releases/tag/v1.56.1"},{"title":"Meilisearch v1.55.1 security release","url":"https://github.com/meilisearch/meilisearch/releases/tag/v1.55.1"}],"url":"https://launchinyourcloud.com/directory/meilisearch-community/","website":"https://www.meilisearch.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/"},{"advisories":[{"action":"Upgrade Open Source to at least 0.64.3.4 or Pro/Enterprise to at least 1.64.3.4 and follow the vendor security checklist.","conditions":"Self-hosted edition, configured integrations and exposed endpoints determine which fixes apply; optional key settings need explicit configuration.","id":"metabase-64-security-update","listingIds":["metabase"],"reviewed":"2026-11-17","scope":"Open Source 0.64.0 to before 0.64.3.4 and corresponding Pro/Enterprise 1.64 versions.","source":"https://github.com/metabase/metabase/security/advisories/GHSA-v44v-x8x4-mvcw","summary":"The advisory records API, permission, metadata, session and serialization hardening in the 64 release line.","title":"Metabase 64 critical security update","type":"security-advisory"}],"architecture":"Customer-operated application and database","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Business intelligence and dashboards on your infrastructure."},"cloudEvidence":[{"clouds":["aws","azure","gcp","digitalocean"],"deploymentBoundaries":{"digitalocean":"not-assessed"},"notes":"The vendor names AWS Elastic Beanstalk and Docker, and explicitly identifies Google Cloud, Azure and DigitalOcean as alternative hosts for the Metabase application. Pair this compatibility statement with the current installation guide and a production application database; this is self-hosting, separate from Metabase Cloud.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Metabase production hosting compatibility","url":"https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp","digitalocean"],"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"}],"description":"Business intelligence and dashboards on your infrastructure.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Post-v52 production sizing guidance by concurrent users, not registered accounts","source":"https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-in-production","status":"documented","summary":"The vendor gives an application baseline of 1 core/1 GB, plus 1 core/2 GB per 20 concurrent users. The application database starts at 1 core/2 GB and needs additional capacity. Query databases, HA replicas, storage and background jobs are extra; total registered users alone is insufficient for sizing."},"iac":{"artifactRef":"v65 documentation; select a compatible image tag","artifactUrl":"https://www.metabase.com/docs/latest/installation-and-operation/running-metabase-on-docker#example-docker-compose-yaml-file","reviewed":"2026-11-20","scope":"Official self-hosted Docker/Compose distributions","source":"https://www.metabase.com/docs/latest/installation-and-operation/running-metabase-on-docker","status":"documented","summary":"The vendor supplies separate Open Source and Enterprise images and publishes Compose examples. Production needs an external supported application database; embedded H2 is evaluation-only. Pin the selected image, configure persistence, TLS and backup, and do not assume an officially supported Helm chart."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/metabase/metabase/master/LICENSE.txt","status":"documented","summary":"The repository separates AGPL core code from the commercial enterprise directory and enterprise binaries. Self-hosted Pro/Enterprise features require commercial terms; the core licence does not establish paid-edition prices, support or hosting cost."},"scim":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Self-hosted Pro and Enterprise; identity-provider behavior differs","source":"https://www.metabase.com/docs/latest/people-and-groups/user-provisioning","status":"documented","summary":"Pro and Enterprise support SCIM. The documentation names Okta and Microsoft Entra ID; Okta supports user/group provisioning while Entra supports user provisioning only."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Self-hosted Pro and Enterprise","source":"https://www.metabase.com/docs/latest/people-and-groups/authenticating-with-saml","status":"documented","summary":"SAML authentication is available on Pro and Enterprise for self-hosted deployments. This does not establish SAML for the free/open-source edition."}},"id":"metabase","infrastructure":["servers"],"infrastructureNotes":"The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://www.metabase.com/docs/latest/installation-and-operation/installing-metabase","https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale"],"install":"Docker image or Java JAR","installMethods":["docker","package"],"kind":"platform","license":"Open-source and commercial options","licenseModel":"open-source","licenseModelNotes":"The self-hosted platform offers an AGPL Open Source Edition alongside commercial capabilities and licensing. The classification covers the platform family described in this entry.","licenseModelSources":["https://www.metabase.com/license"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Metabase Self-Hosted","notes":"Metabase documents self-hosting on AWS, Google Cloud, Azure and DigitalOcean. This entry covers self-hosting rather than Metabase Cloud. Infrastructure sizing, the application database and feature entitlements depend on the selected edition. Metabase's critical security advisory affects 0.64.0 through 0.64.3.3 and corresponding Enterprise versions. Self-hosted operators should use Open Source 0.64.3.4 or later, or Enterprise 1.64.3.4 or later. The hardening release strengthens API validation and permission checks, limits metadata exposure, improves deactivated-user session handling, removes database secrets from serialization exports, and adds optional session-signing and encryption keys.","operations":"Your team manages hosting, upgrades and the application database.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Installing Metabase","url":"https://www.metabase.com/docs/latest/installation-and-operation/installing-metabase"},{"title":"Production hosting options","url":"https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-at-scale"},{"title":"Licensing and edition terms","url":"https://www.metabase.com/license"},{"title":"Metabase 64 critical security update","url":"https://github.com/metabase/metabase/security/advisories/GHSA-v44v-x8x4-mvcw"}],"url":"https://launchinyourcloud.com/directory/metabase/","website":"https://www.metabase.com/"},{"architecture":"Customer-operated vector database and persistent storage, with deployment-specific metadata and write-ahead-log services","categories":["databases-vector","ai-tools"],"category":"Databases \u0026 vector","categoryFit":{"ai-tools":"Embedding storage and vector retrieval infrastructure for AI search and RAG applications.","databases-vector":"Vector database for approximate nearest-neighbor retrieval over embeddings and associated metadata."},"cloudEvidence":[{"clouds":["aws"],"notes":"Official instructions provision Amazon EKS and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Milvus deployment on Amazon EKS","url":"https://milvus.io/docs/eks.md","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Official instructions provision Azure Kubernetes Service and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Milvus deployment on Azure Kubernetes Service","url":"https://milvus.io/docs/azure.md","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Official instructions provision Google Kubernetes Engine and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Milvus deployment on Google Kubernetes Engine","url":"https://milvus.io/docs/gcp.md","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Foundation and contributing community","url":"https://github.com/milvus-io/milvus"},{"title":"Current release maintenance","url":"https://github.com/milvus-io/milvus/releases"}],"summary":"Milvus documents governance under the LF AI \u0026 Data Foundation with Zilliz as a major contributor. Its public release stream records continuing October 2026 maintenance."},"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":"Vector database for similarity search and retrieval over embedding collections.","diligence":{"footprint":{"reviewed":"2026-11-14","scope":"Milvus 3.0.x standalone requirements as reviewed","source":"https://milvus.io/docs/prerequisite-docker.md","status":"documented","summary":"The standalone requirements specify 8 GB RAM, recommend 16 GB and recommend at least 4 CPU cores with a supported SIMD instruction set. Dataset/index size and storage performance govern actual resources; distributed requirements differ."},"iac":{"artifactRef":"master script (moving; inspect its selected image)","artifactUrl":"https://raw.githubusercontent.com/milvus-io/milvus/master/scripts/standalone_embed.sh","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://milvus.io/docs/install_standalone-docker.md","status":"documented","summary":"The official standalone Docker guide links a script fetched from master. Its image selection moves and its upgrade command does not validate arbitrary version transitions; inspect the script and use matching versioned Compose when required."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/milvus-io/milvus/master/LICENSE","status":"documented","summary":"The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate."},"release":{"releasePublishedAt":"2026-11-11T08:06:25Z","releaseTag":"v3.0.6","reviewed":"2026-11-14","scope":"Upstream milvus-io/milvus release record; commercial editions and deployment packages may differ","source":"https://github.com/milvus-io/milvus/releases/tag/v3.0.6","status":"documented","summary":"The publisher-designated GitHub release checked was v3.0.6, published 2026-11-11. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package."},"sso":{"reviewed":"2026-11-20","scope":"Self-hosted Milvus core user authentication; federation unresolved","source":"https://milvus.io/docs/authenticate.md","status":"inconclusive","summary":"The current core authentication guide uses username/password credentials and SDK token fields with explicitly enabled authorization. It does not establish native SAML/OIDC federation or automatic IdP/group mapping. Hosted Zilliz console SSO is a different deployment; confirm an upstream integration before relying on it."}},"id":"milvus","infrastructure":["servers"],"infrastructureNotes":"Customer-operated vector database and persistent storage, with deployment-specific metadata and write-ahead-log services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://milvus.io/docs/install_standalone-docker.md"],"install":"Run the official standalone Docker or versioned Docker Compose deployment; distributed deployments have separate operational requirements.","installMethods":["docker"],"kind":"product","license":"Apache License 2.0 for upstream Milvus.","licenseModel":"open-source","licenseModelNotes":"Apache License 2.0 for upstream Milvus. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.","licenseModelSources":["https://github.com/milvus-io/milvus/blob/master/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Milvus","notes":"Current installation scripts can track a different image than a selected stable release; use versioned configurations for reproducibility. Model inference and embedding generation are separate workloads. Managed Zilliz offerings are outside this listing.","operations":"Customer manages persistent volumes, collections, indexes, access controls, capacity, backups and upgrades.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Official installation and runtime","url":"https://milvus.io/docs/install_standalone-docker.md"},{"title":"Upstream project and capabilities","url":"https://github.com/milvus-io/milvus"},{"title":"Current upstream license","url":"https://github.com/milvus-io/milvus/blob/master/LICENSE"}],"url":"https://launchinyourcloud.com/directory/milvus/","website":"https://milvus.io/"},{"architecture":"Customer-operated tracking/API server with configurable metadata database and artifact storage","categories":["ai-observability","ai-tools","observability"],"category":"AI observability \u0026 LLMOps","categoryFit":{"ai-observability":"Experiment tracking and LLM/agent tracing server. This entry describes customer-hosted tracking/observability services, not every model runtime, managed MLflow product or inference backend.","ai-tools":"Self-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.","observability":"Application/model traces and experiment visibility for AI workloads. Infrastructure metrics and broader application monitoring require separately selected tooling."},"cloudEvidence":[{"clouds":["aws"],"notes":"The project documents deployment of the MLflow server, metadata database and artifact storage on AWS. This does not refer to a managed MLflow edition or to model serving alone.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Self-hosted MLflow deployment on AWS","url":"https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/aws/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The project documents deployment of the MLflow server, metadata database and artifact storage on Azure. This does not refer to a managed MLflow edition or to model serving alone.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Self-hosted MLflow deployment on Azure","url":"https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/azure/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The project documents deployment of the MLflow server, metadata database and artifact storage on Google Cloud. This does not refer to a managed MLflow edition or to model serving alone.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Self-hosted MLflow deployment on Google Cloud","url":"https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/gcp/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","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":"Self-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Self-hosted tracking-server topology; numeric production sizing unresolved","source":"https://mlflow.org/docs/latest/self-hosting/architecture/tracking-server/","status":"inconclusive","summary":"The self-hosted guide documents the UI/API tracking server, metadata backend and artifact-store configuration, but not a universal production CPU/RAM minimum. Size runs/traces, request concurrency, database, artifact storage and redundancy; starting the default local SQLite server does not establish production or HA capacity."},"iac":{"artifactRef":"master Compose bundle (moving)","artifactUrl":"https://github.com/mlflow/mlflow/tree/master/docker-compose","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://mlflow.org/docs/latest/self-hosting/","status":"documented","summary":"The self-hosting guide links an upstream Compose bundle with MLflow, PostgreSQL and object storage, plus an official Helm option. Configure production credentials and persistence rather than retaining development defaults."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/mlflow/mlflow/master/LICENSE.txt","status":"documented","summary":"The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate."},"release":{"releasePublishedAt":"2026-11-04T06:51:02Z","releaseTag":"v3.18.0","reviewed":"2026-11-14","scope":"Upstream mlflow/mlflow release record; commercial editions and deployment packages may differ","source":"https://github.com/mlflow/mlflow/releases/tag/v3.18.0","status":"documented","summary":"The publisher-designated GitHub release checked was v3.18.0, published 2026-11-04. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Officially documented community-plugin/proxy integration","source":"https://mlflow.org/docs/latest/self-hosting/security/sso/","status":"documented","summary":"The official guide documents the community-maintained mlflow-oidc-auth plugin and an SSO reverse-proxy pattern. This provides UI/API OIDC integration, but plugin maintenance, MLflow-version compatibility and client token behavior require separate review; it is not a claim of vendor-operated identity support."}},"id":"mlflow","infrastructure":["servers"],"infrastructureNotes":"The tracking server runs as a Python service or container with metadata/artifact stores. A local SQLite example is not a production architecture; separately plan persistent database, storage and application-runtime infrastructure.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://mlflow.org/docs/latest/self-hosting/"],"install":"Python MLflow server command, official Docker Compose bundle or Kubernetes Helm deployment.","installMethods":["helm","docker","source"],"kind":"product","license":"Apache 2.0 for upstream MLflow; connected model providers and managed distributions have separate terms.","licenseModel":"open-source","licenseModelNotes":"The upstream self-hosted tracking server is Apache-2.0 licensed. This classification does not extend to separate managed MLflow distributions, connected model providers or their commercial services.","licenseModelSources":["https://github.com/mlflow/mlflow/blob/master/LICENSE.txt"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"MLflow Tracking Server Self-Hosted","notes":"Traces can capture model inputs, outputs and intermediate metadata. Point clients at the customer-hosted server and review recording/redaction settings. Applications, evaluators and optional model integrations may still call external providers; hosting the tracking server does not host all training or inference runtimes. Production database, storage and security configuration differ from a local quickstart.","operations":"Customer operates server access, metadata and artifact stores, retention, backups, scaling and version upgrades.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Self-hosting server and deployment methods","url":"https://mlflow.org/docs/latest/self-hosting/"},{"title":"LLM/agent tracing and captured data","url":"https://mlflow.org/docs/latest/genai/tracing/"},{"title":"Apache 2.0 license","url":"https://github.com/mlflow/mlflow/blob/master/LICENSE.txt"}],"url":"https://launchinyourcloud.com/directory/mlflow/","website":"https://mlflow.org/"},{"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/"},{"advisories":[{"action":"Use GDS 2026.10.2 or later and assess whether any Java-deserialization path is exposed.","conditions":"Requires the optional GDS component and a reachable attacker-controlled Java-deserialization path.","id":"neo4j-gds-cve-2026-102554","listingIds":["neo4j-self-managed"],"reviewed":"2026-11-18","scope":"Guava 4.0 through 33.7.1 is affected and 33.7.2 is fixed. Neo4j does not identify which earlier GDS releases expose the path or claim that core Neo4j is affected.","source":"https://github.com/advisories/GHSA-xxph-c9ww-hj94","summary":"Graph Data Science 2026.10.2 upgrades Guava to 33.7.2 to fix CVE-2026-102554, an uncontrolled-memory-allocation issue during attacker-controlled Java deserialization.","supportingSources":[{"title":"GDS 2026.10.2 notes","url":"https://neo4j.com/release-notes/gds/graph-data-science-2026-10-2/"}],"title":"Neo4j Graph Data Science Guava denial-of-service dependency","type":"security-advisory"}],"architecture":"Customer-operated standalone or clustered graph database servers with persistent volumes","categories":["databases-vector"],"category":"Databases \u0026 vector","categoryFit":{"databases-vector":"Provides a graph database with Cypher queries, graph traversal and vector-index capabilities in customer-operated deployments."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Neo4j's Operations Manual documents standalone and clustered Helm deployments on Amazon EKS, Microsoft AKS and Google GKE. Edition and license requirements differ between standalone Community and clustered Enterprise deployments.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"Neo4j Helm deployments on EKS, AKS and GKE","url":"https://neo4j.com/docs/operations-manual/current/kubernetes/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-14","clouds":["aws","azure","gcp"],"communityAcceptance":{"reviewed":"2026-11-14","sources":[{"title":"Reviewed maintenance release 2026.10.2","url":"https://neo4j.com/release-notes/database/neo4j-2026102/"},{"title":"Upstream contributor history","url":"https://github.com/neo4j/neo4j/graphs/contributors"},{"title":"Open-source project and contributor participation","url":"https://neo4j.com/open-source-project/"}],"summary":"The upstream open-source project documents its public contribution process and sustained participation from multiple contributors. Vendor release notes record database 2026.10.2 on November 6, 2026, establishing current maintenance. This evidence concerns the project and database release history; it does not make Enterprise-only clustering, backup or bundled tools part of the Community license."},"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":"Self-managed graph database available in open-source Community and commercial Enterprise editions.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Helm per-instance floor; cluster and workload capacity not validated","source":"https://neo4j.com/docs/operations-manual/current/kubernetes/quickstart-cluster/create-value-file/","status":"documented","summary":"The current Helm guide enforces at least 0.5 CPU and 2 GB memory per Neo4j instance and shows a three-member Enterprise cluster. These are deployment floors, not production sizing for a dataset. Graph/index size, page cache, query memory, storage and failure headroom require separate sizing."},"iac":{"artifactRef":"Choose compatible chart and Neo4j versions","artifactUrl":"https://github.com/neo4j/helm-charts","reviewed":"2026-11-20","scope":"Official Enterprise cluster Helm deployment","source":"https://neo4j.com/docs/operations-manual/current/kubernetes/quickstart-cluster/create-value-file/","status":"documented","summary":"The vendor publishes Helm charts and values for a Kubernetes cluster, including an Enterprise three-member example and cloud storage classes. Enterprise requires licence acceptance; select compatible chart/database versions and configure secrets, volumes and backups."},"licensePricing":{"reviewed":"2026-11-20","scope":"Self-managed Community versus commercial Enterprise licensing","source":"https://neo4j.com/licensing/","status":"documented","summary":"The vendor separates Community GPLv3 terms from the self-managed Enterprise Software Agreement and commercial support terms. Enterprise clustering/features require the corresponding entitlement; do not apply Aura hosted per-GB rates or the Community licence to an Enterprise deployment. Obtain a self-managed quote."},"release":{"releasePublishedOn":"2026-11-06","releaseTag":"2026.10.2","reviewed":"2026-11-18","scope":"Neo4j Database and optional Graph Data Science 2026.10.2","source":"https://neo4j.com/release-notes/database/neo4j-2026102/","status":"documented","summary":"Neo4j 2026.10.2 was released November 6, 2026. Its compatible Graph Data Science 2026.10.2 component upgrades Guava to 33.7.2 for CVE-2026-102554; that conditional component finding is not a core DBMS claim.","supportingSources":[{"title":"GDS 2026.10.2","url":"https://neo4j.com/release-notes/gds/graph-data-science-2026-10-2/"}]},"securityControls":{"reviewed":"2026-11-18","scope":"Guava 4.0 through 33.7.1 is affected and 33.7.2 is fixed. Neo4j does not identify which earlier GDS releases expose the path or claim that core Neo4j is affected.","source":"https://github.com/advisories/GHSA-xxph-c9ww-hj94","status":"documented","summary":"Current advisory review: Graph Data Science 2026.10.2 upgrades Guava to 33.7.2 to fix CVE-2026-102554, an uncontrolled-memory-allocation issue during attacker-controlled Java deserialization. Use GDS 2026.10.2 or later and assess whether any Java-deserialization path is exposed.","supportingSources":[{"title":"GDS 2026.10.2 notes","url":"https://neo4j.com/release-notes/gds/graph-data-science-2026-10-2/"}]},"sso":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Self-managed Neo4j Enterprise Edition","source":"https://neo4j.com/docs/operations-manual/current/authentication-authorization/sso-integration/","status":"documented","summary":"Neo4j documents OIDC single sign-on for Enterprise Edition, including role mapping and multiple providers. The server must be able to reach its identity provider; this is not a Community Edition entitlement."}},"id":"neo4j-self-managed","infrastructure":["servers"],"infrastructureNotes":"Neo4j runs persistent standalone or clustered database servers with attached storage. Kubernetes and cloud placement do not remove state, backup or upgrade responsibilities.","infrastructureReviewed":"2026-11-14","infrastructureSources":["https://neo4j.com/docs/operations-manual/current/kubernetes/","https://neo4j.com/docs/operations-manual/current/introduction/"],"install":"Official Helm charts on EKS, AKS or GKE; cloud marketplace and VM options also exist","installMethods":["helm"],"kind":"product","license":"GPLv3 Community Edition; Enterprise Edition uses a commercial Neo4j license.","licenseModel":"open-source","licenseModelNotes":"Neo4j Community Edition is GPLv3. Enterprise Edition is commercially licensed and adds clustering, advanced security and operational capabilities.","licenseModelSources":["https://neo4j.com/open-source-project/","https://neo4j.com/docs/operations-manual/current/introduction/"],"licenseReviewed":"2026-11-14","model":"Fully in your account","modelLabel":"Customer-operated","name":"Neo4j Self-Managed","notes":"Community Edition is designed for standalone deployments. Clustering, advanced security and online backup features require Enterprise Edition. This entry does not cover the managed Neo4j Aura service. Deployments that install Graph Data Science should use GDS 2026.10.2 or later, which moves Guava to 33.7.2 for CVE-2026-102554. The advisory concerns attacker-controlled Java deserialization in GDS's dependency; it does not establish that core Neo4j or a default deployment exposes the vulnerable path.","operations":"Customer manages compute, storage, networking, security, backups, monitoring, capacity and upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Self-managed editions","url":"https://neo4j.com/docs/operations-manual/current/introduction/"},{"title":"Kubernetes deployments","url":"https://neo4j.com/docs/operations-manual/current/kubernetes/"},{"title":"Cloud deployment options","url":"https://neo4j.com/docs/operations-manual/current/cloud-deployments/"},{"title":"Open-source project and contributor participation","url":"https://neo4j.com/open-source-project/"},{"title":"Neo4j 2026.10.2 release notes","url":"https://neo4j.com/release-notes/database/neo4j-2026102/"},{"title":"Upstream contributor history","url":"https://github.com/neo4j/neo4j/graphs/contributors"},{"title":"Graph Data Science 2026.10.2 release notes","url":"https://neo4j.com/release-notes/gds/graph-data-science-2026-10-2/"},{"title":"Guava CVE-2026-102554 advisory","url":"https://github.com/advisories/GHSA-xxph-c9ww-hj94"}],"url":"https://launchinyourcloud.com/directory/neo4j-self-managed/","website":"https://neo4j.com/"},{"architecture":"Customer-operated management, signal, relay or STUN, dashboard, identity and state services; peers form direct WireGuard tunnels where possible","categories":["identity-access-management"],"category":"Identity \u0026 access management","categoryFit":{"identity-access-management":"Provides self-hosted identity-aware zero-trust network access with users, policies, device peers, routes and private-resource controls."},"cloudEvidence":[{"applicableEdition":"Community Edition","clouds":["aws","azure","gcp","digitalocean","hetzner","oci"],"notes":"The advanced self-hosting guide explicitly names AWS, DigitalOcean, Hetzner, Google Cloud and Azure VMs, uses Hetzner for its worked installation and documents OCI guest-firewall requirements for UDP 3478. It describes the older multi-container layout; the current quickstart uses the combined netbird-server layout. Select compatible files and configure provider and guest firewalls for the chosen architecture.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"NetBird self-hosted control plane on a cloud VM","url":"https://docs.netbird.io/selfhosted/selfhosted-guide","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","azure","gcp","digitalocean","hetzner","oci"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Upstream contributor history","url":"https://github.com/netbirdio/netbird/graphs/contributors"},{"title":"Reviewed upstream application release","url":"https://github.com/netbirdio/netbird/releases/tag/v0.83.1"}],"summary":"The reviewed upstream contributor history includes mlsmaycon, pascal-fischer, lixmal, with sustained contributions alongside the dated application release and public installation history. This establishes maintained community participation, not a commercial support, compliance or capacity guarantee."},"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":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"hetzner","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"oci","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Open-source zero-trust networking control plane self-hosted on a customer cloud VM.","diligence":{"airGap":{"reviewed":"2026-11-19","scope":"NetBird Self-Hosted Community Edition: selected customer-operated edition","source":"https://docs.netbird.io/selfhosted/selfhosted-guide","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":"NetBird Self-Hosted Community Edition: selected customer-operated edition","source":"https://docs.netbird.io/selfhosted/selfhosted-guide","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":"NetBird Self-Hosted Community Edition: selected customer-operated edition","source":"https://docs.netbird.io/selfhosted/selfhosted-quickstart","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":"NetBird Self-Hosted Community Edition: selected customer-operated edition","source":"https://docs.netbird.io/selfhosted/selfhosted-guide","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":{"availability":"available","reviewed":"2026-11-19","scope":"NetBird Self-Hosted Community Edition: selected customer-operated edition","source":"https://docs.netbird.io/selfhosted/selfhosted-quickstart","status":"documented","summary":"The quickstart specifies one publicly reachable Linux VM with at least 1 CPU and 2 GB RAM plus Docker Compose, a domain and required TCP/UDP ports. This is a small single-node baseline, not an HA or large-fleet sizing recommendation."},"iac":{"artifactRef":"v0.83.1/getting-started.sh; sha256:25ee5000a7421cb51a7c4c0f9090788951f531aba171d1fbff676f66d3265bfe","artifactUrl":"https://github.com/netbirdio/netbird/releases/download/v0.83.1/getting-started.sh","availability":"available","reviewed":"2026-11-19","scope":"Community combined-server quickstart script; advanced multi-container configuration is separate","source":"https://docs.netbird.io/selfhosted/selfhosted-quickstart","status":"documented","summary":"The v0.83.1 release publishes getting-started.sh with a verified SHA-256 digest. The script defaults several NetBird containers to latest, so pinning the script does not pin the complete deployment. Review and lock the generated Compose images and persistent state before production use.","supportingSources":[{"title":"Upstream release and published installer digest","url":"https://github.com/netbirdio/netbird/releases/tag/v0.83.1"}]},"licensePricing":{"availability":"available","reviewed":"2026-11-19","scope":"NetBird Self-Hosted Community Edition: selected customer-operated edition","source":"https://github.com/netbirdio/netbird/blob/main/LICENSE","status":"documented","summary":"The selected Community Edition is open source under mixed BSD-3-Clause and AGPL-3.0 terms and does not require the Enterprise license. Enterprise HA, SCIM and related capabilities are separately commercial.","supportingSources":[{"title":"Enterprise license boundary","url":"https://docs.netbird.io/selfhosted/enterprise"}]},"marketplace":{"reviewed":"2026-11-19","scope":"NetBird Self-Hosted Community Edition: selected customer-operated edition","source":"https://docs.netbird.io/selfhosted/selfhosted-guide","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-13T12:11:07Z","releaseTag":"v0.83.1","reviewed":"2026-11-19","scope":"NetBird Self-Hosted Community Edition upstream application, independently versioned from provider packages","source":"https://github.com/netbirdio/netbird/releases/tag/v0.83.1","status":"documented","summary":"The reviewed upstream v0.83.1 release was published 2026-11-13. Provider images and installer/component packages can differ; this snapshot does not promise a support window or future cadence."},"scim":{"availability":"unavailable","reviewed":"2026-11-19","scope":"NetBird Self-Hosted Community Edition: selected customer-operated edition","source":"https://docs.netbird.io/selfhosted/enterprise","status":"documented","summary":"NetBird's edition comparison places SCIM user and group provisioning in the Enterprise Commercial License, not Community Edition. Treat SCIM as unavailable for this selected Community listing."},"securityControls":{"availability":"edition-dependent","reviewed":"2026-11-19","scope":"NetBird Self-Hosted Community Edition: selected customer-operated edition","source":"https://docs.netbird.io/selfhosted/selfhosted-guide","status":"documented","summary":"The self-hosted control plane supports OIDC identity, policy-controlled peer access and customer-managed TLS, firewall and state. Community Edition excludes Enterprise SCIM, traffic-flow logging and active-active HA; secure relay, backup and upgrade operations remain customer responsibilities.","supportingSources":[{"title":"Community and Enterprise capability boundary","url":"https://docs.netbird.io/selfhosted/enterprise"}]},"sso":{"availability":"available","reviewed":"2026-11-19","scope":"NetBird Self-Hosted Community Edition: selected customer-operated edition","source":"https://docs.netbird.io/selfhosted/selfhosted-guide","status":"documented","summary":"The advanced Community self-hosting guide supports a custom OpenID Connect identity provider and names self-hosted and managed IdP options. Enterprise-only identity lifecycle features are separate."}},"id":"netbird-self-hosted","infrastructure":["servers"],"infrastructureNotes":"The quickstart deploys the full control plane as persistent containers on a customer-operated Linux VM.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://docs.netbird.io/selfhosted/selfhosted-quickstart","https://docs.netbird.io/selfhosted/selfhosted-guide"],"install":"Official self-hosting script and Docker Compose on a Linux VM; advanced deployment supports a custom identity provider","installMethods":["docker"],"kind":"product","license":"Mixed open-source terms: BSD-3-Clause generally and AGPL-3.0 for server control-plane directories; Enterprise features require a commercial license.","licenseModel":"open-source","licenseModelNotes":"Community code is open source but mixed-licensed: most repository code is BSD-3-Clause, while server control-plane directories are AGPL-3.0. Enterprise-licensed features are excluded.","licenseModelSources":["https://github.com/netbirdio/netbird/blob/main/LICENSE","https://docs.netbird.io/selfhosted/enterprise"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"NetBird Self-Hosted Community Edition","notes":"This entry covers the Community self-hosted edition, not NetBird Cloud or the Enterprise Commercial License. The quickstart is single-node; high availability and commercial SCIM or traffic-flow features are outside this edition. The cited advanced guide also establishes DigitalOcean, Hetzner and OCI paths. Its multi-container configuration differs from the combined-server quickstart; preserve version and migration boundaries. The pinned quickstart script still uses latest for several images, which must be locked separately.","operations":"Customer manages the VM, domain, TLS, firewall ports, identity configuration, control-plane state, relay capacity, backups, upgrades and availability.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"NetBird self-hosting quickstart","url":"https://docs.netbird.io/selfhosted/selfhosted-quickstart"},{"title":"NetBird advanced self-hosting guide","url":"https://docs.netbird.io/selfhosted/selfhosted-guide"},{"title":"NetBird repository license","url":"https://github.com/netbirdio/netbird/blob/main/LICENSE"},{"title":"NetBird Enterprise edition boundary","url":"https://docs.netbird.io/selfhosted/enterprise"},{"title":"Reviewed deployment artifact reference","url":"https://github.com/netbirdio/netbird/releases/download/v0.83.1/getting-started.sh"},{"title":"Upstream release and published installer digest","url":"https://github.com/netbirdio/netbird/releases/tag/v0.83.1"},{"title":"Upstream contributor history","url":"https://github.com/netbirdio/netbird/graphs/contributors"}],"url":"https://launchinyourcloud.com/directory/netbird-self-hosted/","website":"https://netbird.io/"},{"advisories":[{"action":"Upgrade to 2026.10.2 or later and retest shares, forms, workflows, OIDC and SAML IdP-initiated login.","conditions":"Public shares or dashboards, forms, Editor access to workflows, configured-key webhooks, OIDC or SAML determine exposure and upgrade impact.","disclosedOn":"2026-11-19","id":"nocodb-2026-10-2-access-control-hardening","listingIds":["nocodb"],"reviewed":"2026-11-19","scope":"NocoDB self-hosted behavior documented in the 2026.10.2 release; no universal affected-version range was published.","source":"https://github.com/nocodb/nocodb/releases/tag/2026.10.2","summary":"NocoDB 2026.10.2 prevents hidden-field disclosure in shares, unrelated form writes and workflow-secret disclosure to Editors, and caps webhook request bodies.","title":"NocoDB 2026.10.2 access-control hardening","type":"security-advisory"}],"architecture":"Customer-operated application with persistent metadata/database services and optional connected databases","categories":["no-code-databases","internal-tools"],"category":"No-code databases","categoryFit":{"internal-tools":"Interfaces build focused internal pages, dashboards and approval views on base data. The reviewed release limits Interfaces to licensed self-hosted Business plans and above.","no-code-databases":"Spreadsheet-style database interface with linked records, views, forms and programmatic access."},"cloudEvidence":[{"clouds":["aws","gcp","digitalocean","railway"],"deploymentBoundaries":{"digitalocean":"platform-workspace"},"notes":"The upstream community-methods guide includes full application deployment on DigitalOcean App Platform and a Railway template alongside AWS ECS/Fargate and Google Cloud Run. NocoDB explicitly does not maintain these methods or give them first-class installation support. Review image licensing, database configuration, persistence and production requirements.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"NocoDB community cloud installation methods","url":"https://nocodb.com/docs/self-hosting/installation/community-methods","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","gcp","digitalocean","railway"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Vendor-published named organization adoption claims","url":"https://nocodb.com/"},{"title":"Observed user/maintainer discussion of the license change","url":"https://github.com/nocodb/nocodb/discussions/12891"},{"title":"Current maintenance releases","url":"https://github.com/nocodb/nocodb/releases"}],"summary":"NocoDB's published adopter list names Accenture, Bosch and American Express. Its official GitHub discussion records actual exchanges between named users and maintainer o1lab about the 2026 license change, including critical feedback, while the release history shows continuing maintenance. These are adoption and participation signals; they do not establish which edition or hosting model any named organization uses."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"platform-workspace","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Spreadsheet-style database platform with linked records, views and optional licensed internal app interfaces.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Single-server starting guidance; not a complete HA design or 1-TB storage allowance","source":"https://nocodb.com/docs/self-hosting","status":"documented","summary":"The self-hosting guide lists a minimum of 2 vCPU, 2 GB RAM and 10 GB disk, and a production recommendation of 4 vCPU, 8 GB RAM and 50 GB or more disk. Database, attachments, workload and replication require additional sizing."},"iac":{"artifactRef":"develop installer (moving)","artifactUrl":"https://github.com/nocodb/nocodb/blob/develop/docker-compose/1_Auto_Upstall/noco.sh","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://github.com/nocodb/nocodb","status":"documented","summary":"The upstream repository publishes an installer that generates a PostgreSQL/Redis/Traefik Compose stack. Re-running can upgrade the application; inspect the script, preserve secrets/data and control version changes."},"licensePricing":{"reviewed":"2026-11-20","scope":"Reviewed source-available terms; confirm commercial use and paid features for the intended deployment","source":"https://github.com/nocodb/nocodb/blob/2026.10.2/LICENSE.md","status":"documented","summary":"The 2026.10.2 licence identifies the Sustainable Use License for the master/develop code: use and modification are limited to internal business, personal or non-commercial purposes, with restricted distribution. Commercial/self-hosted paid features require separate entitlements; this is not an unrestricted OSI open-source licence."},"release":{"releasePublishedAt":"2026-11-19T10:12:43Z","releaseTag":"2026.10.2","reviewed":"2026-11-19","scope":"Upstream NocoDB self-hosted release; paid-feature and license behavior remains edition-dependent","source":"https://github.com/nocodb/nocodb/releases/tag/2026.10.2","status":"documented","summary":"NocoDB 2026.10.2 was published November 19, 2026. It fixes shared-view, dashboard, form and workflow authorization boundaries, restores NC_SSO=oidc, changes SAML IdP-initiated RelayState handling and repairs air-gapped license refresh.","supportingSources":[{"title":"Prior reviewed release context","url":"https://github.com/nocodb/nocodb/releases/tag/2026.10.1"}]},"securityControls":{"reviewed":"2026-11-19","scope":"NocoDB self-hosted access controls documented in the 2026.10.2 release; no broader affected-version range was published","source":"https://github.com/nocodb/nocodb/releases/tag/2026.10.2","status":"documented","summary":"NocoDB 2026.10.2 prevents shared views and dashboards from returning hidden fields, prevents forms from writing unrelated fields, hides workflow secrets from Editors and limits webhook request bodies. Upgrade and retest shares, forms, workflows and SSO."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-20","scope":"Paid self-hosted user federation; verify the selected Business/Scale/Enterprise entitlement rather than assuming Community includes SSO","source":"https://nocodb.com/docs/product-docs/account-settings/authentication","status":"documented","summary":"The authentication guide documents SAML and OIDC providers and explicitly describes on-premises SSO configuration without Cloud DNS-domain verification. SSO is associated with paid self-hosted plans; optional password login alongside SSO has a separate on-premises setting.","supportingSources":[{"title":"Self-hosted plans and licensing","url":"https://nocodb.com/docs/self-hosting"}]}},"id":"nocodb","infrastructure":["servers"],"infrastructureNotes":"Official Docker images run the NocoDB application on a customer-controlled host with persistent storage and a configured SQLite or PostgreSQL metadata backend; the server installer adds supporting services.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://github.com/nocodb/nocodb"],"install":"Run the official Docker image with persistent storage or use its documented Compose-based server installer.","installMethods":["docker","package"],"kind":"product","license":"Current upstream master/develop code uses the Sustainable Use License: internal business or noncommercial/personal use is permitted, with distribution and other restrictions. Paid self-hosted features require a separate license.","licenseModel":"source-available","licenseModelNotes":"Current upstream master/develop code uses the Sustainable Use License: internal business or noncommercial/personal use is permitted, with distribution and other restrictions. Paid self-hosted features require a separate license. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.","licenseModelSources":["https://raw.githubusercontent.com/nocodb/nocodb/develop/LICENSE.md"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"NocoDB Self-Hosted","notes":"The upstream license changed in January 2026; this is classified as source-available. Internal-tool Interfaces are a licensed feature, while AI apps have separate availability. Connected databases, AI providers and integrations can send data outside the account. NocoDB 2026.10.2 restricts shared views and dashboards to displayed fields, limits forms to their own fields, prevents Editors from reading workflow-step secrets and caps workflow webhook bodies at 1 MB. It also restores NC_SSO=oidc, requires unchanged RelayState for SAML IdP-initiated login and repairs air-gapped license refresh. Retest public shares, forms, workflow permissions and SSO after upgrading.","operations":"Customer manages app services, databases, access rules, secrets, backups, upgrades and any paid license.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Upstream project and capabilities","url":"https://github.com/nocodb/nocodb"},{"title":"Current upstream license","url":"https://raw.githubusercontent.com/nocodb/nocodb/develop/LICENSE.md"},{"title":"Internal Interfaces and self-hosted plan availability","url":"https://nocodb.com/docs/changelog/2026.08.0"},{"title":"Product functionality","url":"https://nocodb.com/docs/product"},{"title":"NocoDB 2026.10.2 release","url":"https://github.com/nocodb/nocodb/releases/tag/2026.10.2"}],"url":"https://launchinyourcloud.com/directory/nocodb/","website":"https://nocodb.com/"},{"architecture":"Licensed NVIDIA AI containers and infrastructure software on customer GPU virtual machines, managed Kubernetes clusters or marketplace OpenShift","categories":["ai-tools","ai-inference-gateways"],"category":"AI tools \u0026 infrastructure","categoryFit":{"ai-inference-gateways":"Includes supported inference and model-serving components for deploying generative-AI and machine-learning workloads.","ai-tools":"Provides an enterprise-supported suite of AI frameworks, infrastructure software, operations components and development tools."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"NVIDIA documents standard instances, NVIDIA VM images, GPU-optimized VM images, managed Kubernetes and marketplace OpenShift paths across AWS, Azure and Google Cloud. License inclusion varies by image and offer; standard instances and managed Kubernetes generally require BYOL.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"NVIDIA AI Enterprise on AWS, Azure and Google Cloud","url":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html","vendorSupport":"not-assessed"},{"clouds":["oci","alibaba"],"notes":"NVIDIA's current cloud matrix includes standard instances on Oracle Cloud Infrastructure and Alibaba Cloud, NVIDIA AI Enterprise VM images on OCI and GPU-optimized VM images on Alibaba Cloud. Customers must confirm the supported component set, certified instance and license path.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"NVIDIA AI Enterprise on Oracle Cloud and Alibaba Cloud","url":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html","vendorSupport":"not-assessed"},{"applicableEdition":"NVIDIA AI Enterprise standard-instance BYOL","clouds":["tencent"],"notes":"NVIDIA documents installing its licensed stack on customer standard instances using a certified Ubuntu operating system, supported NVIDIA drivers, Docker and Container Toolkit, then pulling NGC containers. This is a BYOL installation rather than an included-license marketplace image. Select an instance from the supported-cloud-services matrix; the guide states one license per cloud instance, which must be reconciled with the general licensing guide and the customer agreement.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"NVIDIA AI Enterprise on Tencent Cloud standard instances","url":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html","vendorSupport":"not-assessed"},{"applicableEdition":"NVIDIA AI Enterprise standard-instance BYOL","clouds":["volcano"],"notes":"NVIDIA documents installing its licensed stack on customer standard instances using a certified Ubuntu operating system, supported NVIDIA drivers, Docker and Container Toolkit, then pulling NGC containers. This is a BYOL installation rather than an included-license marketplace image. Select an instance from the supported-cloud-services matrix; the guide states one license per cloud instance, which must be reconciled with the general licensing guide and the customer agreement.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"NVIDIA AI Enterprise on ByteDance Volcano Engine standard instances","url":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-16","clouds":["aws","azure","gcp","oci","alibaba","tencent","volcano"],"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":"cloud-account","cloud":"oci","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"alibaba","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"tencent","controlPlane":"not-assessed","evidence":[2],"operator":"customer"},{"boundary":"cloud-account","cloud":"volcano","controlPlane":"not-assessed","evidence":[3],"operator":"customer"}],"description":"Commercial enterprise AI software suite deployed on customer cloud GPU instances or managed Kubernetes clusters.","diligence":{"airGap":{"reviewed":"2026-11-16","scope":"NVIDIA License System DLS workflow; component licensing and application dependencies differ","source":"https://docs.nvidia.com/license-system/latest/nvidia-license-system-quick-start-guide/","status":"documented","summary":"NVIDIA documents registering a Delegated License Service appliance on an air-gapped network by manually transferring registration details through its Licensing Portal. This confirms an offline licensing workflow for applicable components, not disconnected compatibility of every AI Enterprise service or model.","supportingSources":[{"title":"When AI Enterprise requires the license system","url":"https://docs.nvidia.com/ai-enterprise/planning-resource/licensing-guide/latest/license-system.html"}]},"commitments":{"availability":"edition-dependent","reviewed":"2026-11-16","scope":"Vendor statement for AI Enterprise AWS Marketplace private offers only","source":"https://www.nvidia.com/en-us/data-center/lp/aws-marketplace-offer/","status":"documented","summary":"NVIDIA explicitly states that AI Enterprise AWS Marketplace private offers are eligible toward an AWS committed-spend agreement. Confirm the specific offer and buyer agreement; this statement does not establish Azure/GCP credit or eligibility for every image or BYOL purchase."},"compliance":{"reviewed":"2026-11-16","scope":"Selected software-artifact assurances versus a customer-deployment audit","source":"https://docs.nvidia.com/ai-enterprise/planning-resource/ai-enterprise-infrastructure-software/latest/enterprise-software-built-on-open-source.html","status":"inconclusive","summary":"Government Ready, STIG-hardening and FIPS-library statements describe selected NVIDIA software branches. The reviewed page does not establish a current independent attestation for the complete customer-account deployment, third-party integrations or every suite component."},"footprint":{"reviewed":"2026-11-20","scope":"Suite/component/model dependent; complete workload footprint unresolved","source":"https://docs.nvidia.com/ai-enterprise/latest/user-guide/index.html","status":"inconclusive","summary":"The suite includes multiple frameworks, drivers, operators and NIM services, each with its own support matrix. NIM directs buyers to model- and hardware-specific prerequisites. No suite-wide CPU/RAM/VRAM minimum is established; select components, model profiles, supported GPUs, concurrency and redundancy before sizing.","supportingSources":[{"title":"NIM component-specific prerequisite path","url":"https://docs.nvidia.com/nim/large-language-models/latest/get-started/index.html"}]},"iac":{"reviewed":"2026-11-16","scope":"Supported cloud matrix; component, operating system and instance compatibility must all match","source":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html","status":"documented","summary":"NVIDIA provides provider-specific image, standard-instance and Kubernetes procedures rather than one universal template. Tencent and Volcano standard-instance guides require a supported instance, certified Ubuntu, NVIDIA driver, Docker, Container Toolkit and NGC tooling, with BYOL.","supportingSources":[{"title":"Tencent standard instance","url":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html"},{"title":"Volcano Engine standard instance","url":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html"}]},"licensePricing":{"reviewed":"2026-11-20","scope":"Self-managed NVIDIA Partner Network list price; CSP marketplace terms differ","source":"https://docs.nvidia.com/ai-enterprise/planning-resource/licensing-guide/latest/pricing.html","status":"documented","summary":"The current licensing guide lists a one-year self-managed subscription at USD 4,500 per GPU including standard support. Multi-year, perpetual, educational and partner terms differ. Cloud-marketplace and bundled-hardware entitlements have separate rules; this software list price excludes GPU infrastructure and is not a workload quote. For Tencent/Volcano BYOL paths, the previously noted per-instance versus per-GPU unit still needs contract confirmation.","supportingSources":[{"title":"Cloud BYOL unit requires separate confirmation","url":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html"},{"title":"Volcano Engine BYOL path","url":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html"}]},"marketplace":{"availability":"edition-dependent","reviewed":"2026-11-16","scope":"Offer-specific licensing; no cloud-commitment eligibility established","source":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html","status":"documented","summary":"The deployment matrix distinguishes license-included AI Enterprise VM images/private offers from BYOL paths. A generic GPU-optimized image or Kubernetes installation does not include AI Enterprise licensing merely because it comes from a cloud provider."},"release":{"reviewed":"2026-11-18","scope":"AI Enterprise component and branch lifecycle; no single suite version covers every deployment","source":"https://docs.nvidia.com/ai-enterprise/lifecycle/latest/index.html","status":"documented","summary":"NVIDIA's November 2026 lifecycle material lists active 9.0/R620, 8.3/R595, and 7.9 LTSB/R580 branches with distinct support windows. NeMo Microservices support ended October 1, 2026, after 25.12 was designated the final GA release."},"securityControls":{"reviewed":"2026-11-16","scope":"AI Enterprise infrastructure software and application Production Branch; not an independent customer-environment attestation","source":"https://docs.nvidia.com/ai-enterprise/planning-resource/ai-enterprise-infrastructure-software/latest/enterprise-software-built-on-open-source.html","status":"documented","summary":"NVIDIA describes Government Ready infrastructure software and Production Branch application software using STIG-hardened containers, FIPS-compliant libraries and monthly security/maintenance patches. The statement is branch-specific; it does not certify every suite component, cloud image or customer deployment."},"sso":{"reviewed":"2026-11-20","scope":"Suite-wide runtime SSO cannot be established from distribution/account access","source":"https://docs.nvidia.com/ai-enterprise/latest/user-guide/index.html","status":"inconclusive","summary":"AI Enterprise is a suite with independently versioned application and infrastructure components. NGC/catalog account authentication does not establish SAML/OIDC for every deployed microservice or workload. Select the actual NIM/framework/management components and confirm their runtime identity integrations and entitlements."}},"id":"nvidia-ai-enterprise","infrastructure":["servers"],"infrastructureNotes":"NVIDIA AI Enterprise runs licensed AI containers and infrastructure components on persistent customer GPU or CPU instances and Kubernetes worker nodes.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html","https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/index.html","https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html","https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html"],"install":"NVIDIA AI Enterprise or GPU-optimized cloud VM images, standard instances with BYOL, or managed Kubernetes on supported cloud providers","installMethods":["vm-image","helm","kubernetes"],"kind":"product","license":"Commercial NVIDIA AI Enterprise subscription, consumption or perpetual license; most customer-cloud paths require BYOL.","licenseModel":"commercial-only","licenseModelNotes":"NVIDIA AI Enterprise requires a commercial subscription, consumption or perpetual entitlement. Cloud instances are usually BYOL unless the selected on-demand VMI or private offer explicitly includes licensing. The Tencent and Volcano standard-instance guides state one license per cloud instance, while the general licensing guide describes per-GPU BYOL. Confirm the applicable unit for the selected instance, GPU count and agreement before purchase.","licenseModelSources":["https://docs.nvidia.com/ai-enterprise/planning-resource/licensing-guide/latest/licensing.html","https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html","https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"NVIDIA AI Enterprise","notes":"This entry covers customer-operated NVIDIA AI Enterprise software, not a managed AI service. A license is required and is not included with most standard, GPU-optimized VMI or managed-Kubernetes deployments; on-demand NVIDIA AI Enterprise VMIs and private offers use separate included-license processes. Not every component is available on every cloud or deployment model. GPU deployments are generally licensed per GPU, while CPU-only instances require an instance license. Tencent Cloud and ByteDance Volcano Engine have documented standard-instance BYOL paths. These guides require certified software and supported instance types; they do not establish that every GPU, component or provider image is eligible. Their per-instance wording differs from the general per-GPU licensing guidance, so confirm the applicable licensing unit. The November lifecycle matrix lists active 9.0/R620, 8.3/R595, and 7.9 LTSB/R580 branches with different end dates. NeMo Microservices support ended October 1, 2026, after 25.12 became the final GA release; select and patch each component branch independently.","operations":"Customer manages cloud GPU instances or Kubernetes, drivers, GPU Operator and container runtime, networking, storage, identities, NGC access, model services, monitoring, upgrades and license activation.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"NVIDIA AI Enterprise cloud deployment guide","url":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/index.html"},{"title":"NVIDIA AI Enterprise cloud deployment overview","url":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/overview.html"},{"title":"NVIDIA AI Enterprise on AWS","url":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/aws-overview.html"},{"title":"NVIDIA AI Enterprise on Azure","url":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/azure-overview.html"},{"title":"NVIDIA AI Enterprise on Google Cloud","url":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/google-overview.html"},{"title":"NVIDIA AI Enterprise licensing","url":"https://docs.nvidia.com/ai-enterprise/planning-resource/licensing-guide/latest/licensing.html"},{"title":"NVIDIA AI Enterprise on Tencent Cloud standard instances","url":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/tencent-standard-instance.html"},{"title":"NVIDIA AI Enterprise on ByteDance Volcano Engine standard instances","url":"https://docs.nvidia.com/ai-enterprise/deployment/cloud/latest/bytedance-volcano-engine-standard-instance.html"},{"title":"NVIDIA AI Enterprise documentation","url":"https://docs.nvidia.com/ai-enterprise/"},{"title":"NVIDIA AI Enterprise lifecycle","url":"https://docs.nvidia.com/ai-enterprise/lifecycle/latest/index.html"}],"url":"https://launchinyourcloud.com/directory/nvidia-ai-enterprise/","website":"https://www.nvidia.com/en-us/data-center/products/ai-enterprise/"},{"advisories":[{"action":"Upgrade to the branch-specific fixed build or vendor-recommended 2026.3.16117 and review privileged sessions and delegated roles.","conditions":"Authentication configuration, OIDC use, and delegated roles determine exposure. SA2026-28 has no mitigation.","id":"octopus-server-november-2026-security-update","listingIds":["octopus-server"],"reviewed":"2026-11-18","scope":"CVE-2026-96414, CVE-2026-116835, and CVE-2026-116288; fixed builds differ between the 2026.2 and 2026.3 lines.","source":"https://advisories.octopus.com/post/2026/sa2026-28/","summary":"SA2026-19, SA2026-22, and SA2026-28 cover authentication-cookie forgery, OIDC subject spoofing, and delegated-role privilege escalation.","supportingSources":[{"title":"SA2026-19","url":"https://advisories.octopus.com/post/2026/sa2026-19/"},{"title":"SA2026-22","url":"https://advisories.octopus.com/post/2026/sa2026-22/"}],"title":"Octopus Server November 2026 privilege and authentication fixes","type":"security-advisory"}],"architecture":"Customer-operated stateful Octopus Server nodes with SQL Server and persistent storage.","categories":["devops"],"category":"DevOps","categoryFit":{"devops":"Continuous delivery, release orchestration and operational runbook automation."},"cloudEvidence":[{"clouds":["aws"],"notes":"Octopus explicitly lists Amazon ECS and EKS among supported underlying technologies for the Server Linux container. This is the server application in customer-operated AWS infrastructure.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Octopus Server container on AWS ECS or EKS","url":"https://octopus.com/docs/installation","vendorSupport":"not-assessed"},{"clouds":["azure","gcp"],"notes":"Octopus documents hosting the full Server application in the customer's Kubernetes cluster and calls out provider-specific AKS and GKE considerations. Customers supply supported database and storage architecture.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Octopus Server in customer Kubernetes clusters with AKS and GKE guidance","url":"https://octopus.com/docs/installation/octopus-server-linux-container/octopus-in-kubernetes","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":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Deployment automation and runbook platform installed on servers or Kubernetes infrastructure you operate.","diligence":{"airGap":{"reviewed":"2026-11-17","scope":"Server isolation versus an offline deployment target","source":"https://octopus.com/docs/installation/isolated-octopus-deploy-servers/","status":"inconclusive","summary":"The isolated-server guide covers separate networks and offline package-drop targets. It does not by itself establish a complete no-internet Server licensing, dependency and update workflow for the selected licence."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Octopus Server; unresolved within this edition/deployment","source":"https://octopus.com/pricing/faq","status":"inconclusive","summary":"Server purchasing terms did not establish an eligible offer or qualifying fees against an existing cloud commitment agreement."},"compliance":{"reviewed":"2026-11-17","scope":"Self-hosted PCI controls versus independent certification","source":"https://octopus.com/docs/security/pci-compliance-and-octopus-deploy","status":"inconclusive","summary":"The PCI guidance describes deployment controls and network separation, not an attestation covering a customer-operated Server environment. Obtain the applicable report and deployment scope."},"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://octopus.com/docs/administration/managing-infrastructure/performance/","status":"inconclusive","summary":"Confirm HA Server replicas, workers, concurrent tasks and a supported SQL Server HA/licensing design. The small single-server task baseline does not establish the requested HA topology. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"Vendor small-workload baseline; not the total HA topology","source":"https://octopus.com/docs/administration/managing-infrastructure/performance/","status":"documented","summary":"The small 5–10 concurrent-task baseline is one Server with 2 cores/4 GB RAM plus SQL Server Express with 2 cores/4 GB, or Azure SQL with 25–50 DTUs. HA servers, workers, database and task load require separate sizing."},"iac":{"reviewed":"2026-11-17","scope":"Octopus Server in customer Kubernetes","source":"https://octopus.com/docs/installation/octopus-server-linux-container/octopus-in-kubernetes","status":"documented","summary":"The vendor supplies a Server Linux-container Kubernetes deployment workflow, with separate persistent storage and SQL database configuration. Pin compatible server images and configure the selected cluster and secrets."},"licensePricing":{"reviewed":"2026-11-17","scope":"Octopus Server: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://octopus.com/pricing/faq","status":"documented","summary":"Octopus Server is proprietary software governed by the Octopus Customer Agreement. Its no-cost Free tier is usage-limited and license-key activated; Professional and Enterprise are paid annual tiers."},"marketplace":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Octopus Server; unresolved within this edition/deployment","source":"https://octopus.com/pricing/faq","status":"inconclusive","summary":"The purchasing FAQ distinguishes Octopus Cloud and Server licences. A current Marketplace offer explicitly delivering/entitling self-hosted Server was not established."},"release":{"reviewed":"2026-11-18","scope":"Octopus Server 2026.2 and 2026.3 maintained lines","source":"https://advisories.octopus.com/2026/","status":"documented","summary":"Octopus recommends 2026.3.16117 after November security advisories. Branch-specific minimum fixes include 2026.2.13487/2026.3.15875, 2026.2.13503/2026.3.15894, and 2026.2.13526/2026.3.15909."},"scim":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"Self-hosted SCIM, supported provider and licence required","source":"https://octopus.com/docs/security/authentication/scim/","status":"documented","summary":"SCIM 2 is documented for the Microsoft Entra ID authentication provider with a licence including SCIM, such as Enterprise. The IdP needs inbound HTTPS access to the Octopus API."},"securityControls":{"reviewed":"2026-11-18","scope":"Server sessions and access revocation CVE-2026-96414, CVE-2026-116835, and CVE-2026-116288; fixed builds differ between the 2026.2 and 2026.3 lines.","source":"https://advisories.octopus.com/post/2026/sa2026-28/","status":"documented","summary":"External authentication creates an Octopus session cookie; immediate revocation also requires disabling the user in Octopus. Scope API keys and configure HTTPS, server encryption and target communication separately. Current advisory review: SA2026-19, SA2026-22, and SA2026-28 cover authentication-cookie forgery, OIDC subject spoofing, and delegated-role privilege escalation. Upgrade to the branch-specific fixed build or vendor-recommended 2026.3.16117 and review privileged sessions and delegated roles.","supportingSources":[{"title":"Prior security-controls source","url":"https://octopus.com/docs/security/authentication/"},{"title":"SA2026-19","url":"https://advisories.octopus.com/post/2026/sa2026-19/"},{"title":"SA2026-22","url":"https://advisories.octopus.com/post/2026/sa2026-22/"}]},"sso":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"Self-hosted Octopus authentication","source":"https://octopus.com/docs/security/authentication/","status":"documented","summary":"Octopus Server documents external identity providers and OpenID Connect. Provider compatibility and licence features vary; disabling a user in the IdP does not immediately revoke an already active Octopus session."}},"id":"octopus-server","infrastructure":["servers"],"infrastructureNotes":"Octopus Server runs as a Windows service or Linux container and depends on SQL Server plus persistent package, artifact, task-log and configuration storage.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://octopus.com/docs/installation","https://octopus.com/docs/installation/sql-database/"],"install":"Windows MSI, Docker or Docker Compose, or the official Helm chart on Kubernetes","installMethods":["package","docker","helm","kubernetes"],"kind":"platform","license":"Proprietary Free tier or annual Professional and Enterprise licenses.","licenseModel":"commercial-only","licenseModelNotes":"Octopus Server is proprietary software governed by the Octopus Customer Agreement. Its no-cost Free tier is usage-limited and license-key activated; Professional and Enterprise are paid annual tiers.","licenseModelSources":["https://octopus.com/pricing/faq","https://octopus.com/free"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"Octopus Server","notes":"This entry covers self-hosted Octopus Server, not Octopus Cloud. Octopus Server requires SQL Server 2016 or later or Azure SQL and a license key, including for the Free tier. The Linux container is stateful and needs persistent storage and monitoring. Self-hosted releases trail the cloud product by at least one quarter; each self-hosted major.minor release receives critical patches and support for six months. Octopus advisories SA2026-19, SA2026-22, and SA2026-28 cover authentication-cookie forgery, OIDC subject spoofing, and delegated-role privilege escalation. The last issue has no mitigation; Octopus recommends current 2026.3.16117, with branch-specific fixed builds also documented.","operations":"Customer operates the server or cluster, SQL database, persistent storage, backups, security, upgrades and availability configuration.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Install Octopus Server","url":"https://octopus.com/docs/installation"},{"title":"Run Octopus Server in Kubernetes","url":"https://octopus.com/docs/installation/octopus-server-linux-container/octopus-in-kubernetes"},{"title":"Octopus Server installation requirements","url":"https://octopus.com/docs/installation/requirements"},{"title":"SQL database requirements","url":"https://octopus.com/docs/installation/sql-database/"},{"title":"Octopus licensing and purchasing FAQ","url":"https://octopus.com/pricing/faq"},{"title":"Octopus Server downloads","url":"https://octopus.com/downloads"},{"title":"Octopus SA2026-19","url":"https://advisories.octopus.com/post/2026/sa2026-19/"},{"title":"Octopus SA2026-22","url":"https://advisories.octopus.com/post/2026/sa2026-22/"},{"title":"Octopus SA2026-28","url":"https://advisories.octopus.com/post/2026/sa2026-28/"}],"url":"https://launchinyourcloud.com/directory/octopus-server/","website":"https://octopus.com/"},{"architecture":"Customer-operated web/API services, background workers, PostgreSQL, Redis, search and object storage","categories":["ai-applications-rag","ai-tools"],"category":"AI applications \u0026 RAG","categoryFit":{"ai-applications-rag":"Provides enterprise search, connectors and retrieval-augmented AI assistants over customer-selected knowledge sources.","ai-tools":"Provides self-hosted indexing, retrieval, model integration and agent services for building internal AI experiences."},"cloudEvidence":[{"clouds":["aws"],"notes":"Onyx documents self-hosting on a customer EC2 instance and links a production EKS architecture using AWS managed dependencies.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"Onyx on AWS","url":"https://docs.onyx.app/deployment/cloud/aws/ec2","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Onyx documents self-hosting on an Azure VM and an AKS Terraform path using customer Azure managed services.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"Onyx on Azure","url":"https://docs.onyx.app/deployment/cloud/azure","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Onyx documents Compute Engine and production GKE deployment paths in the customer's Google Cloud project.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"Onyx on Google Cloud","url":"https://docs.onyx.app/deployment/cloud/gcp","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"Onyx documents installing its self-hosted stack on a customer DigitalOcean Droplet.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"Onyx on DigitalOcean","url":"https://docs.onyx.app/deployment/cloud/digital_ocean","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-14","clouds":["aws","azure","gcp","digitalocean"],"communityAcceptance":{"reviewed":"2026-11-14","sources":[{"title":"Reviewed maintenance release v5.1.2","url":"https://github.com/onyx-dot-app/onyx/releases/tag/v5.1.2"},{"title":"Upstream contributor history","url":"https://github.com/onyx-dot-app/onyx/graphs/contributors"}],"summary":"Onyx has sustained, substantive code participation from multiple contributors. Release 5.1.2 on November 12, 2026 records continuing maintenance, including permission-handling and retrieval fixes. Contributor and release histories establish maintained project participation; they do not establish that paid Business or Enterprise features are included in the MIT Community Edition."},"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"}],"description":"Self-hosted enterprise search and AI assistant platform with connectors and retrieval infrastructure.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Vendor Lite/Standard profiles; per-container and single-instance recommendations differ","source":"https://docs.onyx.app/deployment/getting_started/resourcing.md","status":"documented","summary":"The vendor gives Lite minimum 2 vCPUs/2 GB RAM/10 GB disk and Standard minimum 4 vCPUs/10 GB RAM/32 GB plus roughly 2.5 times indexed data. Its Standard per-container example totals about 12 CPUs/24 GB. These describe different profiles; connector/index volume, model services and HA require additional sizing."},"iac":{"artifactRef":"main (moving branch)","artifactUrl":"https://github.com/onyx-dot-app/onyx/tree/main/deployment/docker_compose","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://docs.onyx.app/deployment/local/docker","status":"documented","summary":"The official Docker guide uses the upstream deployment/docker_compose directory and an environment template. The default image tag moves; replace example storage credentials and configure the selected inference/storage services."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/onyx-dot-app/onyx/main/LICENSE","status":"documented","summary":"Core code is MIT licensed; ee directories are under the Onyx Enterprise License. Enterprise features need their own entitlement and quote. The MIT core licence does not establish all-edition feature access, support or model/hosting prices."},"release":{"releasePublishedAt":"2026-11-12T21:02:29Z","releaseTag":"v5.1.2","reviewed":"2026-11-14","scope":"Upstream onyx-dot-app/onyx release record; commercial editions and deployment packages may differ","source":"https://github.com/onyx-dot-app/onyx/releases/tag/v5.1.2","status":"documented","summary":"The publisher-designated GitHub release checked was v5.1.2, published 2026-11-12. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package."},"scim":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Onyx Enterprise feature statement","source":"https://github.com/onyx-dot-app/onyx","status":"documented","summary":"The upstream Enterprise section describes group synchronization and SCIM user provisioning. Confirm the licensed self-hosted implementation and supported lifecycle operations rather than assuming Community includes them."},"sso":{"reviewed":"2026-11-14","scope":"Enterprise feature statement; exact protocol entitlement not fully established","source":"https://github.com/onyx-dot-app/onyx","status":"documented","summary":"The upstream Enterprise section advertises Google OAuth, OIDC and SAML sign-in. The README does not establish every Community-versus-Enterprise protocol entitlement; confirm the selected self-hosted edition and identity configuration."}},"id":"onyx","infrastructure":["servers"],"infrastructureNotes":"Onyx runs web services, workers and persistent database, cache, search and object-storage dependencies on VMs or Kubernetes.","infrastructureReviewed":"2026-11-14","infrastructureSources":["https://docs.onyx.app/deployment/cloud/aws/ec2","https://docs.onyx.app/deployment/cloud/gcp"],"install":"Docker Compose on a VM or official Kubernetes and Terraform deployment","installMethods":["terraform","docker"],"kind":"product","license":"MIT Community Edition; Business and Enterprise features use separate commercial terms.","licenseModel":"open-source","licenseModelNotes":"Onyx Community Edition is MIT-licensed. Business and Enterprise features, images and support have separate commercial terms.","licenseModelSources":["https://github.com/onyx-dot-app/onyx/blob/main/LICENSE","https://docs.onyx.app/deployment/enterprise_edition.md"],"licenseReviewed":"2026-11-14","model":"Fully in your account","modelLabel":"Customer-operated","name":"Onyx Self-Hosted","notes":"This entry covers self-hosted Onyx, not a vendor-hosted environment. External LLM, embedding and connector services receive data according to the customer's configuration. Business and Enterprise features and support require separate commercial entitlements.","operations":"Customer manages application services, databases, search, object storage, connectors, model credentials, backups, scaling and upgrades.","publisher":false,"reviewed":"2026-11-14","sources":[{"title":"AWS EC2 deployment","url":"https://docs.onyx.app/deployment/cloud/aws/ec2"},{"title":"Azure deployment","url":"https://docs.onyx.app/deployment/cloud/azure"},{"title":"Google Cloud deployment","url":"https://docs.onyx.app/deployment/cloud/gcp"},{"title":"DigitalOcean deployment","url":"https://docs.onyx.app/deployment/cloud/digital_ocean"},{"title":"Community license","url":"https://github.com/onyx-dot-app/onyx/blob/main/LICENSE"},{"title":"Reviewed maintenance release v5.1.2","url":"https://github.com/onyx-dot-app/onyx/releases/tag/v5.1.2"},{"title":"Upstream contributor history","url":"https://github.com/onyx-dot-app/onyx/graphs/contributors"},{"title":"Current Business and Enterprise edition boundaries","url":"https://docs.onyx.app/deployment/enterprise_edition.md"}],"url":"https://launchinyourcloud.com/directory/onyx/","website":"https://www.onyx.app/"},{"architecture":"Customer-operated web application and conversation storage connected to model providers","categories":["ai-applications-rag","ai-tools"],"category":"AI applications \u0026 RAG","categoryFit":{"ai-applications-rag":"Deployable team chat and model-access interface with retrieval features. It is an interface and application layer, not an included license or runtime for every connected model.","ai-tools":"Self-hosted AI chat and knowledge interface for local model servers and cloud APIs."},"cloudEvidence":[{"clouds":["aws"],"notes":"Project deployment instructions cover the application on AWS ECS / Fargate with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Open WebUI deployment on AWS ECS / Fargate","url":"https://docs.openwebui.com/deployment/aws-ecs/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Project deployment instructions cover the application on Azure Container Apps with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Open WebUI deployment on Azure Container Apps","url":"https://docs.openwebui.com/deployment/azure-container-apps/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Project deployment instructions cover the application on Google Cloud Run with external database, Redis and file storage. Model inference is separate; review model endpoints, egress and WebSocket/runtime limits.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Open WebUI deployment on Google Cloud Run","url":"https://docs.openwebui.com/deployment/google-cloud-run/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","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":"Self-hosted AI chat and knowledge interface for local model servers and cloud APIs.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Application-container example; full stack and workload sizing excluded","source":"https://docs.openwebui.com/troubleshooting/performance/","status":"documented","summary":"The performance guide shows a container example reserving 2 CPUs/4 GB RAM with limits of 4 CPUs/8 GB. Multi-user deployments need PostgreSQL; scaled replicas also require shared services. Local inference, embeddings, extraction, vector storage and HA are additional. This is an example allocation, not a validated 100-user or 1-TB minimum.","supportingSources":[{"title":"Shared infrastructure for scaled deployments","url":"https://docs.openwebui.com/enterprise/deployment/"}]},"iac":{"artifactRef":"main (moving branch)","artifactUrl":"https://github.com/open-webui/open-webui/blob/main/docker-compose.yaml","reviewed":"2026-11-14","scope":"Upstream example; model resources and service exposure require separate review","source":"https://github.com/open-webui/open-webui/blob/main/docker-compose.yaml","status":"documented","summary":"The upstream Compose example includes Open WebUI and Ollama with persistent volumes. Its defaults use moving image references and an empty application secret; configure production credentials and pin versions."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/open-webui/open-webui/main/LICENSE","status":"documented","summary":"Current Open WebUI has custom terms restricting branding changes, with exceptions including deployments of at most 50 end users in a rolling 30-day period, written permission or an enterprise licence. A 100-user deployment cannot assume the small-deployment branding exception. Model and infrastructure costs are separate."},"release":{"releasePublishedAt":"2026-11-17T14:46:26Z","releaseTag":"v0.13.4","reviewed":"2026-11-18","scope":"Upstream Open WebUI self-hosted release; the Terminals version and migration requirements apply only to deployments using Terminals server connections","source":"https://github.com/open-webui/open-webui/releases/tag/v0.13.4","status":"documented","summary":"Open WebUI v0.13.4 was published November 17, 2026. Deployments using Terminals server connections require Terminals 0.4.0 or later; upgrading that server from 0.3.x requires manual migration. Open Terminal and Tether terminal connections are unaffected by this migration. The release also replaces Direct Connections and Integrations with Tether and migrates image settings."},"sso":{"availability":"available","reviewed":"2026-11-14","scope":"Upstream authentication configuration; review provider and session settings","source":"https://docs.openwebui.com/features/authentication-access/auth/sso/","status":"documented","summary":"Upstream documents OAuth/OIDC and trusted-header authentication. Only one generic OIDC provider is configured through OPENID_PROVIDER_URL at a time; trusted-header use requires an isolated trusted proxy."}},"id":"open-webui","infrastructure":["servers"],"infrastructureNotes":"The application runs as a Docker/Python server or Kubernetes workload with persistent conversation/user storage. Local inference is a separate server or accelerator workload, depending on the chosen model.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.openwebui.com/getting-started/quick-start/"],"install":"Official Docker image, Python installation or Kubernetes deployment.","installMethods":["docker","source"],"kind":"product","license":"Open WebUI license based on BSD-style terms with additional branding restrictions and defined exceptions; enterprise terms may be required for rebranding.","licenseModel":"source-available","licenseModelNotes":"The current Open WebUI license adds branding restrictions to BSD-style terms, with small-deployment and permission/license exceptions. Classified here as source-available rather than treating the current version as unmodified BSD-3-Clause.","licenseModelSources":["https://github.com/open-webui/open-webui/blob/main/LICENSE","https://docs.openwebui.com/license/"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Open WebUI Self-Hosted","notes":"The UI sends messages to the model endpoint selected for a conversation. Local Ollama or vLLM endpoints can keep inference on customer infrastructure; cloud APIs, embeddings, tools and plugins have separate data flows. The current license restricts branding removal in larger deployments, with small-deployment, permission and enterprise-license exceptions; review the actual terms. Open WebUI v0.13.4 replaces Direct Connections and Integrations with Tether and migrates image settings. Deployments using Terminals server connections require Terminals 0.4.0 or later; upgrading that server from 0.3.x requires manual migration. Open Terminal and Tether terminal connections are unaffected by this migration. Tether introduces user-device and local-command paths that require explicit trust review.","operations":"Customer runs application storage, authentication, provider configuration, updates and backups.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Installation options","url":"https://docs.openwebui.com/getting-started/quick-start/"},{"title":"Local and cloud model connections","url":"https://docs.openwebui.com/getting-started/quick-start/connect-a-provider/"},{"title":"Current license and branding conditions","url":"https://docs.openwebui.com/license/"},{"title":"Licensing and edition terms","url":"https://github.com/open-webui/open-webui/blob/main/LICENSE"},{"title":"Open WebUI v0.13.4 release","url":"https://github.com/open-webui/open-webui/releases/tag/v0.13.4"}],"url":"https://launchinyourcloud.com/directory/open-webui/","website":"https://openwebui.com/"},{"architecture":"OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates.","categories":["case-management"],"category":"Case management","categoryFit":{"case-management":"Open-source civil registration software for birth, death and related registration workflows."},"cloudEvidence":[{"clouds":["aws"],"notes":"OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"AWS EKS Terraform","url":"https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/amazon-web-services/README.md","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"GCP GKE Terraform","url":"https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/google-cloud-platform/README.md","vendorSupport":"not-assessed"},{"clouds":["hetzner"],"notes":"OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Hetzner K8s Terraform","url":"https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/hetzner-cloud/k8s_cluster.tf","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","gcp","hetzner"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/opencrvs/opencrvs-core/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/opencrvs/opencrvs-core"}],"summary":"The reviewed upstream contributor history includes rikukissa, euanmillar, makelicious, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee."},"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":"cloud-account","cloud":"hetzner","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Open-source civil registration software for birth, death and related registration workflows.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Versioned OpenCRVS v1.7 environment-specific baseline; current deployment/version sizing separate","source":"https://documentation.opencrvs.org/v1.7/setup/3.-installation/3.3-set-up-a-server-hosted-environment","status":"documented","summary":"The v1.7 guide lists production/staging at 8 CPUs/16 GB RAM with storage calculated from registration volume/attachments, versus development/QA at 4 CPUs/16 GB/320 GB. It specifies x86_64 Ubuntu 24.04 and separate backup requirements. Revalidate the selected release, clustering, throughput and recovery rather than applying this as an unrestricted current HA minimum."},"iac":{"artifactRef":"main (moving branch)","artifactUrl":"https://github.com/opencrvs/cloud-infrastructure/tree/main/terraform-templates/amazon-web-services","reviewed":"2026-11-19","scope":"Reviewed deployment source collection; application images and infrastructure components have separate versions","source":"https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/amazon-web-services/README.md","status":"documented","summary":"The reviewed source supplies deployment configuration for OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. Set organization-specific secrets, networking, storage and compatible image versions before use."},"licensePricing":{"reviewed":"2026-11-19","scope":"OpenCRVS; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://raw.githubusercontent.com/opencrvs/opencrvs-core/master/LICENSE","status":"documented","summary":"GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"sso":{"reviewed":"2026-11-21","scope":"OpenCRVS enterprise/user federation remains unconfirmed","source":"https://documentation.opencrvs.org/v1.7/setup/3.-installation/3.3-set-up-a-server-hosted-environment","status":"inconclusive","summary":"The server-hosting guide distinguishes production user two-factor codes, test accounts and government VPN access, but does not establish a supported external user SAML/OIDC login path. VPN/server identity and the application authentication service are separate; verify the selected current release and country configuration."}},"id":"opencrvs","infrastructure":["servers"],"infrastructureNotes":"OpenCRVS application and persistent services on the project's named-cloud Kubernetes infrastructure templates. 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/opencrvs/cloud-infrastructure/main/terraform-templates/amazon-web-services/README.md","https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/google-cloud-platform/README.md","https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/hetzner-cloud/k8s_cluster.tf"],"install":"Terraform; Kubernetes manifests","installMethods":["terraform","kubernetes"],"kind":"product","license":"GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://raw.githubusercontent.com/opencrvs/opencrvs-core/master/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"OpenCRVS","notes":"A country configuration, institutional identity, registration rules and integrations must be supplied. Infrastructure templates and the application release are separate, and public source does not confer authority to issue civil records.","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 EKS Terraform","url":"https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/amazon-web-services/README.md"},{"title":"GCP GKE Terraform","url":"https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/google-cloud-platform/README.md"},{"title":"Hetzner K8s Terraform","url":"https://raw.githubusercontent.com/opencrvs/cloud-infrastructure/main/terraform-templates/hetzner-cloud/k8s_cluster.tf"},{"title":"MPL-2.0","url":"https://raw.githubusercontent.com/opencrvs/opencrvs-core/master/LICENSE"},{"title":"Releases","url":"https://github.com/opencrvs/opencrvs-core/releases"}],"url":"https://launchinyourcloud.com/directory/opencrvs/","website":"https://www.opencrvs.org"},{"architecture":"Customer-operated application services and database","categories":["claims-management"],"category":"Claims management","categoryFit":{"claims-management":"Health-insurance claim submission, automated checks, medical review and reimbursement are documented; this is not a general property-and-casualty claims platform."},"cloudEvidence":[{"clouds":["aws","azure","gcp","digitalocean"],"notes":"The project wiki explicitly names AWS, Azure, Google Cloud and DigitalOcean for a VPS deployment of the Django/Gunicorn backend and Nginx frontend. Review the current distribution and modules, database and TLS configuration. Harden example settings such as debug mode, service users and credentials before handling production or health data.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"openIMIS production server deployment on named VPS providers","url":"https://openimis.atlassian.net/wiki/spaces/OP/pages/4228349954/Production%2BServer%2BopenIMIS%2BWith%2BGunicorn%2BAnd%2BNginx%2BOn%2BA%2BLinux%2BServer.","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp","digitalocean"],"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":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Self-hosted health-financing software supporting health-insurance claim submission, review and reimbursement.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Official modular openIMIS production minimum; workload and HA additions excluded","source":"https://openimis.atlassian.net/wiki/spaces/OP/pages/3771727873/MO1.+Server+Requirements","status":"documented","summary":"The official server requirements list a production minimum of two CPU cores, 8 GB RAM and 100 GB disk, with Linux as reference OS. This is a starting baseline, not a validated 100-user/1-TB HA deployment; separately size claims processing, attachments, database, replicas and backups."},"iac":{"artifactRef":"repository default branch (moving); pin matching component release tags","artifactUrl":"https://github.com/openimis/openimis-dist_dkr","reviewed":"2026-11-14","scope":"Modular openIMIS production Docker workflow; reconcile component and distribution releases","source":"https://openimis.atlassian.net/wiki/spaces/OP/pages/5314347015/Installation+Guide+Development+Production+Deployment","status":"documented","summary":"The project production guide links its Docker distribution and requires release-pinned database, backend and frontend image tags, strong secrets and disabled demo data. Development images and example administrator credentials are not the production configuration."},"licensePricing":{"reviewed":"2026-11-21","scope":"Moving upstream Docker distribution licence reviewed on this date","source":"https://github.com/openimis/openimis-dist_dkr/blob/develop/LICENSE.md","status":"documented","summary":"The reviewed Docker distribution grants GNU AGPLv3 rights and disclaims warranty. Individual services/modules and implementation or hosting agreements require separate licence and support review; no commercial-service entitlement follows from the distribution licence."},"sso":{"reviewed":"2026-11-21","scope":"openIMIS student-project integration versus the supported distribution; release inclusion unconfirmed","source":"https://openimis.atlassian.net/wiki/spaces/OP/pages/4661641223/Keycloak+-+Deployment+Guide","status":"inconclusive","summary":"The project wiki documents a tested 2025 Keycloak OIDC integration, but its deployment guide requires contributor forks and feature/keycloak-integration branches. This establishes a prototype path, not inclusion in the current supported distribution. Confirm a merged/released integration and release-specific configuration before relying on production SSO.","supportingSources":[{"title":"User login and role mapping","url":"https://openimis.atlassian.net/wiki/spaces/OP/pages/4661739527/Keycloak+-+User+Guide"}]}},"id":"openimis","infrastructure":["servers"],"infrastructureNotes":"The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://openimis.org/faq","https://github.com/openimis/openimis-dist_dkr"],"install":"Official Docker distribution and installation guide","installMethods":["docker"],"kind":"product","license":"Open-source; official distribution licensed under AGPL v3","licenseModel":"open-source","licenseModelNotes":"The official openIMIS distribution is licensed under AGPL v3 and is available for operators to deploy and maintain. Implementation, hosting and operational services may have separate costs and agreements.","licenseModelSources":["https://raw.githubusercontent.com/openimis/openimis-dist_dkr/develop/LICENSE.md","https://openimis.org/faq"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"openIMIS","notes":"A sector-specific claims product for health-financing and social-protection programs. Workflows include automated checks, medical review and reimbursement calculations. General property-and-casualty claims functionality was not established. Follow the official production and security guidance when implementing the Docker distribution.","operations":"Scheme operator and implementation partner host, configure and maintain the installation.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Self-hosting and implementation responsibilities","url":"https://openimis.org/faq"},{"title":"Claims workflows","url":"https://openimis.org/workflows-and-functionalities"},{"title":"Health-insurance solution","url":"https://openimis.org/health-insurance"},{"title":"Official Docker distribution","url":"https://github.com/openimis/openimis-dist_dkr"},{"title":"Docker installation guide","url":"https://openimis.atlassian.net/wiki/spaces/OP/pages/963182705/MO1.1+Install+the+modular+openIMIS+using+Docker"},{"title":"Licensing and edition terms","url":"https://raw.githubusercontent.com/openimis/openimis-dist_dkr/develop/LICENSE.md"}],"url":"https://launchinyourcloud.com/directory/openimis/","website":"https://openimis.org/"},{"advisories":[{"action":"Upgrade to 2.0.8 or later and retest authentication, token revocation, MCP consent, and impersonation.","conditions":"Applicability depends on enabled AI Context, MCP, SSO, impersonation, Airflow, and affected dependencies.","id":"openmetadata-2-0-8-security-maintenance","listingIds":["openmetadata"],"reviewed":"2026-11-18","scope":"Upstream 2.0.8 release notes; the individual fixes do not share one universal affected-version range.","source":"https://github.com/open-metadata/OpenMetadata/releases/tag/2.0.8-release","summary":"OpenMetadata 2.0.8 fixes incomplete authorization, revoked-token validity, SSO state and stale credentials, MCP consent, API-token sessions, impersonation boundaries, backend authorization, unsafe URL schemes, and security dependencies.","title":"OpenMetadata 2.0.8 security maintenance","type":"security-advisory"}],"architecture":"Customer-operated application, ingestion jobs, relational metadata database and search service","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Catalogs data assets, lineage, quality, governance and observability metadata across connected systems."},"cloudEvidence":[{"clouds":["aws"],"notes":"The official guide deploys OpenMetadata with Helm on a customer EKS cluster and documents AWS database and search dependencies.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"OpenMetadata on Amazon EKS","url":"https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/eks","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The official guide deploys OpenMetadata with Helm on a customer AKS cluster and documents Azure database and search dependencies.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"OpenMetadata on Azure Kubernetes Service","url":"https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/aks","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The official guide deploys OpenMetadata with Helm on GKE. It explicitly notes that GKE Autopilot is incompatible with the documented Elasticsearch configuration.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"OpenMetadata on Google Kubernetes Engine","url":"https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/gke","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-14","clouds":["aws","azure","gcp"],"communityAcceptance":{"reviewed":"2026-11-18","sources":[{"title":"OpenMetadata 2.0.8 release","url":"https://github.com/open-metadata/OpenMetadata/releases/tag/2.0.8-release"},{"title":"Upstream contributor history","url":"https://github.com/open-metadata/OpenMetadata/graphs/contributors"},{"title":"Community meetups and FDNY/Wix user spotlights","url":"https://open-metadata.org/community"}],"summary":"The project community publishes recurring meetups and user spotlights describing OpenMetadata use at the Fire Department of New York and Wix. Substantive contributions from multiple participants and the November 13, 2026 release 2.0.8 establish continuing maintenance, including authorization, token, SSO, consent, impersonation and dependency fixes. The spotlights establish project adoption without certifying a particular cloud or commercial edition."},"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 metadata catalog and data-governance platform deployed with customer-operated services.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Local Docker stack allocation; production and HA excluded","source":"https://docs.open-metadata.org/latest/quick-start/local-docker-deployment","status":"documented","summary":"The local Docker quickstart allocates at least 6 GiB memory and 4 vCPUs to Docker for the standalone stack. This is a local quickstart profile, not a production or HA minimum. External database, search, ingestion and concurrency need separate capacity planning."},"iac":{"artifactRef":"Select a release matching the chosen OpenMetadata version","artifactUrl":"https://github.com/open-metadata/openmetadata-helm-charts","reviewed":"2026-11-20","scope":"Official Kubernetes Helm distribution","source":"https://docs.open-metadata.org/latest/deployment/kubernetes","status":"documented","summary":"The project publishes Helm deployment for OpenMetadata and external database, search and ingestion dependencies. Ingress and network policies are optional and disabled by default. Choose compatible chart/application versions and configure authentication, secrets, persistence and production network controls."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/open-metadata/OpenMetadata/main/LICENSE","status":"documented","summary":"The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate."},"release":{"releasePublishedAt":"2026-11-13T05:02:47Z","releaseTag":"2.0.8-release","reviewed":"2026-11-18","scope":"Upstream OpenMetadata 2.0 release","source":"https://github.com/open-metadata/OpenMetadata/releases/tag/2.0.8-release","status":"documented","summary":"OpenMetadata 2.0.8-release, corresponding to product version 2.0.8, was published November 13, 2026. It contains material authorization, token, SSO, consent, impersonation, URL-scheme, and dependency security fixes."},"securityControls":{"reviewed":"2026-11-18","scope":"Upstream 2.0.8 release notes; the individual fixes do not share one universal affected-version range.","source":"https://github.com/open-metadata/OpenMetadata/releases/tag/2.0.8-release","status":"documented","summary":"Current advisory review: OpenMetadata 2.0.8 fixes incomplete authorization, revoked-token validity, SSO state and stale credentials, MCP consent, API-token sessions, impersonation boundaries, backend authorization, unsafe URL schemes, and security dependencies. Upgrade to 2.0.8 or later and retest authentication, token revocation, MCP consent, and impersonation."},"sso":{"availability":"available","reviewed":"2026-11-14","scope":"OpenMetadata 2.0.x server authentication","source":"https://docs.open-metadata.org/v2.0.x/deployment/security","status":"documented","summary":"The 2.0.x deployment guide lists Google, Okta, Auth0, Azure, Cognito, OneLogin and custom OIDC. It states that multiple authentication mechanisms cannot be used simultaneously."}},"id":"openmetadata","infrastructure":["servers"],"infrastructureNotes":"OpenMetadata runs persistent application and ingestion workloads backed by a relational database and search service. Managed dependencies do not make the application runtime serverless.","infrastructureReviewed":"2026-11-14","infrastructureSources":["https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/eks","https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/aks","https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/gke"],"install":"Official Helm charts on EKS, AKS or GKE","installMethods":["helm"],"kind":"product","license":"Apache License 2.0.","licenseModel":"open-source","licenseModelNotes":"The OpenMetadata repository is Apache-2.0 licensed. Collate's managed and enterprise services have separate commercial terms.","licenseModelSources":["https://github.com/open-metadata/OpenMetadata/blob/main/LICENSE"],"licenseReviewed":"2026-11-14","model":"Fully in your account","modelLabel":"Customer-operated","name":"OpenMetadata","notes":"This entry covers OpenMetadata self-hosting, not the managed Collate service. Production guides use provider-managed database and search options. GKE Autopilot is incompatible with the documented Elasticsearch dependency configuration. OpenMetadata 2.0.8 fixes authorization, revoked-token, SSO state and stale-credential, MCP consent, API-token session, impersonation, Airflow/backend authorization, unsafe URL-scheme, and dependency issues. Upgrade from 2.0.7 and retest identity and MCP flows.","operations":"Customer manages Kubernetes, database, search, ingestion orchestration, secrets, backups, scaling and upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Amazon EKS deployment","url":"https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/eks"},{"title":"Azure AKS deployment","url":"https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/aks"},{"title":"Google GKE deployment","url":"https://docs.open-metadata.org/v2.0.x/deployment/kubernetes/gke"},{"title":"Apache 2.0 license","url":"https://github.com/open-metadata/OpenMetadata/blob/main/LICENSE"},{"title":"Upstream contributor history","url":"https://github.com/open-metadata/OpenMetadata/graphs/contributors"},{"title":"Community meetups and FDNY/Wix user spotlights","url":"https://open-metadata.org/community"},{"title":"OpenMetadata 2.0.8 release","url":"https://github.com/open-metadata/OpenMetadata/releases/tag/2.0.8-release"}],"url":"https://launchinyourcloud.com/directory/openmetadata/","website":"https://open-metadata.org/"},{"architecture":"Customer-operated Kubernetes workloads use PostgreSQL for metadata, NATS for coordination and cloud object storage for Parquet telemetry.","categories":["observability"],"category":"Observability","categoryFit":{"observability":"Collects and analyzes application and infrastructure telemetry, with dashboards and alerts for operational monitoring."},"cloudEvidence":[{"clouds":["aws"],"notes":"The vendor walkthrough deploys the Enterprise application to the customer's EKS cluster, with S3 for telemetry and IAM permissions for storage access. The linked cluster sample pins Kubernetes 1.30; verify AWS availability and application compatibility and update that example version before use.","reviewed":"2026-11-20","sourceType":"vendor-documentation","title":"OpenObserve Enterprise on Amazon EKS","url":"https://openobserve.ai/docs/enterprise-setup/amazon-eks/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The vendor walkthrough deploys the Enterprise application to the customer's AKS cluster, with Azure Blob Storage, CloudNativePG and clustered NATS.","reviewed":"2026-11-20","sourceType":"vendor-documentation","title":"OpenObserve Enterprise on Azure AKS","url":"https://openobserve.ai/docs/enterprise-setup/azure-aks/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The vendor walkthrough deploys the Enterprise application to a Standard GKE cluster in the customer's Google Cloud project. The documented Cloud Storage configuration uses S3 interoperability and HMAC credentials.","reviewed":"2026-11-20","sourceType":"vendor-documentation","title":"OpenObserve Enterprise on Google GKE","url":"https://openobserve.ai/docs/enterprise-setup/google-gke/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-20","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":"Self-hosted observability platform for ingesting, searching and analyzing logs, metrics and traces.","diligence":{"airGap":{"reviewed":"2026-11-20","scope":"OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment","source":"https://openobserve.ai/docs/enterprise-setup/","status":"inconclusive","summary":"The reviewed sources do not establish a complete disconnected installation, update and licensing workflow. A telemetry opt-out alone does not establish air-gapped support; review registry, package, identity and optional external-service dependencies."},"commitments":{"reviewed":"2026-11-20","scope":"OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment","source":"https://openobserve.ai/docs/enterprise-setup/","status":"inconclusive","summary":"No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately."},"compliance":{"reviewed":"2026-11-20","scope":"OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment","source":"https://openobserve.ai/docs/enterprise-setup/","status":"inconclusive","summary":"No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities."},"cost":{"reviewed":"2026-11-20","scope":"OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment","source":"https://openobserve.ai/docs/enterprise-setup/","status":"inconclusive","summary":"No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend."},"footprint":{"reviewed":"2026-11-20","scope":"Reviewed AWS example, not a production workload benchmark","source":"https://openobserve.ai/docs/enterprise-setup/amazon-eks/","status":"documented","summary":"The vendor-linked EKS example provisions three m7i.xlarge nodes, with desired/minimum count 3 and maximum 6, alongside a managed EKS control plane. PostgreSQL, NATS, storage and enabled application roles also require sizing. This example is not a universal minimum or a measured fit for 100 users/1 TB. The linked EKS cluster example pins Kubernetes 1.30, which is absent from AWS’s currently available EKS versions; select an available version compatible with the application before using the example.","supportingSources":[{"title":"EKS example node configuration","url":"https://raw.githubusercontent.com/openobserve/eks-openobserve/main/o2-eks.yaml"},{"title":"Capacity planning inputs","url":"https://openobserve.ai/docs/enterprise-setup/capacity-planning/"},{"title":"Current EKS version availability and lifecycle","url":"https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html"}]},"iac":{"artifactRef":"openobserve 1.1.7; Enterprise image v1.1.2; sha256:394886d2c521acfc25012190d99c788814bf0a6f944674febd993ec8be40abe2","artifactUrl":"https://charts.openobserve.ai/openobserve-1.1.7.tgz","availability":"available","reviewed":"2026-11-20","scope":"Helm package and Enterprise image settings; not a complete production approval","source":"https://openobserve.ai/docs/enterprise-setup/","status":"documented","summary":"The inspected Enterprise-capable Helm package is openobserve 1.1.7. Its values pin the Enterprise image to v1.1.2; chart, application, report-server and optional AI images have separate versions. Install CloudNativePG and provider storage prerequisites separately.","supportingSources":[{"title":"Published chart index","url":"https://charts.openobserve.ai/index.yaml"}]},"licensePricing":{"reviewed":"2026-11-20","scope":"Enterprise software entitlement and documented usage limits, not cloud operating cost","source":"https://openobserve.ai/docs/enterprise-setup/license-and-pricing/","status":"documented","summary":"The Enterprise EULA and licensing guide describe a free tier up to 50 GB/day of ingestion, with registration/licensing above that level and feature-specific entitlements. The guide permits three monthly over-limit occurrences before restricting search. Infrastructure, operating labor and support are separate.","supportingSources":[{"title":"Enterprise EULA","url":"https://openobserve.ai/legal/enterprise-license/"}]},"marketplace":{"reviewed":"2026-11-20","scope":"OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment","source":"https://openobserve.ai/docs/enterprise-setup/","status":"inconclusive","summary":"The reviewed edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient."},"release":{"reviewed":"2026-11-20","scope":"Partial Enterprise package/image evidence; application publication and supported bundle unresolved","source":"https://charts.openobserve.ai/index.yaml","status":"inconclusive","summary":"Chart 1.1.7 pins o2cr.ai/openobserve/openobserve-enterprise:v1.1.2. This establishes a reviewed deployable image reference, but not its publication timestamp, a current Enterprise release/support designation or parity with public OSS/prerelease tags. Request the applicable Enterprise release notes and compatibility matrix.","supportingSources":[{"title":"Inspected Enterprise-capable chart","url":"https://charts.openobserve.ai/openobserve-1.1.7.tgz"}]},"scim":{"reviewed":"2026-11-20","scope":"OpenObserve Enterprise Self-Hosted: reviewed customer-cloud deployment","source":"https://openobserve.ai/docs/enterprise-setup/","status":"inconclusive","summary":"The reviewed sources do not establish a SCIM endpoint and supported user/group lifecycle for this edition. SSO and just-in-time account creation are not SCIM evidence."},"securityControls":{"reviewed":"2026-11-20","scope":"Configurable Enterprise controls, not an independent deployment attestation","source":"https://openobserve.ai/docs/enterprise-setup/","status":"documented","summary":"Enterprise documentation describes OpenFGA-based RBAC, Dex SSO and configurable secure authentication cookies. The cloud guides scope storage credentials through provider IAM. Operators must configure these controls and review telemetry, external connectors and optional AI/reporting services.","supportingSources":[{"title":"Enterprise access-control features","url":"https://openobserve.ai/docs/features/enterprise/"},{"title":"Configuration and telemetry opt-out","url":"https://openobserve.ai/docs/administration/configuration/environment-variables/"}]},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Configured self-hosted Enterprise authentication and licensed features","source":"https://openobserve.ai/docs/user-guide/account-administration/identity-and-access-management/sso/","status":"documented","summary":"Enterprise supports SSO through Dex with external identity providers. Configure the Dex client, redirect/callback URLs and provider connector; the EKS guide enables Dex explicitly. The feature is not available in the separate OSS edition."}},"id":"openobserve-enterprise-self-hosted","infrastructure":["servers"],"infrastructureNotes":"Application services and dependencies run in Kubernetes. The provider-specific examples use object storage and persistent PostgreSQL and NATS workloads.","infrastructureReviewed":"2026-11-20","infrastructureSources":["https://openobserve.ai/docs/enterprise-setup/"],"install":"Install the Enterprise Helm chart and CloudNativePG operator, then configure the cluster, object storage and application settings for the selected provider.","installMethods":["helm"],"kind":"product","license":"Enterprise End User License Agreement. The vendor publishes a free tier through 50 GB/day of ingestion, with a license required above that threshold.","licenseModel":"commercial-only","licenseModelNotes":"The reviewed Enterprise build is proprietary under the vendor EULA. The separate open-source distribution uses AGPL-3.0.","licenseModelSources":["https://openobserve.ai/legal/enterprise-license/","https://openobserve.ai/docs/enterprise-setup/license-and-pricing/","https://openobserve.ai/downloads/"],"licenseReviewed":"2026-11-20","model":"Fully in your account","modelLabel":"Customer-operated","name":"OpenObserve Enterprise Self-Hosted","notes":"The documented paths cover Enterprise Edition. Feature access depends on the enterprise entitlement. OpenObserve documents outbound product usage reporting and a ZO_TELEMETRY opt-out. Plan for separate recovery of telemetry objects and PostgreSQL metadata. The reviewed chart 1.1.7 pins Enterprise image v1.1.2; do not substitute an OSS or release-candidate tag by name alone. Dex is optional and must be configured. The EKS node example is a sizing starting point, not an HA workload benchmark. The linked EKS cluster example pins Kubernetes 1.30, which is absent from AWS’s currently available EKS versions; select an available version compatible with the application before using the example.","operations":"The customer runs the cluster, configures storage credentials and ingestion endpoints, sizes components, manages backups and retention, and applies chart and application upgrades.","publisher":false,"reviewed":"2026-11-20","sources":[{"title":"Enterprise installation and architecture","url":"https://openobserve.ai/docs/enterprise-setup/"},{"title":"Enterprise EULA","url":"https://openobserve.ai/legal/enterprise-license/"},{"title":"Enterprise licensing, limits and feature entitlements","url":"https://openobserve.ai/docs/enterprise-setup/license-and-pricing/"},{"title":"Edition comparison and download channels","url":"https://openobserve.ai/downloads/"},{"title":"Application configuration and usage telemetry","url":"https://openobserve.ai/docs/administration/configuration/environment-variables/"},{"title":"OpenObserve Enterprise on Amazon EKS","url":"https://openobserve.ai/docs/enterprise-setup/amazon-eks/"},{"title":"OpenObserve Enterprise on Azure AKS","url":"https://openobserve.ai/docs/enterprise-setup/azure-aks/"},{"title":"OpenObserve Enterprise on Google GKE","url":"https://openobserve.ai/docs/enterprise-setup/google-gke/"},{"title":"Published chart index","url":"https://charts.openobserve.ai/index.yaml"},{"title":"Buyer evidence: sso","url":"https://openobserve.ai/docs/user-guide/account-administration/identity-and-access-management/sso/"},{"title":"Enterprise access-control features","url":"https://openobserve.ai/docs/features/enterprise/"},{"title":"EKS example node configuration","url":"https://raw.githubusercontent.com/openobserve/eks-openobserve/main/o2-eks.yaml"},{"title":"Capacity planning inputs","url":"https://openobserve.ai/docs/enterprise-setup/capacity-planning/"},{"title":"Inspected Enterprise-capable chart","url":"https://charts.openobserve.ai/openobserve-1.1.7.tgz"},{"title":"Current EKS version availability and lifecycle","url":"https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html"}],"url":"https://launchinyourcloud.com/directory/openobserve-enterprise-self-hosted/","website":"https://openobserve.ai/"},{"architecture":"Customer-operated Access Server VM or container with Admin Web UI, VPN data plane and optional multi-node clustering","categories":["identity-access-management"],"category":"Identity \u0026 access management","categoryFit":{"identity-access-management":"Provides a self-hosted business VPN and policy-controlled remote or site-to-site network access server."},"cloudEvidence":[{"clouds":["aws"],"notes":"Official documentation covers CloudFormation resources in the signed-in AWS account, Linux or Docker on customer AWS infrastructure, and Marketplace bring-your-own-license or pay-as-you-go options.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Access Server AWS customer-account deployment","url":"https://openvpn.net/as-docs/v3/aws/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The official bring-your-own-license guide creates the Access Server VM, network interface, public IP and network security group in the selected Azure subscription and resource group.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Access Server Azure Marketplace VM","url":"https://openvpn.net/as-docs/v3/azure/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The official guide deploys the self-hosted Access Server instance into the customer's selected Google Cloud project and VPC.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Access Server Google Cloud Marketplace deployment","url":"https://openvpn.net/as-docs/v3/google-cloud/","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":"Self-hosted business VPN and network-access server deployed in the customer's cloud account.","diligence":{"airGap":{"reviewed":"2026-11-19","scope":"OpenVPN Access Server: selected customer-operated edition","source":"https://openvpn.net/as-docs/v3/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":"OpenVPN Access Server: selected customer-operated edition","source":"https://openvpn.net/as-docs/v3/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":"OpenVPN Access Server: selected customer-operated edition","source":"https://openvpn.net/as-docs/installation-overview/","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":"OpenVPN Access Server: selected customer-operated edition","source":"https://openvpn.net/as-docs/v3/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":"OpenVPN Access Server: selected customer-operated edition","source":"https://openvpn.net/as-docs/v3/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":"docker.io/openvpn/openvpn-as:3.2.4-f3c295a7-Ubuntu26; sha256:b5091b2b5dbebd302c1a61fe8154453e3ff84bd9df7894e530d45e22c76dcdf8","artifactUrl":"https://hub.docker.com/r/openvpn/openvpn-as/tags?name=3.2.4-f3c295a7-Ubuntu26","availability":"available","reviewed":"2026-11-19","scope":"Official commercial Access Server container, separate from the AWS/Azure/GCP marketplace AMIs","source":"https://openvpn.net/as-docs/v3/docker/","status":"documented","summary":"OpenVPN documents its official Access Server Docker image as an additional installation option. The registry identifies tag 3.2.4-f3c295a7-Ubuntu26 and its manifest digest. Persist /openvpn and review the TUN device and NET_ADMIN/MKNOD capabilities. This container reference does not establish the version of any provider marketplace VM image.","supportingSources":[{"title":"Published tag and manifest digest","url":"https://hub.docker.com/v2/repositories/openvpn/openvpn-as/tags?page_size=5"}]},"licensePricing":{"availability":"edition-dependent","reviewed":"2026-11-19","scope":"OpenVPN Access Server: selected customer-operated edition","source":"https://openvpn.net/as-docs/subscription/","status":"documented","summary":"Access Server supports commercial subscription, fixed and marketplace licensing, while unlicensed mode is capped at two connections. Price the selected connection entitlement and HA nodes separately from cloud infrastructure.","supportingSources":[{"title":"Access Server pricing","url":"https://openvpn.net/access-server/pricing/"}]},"marketplace":{"availability":"available","reviewed":"2026-11-19","scope":"OpenVPN Access Server: selected customer-operated edition","source":"https://openvpn.net/as-docs/v3/aws/","status":"documented","summary":"OpenVPN documents Access Server Marketplace deployment for AWS, Azure and Google Cloud, with provider-specific bring-your-own-license, pay-as-you-go or fixed licensing choices. Confirm the exact offer and connection entitlement.","supportingSources":[{"title":"Azure Marketplace deployment","url":"https://openvpn.net/as-docs/v3/azure/"},{"title":"Google Cloud Marketplace deployment","url":"https://openvpn.net/as-docs/v3/google-cloud/"}]},"release":{"reviewed":"2026-11-19","scope":"OpenVPN Access Server: selected customer-operated edition","source":"https://hub.docker.com/v2/repositories/openvpn/openvpn-as/tags?page_size=5","status":"inconclusive","summary":"The official registry identifies Docker image 3.2.4-f3c295a7-Ubuntu26 and its manifest digest. Registry update time is not an application release-publication timestamp, and provider VM images are separately versioned. Confirm the intended application build, marketplace image and upgrade path before treating them as one release snapshot."},"scim":{"reviewed":"2026-11-19","scope":"OpenVPN Access Server: selected customer-operated edition","source":"https://openvpn.net/as-docs/installation-overview/","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":"OpenVPN Access Server: selected customer-operated edition","source":"https://openvpn.net/as-docs/installation-overview/","status":"documented","summary":"Access Server is deployed as a customer-controlled VPN data plane and administration service with customer-managed routing, identity, certificates and network exposure. The reviewed cloud guides require explicit security-group or firewall configuration; validate TLS, MFA, logging and administrator access for the chosen license and topology."},"sso":{"reviewed":"2026-11-19","scope":"OpenVPN Access Server: selected customer-operated edition","source":"https://openvpn.net/as-docs/installation-overview/","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":"openvpn-access-server","infrastructure":["servers"],"infrastructureNotes":"The full Access Server application runs on customer-operated compute; marketplace images and CloudFormation deployments create customer-cloud VMs and networking.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://openvpn.net/as-docs/installation-overview/"],"install":"Official cloud marketplace image or AWS CloudFormation stack, or package or container on a supported Linux VM","installMethods":["cloudformation","vm-image","package","docker"],"kind":"product","license":"Commercial subscription, fixed and cloud-marketplace licenses; unlicensed mode is limited to two connections.","licenseModel":"commercial-only","licenseModelNotes":"Access Server is commercially licensed even though it permits two connections without a paid key; OpenVPN Community Edition is a separate product.","licenseModelSources":["https://openvpn.net/as-docs/subscription/","https://openvpn.net/access-server/pricing/"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"OpenVPN Access Server","notes":"This entry covers OpenVPN Access Server, not CloudConnexa or OpenVPN Community Edition. Bring-your-own-license, pay-as-you-go and fixed marketplace entitlements differ by provider.","operations":"Customer manages compute, routing, network exposure, identity integration, certificates, upgrades, backups and availability.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"OpenVPN Access Server installation overview","url":"https://openvpn.net/as-docs/installation-overview/"},{"title":"OpenVPN Access Server on AWS","url":"https://openvpn.net/as-docs/v3/aws/"},{"title":"OpenVPN Access Server on Azure","url":"https://openvpn.net/as-docs/v3/azure/"},{"title":"OpenVPN Access Server on Google Cloud","url":"https://openvpn.net/as-docs/v3/google-cloud/"},{"title":"OpenVPN Access Server subscription licensing","url":"https://openvpn.net/as-docs/subscription/"},{"title":"Buyer evidence: iac","url":"https://openvpn.net/as-docs/v3/docker/"},{"title":"Reviewed deployment artifact reference","url":"https://hub.docker.com/r/openvpn/openvpn-as/tags?name=3.2.4-f3c295a7-Ubuntu26"},{"title":"Published tag and manifest digest","url":"https://hub.docker.com/v2/repositories/openvpn/openvpn-as/tags?page_size=5"},{"title":"Access Server pricing","url":"https://openvpn.net/access-server/pricing/"}],"url":"https://launchinyourcloud.com/directory/openvpn-access-server/","website":"https://openvpn.net/access-server/"},{"architecture":"EKS or AKS application containers, PostgreSQL, object storage and workload identity.","categories":["policy-procedure-management"],"category":"Policy \u0026 procedure management","categoryFit":{"policy-procedure-management":"Customer-operated compliance-documentation and security-plan platform installed with the vendor's platform installer or Helm."},"cloudEvidence":[{"clouds":["aws"],"notes":"EKS or AKS application containers, PostgreSQL, object storage and workload identity. AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"AWS EKS via PPI","url":"https://docs.paramify.com/deploy-ppi-eks.html","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"EKS or AKS application containers, PostgreSQL, object storage and workload identity. AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Azure AKS via Helm","url":"https://docs.paramify.com/deploy-helm-azure.html","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"EKS or AKS application containers, PostgreSQL, object storage and workload identity. AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"# Paramify configuration\n#\n# Example install:\n#   helm registry login registry.paramify.com --username paramify@mycompan","url":"https://raw.githubusercontent.com/paramify/support/main/gcp/values-gke.yaml.example","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":"Customer-operated compliance-documentation and security-plan platform installed with the vendor's platform installer or Helm.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Paramify complete production footprint remains unconfirmed","source":"https://docs.paramify.com/deploy-ppi-eks.html","status":"inconclusive","summary":"The reviewed installation examples identify Kubernetes, PostgreSQL and object storage, while an example Node heap option configures one process. They do not establish complete production CPU/RAM/storage capacity; document generation workers, database, cluster overhead and HA need workload sizing."},"iac":{"artifactRef":"main (moving branch)","artifactUrl":"https://github.com/paramify/support/blob/main/gcp/gcp-paramify-gke-infra.tf","reviewed":"2026-11-19","scope":"Paramify deployment example; review the full linked installation instructions","source":"https://github.com/paramify/support/blob/main/gcp/gcp-paramify-gke-infra.tf","status":"documented","summary":"The reviewed source supplies deployment configuration for EKS or AKS application containers, PostgreSQL, object storage and workload identity. Set organization-specific secrets, networking, storage and compatible image versions before use."},"licensePricing":{"reviewed":"2026-11-19","scope":"Selected self-hosted commercial product; contract confirmation remains necessary","source":"https://www.paramify.com/legal/terms-and-conditions","status":"inconclusive","summary":"Deployment requires a Paramify licence and registry credentials, but the public SaaS access agreement does not establish the self-hosted software order, price or support scope."},"sso":{"availability":"available","reviewed":"2026-11-21","scope":"Paramify self-hosted documented provider login; planned SAML excluded","source":"https://docs.paramify.com/login-options.html","status":"documented","summary":"The vendor explicitly supports Google, Microsoft and Okta login in self-hosted environments, with provider/client setup guides and application-local permissions. The overview still describes SAML as planned; do not treat that date or email magic links as confirmation of current SAML capability.","supportingSources":[{"title":"Okta configuration","url":"https://docs.paramify.com/login-okta.html"}]}},"id":"paramify","infrastructure":["servers"],"infrastructureNotes":"EKS or AKS application containers, PostgreSQL, object storage and workload identity. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://docs.paramify.com/deploy-ppi-eks.html","https://docs.paramify.com/deploy-helm-azure.html","https://raw.githubusercontent.com/paramify/support/main/gcp/values-gke.yaml.example"],"install":"Helm / Kubernetes operator; Kubernetes manifests","installMethods":["helm","kubernetes"],"kind":"product","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.paramify.com/legal/terms-and-conditions","https://www.paramify.com/legal/access-and-services-agreement"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Paramify","notes":"AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.","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 EKS via PPI","url":"https://docs.paramify.com/deploy-ppi-eks.html"},{"title":"Azure AKS via Helm","url":"https://docs.paramify.com/deploy-helm-azure.html"},{"title":"# Paramify configuration\n#\n# Example install:\n#   helm registry login registry.paramify.com --username paramify@mycompan","url":"https://raw.githubusercontent.com/paramify/support/main/gcp/values-gke.yaml.example"},{"title":"GCP GKE Terraform","url":"https://github.com/paramify/support/blob/main/gcp/gcp-paramify-gke-infra.tf"},{"title":"Deployment Options","url":"https://docs.paramify.com/deployment-options.html"},{"title":"Paramify Policies \u0026 SSPs","url":"https://www.paramify.com/"},{"title":"Terms \u0026 Conditions","url":"https://www.paramify.com/legal/terms-and-conditions"},{"title":"Access \u0026 Services Agreement","url":"https://www.paramify.com/legal/access-and-services-agreement"},{"title":"Support Commits (`2026-10-29`)","url":"https://github.com/paramify/support/commits/main.atom"},{"title":"Legacy Release Notes","url":"https://docs.paramify.com/release-notes.html"}],"url":"https://launchinyourcloud.com/directory/paramify/","website":"https://github.com/paramify/support"},{"architecture":"Customer-operated Node.js backend with database and selected file/push integrations","categories":["backend-platforms"],"category":"Backend platforms","categoryFit":{"backend-platforms":"Application backend with data APIs, user authentication, access rules and server-side Cloud Code; database and file adapters are separately configured."},"cloudEvidence":[{"clouds":["aws","azure","gcp","digitalocean"],"deploymentBoundaries":{"digitalocean":"not-assessed"},"notes":"The upstream guide explicitly lists AWS, Google Cloud, Azure and DigitalOcean as hosts for the Parse Server application and provides installation guidance. This compatibility statement is separate from the DigitalOcean Spaces file adapter; select current Node.js/database versions and secure the deployed server.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Parse Server cloud hosting options","url":"https://docs.parseplatform.org/parse-server/guide/","vendorSupport":"not-assessed"},{"clouds":["heroku"],"notes":"The upstream guide documents the Parse Server application on Heroku with MongoDB Atlas, including project configuration and validation. The application and database are in separate customer-controlled services; verify database network access, current runtime versions, secrets and production security.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Parse Server deployment on Heroku","url":"https://docs.parseplatform.org/parse-server/guide/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp","digitalocean","heroku"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Current stable and LTS releases","url":"https://github.com/parse-community/parse-server/releases"},{"title":"Community contribution process","url":"https://github.com/parse-community/parse-server/blob/alpha/CONTRIBUTING.md"},{"title":"Long-running community governance discussion","url":"https://community.parseplatform.org/t/official-discord-server/1506"}],"summary":"Parse Community maintains an established public project, contributor review process and community forum. The current release stream includes November 2026 stable and LTS maintenance."},"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":"heroku","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Node.js application backend for data APIs, users, permissions and server-side application logic.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Published upstream runtime/dependency scope; complete production sizing remains unconfirmed","source":"https://github.com/parse-community/parse-server/blob/8.6.123/README.md","status":"inconclusive","summary":"The published server identifies Node.js plus a supported database and configurable storage/live-query services, but not a workload-specific whole-system CPU/RAM/storage minimum. Size request/query rates, files, live subscriptions, database indexes and replication separately. A managed Parse hosting plan or tutorial allocation is not a self-hosted HA capacity guarantee."},"iac":{"artifactRef":"repository default branch (moving; select matching application release)","artifactUrl":"https://github.com/parse-community/parse-server","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://github.com/parse-community/parse-server","status":"documented","summary":"The official server repository documents a Node.js application/package with a separately configured database. The server, dashboard and optional adapters have separate configuration and lifecycle; they are not one cloud appliance."},"licensePricing":{"reviewed":"2026-11-20","scope":"Parse Server 8.6.123 upstream application; not a managed Parse hosting plan; software terms only, excluding infrastructure and operations","source":"https://github.com/parse-community/parse-server/blob/8.6.123/LICENSE","status":"documented","summary":"The reviewed upstream application uses Apache License 2.0. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote."},"release":{"releasePublishedAt":"2026-11-09T22:42:42Z","releaseTag":"8.6.123","reviewed":"2026-11-15","scope":"Upstream parse-community/parse-server release record; commercial editions and deployment packages may differ","source":"https://github.com/parse-community/parse-server/releases/tag/8.6.123","status":"documented","summary":"The publisher-designated GitHub release checked was 8.6.123, published 2026-11-09. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. The November 14 advisory GHSA-43rg-r2xr-q686 says Parse Server 8 is unpatched; this historical stable-release snapshot is not a secure-version recommendation.","supportingSources":[{"title":"Parse Server auth-data disclosure advisory","url":"https://github.com/parse-community/parse-server/security/advisories/GHSA-43rg-r2xr-q686"}]},"securityControls":{"reviewed":"2026-11-15","scope":"Auth-data login response advisory reviewed November 15; not an arbitrary-user disclosure or a recommendation to adopt a prerelease without compatibility review","source":"https://github.com/parse-community/parse-server/security/advisories/GHSA-43rg-r2xr-q686","status":"documented","summary":"GHSA-43rg-r2xr-q686 can expose protected fields or hidden auth-adapter data in the logging-in user object, including MFA secrets and recovery codes. The advisory affects versions before 9.12.0-alpha.3 and identifies that prerelease as patched; Parse Server 8 is unpatched and no workaround is known. It requires the user auth data or applicable session-token conditions; master/maintenance-key requests are unaffected."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Published application-user federation adapter, distinct from separately deployed management dashboards","source":"https://github.com/parse-community/parse-server/blob/8.6.123/src/Adapters/Auth/keycloak.js","status":"documented","summary":"Parse Server supports external application-user authentication adapters; published 8.6.123 includes a Keycloak adapter that verifies provider tokens and returned user attributes. Configure the adapter/provider and map application users and permissions. This is an app-user backend capability, not proof of administrator SSO in Parse Dashboard, and does not establish SCIM.","supportingSources":[{"title":"Official third-party authentication guide","url":"https://github.com/parse-community/docs/blob/gh-pages/_includes/parse-server/third-party-auth.md"}]}},"id":"parse-server","infrastructure":["servers"],"infrastructureNotes":"Customer-operated Node.js backend with database and selected file/push integrations. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.parseplatform.org/parse-server/guide/"],"install":"Install the upstream Node.js package and configure a supported MongoDB or PostgreSQL backend; run standalone or in an Express application.","installMethods":["package","source"],"kind":"product","license":"Apache License 2.0 for upstream Parse Server.","licenseModel":"open-source","licenseModelNotes":"Apache License 2.0 for upstream Parse Server. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.","licenseModelSources":["https://raw.githubusercontent.com/parse-community/parse-server/alpha/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Parse Server","notes":"Cloud Code is code executed in the server environment, not evidence of a vendor-operated cloud dependency. External storage, push-notification providers and third-party adapters have their own boundaries and licenses. GHSA-43rg-r2xr-q686 affects Parse Server versions before 9.12.0-alpha.3: creating a user with an existing user's auth data can return protected fields and hidden auth-adapter data, including MFA secrets and recovery codes. The advisory concerns the logging-in user's own object and requires that user's auth data or an applicable session token; it is not an arbitrary-user disclosure. Requests using the master or maintenance key are unaffected. There is no known workaround; Parse Server 8 is not patched, and the first published patched version is the 9.12.0-alpha.3 prerelease.","operations":"Customer manages Node services, database, class/object permissions, master keys, storage adapters, backups and upgrades.","publisher":false,"reviewed":"2026-11-15","sources":[{"title":"Official installation and runtime","url":"https://docs.parseplatform.org/parse-server/guide/"},{"title":"Upstream project and capabilities","url":"https://github.com/parse-community/parse-server"},{"title":"Current upstream license","url":"https://raw.githubusercontent.com/parse-community/parse-server/alpha/LICENSE"},{"title":"Security advisory GHSA-43rg-r2xr-q686","url":"https://github.com/parse-community/parse-server/security/advisories/GHSA-43rg-r2xr-q686"}],"url":"https://launchinyourcloud.com/directory/parse-server/","website":"https://parseplatform.org/"},{"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":"P4 Server on a customer VM with persistent metadata and depot storage; replication and edge services are optional separate topology choices.","categories":["devops"],"category":"DevOps","categoryFit":{"devops":"Provides centralized version control and a high-volume repository for source code, binaries and digital assets used by development teams."},"cloudEvidence":[{"clouds":["aws"],"notes":"Perforce documents a customer AWS deployment using EC2 and a CloudFormation quickstart.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"P4 Server on AWS","url":"https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-aws.html","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Perforce documents launching P4 Server in the customer's own Azure cloud instance through Marketplace.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"P4 Server on Azure","url":"https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-azure.html","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Perforce documents deployment into the customer's selected Google Cloud project.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"P4 Server on Google Cloud","url":"https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-gcp.html","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"Perforce documents a P4 Server Droplet in the customer's DigitalOcean account.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"P4 Server on DigitalOcean","url":"https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-digitalocean.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-18","clouds":["aws","azure","gcp","digitalocean"],"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"}],"description":"Commercial centralized version-control server deployed from Perforce's cloud quickstarts into customer infrastructure.","diligence":{"airGap":{"availability":"available","reviewed":"2026-11-18","scope":"Self-managed P4 with staged SDP/server/client artifacts and valid local licence files; external SSO services are not made offline automatically","source":"https://workshop.perforce.com/files/guest/perforce_software/sdp/main/Server/Unix/p4/common/bin/upgrade.sh?v=25","status":"documented","summary":"Perforce’s SDP upgrade tool explicitly covers air-gapped servers: stage the binaries from the locations reported by get_helix_binaries.sh -n. P4 installs a local licence file; request it outside the isolated network and transfer it securely. Commit/central servers and any replica intended for failover need appropriate licences bound to their host identity. Stage client/SDP updates and use reachable internal identity, DNS, backup and support procedures.","supportingSources":[{"title":"Install and reload the local licence file","url":"https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/install.tips.release.html"},{"title":"Replica and cloud-host licence requirements","url":"https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/request-license.html"}]},"commitments":{"availability":"unavailable","reviewed":"2026-11-18","scope":"Externally billed software licence for the exact reviewed public Perforce P4 CFT offer; not all provider spend or future private offers","source":"https://aws.amazon.com/marketplace/pp/prodview-nw7wxff425so4","status":"documented","summary":"The reviewed Perforce P4 CFT offer explicitly requires buying the software licence outside AWS Marketplace. That externally billed licence is not a software charge on the AWS Marketplace invoice for this offer. This answers the licence-billing route only; eligible EC2/EBS spend or a separately negotiated private offer still requires the buyer’s AWS agreement and seller order terms.","supportingSources":[{"title":"AWS BYOL pricing boundary","url":"https://docs.aws.amazon.com/marketplace/latest/userguide/BYOL-pricing.html"},{"title":"Commitment qualification remains product/agreement-specific","url":"https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html"}]},"compliance":{"reviewed":"2026-11-18","scope":"Perforce P4 Server (Helix Core): selected customer-operated edition","source":"https://trust.perforce.com/resources","status":"inconclusive","summary":"Perforce’s Trust Center separates assurance resources by product, including Delphix, BlazeMeter, Puppet and QAC/Klocwork. Those gated reports and corporate badges do not identify a current P4 Server/Authentication Service assurance boundary. Request the applicable report/certificate, entity, period and customer-control scope; do not transfer another Perforce product’s report to P4."},"cost":{"estimate":{"currency":"USD","exclusions":["Separate P4 Authentication Service/SSO components","Additional edges/replicas, archive growth and provisioned IOPS/throughput","Backup and restore testing","Networking, IPv4 and all data transfer","Software/image licence and support","Operating labor, monitoring, taxes and discounts"],"kind":"partial-infrastructure","period":"month","region":"AWS us-east-1","rows":[{"description":"2 Linux m6i.2xlarge VMs × 730 h; editorial capacity choice, not a vendor 100-user benchmark","id":"compute","quantity":1460,"rate":0.384},{"description":"2 × (1,000 GB depot archive + 100 GB metadata/journals + 30 GB boot) gp3; base performance only","id":"storage","quantity":2260,"rate":0.08},{"description":"Unpriced: any separately selected data/storage tier beyond the local volumes; this illustration does not require an external database service","id":"database","quantity":1,"rate":""},{"description":"Unpriced: Backup capacity, retention, restore testing and recovery services","id":"backup","quantity":1,"rate":""},{"description":"Unpriced: Load balancers, NAT/endpoints, IPv4 and all transfer, including cross-AZ replication","id":"network","quantity":1,"rate":""},{"description":"Unpriced: Software/image licences, commercial support and entitlement for failover","id":"license","quantity":1,"rate":""},{"description":"Unpriced: Operation, patching, monitoring and incident/recovery labor","id":"labor","quantity":1,"rate":""}],"workload":"100 internal users; 1 TB (1,000 GB) logical data; HA target; average usage unmeasured; 730 h/month. Only the explicitly identified layer is priced; see scope and excluded components."},"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":"Editorial P4 compute/storage layer on two AZs; configure journal/archive replication, licensing, failover and recovery tests. Metadata allowance and VM size are assumptions to validate against depot file count and throughput, not a vendor sizing guarantee.","source":"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","status":"inconclusive","summary":"Illustrative priced infrastructure subtotal: USD 741.44/month. Two 8-vCPU/32-GiB VMs model a primary and licensed failover standby. Each has 1,000 GB archive, 100 GB metadata/journals and 30 GB boot gp3 capacity (2,260 GB total). P4 licences, file/revision-driven sizing, backup and replication transfer are unpriced. This is not a complete operating-cost estimate or validated capacity/SLA claim.","supportingSources":[{"title":"Product topology/sizing basis","url":"https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/failover.html"},{"title":"Current AWS us-east-1 gp3 capacity example","url":"https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html"},{"title":"EBS performance and charging qualifications","url":"https://aws.amazon.com/ebs/pricing/"},{"title":"Single-server memory planning factors","url":"https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/install.memory.html"},{"title":"Primary and failover licence requirements","url":"https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/request-license.html"}]},"footprint":{"reviewed":"2026-11-18","scope":"Perforce P4 Server (Helix Core): selected customer-operated edition","source":"https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/install.memory.html","status":"documented","summary":"The server administration guide gives memory planning factors of 64 MB per licensed user and 1.5 KB per depot file for a single server, with additional memory useful for filesystem cache. Depot file count, revisions, concurrency and replication matter. The quickstart’s t3.small default is not an HA design for 100 users.","supportingSources":[{"title":"Small-team AWS quickstart","url":"https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-aws.html"}]},"iac":{"reviewed":"2026-11-18","scope":"Perforce P4 Server (Helix Core): selected customer-operated edition","source":"https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-aws.html","status":"documented","summary":"The AWS quickstart launches the Perforce Marketplace CloudFormation package and configures EC2, SSH/P4 security groups and separate encrypted EBS data volumes. It defaults to small-team capacity. Review IAM and source-IP restrictions, then record the resolved template and server build in the deployment inventory.","supportingSources":[{"title":"Exact CFT offer and package version","url":"https://aws.amazon.com/marketplace/pp/prodview-nw7wxff425so4"}]},"licensePricing":{"reviewed":"2026-11-18","scope":"Perforce P4 Server (Helix Core): selected customer-operated edition","source":"https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/admin-plan-deployment.html","status":"documented","summary":"P4 is proprietary. The published free threshold is up to five users and fewer than twenty workspaces. Larger self-managed installations require a commercial quote; hosted P4 Cloud per-user pricing is a different product. The reviewed AWS offer bills its software licence outside AWS Marketplace.","supportingSources":[{"title":"External licence billing in the exact AWS offer","url":"https://aws.amazon.com/marketplace/pp/prodview-nw7wxff425so4"},{"title":"Separate failover-server licensing requirements","url":"https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/request-license.html"}]},"marketplace":{"availability":"available","offers":[{"cloud":"aws","delivery":"CloudFormation Template (CFT)","id":"prodview-nw7wxff425so4","publisher":"Perforce","url":"https://aws.amazon.com/marketplace/pp/prodview-nw7wxff425so4","version":"2026.1.0"}],"reviewed":"2026-11-18","scope":"Perforce P4 Server (Helix Core): selected customer-operated edition","source":"https://aws.amazon.com/marketplace/pp/prodview-nw7wxff425so4","status":"documented","summary":"Perforce publishes P4 (Self-Managed) on AWS Marketplace as a CloudFormation delivery, package 2026.1.0, on Rocky Linux. The offer is a deployment package; the P4 server patch level and purchased licence must be checked separately."},"release":{"releasePublishedOn":"2026-11-12","releaseTag":"2026.1/3141402","reviewed":"2026-11-18","scope":"Perforce P4 Server (Helix Core): selected customer-operated edition","source":"https://www.perforce.com/perforce/doc.current/user/relnotes.txt","status":"documented","summary":"The server release notes identify P4 2026.1 Patch 4 as 2026.1/3141402, dated November 12, 2026. Check p4d -V against the bugfix change level. This is distinct from the Marketplace package 2026.1.0 and Authentication Service’s own release line."},"scim":{"availability":"available","reviewed":"2026-11-18","scope":"Perforce P4 Server (Helix Core): selected customer-operated edition","source":"https://help.perforce.com/helix-core/integrations-plugins/helix-auth-svc/current/Content/HAS/provisioning.html","status":"documented","summary":"P4 Authentication Service exposes SCIM v2 at /scim/v2 for user/group provisioning, protected by a bearer token and a P4 super-user ticket. The documented implementation explicitly does not support deprovisioning; user renames are rejected by default. Do not rely on it for automated offboarding."},"securityControls":{"reviewed":"2026-11-18","scope":"Perforce P4 Server (Helix Core): selected customer-operated edition","source":"https://www.perforce.com/perforce/doc.current/user/relnotes.txt","status":"documented","summary":"P4 2026.1 changes security defaults, including raising a lower security level to 4 during p4d -xu. Other configurables keep explicitly set values on upgrade; new defaults are not proof that an existing deployment is hardened. Review protections, TLS, authentication extension privileges and the upgrade procedure.","supportingSources":[{"title":"SCIM endpoint and privileged ticket requirements","url":"https://help.perforce.com/helix-core/integrations-plugins/helix-auth-svc/current/Content/HAS/provisioning.html"}]},"sso":{"availability":"available","reviewed":"2026-11-18","scope":"Perforce P4 Server (Helix Core): selected customer-operated edition","source":"https://help.perforce.com/helix-core/integrations-plugins/helix-auth-svc/current/Content/HAS/overview-of-has.html","status":"documented","summary":"P4 Authentication Service integrates SAML and OIDC identity providers with P4 through the authentication extension and supported clients. Deploy and secure the service and extension separately. Logging out of P4 does not necessarily terminate the IdP session."}},"id":"perforce-p4-server","infrastructure":["servers"],"infrastructureNotes":"The quickstarts launch a persistent P4 Server VM and attached depot/metadata storage in the customer's cloud.","infrastructureReviewed":"2026-11-18","infrastructureSources":["https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/admin-plan-deployment.html"],"install":"Perforce quickstart images for AWS, Azure, Google Cloud or DigitalOcean; AWS also uses CloudFormation","installMethods":["cloudformation","vm-image","platform-template"],"kind":"product","license":"Proprietary P4 license; free within the published small-team limits, with commercial licensing and support above them.","licenseModel":"commercial-only","licenseModelNotes":"P4 is proprietary software. Perforce publishes a free-use threshold, but larger deployments and support require commercial licensing.","licenseModelSources":["https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/admin-plan-deployment.html"],"licenseReviewed":"2026-11-18","model":"Fully in your account","modelLabel":"Customer-operated","name":"Perforce P4 Server (Helix Core)","notes":"Helix Core is being renamed P4 in current documentation. The quickstarts establish single-server deployment, not an HA or disaster-recovery design. Confirm current user/workspace entitlements before production use.","operations":"Customer manages VM and OS security, depot and metadata storage, accounts, firewall, backups, logs, upgrades, capacity and any replication or edge topology.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Plan a P4 Server cloud deployment","url":"https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/admin-plan-deployment.html"},{"title":"Deploy P4 Server on AWS","url":"https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-aws.html"},{"title":"Deploy P4 Server on Azure","url":"https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-azure.html"},{"title":"Deploy P4 Server on Google Cloud","url":"https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-gcp.html"},{"title":"Deploy P4 Server on DigitalOcean","url":"https://help.perforce.com/helix-core/quickstart/current/Content/quickstart/deploy-digitalocean.html"}],"url":"https://launchinyourcloud.com/directory/perforce-p4-server/","website":"https://www.perforce.com/products/helix-core"},{"advisories":[{"action":"Check the installed runtime against Philter 4.0.1 dependency corrections and update the image or affected libraries through the documented process.","conditions":"Exposure depends on the actual Ubuntu/JVM libraries and configured document/API processing.","id":"2026-11-19-philter-runtime","listingIds":["philter"],"reviewed":"2026-11-19","scope":"The Philter 4.0.1 release identifies corrected dependencies; no blanket affected range is inferred for independently patched systems.","source":"https://github.com/philterd/philter/releases/tag/4.0.1","summary":"Philter 4.0.1 updates Brotli and Jackson-related dependencies.","title":"Philter runtime and library corrections","type":"security-advisory"}],"architecture":"Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application.","categories":["freedom-of-information","document-management"],"category":"Freedom of information \u0026 public access","categoryFit":{"document-management":"Open-source API that identifies and redacts sensitive information in text and PDFs.","freedom-of-information":"Open-source API that identifies and redacts sensitive information in text and PDFs."},"cloudEvidence":[{"clouds":["aws"],"notes":"Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations.","reviewed":"2026-11-19","sourceType":"marketplace-offer","title":"AWS Marketplace AMI","url":"https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations.","reviewed":"2026-11-19","sourceType":"marketplace-offer","title":"Azure Marketplace VM","url":"https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Philter: Open Source, Self-Hosted PII \u0026 PHI Redaction API","url":"https://www.philterd.ai/philter/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","azure","gcp"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/philterd/philter/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/philterd/philter"}],"summary":"The reviewed upstream contributor history includes jzonthemtn, AzazelSensei, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-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 API that identifies and redacts sensitive information in text and PDFs.","diligence":{"commitments":{"availability":"unavailable","reviewed":"2026-11-19","scope":"philterdllc1687189098111.philter public offer, reviewed 2026-11-19","source":"https://catalogapi.azure.com/offers/philterdllc1687189098111.philter?api-version=2021-10-01\u0026market=US\u0026language=en","status":"documented","summary":"The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement."},"footprint":{"reviewed":"2026-11-20","scope":"Self-hosted Philter application and selected processing/cache dependencies; marketplace VM size is not a universal minimum","source":"https://github.com/philterd/philter/blob/4.0.1/README.md","status":"inconclusive","summary":"The reviewed runtime and configuration documentation does not establish a quantitative whole-host CPU/RAM/storage floor for the selected redaction workload. Document rendering, OCR/models, request concurrency, cache and durable data can change memory and storage needs; per-document limits are not host sizing.","supportingSources":[{"title":"Runtime settings and processing limits","url":"https://github.com/philterd/philter/blob/main/docs/docs/settings.md"}]},"iac":{"artifactRef":"philterd/philter:4.0.1; upstream documentation states there is no latest tag","artifactUrl":"https://hub.docker.com/r/philterd/philter","reviewed":"2026-11-20","scope":"Philter 4.0.1 upstream runtime packaging; not a complete provider infrastructure or HA template","source":"https://github.com/philterd/philter/blob/4.0.1/README.md","status":"documented","summary":"The upstream README publishes versioned philterd/philter Docker images, including 4.0.1, and a Compose recipe that builds the checked-out source. Use the released image for a release-specific deployment, configure API credentials and persistence/cache services, and distinguish source builds from the marketplace package."},"licensePricing":{"reviewed":"2026-11-19","scope":"Philter by Philterd (Self-Hosted / Cloud Marketplace); software terms only, excluding cloud charges, labour and separately licensed services","source":"https://raw.githubusercontent.com/philterd/philter/main/LICENSE.txt","status":"documented","summary":"Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"marketplace":{"availability":"available","offers":[{"cloud":"azure","delivery":"Virtual machine","id":"philterdllc1687189098111.philter","publisher":"Philterd, LLC","url":"https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter"},{"cloud":"aws","delivery":"Amazon Machine Image (AMI)","id":"prodview-y32h6usoum7zy","publisher":"Philterd","url":"https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy","version":"4.0.1"}],"reviewed":"2026-11-19","scope":"Philter by Philterd (Self-Hosted / Cloud Marketplace) selected Azure public offer","source":"https://catalogapi.azure.com/offers/philterdllc1687189098111.philter?api-version=2021-10-01\u0026market=US\u0026language=en","status":"documented","summary":"The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from Philterd, LLC. The publisher package and upstream application have separate maintenance. The reviewed AWS offer delivers Amazon Machine Image (AMI) from Philterd. Its package version is 4.0.1; verify the contained application and required entitlements separately.","supportingSources":[{"title":"AWS delivery and package version","url":"https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy"}]},"release":{"releasePublishedAt":"2026-11-03T13:30:54Z","releaseTag":"4.0.1","reviewed":"2026-11-19","scope":"Philter by Philterd (Self-Hosted / Cloud Marketplace) upstream application; verify compatibility with the selected package","source":"https://github.com/philterd/philter/releases/tag/4.0.1","status":"documented","summary":"Reviewed upstream 4.0.1 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence."},"sso":{"reviewed":"2026-11-20","scope":"Philter redaction API authentication; separate UI, cloud marketplace subscription and customer portal sign-in are distinct surfaces","source":"https://github.com/philterd/philter/blob/main/docs/docs/sign_in_security.md","status":"inconclusive","summary":"Philter documents API keys and optional password sign-in for its own users, while its separate UI is described as in development. The reviewed material does not establish an external SAML/OIDC user-federation path for the self-hosted redaction service. API bearer/session keys are not sufficient SSO evidence."}},"id":"philter","infrastructure":["servers"],"infrastructureNotes":"Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy","https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter","https://www.philterd.ai/philter/"],"install":"VM image","installMethods":["vm-image"],"kind":"product","license":"Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://raw.githubusercontent.com/philterd/philter/main/LICENSE.txt","https://philterd.ai/pricing/","https://d7umqicpi7263.cloudfront.net/eula/dKWyRA8OFGG7dZHQQ11-sVYBd8p0ZdR4ZLHVrytHdhs"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Philter by Philterd (Self-Hosted / Cloud Marketplace)","notes":"Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations. Check the installed runtime against Philter 4.0.1 dependency corrections and update the image or affected libraries through the documented process.","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 Marketplace AMI","url":"https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy"},{"title":"Azure Marketplace VM","url":"https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter"},{"title":"Philter: Open Source, Self-Hosted PII \u0026 PHI Redaction API","url":"https://www.philterd.ai/philter/"},{"title":"Apache-2.0 LICENSE.txt","url":"https://raw.githubusercontent.com/philterd/philter/main/LICENSE.txt"},{"title":"Philterd Pricing","url":"https://philterd.ai/pricing/"},{"title":"AWS Marketplace EULA PDF","url":"https://d7umqicpi7263.cloudfront.net/eula/dKWyRA8OFGG7dZHQQ11-sVYBd8p0ZdR4ZLHVrytHdhs"},{"title":"GitHub Releases","url":"https://github.com/philterd/philter/releases"},{"title":"Philter runtime and library corrections","url":"https://github.com/philterd/philter/releases/tag/4.0.1"}],"url":"https://launchinyourcloud.com/directory/philter/","website":"https://www.philterd.ai"},{"advisories":[{"action":"Avoid credentials in repository URLs, restrict logs, rotate exposed tokens and validate the eventual stable fixed release before production use.","conditions":"Credential-bearing repository URLs, DEBUG logging and the UI v2 login redirect path determine exposure.","disclosedOn":"2026-11-19","id":"prefect-3-9-4-dev6-credential-log-exposure","listingIds":["prefect"],"reviewed":"2026-11-19","scope":"Prefect GitRepository logging and UI v2 redirects; no stable remediated release was available when reviewed.","source":"https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6","summary":"Prefect 3.9.4.dev6 stops GitRepository URL credentials from appearing in DEBUG logs and repr output and adds same-origin UI redirect validation.","supportingSources":[{"title":"Credential-log fix","url":"https://github.com/PrefectHQ/prefect/pull/23969"},{"title":"Same-origin redirect validation","url":"https://github.com/PrefectHQ/prefect/pull/23980"}],"title":"Prefect GitRepository credential-log fix is prerelease-only","type":"security-advisory"}],"architecture":"Customer-operated API/UI, background services, database and execution workers","categories":["workflow-orchestration"],"category":"Workflow orchestration","categoryFit":{"workflow-orchestration":"Python flow/task orchestration with retries, scheduling, state tracking and workers that execute deployments on configured infrastructure."},"cloudEvidence":[{"clouds":["northflank"],"notes":"Northflank documents the Prefect server/API/UI, PostgreSQL and worker in a customer project, with flow runs launched as separate jobs. This covers the self-hosted control plane, not a worker connected to Prefect Cloud. The hosted platform manages underlying infrastructure; customer project ownership does not imply ownership of its underlying hyperscaler account.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"Self-hosted Prefect server and worker on Northflank","url":"https://northflank.com/guides/how-to-deploy-prefect","vendorSupport":"not-assessed"},{"clouds":["aws","azure","gcp"],"notes":"The provider guide installs the self-hosted Prefect server/API/UI, PostgreSQL and worker and explicitly offers AWS, Google Cloud or Azure through Northflank Bring Your Own Cloud. These hyperscaler badges require the BYOC deployment option and its commercial/access prerequisites; a default Northflank hosted project does not run in the customer hyperscaler account. This is a Northflank deployment recipe, not a claim of Prefect vendor-managed BYOC.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"Prefect deployment through Northflank BYOC","url":"https://northflank.com/guides/how-to-deploy-prefect","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["northflank","aws","azure","gcp"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Release history and named contributor participation","url":"https://github.com/PrefectHQ/prefect/releases"},{"title":"Public project and self-hosted server usage","url":"https://github.com/PrefectHQ/prefect"}],"summary":"The official release history records November 2026 maintenance, multiple named contributors and first-time contributions across successive releases."},"deploymentPaths":[{"boundary":"platform-workspace","cloud":"northflank","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Self-hosted workflow server and Python framework for resilient task and data pipelines.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Current multi-server topology; numeric production/worker sizing remains unconfirmed","source":"https://docs.prefect.io/v3/advanced/self-hosted","status":"inconclusive","summary":"The scaling guide specifies multiple API/background-service instances, PostgreSQL and persistent Redis coordination, but no numeric whole-stack CPU/RAM/storage minimum. Workflow workers and execution infrastructure are separate. Size run/event rate, queues, database history/retention and failover before estimating the requested HA workload."},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://raw.githubusercontent.com/PrefectHQ/prefect/main/docs/v3/advanced/self-hosted.mdx","status":"documented","summary":"The self-hosted scaling guide supplies Compose with multiple API/background services, PostgreSQL, Redis and migrations. This scaled architecture is distinct from a single local SQLite instance and requires coordinated versions and persistence."},"licensePricing":{"reviewed":"2026-11-20","scope":"Prefect 3.9.3 upstream Server; not a Prefect Cloud subscription; software terms only, excluding infrastructure and operations","source":"https://github.com/PrefectHQ/prefect/blob/3.9.3/LICENSE","status":"documented","summary":"The reviewed upstream application uses Apache License 2.0. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote."},"release":{"releasePublishedAt":"2026-11-13T19:24:07Z","releaseTag":"3.9.3","reviewed":"2026-11-19","scope":"Upstream PrefectHQ/prefect release record; commercial editions and deployment packages may differ","source":"https://github.com/PrefectHQ/prefect/releases/tag/3.9.3","status":"documented","summary":"The publisher-designated GitHub release checked was 3.9.3, published 2026-11-13. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. The prerelease 3.9.4.dev6 contains credential-log and same-origin redirect hardening; it is not a stable upgrade target.","supportingSources":[{"title":"Prerelease-only security fixes","url":"https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6"}]},"securityControls":{"reviewed":"2026-11-19","scope":"Prefect GitRepository logging and UI v2 redirect behavior; remediation was prerelease-only when reviewed","source":"https://github.com/PrefectHQ/prefect/pull/23969","status":"documented","summary":"Prefect 3.9.4.dev6 prevents GitRepository credentials embedded in URLs from appearing in DEBUG logs or repr output and validates same-origin UI v2 post-login redirects. No stable fixed release was available at review time; avoid credential-bearing URLs, protect logs and rotate exposed tokens.","supportingSources":[{"title":"3.9.4.dev6 prerelease","url":"https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6"},{"title":"Same-origin redirect hardening","url":"https://github.com/PrefectHQ/prefect/pull/23980"}]},"sso":{"reviewed":"2026-11-20","scope":"Prefect Server security settings; external user federation remains unconfirmed","source":"https://docs.prefect.io/v3/advanced/security-settings","status":"inconclusive","summary":"The self-hosted security guide documents shared Basic authentication, proxy configuration and client headers, not a specific SAML/OIDC user federation integration. Prefect Cloud API keys and Cloud SSO are separate. An identity-aware proxy design would need verified UI/API coverage, individual account mapping and client/worker authorization."}},"id":"prefect","infrastructure":["servers"],"infrastructureNotes":"Customer-operated API/UI, background services, database and execution workers. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://raw.githubusercontent.com/PrefectHQ/prefect/main/docs/v3/advanced/self-hosted.mdx"],"install":"Install Prefect and start its server; use the documented PostgreSQL/Redis architecture when scaling multiple API and background-service instances.","installMethods":["other"],"kind":"product","license":"Apache License 2.0 for upstream Prefect. Prefect Cloud is a separate managed offering.","licenseModel":"open-source","licenseModelNotes":"Apache License 2.0 for upstream Prefect. Prefect Cloud is a separate managed offering. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.","licenseModelSources":["https://raw.githubusercontent.com/PrefectHQ/prefect/main/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Prefect Server","notes":"Configure clients and workers against the self-hosted API. Task code and worker integrations can still use external compute and services. Self-hosted control-plane capacity is separate from any serverless execution target. Prefect 3.9.4.dev6 is a prerelease that stops GitRepository from exposing URL-embedded credentials in DEBUG logs and repr output and adds same-origin validation for UI v2 post-login redirects. No stable fixed release was published at review time. Avoid credential-bearing repository URLs, restrict DEBUG logs, rotate exposed tokens and validate the eventual stable release before production rollout.","operations":"Customer manages server services, database, queue/cache, worker pools, secrets, access controls and upgrades.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Official installation and runtime","url":"https://raw.githubusercontent.com/PrefectHQ/prefect/main/docs/v3/advanced/self-hosted.mdx"},{"title":"Upstream project and capabilities","url":"https://github.com/PrefectHQ/prefect"},{"title":"Current upstream license","url":"https://raw.githubusercontent.com/PrefectHQ/prefect/main/LICENSE"},{"title":"Self-hosted startup and workflow functionality","url":"https://raw.githubusercontent.com/PrefectHQ/prefect/main/README.md"},{"title":"Prefect deployment through Northflank BYOC","url":"https://northflank.com/guides/how-to-deploy-prefect"},{"title":"Prefect 3.9.4.dev6 prerelease","url":"https://github.com/PrefectHQ/prefect/releases/tag/3.9.4.dev6"},{"title":"GitRepository credential-log fix","url":"https://github.com/PrefectHQ/prefect/pull/23969"},{"title":"UI v2 redirect hardening","url":"https://github.com/PrefectHQ/prefect/pull/23980"}],"url":"https://launchinyourcloud.com/directory/prefect/","website":"https://www.prefect.io/"},{"advisories":[{"action":"Obtain and deploy the entitled API image containing the documented trust-store update, restart the service and verify its image/trust configuration. Review the separate OpenSearch 2.x-to-3.7.0 installer migration before redeployment.","conditions":"The running API image and effective certificate trust store determine applicability. Pinning public installer source does not establish the private service image version.","id":"pulumi-self-hosted-october-2026-ca-trust-update","listingIds":["pulumi-cloud-self-hosted"],"reviewed":"2026-11-19","scope":"The licensed self-hosted API-service update described in the October 2026 changelog; an immutable patched image ID and exact release day are not published there.","source":"https://www.pulumi.com/docs/administration/self-hosting/changelog/","summary":"The public October changelog removes trust in eight compromised eMudhra intermediate certificates and identifies a Go 1.27.3 API-service rebuild.","title":"Pulumi self-hosted API October 2026 trust-store update","type":"security-advisory"}],"architecture":"Customer-operated Pulumi Cloud frontend and API with customer networking, database, object storage and container infrastructure","categories":["devops"],"category":"DevOps","categoryFit":{"devops":"Provides a customer-operated Pulumi control plane for infrastructure delivery, state, policy, access and deployment workflows."},"cloudEvidence":[{"applicableEdition":"Pulumi Enterprise Self-Hosted","clouds":["aws"],"notes":"Pulumi lists production self-hosting options for AWS ECS and EKS and links official deployment programs that create the application in the customer's AWS environment.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Pulumi Cloud Self-Hosted on AWS ECS or EKS","url":"https://www.pulumi.com/docs/administration/self-hosting/","vendorSupport":"not-assessed"},{"applicableEdition":"Pulumi Enterprise Self-Hosted","clouds":["azure"],"notes":"The official deployment option installs the full self-hosted Pulumi Cloud service on customer Azure AKS and supporting Azure resources.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Pulumi Cloud Self-Hosted on Azure AKS","url":"https://www.pulumi.com/docs/administration/self-hosting/deployment-options/aks-hosted/","vendorSupport":"not-assessed"},{"applicableEdition":"Pulumi Enterprise Self-Hosted","clouds":["gcp"],"notes":"The official deployment option installs the full self-hosted Pulumi Cloud service on customer Google GKE and supporting Google Cloud resources.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Pulumi Cloud Self-Hosted on Google GKE","url":"https://www.pulumi.com/docs/administration/self-hosting/deployment-options/gke-hosted/","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":"Enterprise infrastructure-delivery control plane deployed and operated in the customer's cloud account.","diligence":{"airGap":{"availability":"available","reviewed":"2026-11-19","scope":"Configured self-hosted Enterprise installation with staged licensed images and internal artifact mirrors","source":"https://www.pulumi.com/docs/administration/self-hosting/airgapped/","status":"documented","summary":"Pulumi documents an air-gapped self-hosted Enterprise deployment using an entitled licence key and service images, internal infrastructure, and mirrors for CLI/SDK packages, provider plugins and container images. Configure all tools to use the mirrors and review identity and cloud-API connectivity for the selected workflows."},"commitments":{"reviewed":"2026-11-19","scope":"Pulumi Cloud Self-Hosted: selected customer-operated edition","source":"https://www.pulumi.com/docs/administration/self-hosting/","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":"Pulumi Cloud Self-Hosted: selected customer-operated edition","source":"https://www.pulumi.com/docs/administration/self-hosting/","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":"Pulumi Cloud Self-Hosted: selected customer-operated edition","source":"https://www.pulumi.com/docs/administration/self-hosting/","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":"Self-hosted Enterprise production component baseline; size every selected service and workload separately","source":"https://www.pulumi.com/docs/administration/self-hosting/operations/compute-sizing/","status":"documented","summary":"The production baseline specifies two or more API instances across two or more AZs, at least 2 vCPU and 4 GB RAM per API instance, a 0.5-vCPU/512-Mi console, a MySQL writer/reader setup with 20 GB+ SSD, and 200 GB+ object storage. Add migrations, networking, backups and workload growth; this is a vendor baseline, not a validated 100-user/1-TB cost or performance model."},"iac":{"artifactRef":"e7a8007335f692d5d343a16d121057bcabc2bab3; installer source commit, not a Pulumi Cloud application version","artifactUrl":"https://github.com/pulumi/pulumi-self-hosted-installers/tree/e7a8007335f692d5d343a16d121057bcabc2bab3","availability":"available","reviewed":"2026-11-19","scope":"Public self-hosted infrastructure/application deployment programs; not a licence to the commercial service images","source":"https://www.pulumi.com/docs/administration/self-hosting/deployment-options/ecs-hosted/","status":"documented","summary":"The official installer repository supplies ECS, EKS, AKS and GKE deployment programs. The reviewed repository commit is pinned independently of the licensed API/console images and licence key, which must be obtained from Pulumi. Pin compatible service images and review installer-specific changes before applying the code."},"licensePricing":{"availability":"edition-dependent","reviewed":"2026-11-19","scope":"Pulumi Cloud Self-Hosted: selected customer-operated edition","source":"https://www.pulumi.com/docs/administration/get-started/choose-edition/","status":"documented","summary":"Commercial Pulumi Enterprise subscription with the Self-Hosted deployment option Infrastructure, support and operating labor are separate unless the order states otherwise."},"marketplace":{"reviewed":"2026-11-19","scope":"Pulumi Cloud Self-Hosted: selected customer-operated edition","source":"https://www.pulumi.com/docs/administration/self-hosting/","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":{"reviewed":"2026-11-19","scope":"Licensed self-hosted service image release snapshot, distinct from the Pulumi CLI or public installer commit","source":"https://www.pulumi.com/docs/administration/self-hosting/changelog/","status":"inconclusive","summary":"The public self-hosted changelog documents an October 2026 API trust-store update and a September OpenSearch 3.7.0 installer change, but does not identify one immutable licensed API/console image bundle and precise release timestamp. The public installer commit is separately pinned; obtain the entitled service image versions/digests and upgrade matrix from Pulumi."},"scim":{"reviewed":"2026-11-19","scope":"Pulumi Cloud Self-Hosted: selected customer-operated edition","source":"https://www.pulumi.com/docs/administration/self-hosting/","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.","supportingSources":[{"title":"Self-hosted feature parity checked; no specific SCIM endpoint established","url":"https://www.pulumi.com/docs/administration/self-hosting/feature-parity/"}]},"securityControls":{"reviewed":"2026-11-19","scope":"Documented self-hosted Enterprise controls and configuration responsibilities; compliance attestations are separate","source":"https://www.pulumi.com/docs/administration/self-hosting/operations/security-hardening/","status":"documented","summary":"The hardening guide specifies private application/database subnets, restricted inter-tier traffic, configurable CIDR ingress allowlists, encrypted database/object storage, encrypted Pulumi configuration secrets and TLS between clients, console, API and MySQL. These are controls the customer configures, not proof that an installation is hardened or independently attested."},"sso":{"availability":"available","reviewed":"2026-11-19","scope":"Licensed self-hosted Pulumi Enterprise console authentication; not an assertion of SCIM provisioning","source":"https://www.pulumi.com/docs/administration/self-hosting/saml-sso/","status":"documented","summary":"Self-hosted Pulumi Enterprise supports SAML SSO. Configure the API service’s signing/validation key pair, enable SAML_SSO_ENABLED on the console, and complete the IdP and organization setup. The guide requires restarting the affected services after configuration changes."}},"id":"pulumi-cloud-self-hosted","infrastructure":["servers"],"infrastructureNotes":"The application runs on customer container compute and uses customer database, object storage, networking and key-management services.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://www.pulumi.com/docs/administration/self-hosting/","https://www.pulumi.com/docs/administration/self-hosting/deployment-options/ecs-hosted/"],"install":"Official Pulumi programs for ECS or EKS, AKS or GKE","installMethods":["pulumi","kubernetes"],"kind":"platform","license":"Commercial Pulumi Enterprise subscription with the Self-Hosted deployment option","licenseModel":"commercial-only","licenseModelNotes":"The Self-Hosted option is available with Pulumi Enterprise; Pulumi's open-source CLI and SDK do not by themselves license this control plane.","licenseModelSources":["https://www.pulumi.com/docs/administration/get-started/choose-edition/","https://www.pulumi.com/docs/administration/self-hosting/"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Pulumi Cloud Self-Hosted","notes":"Self-hosting is an Enterprise-only option. The installers bootstrap with a separate state backend because the self-hosted Pulumi service does not yet exist during its own deployment. Validate the supported database, storage and identity configuration for the selected release. The public October changelog removes trust in eight compromised eMudhra intermediate certificates and identifies a Go 1.27.3 API-service rebuild. Obtain and deploy the entitled API image containing the documented trust-store update, restart the service and verify its image/trust configuration. Review the separate OpenSearch 2.x-to-3.7.0 installer migration before redeployment.","operations":"Customer operates backups, uptime, infrastructure and upgrades; Pulumi supplies the licensed application and deployment tooling.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Pulumi Cloud self-hosting overview","url":"https://www.pulumi.com/docs/administration/self-hosting/"},{"title":"Pulumi edition comparison","url":"https://www.pulumi.com/docs/administration/get-started/choose-edition/"},{"title":"Self-hosted Pulumi Cloud on ECS","url":"https://www.pulumi.com/docs/administration/self-hosting/deployment-options/ecs-hosted/"},{"title":"Self-hosted Pulumi Cloud on EKS","url":"https://www.pulumi.com/docs/administration/self-hosting/deployment-options/eks-hosted/"},{"title":"Self-hosted Pulumi Cloud on AKS","url":"https://www.pulumi.com/docs/administration/self-hosting/deployment-options/aks-hosted/"},{"title":"Self-hosted Pulumi Cloud on GKE","url":"https://www.pulumi.com/docs/administration/self-hosting/deployment-options/gke-hosted/"},{"title":"Buyer evidence: sso","url":"https://www.pulumi.com/docs/administration/self-hosting/saml-sso/"},{"title":"Self-hosted feature parity checked; no specific SCIM endpoint established","url":"https://www.pulumi.com/docs/administration/self-hosting/feature-parity/"},{"title":"Buyer evidence: securityControls","url":"https://www.pulumi.com/docs/administration/self-hosting/operations/security-hardening/"},{"title":"Buyer evidence: airGap","url":"https://www.pulumi.com/docs/administration/self-hosting/airgapped/"},{"title":"Reviewed deployment artifact reference","url":"https://github.com/pulumi/pulumi-self-hosted-installers/tree/e7a8007335f692d5d343a16d121057bcabc2bab3"},{"title":"Buyer evidence: footprint","url":"https://www.pulumi.com/docs/administration/self-hosting/operations/compute-sizing/"},{"title":"Buyer evidence: release","url":"https://www.pulumi.com/docs/administration/self-hosting/changelog/"}],"url":"https://launchinyourcloud.com/directory/pulumi-cloud-self-hosted/","website":"https://www.pulumi.com/product/pulumi-cloud/"},{"architecture":"Customer-operated vector-search server and persistent collection storage","categories":["databases-vector","ai-tools"],"category":"Databases \u0026 vector","categoryFit":{"ai-tools":"Self-hosted vector database for semantic retrieval and AI application data.","databases-vector":"Vector database for similarity and hybrid retrieval in AI applications. Model inference and embedding creation are separate from the core database deployment."},"cloudEvidence":[{"clouds":["gcp"],"notes":"Google documents provisioning a regional GKE cluster and installing Qdrant with Helm and persistent disks. The customer operates the database cluster; this is separate from Qdrant Cloud and its separately offered Hybrid Cloud service.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"Self-operated Qdrant cluster on Google Kubernetes Engine","url":"https://docs.cloud.google.com/kubernetes-engine/docs/tutorials/deploy-qdrant","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Self-hosted vector database for semantic retrieval and AI application data.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Vector/workload-specific sizing methodology; numeric minimum for the requested deployment unresolved","source":"https://qdrant.tech/documentation/capacity-planning/","status":"inconclusive","summary":"The capacity guide models vectors, dimensions/datatype, HNSW, payload indexes, memory tiers and replication, with headroom and representative-data testing. It does not establish a single minimum from a user count or total source-data size. Determine vector counts/dimensions, retention, replicas and query/ingestion rates, then use the sizing calculator and benchmark."},"iac":{"artifactRef":"select a released Qdrant image tag","artifactUrl":"https://hub.docker.com/r/qdrant/qdrant","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://qdrant.tech/documentation/quickstart/","status":"documented","summary":"The local quickstart identifies the official Qdrant Docker server and persistent storage. A local evaluation command is not a hardened production installation; configure network access, authentication and durable storage."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/qdrant/qdrant/master/LICENSE","status":"documented","summary":"The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate."},"release":{"releasePublishedAt":"2026-11-13T12:30:26Z","releaseTag":"v1.20.1","reviewed":"2026-11-14","scope":"Upstream qdrant/qdrant release record; commercial editions and deployment packages may differ","source":"https://github.com/qdrant/qdrant/releases/tag/v1.20.1","status":"documented","summary":"The publisher-designated GitHub release checked was v1.20.1, published 2026-11-13. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package."},"sso":{"reviewed":"2026-11-20","scope":"Self-hosted core authentication; federated user sign-on unresolved","source":"https://qdrant.tech/documentation/security/","status":"inconclusive","summary":"The self-hosted core security guide documents API keys, including scoped access keys, TLS and audit controls. It does not establish a native SAML/OIDC login flow or a reviewed external-IdP integration for this edition. Qdrant Cloud console identity is a separate service and is not transferred to the core database."}},"id":"qdrant","infrastructure":["servers"],"infrastructureNotes":"The database runs as a persistent server/container process with collection storage; production capacity, replicas and backup storage must be planned. Embedding-model compute is separate.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://qdrant.tech/documentation/quickstart/"],"install":"Official Docker image for local/server deployment; production storage, access controls and scaling require configuration.","installMethods":["docker"],"kind":"product","license":"Apache 2.0 for the upstream database; managed cloud offerings and support have separate commercial terms.","licenseModel":"open-source","licenseModelNotes":"The listed upstream self-hosted database is Apache-2.0 licensed. Separate managed hosting or support does not change this database classification; this entry does not classify a proprietary managed-cloud control plane.","licenseModelSources":["https://github.com/qdrant/qdrant/blob/master/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Qdrant Self-Hosted","notes":"The local quickstart is an installation starting point, not a secured production configuration. Applications can supply their own vectors or use separately configured embedding models. External embedding APIs and hosted inference can receive source data even when the database is self-hosted; local FastEmbed is a documented alternative. This entry excludes Qdrant Cloud hosting. Qdrant 1.20.1, released November 13, 2026, prevents collection-scoped JWTs from viewing snapshot telemetry for collections they cannot access; operators using scoped JWTs should upgrade.","operations":"Customer manages persistence, backups, access controls, upgrades and any distributed-cluster operations.","publisher":false,"reviewed":"2026-11-14","sources":[{"title":"Local/server Docker quickstart","url":"https://qdrant.tech/documentation/quickstart/"},{"title":"Embedding options, including local FastEmbed","url":"https://qdrant.tech/documentation/embeddings/"},{"title":"Apache 2.0 license","url":"https://github.com/qdrant/qdrant/blob/master/LICENSE"},{"title":"Qdrant 1.20.1 security and maintenance release","url":"https://github.com/qdrant/qdrant/releases/tag/v1.20.1"}],"url":"https://launchinyourcloud.com/directory/qdrant/","website":"https://qdrant.tech/"},{"architecture":"Single- or multi-node Windows services with repository database, shared storage, identity and load-balancing dependencies","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Provides customer-operated business intelligence, associative analytics, dashboards and governed data applications."},"cloudEvidence":[{"clouds":["aws"],"notes":"Qlik documents preparing customer Amazon EC2 Windows infrastructure and installing Qlik Sense Enterprise on Windows.","reviewed":"2026-11-15","sourceType":"vendor-documentation","title":"Qlik Sense Enterprise on AWS","url":"https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/AWS-deployment-instruction.htm","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Qlik documents preparing Azure virtual machines, resource groups and networking before installing Qlik Sense Enterprise on Windows.","reviewed":"2026-11-15","sourceType":"vendor-documentation","title":"Qlik Sense Enterprise on Azure","url":"https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Azure-deployment-instruction.htm","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Qlik documents preparing Google Compute Engine Windows instances and installing Qlik Sense Enterprise on Windows.","reviewed":"2026-11-15","sourceType":"vendor-documentation","title":"Qlik Sense Enterprise on Google Cloud","url":"https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/GCP-deployment-instruction.htm","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-15","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 client-managed analytics platform installed on customer cloud Windows virtual machines.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Qlik Sense Enterprise client-managed installation baseline; production data/model capacity separate","source":"https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/Common/system-requirements.htm","status":"documented","summary":"The May 2026 requirements list multi-core x64/AVX hardware, at least 8 GB RAM and 5 GB installation disk, with data-dependent additional memory/storage and shared storage for multi-server sites. These installation requirements do not size an in-memory 1-TB analytical workload, concurrency, repository database or HA replicas."},"iac":{"artifactRef":"May 2026 documentation","artifactUrl":"https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/AWS-deployment-instruction.htm","reviewed":"2026-11-21","scope":"Qlik Sense Enterprise on Windows May 2026 AWS installation guide","source":"https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/AWS-deployment-instruction.htm","status":"documented","summary":"The client-managed AWS guide documents Windows infrastructure and Qlik Sense deployment choices. Obtain the licensed installer and configure supported nodes, networking, repository/database and shared storage; cloud guidance is not a universal unattended or HA application template."},"licensePricing":{"reviewed":"2026-11-16","scope":"Qlik Sense Enterprise client-managed, May 2026 administration guide","source":"https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/Common/Qlik-product-licenses.htm","status":"documented","summary":"Qlik Sense Enterprise supports access-type or token licensing. Professional/Analyzer user and Analyzer Capacity entitlements have different conditions. Signed license keys require access to the cloud license backend; confirm activation and usage terms for the customer-managed installation."},"sso":{"availability":"available","reviewed":"2026-11-21","scope":"Qlik Sense Enterprise on Windows May 2026 application-user SAML","source":"https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Administer_QSEoW/Managing_QSEoW/Configure-SAML.htm","status":"documented","summary":"The May 2026 client-managed guide documents SAML using a configured virtual proxy, linked proxy, IdP metadata and user attributes. Configure the selected proxy prefix and identity mapping; Qlik Cloud sign-in and database-connection SSO are separate concerns."}},"id":"qlik-sense-enterprise-client-managed","infrastructure":["servers"],"infrastructureNotes":"Qlik Sense Enterprise Client-Managed runs persistent Windows services and repository components on customer virtual machines.","infrastructureReviewed":"2026-11-15","infrastructureSources":["https://help.qlik.com/en-US/sense-admin/May2026/Content/Sense_Helpsites/Home-deployadminister.htm"],"install":"Qlik Sense Enterprise on Windows using provider-specific AWS, Azure or Google Cloud VM guidance","installMethods":["package"],"kind":"product","license":"Commercial Qlik Sense Enterprise license.","licenseModel":"commercial-only","licenseModelNotes":"Qlik Sense Enterprise Client-Managed is activated through a commercial subscription, perpetual or capacity/core-based license model as applicable to the agreement.","licenseModelSources":["https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/Common/Qlik-product-licenses.htm"],"licenseReviewed":"2026-11-15","model":"Fully in your account","modelLabel":"Customer-operated","name":"Qlik Sense Enterprise Client-Managed","notes":"This entry covers Qlik Sense Enterprise Client-Managed on Windows, not Qlik Cloud. Review current system requirements, supported Windows and database versions, multi-node topology and licensing terms before deployment.","operations":"Customer manages Windows hosts, networking, certificates, identity, repository database, shared storage, load balancing, backups, scaling, upgrades and license activation.","publisher":false,"reviewed":"2026-11-15","sources":[{"title":"Qlik Sense client-managed administration and deployment","url":"https://help.qlik.com/en-US/sense-admin/May2026/Content/Sense_Helpsites/Home-deployadminister.htm"},{"title":"Qlik Sense on AWS","url":"https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/AWS-deployment-instruction.htm"},{"title":"Qlik Sense on Azure","url":"https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Azure-deployment-instruction.htm"},{"title":"Qlik Sense on Google Cloud","url":"https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/GCP-deployment-instruction.htm"},{"title":"Qlik product licenses","url":"https://help.qlik.com/en-US/sense-admin/May2026/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/Common/Qlik-product-licenses.htm"}],"url":"https://launchinyourcloud.com/directory/qlik-sense-enterprise-client-managed/","website":"https://www.qlik.com/us/products/qlik-sense"},{"advisories":[{"action":"Verify the actual AMI OS and use maintained operating-system packaging before production. Migrate any confirmed AL2 host under the vendor/provider upgrade procedure and test backup/recovery.","conditions":"Marketplace metadata can lag the actual AMI. Confirm the resolved image ID and OS before concluding that a deployed instance uses AL2; application version alone does not establish OS maintenance.","effectiveDate":"2026-06-30","id":"questdb-oss-aws-ami-al2-lifecycle","listingIds":["questdb-self-hosted"],"reviewed":"2026-11-18","scope":"The OS label of AWS offer prodview-cddeafdirexw6; not all QuestDB versions, manual VM installs or other cloud packages.","source":"https://aws.amazon.com/amazon-linux-2/faqs/","summary":"The reviewed QuestDB OSS AWS AMI package 10.1.0 lists Amazon Linux 2.0.20210318.0. AWS ended AL2 standard support on June 30, 2026.","supportingSources":[{"title":"Exact QuestDB OSS offer, package and OS label","url":"https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6"}],"title":"QuestDB OSS AWS offer lists an operating system past standard support","type":"lifecycle"}],"architecture":"Persistent QuestDB process with dedicated data disks, network endpoints and customer-managed operating system.","categories":["databases-vector","data-analytics"],"category":"Databases \u0026 vector","categoryFit":{"data-analytics":"Supports time-series ingestion, SQL analytics and operational analysis of large event datasets.","databases-vector":"Provides a high-performance time-series database with SQL and ingestion protocols on customer infrastructure."},"cloudEvidence":[{"clouds":["aws"],"notes":"QuestDB documents manual installation of the full OSS application on customer EC2 with VPC, persistent storage and operating choices. Enterprise marketplace features are not inherited.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"QuestDB on AWS","url":"https://questdb.com/docs/deployment/aws/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The Azure guide includes customer VM deployment. Its Marketplace offer is Enterprise; use the manual OSS path for this listing and do not transfer Enterprise entitlements.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"QuestDB on Azure","url":"https://questdb.com/docs/deployment/azure/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"QuestDB documents deployment to customer Compute Engine with separate durable storage.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"QuestDB on Google Cloud","url":"https://questdb.com/docs/deployment/gcp/","vendorSupport":"not-assessed"},{"applicableEdition":"QuestDB Open Source","applicableVersions":["AMI package 10.1.0"],"clouds":["aws"],"notes":"The QuestDB-published AMI installs the OSS database on customer EC2. Package 10.1.0 lists Amazon Linux 2; verify the resolved image and replace unsupported OS packaging. Availability does not supply Enterprise HA, OIDC or a support entitlement.","reviewed":"2026-11-18","sourceType":"marketplace-offer","title":"Vendor-published QuestDB Open Source AWS AMI","url":"https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-18","clouds":["aws","azure","gcp"],"communityAcceptance":{"reviewed":"2026-11-18","sources":[{"title":"Official maintenance and adoption evidence","url":"https://github.com/questdb/questdb"},{"title":"Official maintenance and adoption evidence","url":"https://github.com/questdb/questdb/releases/tag/10.2.0"}],"summary":"QuestDB maintains an open source repository with contributor participation, installation instructions and current OSS releases. Enterprise customer stories do not establish OSS entitlements or customer-account hosting; provider-specific manual guides supply that evidence."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0,3],"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":"Apache-licensed time-series database installed on customer virtual machines in AWS, Azure or Google Cloud.","diligence":{"airGap":{"reviewed":"2026-11-18","scope":"QuestDB Open Source Self-Hosted: selected customer-operated edition","source":"https://questdb.com/docs/configuration/telemetry/","status":"inconclusive","summary":"QuestDB documents telemetry.enabled=false, which stops Web Console usage telemetry and removes its Metrics View. Manual binaries are also available. These facts do not validate the complete disconnected OSS lifecycle: confirm a local JRE/artifact supply, restart/configuration, ingest/query clients, updates and backup/recovery. Enterprise offline-trial and backup claims are not inherited by OSS.","supportingSources":[{"title":"OSS installation and upgrade artifact","url":"https://questdb.com/docs/deployment/aws/"}]},"commitments":{"availability":"unavailable","reviewed":"2026-11-18","scope":"Software amount through the exact free AWS AMI prodview-cddeafdirexw6; infrastructure, paid support, other editions and private offers assessed separately","source":"https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6","status":"documented","summary":"The exact reviewed QuestDB Open Source AWS AMI is free of charge in Marketplace. It supplies no billed software amount to apply toward a software-spend commitment through this offer. EC2/EBS, paid support, other editions and separately negotiated offers have separate charges and require the buyer’s applicable order and AWS agreement; the free software finding does not settle those charges.","supportingSources":[{"title":"AWS product-by-product commitment qualifications","url":"https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html"}]},"compliance":{"reviewed":"2026-11-18","scope":"QuestDB Open Source Self-Hosted: selected customer-operated edition","source":"https://questdb.com/docs/security/governance/","status":"inconclusive","summary":"The current governance material advertises SOC 2 Type 2 while distinguishing Enterprise controls from OSS. No public audit period/system description established that the report covers this customer-operated OSS database and its external encryption/network controls. Obtain the full report and relevant customer-control scope; a footer badge is insufficient."},"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://questdb.com/enterprise/","status":"inconclusive","summary":"The requested HA architecture is not supplied by native QuestDB Open Source replication/failover. Decide whether to change edition or separately validate an external recovery design before costing. Then supply ingestion rate, series/cardinality, query concurrency, retained rows, storage compression and recovery objectives.","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":"QuestDB Open Source Self-Hosted: selected customer-operated edition","source":"https://questdb.com/docs/getting-started/capacity-planning/","status":"documented","summary":"Capacity guidance recommends 8 GB RAM for basic and 32 GB for advanced use, fast local/NVMe storage and workload-specific CPU planning. The edition comparison explicitly excludes replication and automatic failover from OSS, so this listing cannot satisfy the requested native HA design.","supportingSources":[{"title":"OSS versus Enterprise availability features","url":"https://questdb.com/enterprise/"}]},"iac":{"artifactRef":"QuestDB OSS 10.2.0, no-JRE archive","artifactUrl":"https://github.com/questdb/questdb/releases/download/10.2.0/questdb-10.2.0-no-jre-bin.tar.gz","reviewed":"2026-11-18","scope":"QuestDB Open Source Self-Hosted: selected customer-operated edition","source":"https://questdb.com/docs/deployment/aws/","status":"documented","summary":"The manual EC2 guide links the versioned QuestDB 10.2.0 no-JRE binary archive and systemd upgrade steps. Supply a compatible JRE and review service configuration. This is an application artifact, not a complete HA Terraform stack."},"licensePricing":{"reviewed":"2026-11-18","scope":"QuestDB Open Source Self-Hosted: selected customer-operated edition","source":"https://github.com/questdb/questdb","status":"documented","summary":"QuestDB Open Source is Apache 2.0 licensed. Enterprise adds commercial capabilities, including replication/HA and OIDC, under separate terms; those features and licence costs are outside this OSS listing.","supportingSources":[{"title":"Commercial edition boundary","url":"https://questdb.com/enterprise/"}]},"marketplace":{"availability":"available","offers":[{"cloud":"aws","delivery":"Amazon Machine Image (AMI), x86","id":"prodview-cddeafdirexw6","publisher":"QuestDB","url":"https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6","version":"10.1.0"}],"reviewed":"2026-11-18","scope":"Vendor-published QuestDB Open Source AWS AMI 10.1.0; package availability is not a production recommendation","source":"https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6","status":"documented","summary":"QuestDB publishes the free QuestDB Open Source AMI prodview-cddeafdirexw6 on AWS Marketplace, package 10.1.0, x86. Infrastructure is charged separately. The offer lists Amazon Linux 2.0.20210318.0; AWS ended AL2 standard support on June 30, 2026. Verify the resolved AMI OS and use a maintained image before production. This offer is distinct from Azure Enterprise packaging and does not add OSS replication, HA or OIDC.","supportingSources":[{"title":"Manual customer EC2 installation","url":"https://questdb.com/docs/deployment/aws/"},{"title":"Amazon Linux 2 end of support","url":"https://aws.amazon.com/amazon-linux-2/faqs/"}]},"release":{"releasePublishedAt":"2026-11-10T10:22:14Z","releaseTag":"10.2.0","reviewed":"2026-11-18","scope":"QuestDB Open Source Self-Hosted: selected customer-operated edition","source":"https://github.com/questdb/questdb/releases/tag/10.2.0","status":"documented","summary":"QuestDB OSS 10.2.0 was published November 10, 2026. Enterprise release numbers follow a separate line. Pin the OSS binary/container and dependencies; this snapshot does not establish a support SLA or future cadence. The reviewed AWS OSS AMI packages 10.1.0 rather than upstream 10.2.0 and lists AL2; check the actual OS image lifecycle.","supportingSources":[{"title":"Separate AWS OSS package and OS label","url":"https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6"},{"title":"AL2 support ended June 30, 2026","url":"https://aws.amazon.com/amazon-linux-2/faqs/"}]},"scim":{"reviewed":"2026-11-18","scope":"QuestDB Open Source Self-Hosted: selected customer-operated edition","source":"https://questdb.com/docs/security/governance/","status":"inconclusive","summary":"The governance comparison does not establish a native OSS SCIM endpoint or user/group deprovisioning operations. Enterprise RBAC/OIDC are not evidence that SCIM is supplied in Open Source."},"securityControls":{"reviewed":"2026-11-18","scope":"QuestDB Open Source Self-Hosted: selected customer-operated edition","source":"https://questdb.com/docs/security/governance/","status":"documented","summary":"The edition matrix distinguishes OSS controls from Enterprise TLS, RBAC and OIDC. The AWS guide directs operators to change HTTP/PG credentials, disable unused interfaces and restrict source IPs. Design encryption and network boundaries explicitly rather than inheriting Enterprise capabilities.","supportingSources":[{"title":"OSS instance hardening","url":"https://questdb.com/docs/deployment/aws/"},{"title":"Disable Web Console usage telemetry","url":"https://questdb.com/docs/configuration/telemetry/"},{"title":"AMI operating-system support boundary","url":"https://aws.amazon.com/amazon-linux-2/faqs/"}]},"sso":{"availability":"unavailable","reviewed":"2026-11-18","scope":"Native QuestDB Open Source OIDC SSO; Enterprise entitlement is excluded","source":"https://questdb.com/enterprise/","status":"documented","summary":"QuestDB’s edition comparison assigns OIDC SSO to Enterprise. Open Source has its documented local authentication controls and does not include that Enterprise OIDC feature. An external identity proxy would be a separate architecture."}},"id":"questdb-self-hosted","infrastructure":["servers"],"infrastructureNotes":"QuestDB runs as a persistent database process on provisioned compute with durable data disks.","infrastructureReviewed":"2026-11-18","infrastructureSources":["https://questdb.com/docs/deployment/aws/","https://questdb.com/docs/deployment/azure/","https://questdb.com/docs/deployment/gcp/"],"install":"Vendor AWS OSS AMI 10.1.0, or customer VM binary/systemd/container installation; validate the AMI OS lifecycle; Azure Marketplace packaging is Enterprise","installMethods":["vm-image","package","docker"],"kind":"product","license":"QuestDB Open Source is Apache License 2.0; QuestDB Enterprise is separately proprietary.","licenseModel":"open-source","licenseModelNotes":"QuestDB Open Source is Apache-2.0. QuestDB Enterprise uses separate commercial terms.","licenseModelSources":["https://github.com/questdb/questdb","https://questdb.com/terms/"],"licenseReviewed":"2026-11-18","model":"Fully in your account","modelLabel":"Customer-operated","name":"QuestDB Open Source Self-Hosted","notes":"QuestDB Open Source excludes native replication, automatic failover and OIDC SSO in the vendor edition matrix. The requested native HA scenario therefore requires a different edition or a separately validated external design. Azure Marketplace packaging is Enterprise, not OSS. The separate free upstream AWS OSS AMI is confirmed, but its Marketplace OS label is Amazon Linux 2, whose standard support ended June 30, 2026. Resolve the actual AMI and maintained OS before production.","operations":"Customer manages VM and OS, data disks, networking, authentication, backups, monitoring, upgrades and capacity.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Deploy QuestDB on AWS","url":"https://questdb.com/docs/deployment/aws/"},{"title":"Deploy QuestDB on Azure","url":"https://questdb.com/docs/deployment/azure/"},{"title":"Deploy QuestDB on Google Cloud","url":"https://questdb.com/docs/deployment/gcp/"},{"title":"QuestDB repository and license","url":"https://github.com/questdb/questdb"},{"title":"Exact vendor AWS OSS AMI and package","url":"https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6"},{"title":"Amazon Linux 2 lifecycle","url":"https://aws.amazon.com/amazon-linux-2/faqs/"}],"url":"https://launchinyourcloud.com/directory/questdb-self-hosted/","website":"https://questdb.com/"},{"architecture":"Customer-operated document/retrieval application with deployment-specific stateful storage and configured model services","categories":["ai-applications-rag","ai-tools"],"category":"AI applications \u0026 RAG","categoryFit":{"ai-applications-rag":"Document understanding, knowledge ingestion and retrieval-augmented/agentic question answering with configurable LLM, embedding and reranking endpoints.","ai-tools":"Self-hosted document ingestion, retrieval and context infrastructure for AI applications."},"cloudEvidence":[{"applicableEdition":"Community / upstream open-source; third-party distribution where noted","applicableVersions":["0.26.4"],"clouds":["aws"],"notes":"The sample provisions the RAGFlow application and workers, OpenSearch, Aurora PostgreSQL, Valkey, S3 and a Bedrock gateway in the customer AWS account. Source inspection confirms the v0.26.4 Python image pin; it does not establish compatibility with the 1.0 Go rewrite. This community integration also requires the separately billed stdapi.ai gateway and Bedrock access. Review its documented networking, client-security, availability and cost limitations before use.","reviewed":"2026-11-12","sourceType":"community-template","title":"Community RAGFlow deployment on AWS ECS Fargate through stdapi.ai","url":"https://github.com/stdapi-ai/samples/tree/main/getting_started_ragflow","vendorSupport":"not-assessed"},{"applicableEdition":"Community / upstream open-source; third-party distribution where noted","applicableVersions":["0.26.4"],"clouds":["azure"],"notes":"The image publisher documents an Azure VM in the customer subscription running the complete Compose stack, including Elasticsearch, MySQL, MinIO, Redis and a local embedding service. Its guide pins RAGFlow v0.26.4, not 1.0. This is a third-party repackaged image with additional support charges, not an upstream-endorsed distribution. Confirm image access, current patch/migration requirements, TLS configuration and the separately configured chat-model endpoint.","reviewed":"2026-11-12","sourceType":"third-party-package","title":"cloudimg RAGFlow Azure VM deployment and operations guide","url":"https://www.cloudimg.co.uk/guides/ragflow-on-ubuntu-24-04-azure/","vendorSupport":"not-assessed"},{"applicableEdition":"Community / upstream open-source; third-party distribution where noted","clouds":["gcp"],"notes":"The image publisher documents selecting the customer project, deployment service account, zone, network and Compute Engine VM, then completing RAGFlow initialization and configuring its bundled Ollama models. This is a third-party packaged deployment; the guide does not establish a specific current RAGFlow release or 1.0 compatibility. Confirm the image version, support charges, model licenses, resource sizing and network exposure before use.","reviewed":"2026-11-12","sourceType":"third-party-package","title":"Techlatest RAGFlow VM deployment in a customer Google Cloud project","url":"https://www.techlatest.net/support/ragflow_support/gcp_gettingstartedguide/index.html","vendorSupport":"not-assessed"},{"applicableEdition":"Community / upstream open-source; third-party distribution where noted","clouds":["alibaba"],"notes":"Alibaba Cloud documents provisioning a RAGFlow Community service instance with customer ECS, VPC and vSwitch parameters. This is distinct from the managed AI-Native Database Service integration. Review image version, access controls, model endpoints and the broad example RAM permissions before production.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"RAGFlow Community deployment on Alibaba Cloud Compute Nest","url":"https://help.aliyun.com/en/compute-nest/use-cases/ragflow-community-edition-service-instance-deployment-document","vendorSupport":"not-assessed"},{"applicableEdition":"Community / upstream open-source; third-party distribution where noted","applicableVersions":["0.27.1"],"clouds":["railway"],"notes":"This community template deploys the application, Elasticsearch, MySQL, Redis, a local embedding service and object storage into the customer Railway project. Its linked Dockerfile pins upstream RAGFlow v0.27.1 with a Railway startup/configuration wrapper. The template is not proof of 1.0 compatibility or upstream support; review migrations and the separately configured chat-model endpoint. Railway manages the underlying infrastructure.","reviewed":"2026-11-12","sourceType":"community-template","title":"Community RAGFlow Railway application stack","url":"https://railway.com/deploy/ragflow-ai","vendorSupport":"not-assessed"},{"applicableEdition":"Community / upstream open-source; third-party distribution where noted","applicableVersions":["0.27.1"],"clouds":["railway"],"notes":"Source inspection confirms the v0.27.1 base image and the custom configuration, nginx and startup wrapper used by the linked Railway template. The upstream 1.0 release changes the architecture and requires its documented migration path; do not substitute a new image tag without reviewing the complete stack.","reviewed":"2026-11-12","sourceType":"community-template","title":"Railway deployment image source and release pin","url":"https://github.com/gridalpha/ragflow-railway/blob/main/Dockerfile","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp","alibaba","railway"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Current releases and contributors","url":"https://github.com/infiniflow/ragflow/releases"},{"title":"Release chronology and deployment instructions","url":"https://raw.githubusercontent.com/infiniflow/ragflow/main/README.md"}],"summary":"Current release notes document continued 2026 releases and dozens of named contributors across successive versions; the upstream README records a 1.0.0 release on 6 November 2026."},"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":"alibaba","controlPlane":"not-assessed","evidence":[3],"operator":"customer"},{"boundary":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[4,5],"operator":"customer"}],"description":"Document processing and retrieval platform for building RAG and agentic knowledge applications.","diligence":{"footprint":{"reviewed":"2026-11-14","scope":"Upstream 1.0 quickstart; provider packages may target 0.x","source":"https://ragflow.io/docs/v1.0.0/","status":"documented","summary":"The 1.0 quickstart recommends a starting point of 4 CPU cores, 16 GB RAM and 50 GB free disk. Models, document engines and concurrency can require more; this does not size the older third-party cloud packages."},"iac":{"artifactRef":"v1.0.0","artifactUrl":"https://github.com/infiniflow/ragflow/blob/v1.0.0/docker/docker-compose.yml","reviewed":"2026-11-14","scope":"Upstream v1.0.0 Compose; not evidence of compatibility with the listed 0.x provider packages","source":"https://github.com/infiniflow/ragflow/blob/v1.0.0/docker/docker-compose.yml","status":"documented","summary":"The v1.0.0 Compose file includes a separate dependency configuration and reads its image selection from the release environment. Use the matching release configuration; this artifact does not establish a migration path or compatibility for older provider packages.","supportingSources":[{"title":"Versioned RAGFlow 1.0.0 quickstart","url":"https://ragflow.io/docs/v1.0.0/"}]},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/infiniflow/ragflow/main/LICENSE","status":"documented","summary":"The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Model weights and external model APIs require their own review."},"release":{"releasePublishedAt":"2026-11-06T12:31:31Z","releaseTag":"v1.0.0","reviewed":"2026-11-14","scope":"Upstream infiniflow/ragflow release record; commercial editions and deployment packages may differ","source":"https://github.com/infiniflow/ragflow/releases/tag/v1.0.0","status":"documented","summary":"The publisher-designated GitHub release checked was v1.0.0, published 2026-11-06. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package."},"sso":{"reviewed":"2026-11-20","scope":"RAGFlow v1.0 Go OSS versus Enterprise federation; current entitlement/configuration unresolved","source":"https://raw.githubusercontent.com/infiniflow/ragflow/v1.0.0/docker/README.md","status":"inconclusive","summary":"A vendor maintainer identifies OAuth2/OIDC SSO in Enterprise, while the reviewed v1.0.0 Go deployment reference does not establish a supported federation configuration for that OSS release. Older OAuth configuration examples must not be assumed compatible with the new backend. Confirm edition, release and identity-provider configuration.","supportingSources":[{"title":"Vendor-maintainer Enterprise SSO statement","url":"https://github.com/infiniflow/ragflow/issues/15882"}]}},"id":"ragflow","infrastructure":["servers"],"infrastructureNotes":"Customer-operated document/retrieval application with deployment-specific stateful storage and configured model services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://github.com/infiniflow/ragflow"],"install":"Versioned upstream Docker Compose, provider-specific VM packages or community deployment templates; select a path compatible with the intended RAGFlow release.","installMethods":["docker","vm-image","package"],"kind":"product","license":"Apache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms.","licenseModel":"open-source","licenseModelNotes":"Apache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.","licenseModelSources":["https://raw.githubusercontent.com/infiniflow/ragflow/main/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"RAGFlow","notes":"Deployment options include customer AWS, Azure and Google Cloud infrastructure, Alibaba Compute Nest, and a Railway project. The evidence trail identifies the publishers and template versions. Hosting RAGFlow does not automatically self-host its LLM, embeddings or reranker; choose private or local model endpoints where required.","operations":"Customer manages document storage, indexing, app services, access controls, model endpoints, backups and upgrades.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Upstream project and capabilities","url":"https://github.com/infiniflow/ragflow"},{"title":"Current upstream license","url":"https://raw.githubusercontent.com/infiniflow/ragflow/main/LICENSE"},{"title":"RAGFlow 1.0 release and migration requirements","url":"https://ragflow.io/docs/v1.0.0/release_notes"}],"url":"https://launchinyourcloud.com/directory/ragflow/","website":"https://ragflow.io/"},{"architecture":"Customer-operated Rancher management server, ingress and persistent Kubernetes resources","categories":["devops"],"category":"DevOps","categoryFit":{"devops":"Provides centralized provisioning, access control and lifecycle management for Kubernetes clusters."},"cloudEvidence":[{"clouds":["aws"],"notes":"The upstream guide installs the Rancher server with Helm into an EKS cluster controlled by the customer.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"Rancher Manager on Amazon EKS","url":"https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The upstream guide installs the Rancher server with Helm into an AKS cluster controlled by the customer.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"Rancher Manager on Azure Kubernetes Service","url":"https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The upstream guide installs Rancher into a GKE Standard cluster. GKE Autopilot is explicitly unsupported for the Rancher server.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"Rancher Manager on Google Kubernetes Engine","url":"https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-gke","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-14","clouds":["aws","azure","gcp"],"communityAcceptance":{"reviewed":"2026-11-14","sources":[{"title":"Reviewed maintenance release v2.15.3","url":"https://github.com/rancher/rancher/releases/tag/v2.15.3"},{"title":"Upstream contributor history","url":"https://github.com/rancher/rancher/graphs/contributors"},{"title":"Upstream user community and participation","url":"https://www.rancher.com/community"}],"summary":"Rancher has sustained code participation from multiple contributors and an established upstream user community. The reviewed Community release 2.15.3, published October 29, 2026, records maintenance and security fixes. Public contributor history and the official community program establish participation beyond repository popularity; commercial SUSE support remains separate."},"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 Kubernetes management platform deployed into a customer-operated cluster.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Upstream management-cluster starting profile; downstream applications excluded","source":"https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/installation-requirements","status":"documented","summary":"For a small hosted-Kubernetes management cluster, the guide lists at least three nodes, each with 4 vCPUs and 16 GB RAM. Larger managed fleets need more. Single-node Docker is development/test only; downstream workload clusters, datastore/storage and HA headroom are additional."},"iac":{"artifactRef":"stable Helm repository index (moving; select a supported chart version)","artifactUrl":"https://releases.rancher.com/server-charts/stable/index.yaml","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster","status":"documented","summary":"The Kubernetes guide publishes separate stable, latest and alpha Helm repositories. Stable is recommended for production; check the Kubernetes support matrix and certificate/HA prerequisites before installation."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/rancher/rancher/main/LICENSE","status":"documented","summary":"Rancher Manager core is Apache-2.0 licensed. This does not establish a SUSE support subscription price or the cost and licences of managed Kubernetes clusters and optional components."},"release":{"releasePublishedAt":"2026-10-29T15:51:42Z","releaseTag":"v2.15.3","reviewed":"2026-11-14","scope":"Upstream rancher/rancher release record; commercial editions and deployment packages may differ","source":"https://github.com/rancher/rancher/releases/tag/v2.15.3","status":"documented","summary":"The publisher-designated GitHub release checked was v2.15.3, published 2026-10-29. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Rancher Manager console federation","source":"https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config","status":"documented","summary":"The upstream authentication guide documents OIDC, SAML and OAuth integrations, including Keycloak, Okta, Entra ID, AD FS and a generic OIDC provider. Review version compatibility, local administrator access and downstream-cluster authorization separately from signing into Rancher."}},"id":"rancher-manager","infrastructure":["servers"],"infrastructureNotes":"Rancher runs as persistent management services inside Kubernetes and requires ingress, certificates and durable state. The hosted Kubernetes control plane does not make Rancher serverless.","infrastructureReviewed":"2026-11-14","infrastructureSources":["https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster"],"install":"Official Helm chart on a supported Kubernetes cluster","installMethods":["helm"],"kind":"product","license":"Apache License 2.0; commercial SUSE subscriptions and support are separate.","licenseModel":"open-source","licenseModelNotes":"Rancher Manager is Apache-2.0 licensed. SUSE subscriptions, hosted services and enterprise support use separate commercial terms.","licenseModelSources":["https://github.com/rancher/rancher/blob/master/LICENSE"],"licenseReviewed":"2026-11-14","model":"Fully in your account","modelLabel":"Customer-operated","name":"Rancher Manager","notes":"This entry covers self-managed Rancher Manager, not separate hosted offerings. Rancher documents EKS, AKS and GKE installation paths. GKE Autopilot is not supported for the Rancher server because required kube-system changes are restricted.","operations":"Customer manages the management cluster, ingress, certificates, backups, upgrades, downstream-cluster credentials and availability.","publisher":false,"reviewed":"2026-11-14","sources":[{"title":"Kubernetes installation overview","url":"https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster"},{"title":"Rancher on Amazon EKS","url":"https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks"},{"title":"Rancher on AKS","url":"https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks"},{"title":"Rancher on GKE","url":"https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-gke"},{"title":"Apache 2.0 license","url":"https://github.com/rancher/rancher/blob/master/LICENSE"},{"title":"Reviewed maintenance release v2.15.3","url":"https://github.com/rancher/rancher/releases/tag/v2.15.3"},{"title":"Upstream contributor history","url":"https://github.com/rancher/rancher/graphs/contributors"},{"title":"Upstream user community and participation","url":"https://www.rancher.com/community"}],"url":"https://launchinyourcloud.com/directory/rancher-manager/","website":"https://www.rancher.com/products/rancher"},{"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"},{"advisories":[{"action":"Apply OpenShift AI 3.5.3 or a later supported update following Red Hat's erratum.","conditions":"Installed components and package versions determine applicability.","disclosedOn":"2026-11-06","id":"red-hat-openshift-ai-rhsa-2026-95872","listingIds":["red-hat-openshift-ai-self-managed"],"reviewed":"2026-11-18","scope":"Red Hat OpenShift AI 3.5 packages identified in the erratum.","source":"https://access.redhat.com/errata/RHSA-2026%3A95872","summary":"RHSA-2026:95872 is a critical OpenShift AI 3.5.3 update covering nine CVEs.","title":"Red Hat OpenShift AI 3.5.3 critical security update","type":"security-advisory"}],"architecture":"OpenShift operators and persistent AI workbench, pipeline, model-serving and supporting services on customer Kubernetes infrastructure.","categories":["ai-tools"],"category":"AI tools \u0026 infrastructure","categoryFit":{"ai-tools":"AI workbenches, pipelines, model serving and lifecycle tooling delivered on a customer-operated OpenShift platform."},"cloudEvidence":[{"clouds":["aws","azure","gcp","oci","ibm"],"notes":"Red Hat's Self-Managed matrix explicitly lists OpenShift Container Platform on AWS, Azure, Google Cloud, IBM Cloud and Oracle Cloud. The selected OpenShift release, subscriptions, storage, accelerator and component restrictions apply; managed cloud-service add-ons are a separate offering.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"OpenShift AI Self-Managed on supported OpenShift public-cloud platforms","url":"https://access.redhat.com/articles/rhoai-supported-configs","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-17","clouds":["aws","azure","gcp","oci","ibm"],"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":"cloud-account","cloud":"oci","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"ibm","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Commercial AI and machine-learning platform installed as an Operator on a customer-operated Red Hat OpenShift cluster.","diligence":{"airGap":{"availability":"available","reviewed":"2026-11-17","scope":"Self-managed OpenShift AI disconnected installation","source":"https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed_in_a_disconnected_environment/","status":"documented","summary":"Red Hat supplies a separate disconnected installation guide using mirrored Operator/container content. Required model, notebook, accelerator and object-storage dependencies must also be staged for the selected components."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Red Hat OpenShift AI Self-Managed; unresolved within this edition/deployment","source":"https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install","status":"inconclusive","summary":"Self-Managed AI and underlying OpenShift subscriptions need offer-specific confirmation before software charges are treated as eligible cloud commitment spend."},"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_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install","status":"inconclusive","summary":"The reviewed Red Hat OpenShift AI 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_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install","status":"inconclusive","summary":"Select OpenShift HA topology, enabled AI components, model size, GPU needs, concurrency, object storage and both subscription entitlements. Operator installation minima do not size inference/training. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"OpenShift AI 3.5 installation minima; platform/control-plane resources additional","source":"https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install","status":"documented","summary":"Installing the Operator requires at least two workers with 8 CPU/32 GiB each; single-node OpenShift requires 32 CPU/128 GiB. Workloads, models, accelerators and storage need additional resources; these installation minima do not establish HA workload capacity."},"iac":{"reviewed":"2026-11-17","scope":"OpenShift AI Self-Managed 3.5 Operator installation","source":"https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install","status":"documented","summary":"Install the supported OpenShift AI Operator on an entitled, compatible OpenShift cluster and enable the required components. Cluster creation, storage, accelerators and model assets remain separate deployment work."},"licensePricing":{"reviewed":"2026-11-17","scope":"Red Hat OpenShift AI Self-Managed: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install","status":"documented","summary":"The selected Self-Managed product requires a Red Hat OpenShift AI subscription and an eligible OpenShift platform entitlement. Open-source components do not grant the complete supported product entitlement."},"marketplace":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Red Hat OpenShift AI Self-Managed; unresolved within this edition/deployment","source":"https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install","status":"inconclusive","summary":"OperatorHub installation and required subscriptions do not establish a specific cloud Marketplace offer for the Self-Managed AI entitlement. Managed add-ons and generic OpenShift offers are separate."},"release":{"releasePublishedOn":"2026-11-06","releaseTag":"3.5.3","reviewed":"2026-11-18","scope":"Red Hat OpenShift AI self-managed 3.5","source":"https://access.redhat.com/errata/RHSA-2026%3A95872","status":"documented","summary":"Red Hat OpenShift AI 3.5.3 was published as critical security advisory RHSA-2026:95872 on November 6, 2026 and covers nine CVEs."},"scim":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Red Hat OpenShift AI Self-Managed; unresolved within this edition/deployment","source":"https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install","status":"inconclusive","summary":"AI authentication delegates to the OpenShift IdP. The reviewed installation guide does not establish a separate AI SCIM endpoint or the provisioning capabilities of the buyer’s chosen IdP."},"securityControls":{"reviewed":"2026-11-18","scope":"OpenShift AI cluster access prerequisites Red Hat OpenShift AI 3.5 packages identified in the erratum.","source":"https://access.redhat.com/errata/RHSA-2026%3A95872","status":"documented","summary":"Installation requires cluster administrator access, a configured IdP and compatible subscriptions. Configure access groups and certificate trust for workbenches, models, pipelines and object storage. Current advisory review: RHSA-2026:95872 is a critical OpenShift AI 3.5.3 update covering nine CVEs. Apply OpenShift AI 3.5.3 or a later supported update following Red Hat's erratum.","supportingSources":[{"title":"Certificate trust in disconnected deployments","url":"https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed_in_a_disconnected_environment/working-with-certificates_certs"},{"title":"Prior security-controls source","url":"https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install"}]},"sso":{"availability":"available","reviewed":"2026-11-17","scope":"Self-managed OpenShift AI 3.5 identity through the cluster","source":"https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install","status":"documented","summary":"OpenShift AI uses the identity provider configured for its OpenShift cluster. Configure cluster identity and AI user/admin groups; this does not establish a separate application SCIM endpoint."}},"id":"red-hat-openshift-ai-self-managed","infrastructure":["servers"],"infrastructureNotes":"OpenShift AI runs persistent operator-managed workloads on customer OpenShift clusters with storage, compute and optional accelerator dependencies.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install"],"install":"OpenShift AI Operator through OperatorHub or the oc command-line interface","installMethods":["kubernetes","other"],"kind":"platform","license":"Commercial Red Hat OpenShift AI Self-Managed subscription; an eligible OpenShift subscription is also required.","licenseModel":"commercial-only","licenseModelNotes":"The selected Self-Managed product requires a Red Hat OpenShift AI subscription and an eligible OpenShift platform entitlement. Open-source components do not grant the complete supported product entitlement.","licenseModelSources":["https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"Red Hat OpenShift AI Self-Managed","notes":"This entry covers OpenShift AI Self-Managed, not Red Hat's managed cloud-service add-on. Support depends on a compatible OpenShift Container Platform release, storage and accelerator matrix, and active subscriptions. Underlying OpenShift and cloud infrastructure are operated by the customer. RHSA-2026:95872 is a critical OpenShift AI 3.5.3 security update covering nine CVEs. Use Red Hat's package and deployment scope to determine affected components, then apply 3.5.3 or a later supported update.","operations":"Customer manages the OpenShift cluster, storage, accelerators, identity, networking, model data, backups and upgrades within Red Hat's supported configuration matrix.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"OpenShift AI supported configurations","url":"https://access.redhat.com/articles/rhoai-supported-configs"},{"title":"OpenShift AI Self-Managed 3.5 installation and subscription","url":"https://docs.redhat.com/en/documentation/red_hat_openshift_ai_self-managed/3.5/html/installing_and_uninstalling_openshift_ai_self-managed/installing-and-deploying-openshift-ai_install"},{"title":"RHSA-2026:95872","url":"https://access.redhat.com/errata/RHSA-2026%3A95872"}],"url":"https://launchinyourcloud.com/directory/red-hat-openshift-ai-self-managed/","website":"https://www.redhat.com/en/technologies/cloud-computing/openshift/openshift-ai"},{"architecture":"Customer-operated control-plane and worker machines with integrated operators, networking, storage and cluster services","categories":["backend-platforms","devops"],"category":"Backend platforms","categoryFit":{"backend-platforms":"Provides a self-managed Kubernetes application platform with integrated operators, developer workflows, networking, registry and cluster services.","devops":"Provides platform engineering, build, deployment and operations workflows for applications across customer-managed clusters."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Red Hat's current installation overview explicitly distinguishes self-managed OpenShift Container Platform and documents installer- and user-provisioned installation paths on AWS, Microsoft Azure and Google Cloud using customer accounts and credentials.","reviewed":"2026-11-15","sourceType":"vendor-documentation","title":"Self-managed OpenShift Container Platform on AWS, Azure or Google Cloud","url":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview","vendorSupport":"not-assessed"},{"applicableVersions":["4.21"],"clouds":["ibm"],"notes":"Red Hat documents installer-provisioned deployment into customer IBM Cloud infrastructure, including account IAM/API keys, region selection, VPC networking and cluster administration.","reviewed":"2026-11-15","sourceType":"vendor-documentation","title":"Self-managed OpenShift on IBM Cloud","url":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_ibm_cloud/index","vendorSupport":"not-assessed"},{"applicableVersions":["4.21 Technology Preview"],"clouds":["alibaba"],"notes":"Red Hat documents Assisted Installer deployment using customer Alibaba Cloud OSS images, ECS machines, VPC and DNS. This 4.21 path is Technology Preview: outside production SLAs, potentially incomplete and not recommended by Red Hat for production.","reviewed":"2026-11-15","sourceType":"vendor-documentation","title":"OpenShift on Alibaba Cloud — Technology Preview","url":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_alibaba_cloud/index","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-15","clouds":["aws","azure","gcp","ibm","alibaba"],"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":"cloud-account","cloud":"ibm","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"alibaba","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Commercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"OpenShift 4.20 per-machine installation floors, not complete workload sizing","source":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/installing_on_aws/installer-provisioned-infrastructure","status":"documented","summary":"The 4.20 AWS installation matrix gives bootstrap/control-plane minima of 4 vCPUs, 16 GB RAM and 100 GB disk, and compute nodes 2 vCPUs, 8 GB and 100 GB. A standard cluster uses multiple control-plane and worker machines; workload pods, operators, storage, bootstrap and HA capacity are additional."},"iac":{"artifactRef":"Upstream installer source; obtain matching Red Hat release tooling and pull secret","artifactUrl":"https://github.com/openshift/installer","reviewed":"2026-11-20","scope":"OpenShift Container Platform 4.20 AWS installer path","source":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/installing_on_aws/installer-provisioned-infrastructure","status":"documented","summary":"Red Hat documents installer-provisioned AWS infrastructure using the release-matched openshift-install tool, install configuration, pull secret and cloud credentials. Customer-managed networking and permissions require review. Use the entitled Red Hat release distribution; the upstream installer source alone is not the product entitlement."},"licensePricing":{"reviewed":"2026-11-16","scope":"Red Hat self-managed OpenShift Container Platform subscription guide","source":"https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide","status":"documented","summary":"Self-managed subscriptions can use core-pairs or bare-metal nodes. On hyperscaler VMs, one core-pair covers four vCPUs; aggregate compute-node entitlement and support level must be sized. AI accelerators may require separate subscriptions. Obtain the applicable order and price."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"OpenShift 4.20 platform-user OIDC through the integrated OAuth service","source":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/observability/authentication_and_authorization/using-rbac","status":"documented","summary":"The 4.20 Authentication Operator supports an external OIDC identity provider using authorization-code flow, discovery and mapped claims. This authenticates platform users; applications running on the cluster need their own identity integration. Review browser/CLI token workflows and selected provider compatibility."}},"id":"openshift-container-platform","infrastructure":["servers"],"infrastructureNotes":"OpenShift Container Platform runs persistent control-plane and worker nodes plus integrated cluster operators and storage services in the customer cloud.","infrastructureReviewed":"2026-11-15","infrastructureSources":["https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview"],"install":"OpenShift installation on AWS, Azure, Google Cloud or IBM Cloud; Assisted Installer Technology Preview on Alibaba Cloud","installMethods":["other"],"kind":"product","license":"Commercial Red Hat OpenShift subscription.","licenseModel":"commercial-only","licenseModelNotes":"The selected self-managed OpenShift Container Platform edition is delivered through a commercial Red Hat subscription with entitlement and support terms.","licenseModelSources":["https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide"],"licenseReviewed":"2026-11-15","model":"Fully in your account","modelLabel":"Customer-operated","name":"Red Hat OpenShift Container Platform","notes":"This entry covers self-managed OpenShift Container Platform, not OpenShift Dedicated, ROSA, Azure Red Hat OpenShift or other managed services. The installer can provision infrastructure or integrate with customer-provisioned resources; review credential scope, subscription entitlements and lifecycle support before installation. The documented Alibaba Cloud Assisted Installer path is Technology Preview, outside Red Hat production SLAs and not recommended for production.","operations":"Customer manages cloud accounts, installer credentials, cluster machines, networking, identity, storage, registry, monitoring, backups, upgrades and Red Hat subscriptions.","publisher":false,"reviewed":"2026-11-15","sources":[{"title":"OpenShift Container Platform 4.21 installation overview","url":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installation_overview/installation_overview"},{"title":"Red Hat self-managed OpenShift subscription guide","url":"https://www.redhat.com/en/resources/self-managed-openshift-subscription-guide"},{"title":"Self-managed OpenShift on IBM Cloud","url":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_ibm_cloud/index"},{"title":"OpenShift on Alibaba Cloud — Technology Preview","url":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html-single/installing_on_alibaba_cloud/index"}],"url":"https://launchinyourcloud.com/directory/openshift-container-platform/","website":"https://www.redhat.com/en/technologies/cloud-computing/openshift/container-platform"},{"advisories":[{"action":"Apply a compatible Software/operator update; review SAML role mappings, tokens, backup behavior and module-upgrade limitations.","conditions":"The actual Redis Software image and affected bundled components determine exposure. Redis database and cluster version lifecycles are separate.","id":"redis-software-8-2-6-52-security-review","listingIds":["redis-software-self-managed"],"reviewed":"2026-11-17","scope":"Redis Software 8.2.6-52; not Redis Cloud or every independently installed Redis Open Source distribution.","source":"https://redis.io/docs/latest/operate/rs/release-notes/rs-8-2-releases/rs-8-2-6-52/","summary":"Redis Software 8.2.6-52 patches critical Brotli CVE-2026-111497 through updated bundled components.","title":"Redis Software Brotli and dependency patch","type":"security-advisory"},{"action":"Move databases to a supported compatible database version before the deadline; plan the database upgrade separately from the cluster upgrade.","conditions":"A database can lose support while its enclosing cluster version remains supported. Contract terms and the selected operator/cluster version need separate checks.","effectiveDate":"2026-12-01","id":"redis-database-8-0-end-of-life","listingIds":["redis-software-self-managed"],"reviewed":"2026-11-17","scope":"Redis database 8.0 feature set inside Redis Software; this is not the Redis Software 8.0 cluster-version EOL date.","source":"https://redis.io/docs/latest/operate/rs/8.0/installing-upgrading/product-lifecycle/","summary":"The bundled Redis database 8.0 STS line reaches end of life on December 1, 2026.","title":"Redis database 8.0 support deadline","type":"lifecycle"}],"architecture":"Customer-operated Redis Enterprise cluster and operator with persistent data and management services","categories":["databases-vector"],"category":"Databases \u0026 vector","categoryFit":{"databases-vector":"Provides commercial in-memory data, search and vector capabilities in a customer-operated Redis Enterprise cluster."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Redis lists and tests its current Kubernetes operator on Amazon EKS, Microsoft AKS and Google GKE. The customer operates the Kubernetes cluster and Redis Software deployment; Redis Cloud is separate.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"Redis Software on EKS, AKS and GKE","url":"https://redis.io/docs/latest/operate/kubernetes/reference/supported_k8s_distributions/","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":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Commercial Redis Enterprise software installed and operated in the customer's cloud or data center.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Redis Software 7.8 production node floor; workload/tiering sizing additional","source":"https://redis.io/docs/latest/operate/rs/7.8/installing-upgrading/install/plan-deployment/hardware-requirements/","status":"documented","summary":"The 7.8 production matrix requires at least three nodes, each with 2 CPU cores and 8 GB RAM; it recommends at least 8 cores/32 GB per node. Ephemeral and persistent storage depend on RAM and persistence/tiering modes. This is Redis Software guidance, not Redis Open Source sizing or capacity for a specified dataset."},"iac":{"artifactRef":"Select the supported Redis Software release for the target OS","artifactUrl":"https://redis.io/docs/latest/operate/rs/installing-upgrading/install/install-on-linux/","reviewed":"2026-11-20","scope":"Official Redis Software Linux installation; not Redis Open Source packaging","source":"https://redis.io/docs/latest/operate/rs/installing-upgrading/install/install-on-linux/","status":"documented","summary":"The official installation guide delivers Redis Software as a vendor package and installation script for supported Linux hosts, followed by cluster/database configuration. Obtain the chosen compatible release and licence. This is a product installer path; operating-system provisioning, node placement and HA design remain separate."},"licensePricing":{"reviewed":"2026-11-20","scope":"Commercial self-managed Redis Software cluster licensing; no public price quoted","source":"https://redis.io/docs/latest/operate/rs/clusters/configure/license-keys/","status":"documented","summary":"Redis Software uses a cluster licence controlling features and shard capacity; every cluster, including passive/cold DR, needs a separate licence. Trial mode lasts 30 days and permits four shards. Obtain commercial capacity/support pricing; Redis Open Source licensing does not cover this product."},"scim":{"availability":"unavailable","reviewed":"2026-11-14","scope":"Redis Software administrative users","source":"https://redis.io/docs/latest/operate/rs/security/access-control/saml-sso/","status":"documented","summary":"The Software SAML guide explicitly says SCIM user provisioning is unavailable. It supports just-in-time user creation at first SSO login; JIT is not equivalent to SCIM provisioning/deprovisioning."},"sso":{"availability":"available","reviewed":"2026-11-14","scope":"Redis Software Cluster Manager UI; not Redis Cloud or Open Source","source":"https://redis.io/docs/latest/operate/rs/security/access-control/saml-sso/","status":"documented","summary":"Redis Software supports IdP- and SP-initiated SAML 2.0 for the Cluster Manager UI with role mapping. This is administrative browser identity, not the Redis database client authentication protocol."}},"id":"redis-software-self-managed","infrastructure":["servers"],"infrastructureNotes":"Redis Enterprise runs persistent cluster nodes and an operator inside customer-managed Kubernetes or on customer VMs. It remains a stateful server deployment.","infrastructureReviewed":"2026-11-14","infrastructureSources":["https://redis.io/docs/latest/operate/kubernetes/","https://redis.io/docs/latest/operate/kubernetes/deployment/"],"install":"Redis operator on EKS, AKS or GKE; Linux, container and AWS AMI options are also available","installMethods":["helm","vm-image"],"kind":"product","license":"Commercial Redis Software subscription.","licenseModel":"commercial-only","licenseModelNotes":"This listing is for Redis Software, a subscription product governed by Redis commercial terms. It does not classify Redis Open Source.","licenseModelSources":["https://redis.io/legal/software-agreement/","https://redis.io/deployment/method/"],"licenseReviewed":"2026-11-14","model":"Fully in your account","modelLabel":"Customer-operated","name":"Redis Software Self-Managed","notes":"This entry covers Redis Software and Redis Enterprise for Kubernetes, not Redis Cloud, Azure Managed Redis or the separately licensed Redis Open Source distribution. Confirm operator, Kubernetes and subscription compatibility for the selected release. Redis Software 8.2.6-52 fixes critical Brotli CVE-2026-111497, includes current Redis OSS security fixes, and resolves SAML SSO, S3 backup, Active-Active, certificate, and OCSP problems. Redis database 8.0 reaches end of life on December 1, 2026; migrate databases to a supported feature set before then.","operations":"Customer manages cluster infrastructure, networking, persistence, backups, upgrades, monitoring and licensed capacity.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Redis deployment methods","url":"https://redis.io/deployment/method/"},{"title":"Redis Enterprise for Kubernetes","url":"https://redis.io/docs/latest/operate/kubernetes/"},{"title":"Supported Kubernetes distributions","url":"https://redis.io/docs/latest/operate/kubernetes/reference/supported_k8s_distributions/"},{"title":"Redis Software agreement","url":"https://redis.io/legal/software-agreement/"},{"title":"Redis Software 8.2.6-52 security and lifecycle notes","url":"https://redis.io/docs/latest/operate/rs/release-notes/rs-8-2-releases/rs-8-2-6-52/"},{"title":"Redis database and cluster version lifecycle","url":"https://redis.io/docs/latest/operate/rs/8.0/installing-upgrading/product-lifecycle/"}],"url":"https://launchinyourcloud.com/directory/redis-software-self-managed/","website":"https://redis.io/software/"},{"architecture":"Vendor-managed cluster in customer network","categories":["streaming"],"category":"Streaming","categoryFit":{"streaming":"Managed Kafka-compatible streaming in your cloud account."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Redpanda explicitly documents BYOC clusters in the customer AWS or Google Cloud VPC or Azure VNet, with a Redpanda-operated control plane. The architecture and provisioning requirements differ by provider; this is the BYOC offering, not Dedicated clusters in the vendor account.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Redpanda BYOC supported infrastructure","url":"https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"vendor-hosted","evidence":[0],"operator":"vendor"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"vendor-hosted","evidence":[0],"operator":"vendor"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"vendor-hosted","evidence":[0],"operator":"vendor"}],"description":"Managed Kafka-compatible streaming in your cloud account.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Redpanda Cloud BYOC workload-based sizing; no complete reference-workload machine configuration verified","source":"https://docs.redpanda.com/cloud-data-platform/reference/tiers/byoc-tiers/","status":"inconclusive","summary":"The BYOC tier reference maps throughput tiers to cloud machine types and directs buyers to a sizing calculator for broker count, machine type and RPU rate. Its connection examples are not a universal cluster minimum. A production configuration for 100 users/1 TB/HA still needs ingress/egress rate, partitions, retention, connections and recovery targets."},"iac":{"artifactRef":"Current Cloud provider documentation; pin the selected provider/module versions","artifactUrl":"https://registry.terraform.io/providers/redpanda-data/redpanda/latest/docs","reviewed":"2026-11-21","scope":"Redpanda Cloud BYOC control-plane automation and customer-cloud data plane; not self-managed Redpanda core Helm delivery","source":"https://docs.redpanda.com/cloud-data-platform/manage/terraform-provider/","status":"documented","summary":"Redpanda documents a Cloud Terraform provider for networks, clusters and data-plane resources, with separate BYOVPC modules for AWS/GCP and a BYOVNet module for Azure. Select the BYOC cluster type, customer-managed resource configuration and throughput tier, pin provider/module versions and review replacement behavior. The provider automates the managed Cloud service, not installation of self-managed Community brokers."},"licensePricing":{"reviewed":"2026-11-21","scope":"Redpanda Cloud BYOC service pricing model; no Community licence or hosted Serverless price applied to BYOC","source":"https://www.redpanda.com/pricing","status":"documented","summary":"The vendor distinguishes Redpanda Cloud BYOC as a fully managed commercial service with an annual commitment and a sales-led trial/quote. Its customer-cloud infrastructure and agreed service charges require separate assessment; self-managed Community or Enterprise software terms are different offerings."},"marketplace":{"availability":"edition-dependent","reviewed":"2026-11-14","scope":"Redpanda Cloud marketplace subscription and BYOC path; selected offer terms apply","source":"https://docs.redpanda.com/cloud-data-platform/billing/aws-commit/","status":"documented","summary":"Redpanda documents an AWS Marketplace private-offer subscription workflow and links it to BYOC cluster creation. Confirm that the order is for the intended BYOC deployment, not a vendor-account cluster."},"sso":{"availability":"available","reviewed":"2026-11-21","scope":"Vendor-operated Cloud control-plane user SSO for a BYOC organisation; data-plane broker/client authentication is separate","source":"https://docs.redpanda.com/cloud-data-platform/security/cloud-authentication/","status":"documented","summary":"Redpanda Cloud documents organisation user login through an OIDC-compliant identity provider with discovery. An organisation administrator configures and enables the connection, with optional enrolment and group-based permissions. The BYOC pricing page includes OIDC SSO in that service.","supportingSources":[{"title":"BYOC service identity features","url":"https://www.redpanda.com/pricing"}]}},"id":"redpanda","infrastructure":["servers"],"infrastructureNotes":"BYOC uses a customer-cloud cluster and Kubernetes infrastructure. Redpanda’s separately hosted Serverless service is outside this listing.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.redpanda.com/cloud-data-platform/get-started/byoc-arch/"],"install":"Redpanda Cloud BYOC provisioning","installMethods":["vendor-assisted"],"kind":"platform","license":"Commercial","licenseModel":"commercial-only","licenseModelNotes":"This listing covers the commercially provided managed/BYOC service, not a separately licensed open-source engine or library.","licenseModelSources":["https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/"],"licenseReviewed":"2026-11-10","model":"BYOC","modelLabel":"Vendor-operated BYOC","name":"Redpanda BYOC","notes":"BYOC supports AWS and Google Cloud VPCs and Azure VNets. BYOVPC/BYOVNet lets the customer provision networking first. Review agent permissions and emergency support access. Redpanda Cloud's November update adds Load Factor dashboard metrics for BYOC deployments on version 26.2 or later. Treat the October BYOVNet, self-service scaling, and Azure tier announcements as separate earlier changes when planning upgrades.","operationReview":{"controlPlane":"vendor-hosted","modelLabel":"Vendor-operated BYOC","operator":"vendor","reviewed":"2026-11-20","source":"https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/","summary":"Redpanda provisions, monitors and upgrades the cluster using delegated access to the customer cloud account. Customer-managed networking is a separate BYOVPC/BYOVNet option.","supportingSources":[{"title":"BYOC managed control plane and customer data plane","url":"https://docs.redpanda.com/cloud-data-platform/get-started/byoc-arch/"}]},"operations":"Redpanda manages provisioning, monitoring and upgrades with the permissions you grant.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"BYOC deployment options","url":"https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/"},{"title":"BYOC cluster and Kubernetes architecture","url":"https://docs.redpanda.com/cloud-data-platform/get-started/byoc-arch/"},{"title":"Redpanda Cloud what's new","url":"https://docs.redpanda.com/cloud-data-platform/get-started/whats-new-cloud/"}],"url":"https://launchinyourcloud.com/directory/redpanda/","website":"https://www.redpanda.com/"},{"architecture":"RegScale application containers, SQL database and persistent evidence storage on ECS/EKS, ACA/AKS or Cloud Run/GKE.","categories":["policy-procedure-management"],"category":"Policy \u0026 procedure management","categoryFit":{"policy-procedure-management":"Commercial self-hosted governance and policy platform with provider-specific container and Kubernetes guides."},"cloudEvidence":[{"clouds":["aws"],"notes":"RegScale application containers, SQL database and persistent evidence storage on ECS/EKS, ACA/AKS or Cloud Run/GKE. The guides describe the actual application and evidence storage in customer cloud resources. The reviewed core chart is 3.2.0 with appVersion 6.35.0.1; the separate orchestration-hub chart has a different appVersion. Chart creation timestamps do not establish application release publication dates.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"AWS ECS","url":"https://regscale.readme.io/docs/aws-ecs.md","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"RegScale application containers, SQL database and persistent evidence storage on ECS/EKS, ACA/AKS or Cloud Run/GKE. The guides describe the actual application and evidence storage in customer cloud resources. The reviewed core chart is 3.2.0 with appVersion 6.35.0.1; the separate orchestration-hub chart has a different appVersion. Chart creation timestamps do not establish application release publication dates.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Azure ACA","url":"https://regscale.readme.io/docs/azure-aca.md","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"RegScale application containers, SQL database and persistent evidence storage on ECS/EKS, ACA/AKS or Cloud Run/GKE. The guides describe the actual application and evidence storage in customer cloud resources. The reviewed core chart is 3.2.0 with appVersion 6.35.0.1; the separate orchestration-hub chart has a different appVersion. Chart creation timestamps do not establish application release publication dates.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"GCP Cloud Run","url":"https://regscale.readme.io/docs/gcp-cloud-run.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 self-hosted governance and policy platform with provider-specific container and Kubernetes guides.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Current RegScale component/tier baselines; evaluation, production and HA distinguished","source":"https://regscale.readme.io/docs/sizing-guide","status":"documented","summary":"The sizing guide separates evaluation (web 2 vCPU/4 GB, database 4 vCPU/16 GB) from recommended production (web 4 vCPU/8 GB, database 8 vCPU/32 GB). Its HA tier starts with two or more web nodes and separately sized database availability. Monitor actual imports, users, reporting, storage and backups rather than treating these as workload guarantees."},"iac":{"artifactRef":"Current vendor guide reviewed on this date","artifactUrl":"https://regscale.readme.io/docs/aws-ecs","reviewed":"2026-11-21","scope":"RegScale current vendor AWS ECS deployment reference","source":"https://regscale.readme.io/docs/aws-ecs","status":"documented","summary":"The AWS guide supplies an ECS Fargate task definition and CLI workflow with ALB/TLS, EFS, external SQL Server and secrets; Kubernetes deployment is separately documented. Select compatible image/chart versions and licences. The example is configurable infrastructure guidance, not a complete turnkey HA stack.","supportingSources":[{"title":"Kubernetes deployment","url":"https://regscale.readme.io/docs/kubernetes-deployment"}]},"licensePricing":{"reviewed":"2026-11-19","scope":"RegScale; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://regscale.readme.io/docs/setup-general.md","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-21","scope":"Current RegScale tenant user federation and configuration","source":"https://regscale.readme.io/docs/setup-single-sign-on-sso","status":"documented","summary":"The vendor documents OAuth2/OIDC or SAML2 user SSO, with only one active method per tenant and configured first-login provisioning. Set issuer/client or metadata, identity claims and role policy for the selected installation; orchestration-hub compatibility and service credentials are separate."}},"id":"regscale","infrastructure":["servers"],"infrastructureNotes":"RegScale application containers, SQL database and persistent evidence storage on ECS/EKS, ACA/AKS or Cloud Run/GKE. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://regscale.readme.io/docs/aws-ecs.md","https://regscale.readme.io/docs/azure-aca.md","https://regscale.readme.io/docs/gcp-cloud-run.md"],"install":"Kubernetes manifests","installMethods":["kubernetes"],"kind":"product","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://regscale.readme.io/docs/setup-general.md","https://regscale.com/enterprise-software-license-agreement/"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"RegScale","notes":"The guides describe the actual application and evidence storage in customer cloud resources. The reviewed core chart is 3.2.0 with appVersion 6.35.0.1; the separate orchestration-hub chart has a different appVersion. Chart creation timestamps do not establish application release publication dates.","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","url":"https://regscale.readme.io/docs/aws-ecs.md"},{"title":"Azure ACA","url":"https://regscale.readme.io/docs/azure-aca.md"},{"title":"GCP Cloud Run","url":"https://regscale.readme.io/docs/gcp-cloud-run.md"},{"title":"K8s Helm","url":"https://regscale.readme.io/docs/kubernetes-deployment.md"},{"title":"Policies Module","url":"https://regscale.readme.io/docs/policies.md"},{"title":"RegScale Licensing Docs","url":"https://regscale.readme.io/docs/setup-general.md"},{"title":"RegScale ESLA","url":"https://regscale.com/enterprise-software-license-agreement/"},{"title":"Helm Index YAML","url":"https://regscale.github.io/helm/index.yaml"}],"url":"https://launchinyourcloud.com/directory/regscale/","website":"https://regscale.readme.io/docs/aws-ecs.md"},{"architecture":"Customer-operated DAM application, database and asset storage","categories":["digital-asset-management"],"category":"Digital asset management","categoryFit":{"digital-asset-management":"Dedicated digital asset management for organizing, finding and distributing media. This entry covers self-installation, not vendor-hosted free or managed cloud plans. Validate production sizing and backup design."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"The vendor explicitly identifies AWS, Azure and Google Cloud for self-installation, alongside its separate hosted service. The linked Docker/source installation instructions establish the customer-operated application path; select compatible dependencies and arrange support separately.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"ResourceSpace self-installation cloud compatibility","url":"https://www.resourcespace.com/get?from_rs=true","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","cloudScope":"Documented provider-specific deployment","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":"Open-source digital asset management deployed on your own infrastructure.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Complete self-hosted ResourceSpace deployment; current version and selected preview/AI integrations affect sizing","source":"https://www.resourcespace.com/knowledge-base/systemadmin/general_requirements","status":"inconclusive","summary":"The official requirements specify its LAMP stack and preview-processing tools, but do not establish a quantitative whole-host CPU/RAM/storage floor for the intended DAM workload. PHP limits and hosted storage allowances are not production capacity for originals, previews, video jobs, database and replicas."},"iac":{"artifactRef":"repository default branch (moving)","artifactUrl":"https://github.com/resourcespace/docker","reviewed":"2026-11-14","scope":"Official ResourceSpace Docker recipe","source":"https://github.com/resourcespace/docker","status":"documented","summary":"The official Docker guide links this application/database deployment repository and requires replacing database credentials before building the stack."},"licensePricing":{"reviewed":"2026-11-20","scope":"ResourceSpace self-hosted software pricing; review the actual software licence and any hosting/support agreement separately","source":"https://www.resourcespace.com/faq","status":"documented","summary":"The vendor FAQ states that local installation has no software licence fee or per-user charge. Paid hosting, technical/customer support and services are separate. The hosted free-storage allowance does not establish a self-hosted infrastructure cost or include a support contract."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"ResourceSpace self-hosted SAML plugin; an existing compatible IdP and administrator configuration are required","source":"https://www.resourcespace.com/knowledge-base/plugins/simplesaml","status":"documented","summary":"ResourceSpace publishes a SimpleSAMLphp-based plugin for SAML 2.0 identity-provider login. Enable the plugin and exchange provider metadata; group mapping, local-login fallback and share-access rules are configurable. Metadata-URL handling and migration steps depend on the ResourceSpace/plugin version."}},"id":"resourcespace","infrastructure":["servers"],"infrastructureNotes":"The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://www.resourcespace.com/get?from_rs=true","https://www.resourcespace.com/knowledge-base/systemadmin/install_docker"],"install":"Official Docker Compose or source/LAMP installation","installMethods":["docker","source"],"kind":"product","license":"Open source; paid hosting and support available separately","licenseModel":"open-source","licenseModelNotes":"ResourceSpace publishes its self-hosted code under a permissive BSD-style license allowing modification and redistribution, with attribution and derivative-name trademark conditions. Paid hosting/support is separate, not evidence of proprietary feature code; inspect the actual release license for exact terms.","licenseModelSources":["https://www.resourcespace.com/docs/ResourceSpace_License_Agreement.pdf","https://www.resourcespace.com/faq","https://www.resourcespace.com/terms"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"ResourceSpace Self-Hosted","notes":"The official download page explicitly names AWS, Azure and Google Cloud for self-installed Docker deployments. The installation guide provides the official repository and Compose instructions. Other provider support is not inferred from Docker portability.","operations":"Customer manages the application, database, asset storage, backups and upgrades.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Self-installation and named cloud platforms","url":"https://www.resourcespace.com/get?from_rs=true"},{"title":"Official Docker installation steps","url":"https://www.resourcespace.com/knowledge-base/systemadmin/install_docker"},{"title":"Product and self-hosting FAQ","url":"https://www.resourcespace.com/faq"},{"title":"Licensing and edition terms","url":"https://www.resourcespace.com/docs/ResourceSpace_License_Agreement.pdf"},{"title":"Licensing and edition terms","url":"https://www.resourcespace.com/terms"}],"url":"https://launchinyourcloud.com/directory/resourcespace/","website":"https://www.resourcespace.com/"},{"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"},{"architecture":"Customer-managed SAP Business One application and a certified database on cloud VMs.","categories":["erp-crm"],"category":"ERP \u0026 CRM","categoryFit":{"erp-crm":"Licensed ERP for financials, purchasing, inventory and customer operations."},"cloudEvidence":[{"clouds":["azure"],"notes":"Customer-managed SAP Business One application and a certified database on cloud VMs. The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.","reviewed":"2026-11-19","sourceType":"provider-guide","title":"Azure Docs","url":"https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Customer-managed SAP Business One application and a certified database on cloud VMs. The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.","reviewed":"2026-11-19","sourceType":"provider-guide","title":"GCP Docs","url":"https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide","vendorSupport":"not-assessed"},{"clouds":["alibaba"],"notes":"Customer-managed SAP Business One application and a certified database on cloud VMs. The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Alibaba Docs","url":"https://www.alibabacloud.com/help/en/sap-solution/sap-b1-implementation-guide","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["azure","gcp","alibaba"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"alibaba","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Licensed ERP for financials, purchasing, inventory and customer operations.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Business One 10.0 for SAP HANA on Google Cloud; CPU, memory, storage and redundancy require a selected certified configuration","source":"https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide","status":"inconclusive","summary":"The provider planning guide requires an SAP-certified HANA machine and workload-specific memory/storage sizing. Its 32-vCPU/834-GB disk performance example is not a universal Business One minimum, and the documented single-node architecture is not an HA design for the proposed workload."},"iac":{"reviewed":"2026-11-20","scope":"Business One for SAP HANA on Google Cloud; not the SQL Server edition or an end-to-end HA template","source":"https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide","status":"documented","summary":"The Google Cloud guide provisions SAP HANA using its Terraform scale-up guide, then installs licensed SAP Business One using the SAP administrator guide. Infrastructure/HANA automation is not a complete Business One application installer; acquire and version-match SAP media and entitlements separately.","supportingSources":[{"title":"Planning and BYOL requirements","url":"https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide"}]},"licensePricing":{"reviewed":"2026-11-19","scope":"SAP Business One (BYOL); software terms only, excluding cloud charges, labour and separately licensed services","source":"https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide","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":"SAP Business One 10.0 IAM documentation; verify the selected feature package, provider and client compatibility","source":"https://help.sap.com/docs/SAP_BUSINESS_ONE_IAM/548d6202b2b6491b824a488cfc447343/13c565324759468490589d60e6c75a92.html","status":"documented","summary":"SAP Business One documents external OpenID Connect identity providers registered in the SLD control center, with provider users bound to company users before activation. This is the Business One IAM path, distinct from the separate Cloud Control Center product.","supportingSources":[{"title":"Identity and authentication introduction","url":"https://help.sap.com/docs/SAP_BUSINESS_ONE_IAM/548d6202b2b6491b824a488cfc447343/7f94c5836fad44e6a02322d39e229cc3.html"}]}},"id":"sap-business-one","infrastructure":["servers"],"infrastructureNotes":"Customer-managed SAP Business One application and a certified database on cloud VMs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure","https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide","https://www.alibabacloud.com/help/en/sap-solution/sap-b1-implementation-guide"],"install":"Package / binary installer","installMethods":["package"],"kind":"product","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.cloud.google.com/sap/docs/sap-business-one-planning-guide","https://help.sap.com/docs/SAP_BUSINESS_ONE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"SAP Business One (BYOL)","notes":"The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.","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":"Azure Docs","url":"https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure"},{"title":"GCP Docs","url":"https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide"},{"title":"Alibaba Docs","url":"https://www.alibabacloud.com/help/en/sap-solution/sap-b1-implementation-guide"},{"title":"GCP SAP B1 BYOL Guide","url":"https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide"},{"title":"SAP Help Portal","url":"https://help.sap.com/docs/SAP_BUSINESS_ONE"},{"title":"SAP B1 2026 News","url":"https://news.sap.com/2026/11/sap-business-one-30-years-of-growing-together/"}],"url":"https://launchinyourcloud.com/directory/sap-business-one/","website":"https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure"},{"architecture":"SAP Process Control 12.0 add-on on NetWeaver AS ABAP 7.52 and a supported database on certified customer cloud VMs.","categories":["policy-procedure-management"],"category":"Policy \u0026 procedure management","categoryFit":{"policy-procedure-management":"Licensed SAP internal-control and policy lifecycle management application."},"cloudEvidence":[{"clouds":["aws"],"notes":"SAP Process Control 12.0 add-on on NetWeaver AS ABAP 7.52 and a supported database on certified customer cloud VMs. The SAP Master Guide identifies the actual add-on, required ABAP platform and installation sequence; pair it with the provider NetWeaver deployment guide. Separate development, test and production landscapes are recommended. Check licensed products, current SAP Notes and the customer-specific Product Availability Matrix; the GRC for HANA 2026 roadmap is not a licence or version for Process Control 12.0.","reviewed":"2026-11-19","sourceType":"provider-guide","title":"AWS SAP NetWeaver Guides","url":"https://docs.aws.amazon.com/sap/latest/sap-netweaver/welcome.html","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"SAP Process Control 12.0 add-on on NetWeaver AS ABAP 7.52 and a supported database on certified customer cloud VMs. The SAP Master Guide identifies the actual add-on, required ABAP platform and installation sequence; pair it with the provider NetWeaver deployment guide. Separate development, test and production landscapes are recommended. Check licensed products, current SAP Notes and the customer-specific Product Availability Matrix; the GRC for HANA 2026 roadmap is not a licence or version for Process Control 12.0.","reviewed":"2026-11-19","sourceType":"provider-guide","title":"Azure SAP Planning Guide","url":"https://learn.microsoft.com/en-us/azure/sap/workloads/planning-guide","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"SAP Process Control 12.0 add-on on NetWeaver AS ABAP 7.52 and a supported database on certified customer cloud VMs. The SAP Master Guide identifies the actual add-on, required ABAP platform and installation sequence; pair it with the provider NetWeaver deployment guide. Separate development, test and production landscapes are recommended. Check licensed products, current SAP Notes and the customer-specific Product Availability Matrix; the GRC for HANA 2026 roadmap is not a licence or version for Process Control 12.0.","reviewed":"2026-11-19","sourceType":"provider-guide","title":"GCP SAP NetWeaver Guides","url":"https://docs.cloud.google.com/sap/docs/netweaver-guides","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":"Licensed SAP internal-control and policy lifecycle management application.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"SAP Process Control workload sizing remains unconfirmed","source":"https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html","status":"inconclusive","summary":"Provider deployment patterns require input sizing and do not establish GRC Process Control production capacity. Obtain supported application/database memory, concurrent control/test workflows, batch jobs, data growth and HA requirements for the selected release."},"iac":{"artifactRef":"Current AWS Launch Wizard SAP guide","artifactUrl":"https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html","reviewed":"2026-11-21","scope":"SAP Process Control parent-platform infrastructure automation; GRC application delivery is separate","source":"https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html","status":"documented","summary":"AWS Launch Wizard automates supported SAP NetWeaver platform landscapes and customer-supplied installation media, including distributed and HA patterns. This provisions the underlying platform, not the Process Control application configuration. Verify GRC/NetWeaver/database compatibility, licences and application installation separately."},"licensePricing":{"reviewed":"2026-11-19","scope":"Selected self-managed application or customer-cloud service; contract confirmation required","source":"https://help.sap.com/doc/3110c68ac50046cc8a035bfe348a9bc3/12.0.13/en-US/loio4570e559019f40a587bc3dce4fafbbbd_4570e559019f40a587bc3dce4fafbbbd_en.pdf","status":"inconclusive","summary":"The master guide identifies the Process Control 12.0 add-on and separately licensed Risk Management and Access Control products, but does not establish the selected customer licence or pricing. The GRC for HANA 2026 roadmap is a different scope."},"sso":{"reviewed":"2026-11-21","scope":"SAP Process Control selected-release user identity remains unconfirmed","source":"https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html","status":"inconclusive","summary":"The reviewed deployment and Process Control material does not establish the selected GRC portal/UI and its actual SSO configuration. NetWeaver or SAP workforce identity features alone do not confirm the complete customer-managed Process Control user login path."}},"id":"sap-process-control","infrastructure":["servers"],"infrastructureNotes":"SAP Process Control 12.0 add-on on NetWeaver AS ABAP 7.52 and a supported database on certified customer cloud VMs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://docs.aws.amazon.com/sap/latest/sap-netweaver/welcome.html","https://learn.microsoft.com/en-us/azure/sap/workloads/planning-guide","https://docs.cloud.google.com/sap/docs/netweaver-guides"],"install":"Package / binary installer","installMethods":["package"],"kind":"product","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://help.sap.com/doc/4d01ca92f5884240ab864b9ff08776a6/12.0.26/en-US/SAP%20GRC%20FOR%20HANA,%202026%20_PAM.pdf","https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"SAP Process Control (On-Premise)","notes":"The SAP Master Guide identifies the actual add-on, required ABAP platform and installation sequence; pair it with the provider NetWeaver deployment guide. Separate development, test and production landscapes are recommended. Check licensed products, current SAP Notes and the customer-specific Product Availability Matrix; the GRC for HANA 2026 roadmap is not a licence or version for Process Control 12.0.","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 SAP NetWeaver Guides","url":"https://docs.aws.amazon.com/sap/latest/sap-netweaver/welcome.html"},{"title":"Azure SAP Planning Guide","url":"https://learn.microsoft.com/en-us/azure/sap/workloads/planning-guide"},{"title":"GCP SAP NetWeaver Guides","url":"https://docs.cloud.google.com/sap/docs/netweaver-guides"},{"title":"AWS Launch Wizard SAP","url":"https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html"},{"title":"GCP Business Suite on HANA","url":"https://docs.cloud.google.com/sap/docs/architectures/sap-business-suite-on-hana"},{"title":"PC 12.0 SP27 Admin Guide PDF (2025-01-08)","url":"https://help.sap.com/doc/d83af7d22baa49829e464111338e9c12/12.0.27/en-US/loio60d658f576b6452eb0f943c04b354018_en.pdf"},{"title":"PC 12.0 Master Guide PDF","url":"https://help.sap.com/doc/3110c68ac50046cc8a035bfe348a9bc3/12.0.13/en-US/loio4570e559019f40a587bc3dce4fafbbbd_4570e559019f40a587bc3dce4fafbbbd_en.pdf"},{"title":"SAP Process Control Course","url":"https://learning.sap.com/courses/discovering-the-key-functionalities-of-sap-process-control"},{"title":"SAP GRC for HANA 2026 PAM PDF","url":"https://help.sap.com/doc/4d01ca92f5884240ab864b9ff08776a6/12.0.26/en-US/SAP%20GRC%20FOR%20HANA,%202026%20_PAM.pdf"},{"title":"SAP On-Premise Variants","url":"https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5"},{"title":"SAP Security Notes (2026-11-10)","url":"https://support.sap.com/en/my-support/knowledge-base/security-notes-news.html"},{"title":"SAP 2040 Maintenance Commitment","url":"https://support.sap.com/en/release-upgrade-maintenance/maintenance-information/maintenance-strategy/s4hana-business-suite7.html"}],"url":"https://launchinyourcloud.com/directory/sap-process-control/","website":"https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html"},{"architecture":"SAP S/4HANA application stack with SAP HANA database and EHS Fiori applications","categories":["energy-environmental-compliance","incident-investigation-management"],"category":"Energy \u0026 environmental compliance","categoryFit":{"energy-environmental-compliance":"Environmental requirements, emissions calculations, compliance scenarios, deviations and reports for environmental authorities.","incident-investigation-management":"Safety incident and near-miss capture, investigations, root-cause classifications and follow-up actions. This is industrial EHS scope, rather than a general legal investigation platform."},"cloudEvidence":[{"clouds":["aws"],"notes":"AWS Launch Wizard provisions customer resources and can install customer-provided SAP S/4HANA software. Evidence covers the underlying S/4HANA platform; confirm EHS licensing, supported sizing, database and SAP release before deployment.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"Customer-provided SAP S/4HANA deployment on AWS","url":"https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Microsoft documents S/4HANA infrastructure in a customer Azure subscription. Evidence covers the platform hosting option; confirm EHS modules, SAP licensing, supported operating systems and software installation separately.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"SAP S/4HANA infrastructure deployment on Azure","url":"https://learn.microsoft.com/en-us/azure/sap/center-sap-solutions/deploy-s4hana","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Google documents S/4HANA on SAP-certified Compute Engine infrastructure. This is platform hosting evidence; EHS functionality, licenses and supported SAP configurations still require confirmation.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"SAP S/4HANA reference architecture on Google Cloud","url":"https://docs.cloud.google.com/sap/docs/architectures/sap-s4hana-on-gcp","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","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":"Customer-operated SAP S/4HANA environmental compliance and safety incident-management capabilities.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"S/4HANA EHS workload sizing remains unconfirmed","source":"https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html","status":"inconclusive","summary":"Launch Wizard selects resources from supplied SAP requirements; it does not establish an EHS-specific capacity baseline. Obtain certified S/4HANA/HANA sizing for application/database memory, batch/analytics, data volume and HA rather than interpreting supported maximum memory as a minimum."},"iac":{"artifactRef":"Current AWS Launch Wizard supported SAP deployment guide","artifactUrl":"https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html","reviewed":"2026-11-21","scope":"Provider-documented S/4HANA deployment supporting the EHS parent platform; not a packaged EHS solution","source":"https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html","status":"documented","summary":"AWS Launch Wizard can provision SAP landscapes and install customer-provided supported S/4HANA software, including separate multi-instance/HA patterns. Supply licensed installation media and validate supported releases. This is underlying S/4HANA platform automation; EHS activation, business configuration and data migration remain separate."},"licensePricing":{"reviewed":"2026-11-16","scope":"S/4HANA on-premise deployment model; not a module-specific EHS quote","source":"https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5","status":"documented","summary":"SAP distinguishes customer-managed S/4HANA on-premise perpetual licensing from subscription-based Private Edition with SAP technical managed services. Do not substitute a cloud subscription for the customer-operated scope; EHS module rights and implementation pricing require the actual agreement."},"sso":{"reviewed":"2026-11-21","scope":"Customer-operated S/4HANA EHS identity deployment remains unconfirmed","source":"https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html","status":"inconclusive","summary":"The reviewed EHS and deployment material does not establish the selected application UI, release and complete identity configuration. SAP platform authentication options require the actual Fiori/ABAP/GUI entry points and compatible identity components; do not infer a ready EHS federation setup from a generic SAP capability."}},"id":"sap-s4hana-ehs","infrastructure":["servers"],"infrastructureNotes":"Customer-operated SAP application and HANA database services run on provisioned infrastructure. This is the on-premise edition, separate from SAP-managed cloud services.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://help.sap.com/docs/r/product/SAP_S4HANA_ON-PREMISE/latest"],"install":"Install the licensed SAP S/4HANA on-premise edition and configure the selected EHS components using SAP implementation guides","installMethods":["vendor-assisted"],"kind":"product","license":"Commercial SAP S/4HANA on-premise licensing; verify EHS component entitlements","licenseModel":"commercial-only","licenseModelNotes":"The listed on-premise edition uses SAP commercial software licensing. The official deployment comparison describes its perpetual-license model; the customer agreement defines the exact component rights.","licenseModelSources":["https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"SAP S/4HANA EHS — Customer-Operated","notes":"The on-premise edition is explicitly customer-installed and customer-operated. This entry covers its EHS components, not SAP-managed Cloud Private Edition or Public Edition. Check the selected release, component entitlements and implementation scope. Environmental reporting still requires configured requirements and reliable source data.","operations":"Customer manages the application and database infrastructure, installation, upgrades, access, backups and EHS configuration; agree implementation and support arrangements.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Customer-operated on-premise installation and operations","url":"https://help.sap.com/docs/r/product/SAP_S4HANA_ON-PREMISE/latest"},{"title":"Environment Management scope","url":"https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/1b3596cc5dd5428d887966a4193ddc29/6d08555321d77d77e10000000a441470.html"},{"title":"Current incident-investigation configuration","url":"https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/f5d3e1005efd4e86acf9a65abf428082/96e81bbdc3c54a70b3b374b182bb87c0.html?locale=en-US\u0026version=2025.000"},{"title":"Commercial model and deployment responsibilities","url":"https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5"}],"url":"https://launchinyourcloud.com/directory/sap-s4hana-ehs/","website":"https://help.sap.com/docs/r/product/SAP_S4HANA_ON-PREMISE/latest"},{"advisories":[{"action":"Apply the exact fixed maintenance level for each affected component and review certificate trust.","conditions":"Bundled trust stores, certificates, and Brotli-using components determine exposure.","id":"sas-viya-november-2026-security-bulletins","listingIds":["sas-viya-platform"],"reviewed":"2026-11-18","scope":"Affected and fixed maintenance levels vary by Viya component and branch; consult both vendor matrices.","source":"https://support.sas.com/en/security-bulletins/compromised-emudhra-certificates-vulnerabilities.html","summary":"SAS bulletins address compromised eMudhra certificates and critical Brotli CVE-2026-111497 in specified Viya components and branches.","supportingSources":[{"title":"Brotli CVE-2026-111497 bulletin","url":"https://support.sas.com/en/security-bulletins/google-brotli-decoder-vulnerability-cve-2026-111497.html"}],"title":"SAS Viya November 2026 certificate and Brotli bulletins","type":"security-advisory"}],"architecture":"Customer-operated EKS, AKS or GKE cluster running SAS Viya containers, CAS, PostgreSQL integrations and persistent storage.","categories":["data-analytics","ai-tools"],"category":"Data \u0026 analytics","categoryFit":{"ai-tools":"Model development, machine learning, model management and AI operationalization; exact products depend on the licensed order.","data-analytics":"Enterprise data preparation, analytics, reporting and decisioning delivered by the customer-operated Viya platform."},"cloudEvidence":[{"clouds":["aws"],"notes":"Official SAS Terraform provisions customer AWS resources including EKS, storage and optional RDS, after which the customer deploys licensed Viya assets.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"SAS Viya infrastructure on AWS","url":"https://github.com/sassoftware/viya4-iac-aws","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Official SAS Terraform provisions customer Azure resources including AKS, storage and optional PostgreSQL, after which the customer deploys licensed Viya assets.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"SAS Viya infrastructure on Azure","url":"https://github.com/sassoftware/viya4-iac-azure","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Official SAS Terraform provisions customer Google Cloud resources including GKE, storage and optional Cloud SQL, after which the customer deploys licensed Viya assets.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"SAS Viya infrastructure on Google Cloud","url":"https://github.com/sassoftware/viya4-iac-gcp","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":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Commercial analytics and AI platform deployed into a customer-operated managed Kubernetes cluster.","diligence":{"airGap":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"SAS Viya 2025.10 air-gapped deployment procedure; confirm compatibility with the purchased cadence assets","source":"https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/dplyml0phy0dkr/content/dplyml0phy0dkr.pdf?locale=en","status":"documented","summary":"The reviewed 2025.10 guide documents air-gapped deployment using SAS Mirror Manager: download entitled content outside the isolated network, transfer it and populate an internal registry without contacting the SAS entitlement/container services. Match the order assets, cadence and component dependencies."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for SAS Viya Platform; unresolved within this edition/deployment","source":"https://www.sas.com/en_us/software/viya/how-to-buy-sas-viya.html","status":"inconclusive","summary":"The purchasing page links packaged Viya offerings, but does not establish qualifying charges for this licensed platform deployment under the buyer cloud agreement. Workbench is separate."},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en","status":"inconclusive","summary":"The reviewed SAS Viya Platform 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://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en","status":"inconclusive","summary":"Choose the licensed Viya modules/cadence, CAS/compute pools, data-in-memory requirements, HA services and storage throughput. The order-specific topology and commercial licence price are not public. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"SAS Viya platform and workload-specific sizing; reviewed 2025.10 requirements","source":"https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en","status":"documented","summary":"Sizing depends on licensed workloads, CAS/compute roles, Kubernetes node pools, storage bandwidth and PostgreSQL. The requirements include provider-specific sizing; 100 users and 1 TB alone do not determine a supported HA cluster."},"iac":{"artifactRef":"default branch (moving; select a compatible release)","artifactUrl":"https://github.com/sassoftware/viya4-iac-aws","reviewed":"2026-11-17","scope":"SAS-owned AWS IaC repository","source":"https://github.com/sassoftware/viya4-iac-aws","status":"documented","summary":"SAS publishes Terraform for AWS infrastructure and separate deployment automation for the licensed Viya manifests. Pin a compatible tooling revision and SAS order assets; the Apache-licensed automation does not license the application.","supportingSources":[{"title":"Viya deployment automation","url":"https://github.com/sassoftware/viya4-deployment"}]},"licensePricing":{"reviewed":"2026-11-17","scope":"SAS Viya Platform: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://documentation.sas.com/api/docsets/calintro/v_001/content/calintro.pdf?locale=en","status":"documented","summary":"SAS Viya requires a commercial order, licensed deployment assets and a JWT license. Apache licenses on the public infrastructure repositories apply to tooling, not the Viya product distribution."},"marketplace":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"Viya software procurement; offering selection required","source":"https://www.sas.com/en_us/software/viya/how-to-buy-sas-viya.html","status":"documented","summary":"SAS documents buying Viya through cloud marketplaces and specifically links Microsoft Marketplace. Select the matching packaged offering and delivery/entitlement terms; this is not proof every Marketplace offer matches a Terraform-based licensed deployment."},"release":{"reviewed":"2026-11-17","scope":"Viya platform cadence policy; exact order/version assets remain separate","source":"https://documentation.sas.com/api/collections/itopscdc/v_066/docsets/itopscon/content/itopscon.pdf?locale=en","status":"documented","summary":"SAS publishes monthly Stable releases and Long-Term Support releases about every six months, aggregating prior Stable changes. Obtain deployment assets for the purchased order and cadence; automation repository tags are not Viya application releases."},"scim":{"availability":"available","reviewed":"2026-11-17","scope":"Viya SCIM requirements; selected identity configuration; reviewed 2025.10 requirements","source":"https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en","status":"documented","summary":"Viya supports SCIM 2.0, tested with Okta and Entra ID. Disable LDAP when using SCIM; SAML/OIDC, HTTPS, a public-CA certificate and inbound IdP access are required. Google Identity provisioning is not supported in this reviewed configuration."},"securityControls":{"reviewed":"2026-11-18","scope":"Viya installation security prerequisites; reviewed 2025.10 requirements Affected and fixed maintenance levels vary by Viya component and branch; consult both vendor matrices.","source":"https://support.sas.com/en/security-bulletins/compromised-emudhra-certificates-vulnerabilities.html","status":"documented","summary":"The requirements separate service/user accounts, elevated deployment permissions, TLS/identity and database dependencies. Apply the selected platform security configuration; a reference to a security standard is not an independent deployment attestation. Current advisory review: SAS bulletins address compromised eMudhra certificates and critical Brotli CVE-2026-111497 in specified Viya components and branches. Apply the exact fixed maintenance level for each affected component and review certificate trust.","supportingSources":[{"title":"Prior security-controls source","url":"https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en"},{"title":"Brotli CVE-2026-111497 bulletin","url":"https://support.sas.com/en/security-bulletins/google-brotli-decoder-vulnerability-cve-2026-111497.html"}]},"sso":{"availability":"available","reviewed":"2026-11-17","scope":"Reviewed SAS Viya platform requirements; web authentication; reviewed 2025.10 requirements","source":"https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en","status":"documented","summary":"Viya documents SAML and OIDC web SSO. Configure a compatible identity provider and matching certificates; this is distinct from user provisioning."}},"id":"sas-viya-platform","infrastructure":["servers"],"infrastructureNotes":"SAS Viya runs persistent container workloads on managed Kubernetes with CAS compute, shared storage and PostgreSQL. Terraform projects provision customer infrastructure but do not complete the application deployment.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en","https://github.com/sassoftware/viya4-deployment"],"install":"Provision EKS, AKS or GKE with SAS Terraform projects, then deploy Kubernetes manifests generated through Kustomize and SAS automation","installMethods":["terraform","kubernetes","other"],"kind":"platform","license":"Commercial SAS Viya licensing; deployment assets and a JWT license are delivered for the customer's software order.","licenseModel":"commercial-only","licenseModelNotes":"SAS Viya requires a commercial order, licensed deployment assets and a JWT license. Apache licenses on the public infrastructure repositories apply to tooling, not the Viya product distribution.","licenseModelSources":["https://documentation.sas.com/api/docsets/calintro/v_001/content/calintro.pdf?locale=en","https://www.sas.com/en_us/software/viya/how-to-buy-sas-viya.html"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"SAS Viya Platform","notes":"The public SAS infrastructure repositories are Apache-licensed deployment tooling; SAS Viya itself is commercial software and requires licensed order assets and a JWT license. Kubernetes and PostgreSQL are mandatory. SAS states that its infrastructure-as-code projects satisfy most, not all, deployment requirements. The viya4-deployment project can patch the same manifest but does not move an installation to a different cadence, version or software offering. SAS November bulletins cover compromised eMudhra certificates and critical Brotli CVE-2026-111497 across specified Viya branches. Use the vendor matrices to identify the exact affected component and fixed maintenance level; do not treat a generic Viya version as sufficient.","operations":"Customer manages Kubernetes, networking, ingress, storage, PostgreSQL, identity, sizing, backups, platform updates and licensed deployment assets.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Introduction to SAS Viya Platform","url":"https://documentation.sas.com/api/docsets/calintro/v_001/content/calintro.pdf?locale=en"},{"title":"SAS Viya Platform system requirements","url":"https://documentation.sas.com/api/collections/itopscdc/v_069/docsets/itopssr/content/itopssr.pdf?locale=en"},{"title":"AWS infrastructure as code","url":"https://github.com/sassoftware/viya4-iac-aws"},{"title":"Azure infrastructure as code","url":"https://github.com/sassoftware/viya4-iac-azure"},{"title":"Google Cloud infrastructure as code","url":"https://github.com/sassoftware/viya4-iac-gcp"},{"title":"SAS Viya deployment automation","url":"https://github.com/sassoftware/viya4-deployment"},{"title":"How to buy SAS Viya","url":"https://www.sas.com/en_us/software/viya/how-to-buy-sas-viya.html"},{"title":"SAS compromised eMudhra certificates bulletin","url":"https://support.sas.com/en/security-bulletins/compromised-emudhra-certificates-vulnerabilities.html"},{"title":"SAS Brotli CVE-2026-111497 bulletin","url":"https://support.sas.com/en/security-bulletins/google-brotli-decoder-vulnerability-cve-2026-111497.html"}],"url":"https://launchinyourcloud.com/directory/sas-viya-platform/","website":"https://www.sas.com/en_us/software/viya.html"},{"architecture":"Customer-operated ScyllaDB nodes with cloud networking and local or attached persistent storage","categories":["databases-vector"],"category":"Databases \u0026 vector","categoryFit":{"databases-vector":"Distributed NoSQL wide-column database for high-throughput, low-latency application data."},"cloudEvidence":[{"applicableVersions":["2026.3 documentation"],"clouds":["aws"],"notes":"Official instructions launch ScyllaDB AMIs into the customer's AWS VPC and distinguish this self-managed deployment from ScyllaDB Cloud.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Self-managed ScyllaDB 2026.3 on AWS","url":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html","vendorSupport":"not-assessed"},{"applicableVersions":["2026.3 documentation"],"clouds":["gcp"],"notes":"Official instructions use the customer's active Google Cloud account and gcloud to launch ScyllaDB images and call the deployment self-managed.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Self-managed ScyllaDB 2026.3 on Google Cloud","url":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-gcp.html","vendorSupport":"not-assessed"},{"applicableVersions":["2026.3 documentation"],"clouds":["azure"],"notes":"Official instructions use the customer's Azure subscription and resource group to create a ScyllaDB VM and call the deployment self-managed.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Self-managed ScyllaDB 2026.3 on Azure","url":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-azure.html","vendorSupport":"not-assessed"},{"applicableVersions":["2026.3 documentation"],"clouds":["oci"],"notes":"Official instructions deploy the bring-your-own-license ScyllaDB Marketplace image into the customer's OCI tenancy, compartment, VCN and compute instance and call the deployment self-managed.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Self-managed ScyllaDB 2026.3 on OCI","url":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-oci.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","azure","gcp","oci"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[2],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"oci","controlPlane":"not-assessed","evidence":[3],"operator":"customer"}],"description":"Self-managed distributed NoSQL database deployed on customer-controlled cloud virtual machines.","diligence":{"airGap":{"reviewed":"2026-11-19","scope":"ScyllaDB Enterprise Self-Managed: selected customer-operated edition","source":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html","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":"ScyllaDB Enterprise Self-Managed: selected customer-operated edition","source":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html","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":"ScyllaDB Enterprise Self-Managed: selected customer-operated edition","source":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/","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":"ScyllaDB Enterprise Self-Managed: selected customer-operated edition","source":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html","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":"ScyllaDB 2026.3 GCP image launch minimum only; not a cluster-wide production footprint","source":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-gcp.html","status":"documented","summary":"The GCP image launch guide requires at least 2 vCPUs. This bootstrap requirement does not establish production node count, RAM, local SSD capacity, HA, replication, compaction or a 1-TB workload design; follow provider-specific sizing and licence limits separately."},"iac":{"artifactRef":"scylla_cluster_2026.3.6_x86_64.yaml; SHA-256 71c636562d0e5ea54633ba4c0f95a32a1db139726a46923c2372e6550cfb6c7c","artifactUrl":"https://s3.amazonaws.com/downloads.scylladb.com/downloads/scylla/aws/cloudformation/scylla_cluster_2026.3.6_x86_64.yaml","availability":"available","reviewed":"2026-11-19","scope":"AWS x86 sample stack; ARM templates and other providers have separate images and configuration","source":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html","status":"documented","summary":"The AWS guide links a versioned x86 CloudFormation cluster example for 2026.3.6. It provisions EC2 networking and cluster resources and accepts a regional Scylla AMI. Review its public-address/SSH settings, initial credentials, instance count and licence limits; this sample is not a validated production HA or cost design."},"licensePricing":{"availability":"edition-dependent","reviewed":"2026-11-19","scope":"ScyllaDB Enterprise Self-Managed: selected customer-operated edition","source":"https://www.scylladb.com/scylladb-software-license-agreement/","status":"documented","summary":"The current source-available agreement provides a restricted free grant subject to eligibility and aggregate capacity limits; commercial customers and use beyond those terms require a paid agreement. Validate legal eligibility and capacity calculations.","supportingSources":[{"title":"Source-available licensing FAQ","url":"https://www.scylladb.com/source-available-faq/"}]},"marketplace":{"availability":"available","reviewed":"2026-11-19","scope":"ScyllaDB Enterprise Self-Managed: selected customer-operated edition","source":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-oci.html","status":"documented","summary":"ScyllaDB documents a bring-your-own-license Marketplace image for self-managed Enterprise deployment in OCI. The other reviewed cloud paths use vendor images or instructions and do not establish equivalent Marketplace offers."},"release":{"reviewed":"2026-11-19","scope":"ScyllaDB Enterprise Self-Managed: selected customer-operated edition","source":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/","status":"documented","summary":"The current stable self-managed installation documentation is labeled ScyllaDB 2026.3. Verify the exact patch and its support window before deploying provider images or performing an upgrade."},"scim":{"reviewed":"2026-11-19","scope":"ScyllaDB Enterprise Self-Managed: selected customer-operated edition","source":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/","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":"ScyllaDB Enterprise Self-Managed: selected customer-operated edition","source":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/","status":"documented","summary":"The provider guides deploy customer-controlled database nodes and networking. The buyer must explicitly configure authentication, encryption, firewall rules, monitoring, backup and repair; image delivery alone is not a hardened cluster baseline."},"sso":{"reviewed":"2026-11-19","scope":"ScyllaDB Enterprise Self-Managed: selected customer-operated edition","source":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/","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":"scylladb-enterprise-self-managed","infrastructure":["servers"],"infrastructureNotes":"The database runs directly on customer-controlled cloud compute instances; multi-node durability, storage layout and replication are customer-operated.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://docs.scylladb.com/manual/stable/getting-started/install-scylla/"],"install":"Official cloud image/AMI, with a documented AWS CloudFormation cluster example","installMethods":["vm-image","cloudformation"],"kind":"product","license":"ScyllaDB Source Available License Agreement for current Enterprise releases; eligibility and capacity limits apply unless covered by paid terms.","licenseModel":"source-available","licenseModelNotes":"Current ScyllaDB Enterprise is source-available under ScyllaDB's agreement, not an OSI-approved license. The agreement imposes eligibility, usage and commercial-customer restrictions.","licenseModelSources":["https://www.scylladb.com/scylladb-software-license-agreement/","https://www.scylladb.com/source-available-faq/"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"ScyllaDB Enterprise Self-Managed","notes":"Current stable documentation covers ScyllaDB 2026.3 and labels each provider path self-managed, separately from ScyllaDB Cloud. The source-available license is not OSI open source; its free grant has eligibility and aggregate capacity limits, and commercial customers require paid terms.","operations":"Customer manages topology, networking, authentication, capacity, backups, monitoring, patching and upgrades.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Install ScyllaDB 2026.3","url":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/"},{"title":"ScyllaDB Enterprise self-managed product","url":"https://www.scylladb.com/product/"},{"title":"Supported ScyllaDB versions","url":"https://docs.scylladb.com/stable/versioning/version-support.html"},{"title":"ScyllaDB Source Available License Agreement","url":"https://www.scylladb.com/scylladb-software-license-agreement/"},{"title":"Buyer evidence: marketplace","url":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-oci.html"},{"title":"Buyer evidence: commitments","url":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html"},{"title":"Reviewed deployment artifact reference","url":"https://s3.amazonaws.com/downloads.scylladb.com/downloads/scylla/aws/cloudformation/scylla_cluster_2026.3.6_x86_64.yaml"},{"title":"Buyer evidence: footprint","url":"https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-gcp.html"},{"title":"Source-available licensing FAQ","url":"https://www.scylladb.com/source-available-faq/"}],"url":"https://launchinyourcloud.com/directory/scylladb-enterprise-self-managed/","website":"https://www.scylladb.com/product/scylla-enterprise/"},{"advisories":[{"action":"Disable or isolate debug dumper endpoints and verify an upstream fix before treating a newer release as remediated.","conditions":"Requires dumper configuration access and a subsequent model execution reaching a dumper hook. In shared-API mode, an ordinary API key can suffice without a separate admin key; authentication configuration changes exposure.","id":"sglang-cve-2026-111391","listingIds":["sglang"],"reviewed":"2026-11-16","scope":"CVE record: SGLang 0.5.10–0.5.22. The open upstream report and reviewed v0.5.23 code do not establish a fixed release.","source":"https://cveawg.mitre.org/api/cve/CVE-2026-111391","summary":"CVE-2026-111391 identifies code execution in the debug dumper filter. Check the debug endpoint exposure and authentication boundary.","supportingSources":[{"title":"Upstream report and authentication conditions","url":"https://github.com/sgl-project/sglang/issues/44188"},{"title":"Reviewed v0.5.23 filter implementation","url":"https://github.com/sgl-project/sglang/blob/v0.5.23/python/sglang/srt/debug_utils/dumper.py#L1309-L1320"}],"title":"SGLang debug dumper code execution","type":"security-advisory"}],"architecture":"Customer-operated inference server and model weights on configured accelerator hosts","categories":["ai-inference-gateways","ai-tools"],"category":"AI inference \u0026 gateways","categoryFit":{"ai-inference-gateways":"Model-serving framework for LLM and multimodal inference; an inference runtime rather than a full multi-provider governance gateway.","ai-tools":"Customer-operated inference infrastructure for serving supported model weights."},"cloudEvidence":[{"clouds":["gcp"],"notes":"Google explicitly supports SGLang as an alternative model server in its customer-operated multi-cluster GKE inference architecture. The worked manifests use vLLM; SGLang requires its own deployment, serving port, metric mapping and compatible Endpoint Picker image. Review GPU/model requirements, licenses and resource availability.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"SGLang compatibility with GKE Inference Gateway","url":"https://docs.cloud.google.com/kubernetes-engine/docs/how-to/setup-multicluster-inference-gateway","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["gcp"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Release maintenance and contributor participation","url":"https://github.com/sgl-project/sglang/releases"},{"title":"Project and production-use context","url":"https://raw.githubusercontent.com/sgl-project/sglang/main/README.md"}],"summary":"The upstream release history documents hundreds of pull requests from many named contributors and sustained releases; its README describes production use across labs, platforms and enterprises."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Model-serving framework for running supported language and multimodal models on customer-controlled compute.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Model and serving-configuration dependent; complete production footprint unresolved","source":"https://docs.sglang.ai/advanced_features/server_arguments.html","status":"inconclusive","summary":"The server configuration sizes model loading, quantization, parallelism, KV cache and admitted requests through memory controls such as mem-fraction-static. It does not establish one safe CPU/RAM/VRAM minimum. Select model, precision, context, concurrency and availability, then validate the chosen accelerator topology."},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://docs.sglang.io/docs/get-started/install","status":"documented","summary":"The upstream installation guide supplies container, Compose and Kubernetes options for model serving. Match model/backend, accelerator drivers and selected image; examples do not establish a universal GPU or memory minimum."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/sgl-project/sglang/main/LICENSE","status":"documented","summary":"The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Model weights and external model APIs require their own review."},"release":{"releasePublishedAt":"2026-11-02T22:14:10Z","releaseTag":"v0.5.23","reviewed":"2026-11-14","scope":"Upstream sgl-project/sglang release record; commercial editions and deployment packages may differ","source":"https://github.com/sgl-project/sglang/releases/tag/v0.5.23","status":"documented","summary":"The publisher-designated GitHub release checked was v0.5.23, published 2026-11-02. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package."},"securityControls":{"reviewed":"2026-11-16","scope":"Debug dumper trust boundary and deployment precautions; not a blanket claim that all SGLang endpoints or all later releases are unauthenticated","source":"https://github.com/sgl-project/sglang/issues/44188","status":"documented","summary":"The reported shared-API dumper exposure requires DUMPER_SERVER_PORT=reuse and access to configure a filter followed by a model execution. Without a separate admin key, an ordinary API key can reach the route; without any API key, it can be anonymous. A configured admin key is required when present. Keep dumper/debug routes disabled or network-isolated. The CVE enumerates 0.5.10–0.5.22; retained filter code in 0.5.23 is not by itself a complete assessment of every authentication configuration.","supportingSources":[{"title":"Primary CVE record","url":"https://cveawg.mitre.org/api/cve/CVE-2026-111391"},{"title":"SGLang v0.5.23 shared dumper route and authentication level","url":"https://github.com/sgl-project/sglang/blob/v0.5.23/python/sglang/srt/entrypoints/http_server.py"},{"title":"SGLang v0.5.23 filter implementation","url":"https://github.com/sgl-project/sglang/blob/v0.5.23/python/sglang/srt/debug_utils/dumper.py#L1309-L1320"}]},"sso":{"reviewed":"2026-11-20","scope":"Upstream inference-server/API authentication; federation unresolved","source":"https://docs.sglang.ai/advanced_features/server_arguments.html","status":"inconclusive","summary":"Server arguments document inference and administrative API keys with separate endpoint rules. The reviewed upstream configuration does not establish SAML/OIDC login, user provisioning or a supported IdP integration. Confirm a gateway-based identity design instead of treating a static API key as SSO."}},"id":"sglang","infrastructure":["servers"],"infrastructureNotes":"Customer-operated inference server and model weights on configured accelerator hosts. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.sglang.io/docs/get-started/install"],"install":"Install the package or use official containers; the reviewed primary installation path targets Linux with supported NVIDIA GPUs and compatible drivers.","installMethods":["docker","package"],"kind":"product","license":"Apache License 2.0 for upstream SGLang. Model weights and hardware/runtime dependencies have their own licenses.","licenseModel":"open-source","licenseModelNotes":"Apache License 2.0 for upstream SGLang. Model weights and hardware/runtime dependencies have their own licenses. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.","licenseModelSources":["https://raw.githubusercontent.com/sgl-project/sglang/main/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"SGLang","notes":"Model downloads may require external registries and gated-model credentials. Pin compatible model/runtime/image versions and review model-specific permissions. Generic container instructions do not establish deployment badges for every hyperscaler. CVE-2026-111391 rates SGLang 0.5.10 through 0.5.22 critical (CVSS v4.0 9.2) for Python code execution through the debug dumper filter. The upstream report demonstrates the shared-API path with DUMPER_SERVER_PORT=reuse: an ordinary API-key holder can reach it when no separate admin API key is configured; access can be anonymous when no API key is configured. With an admin API key configured, that key is required. Exploitation also requires access to the dumper configuration and a subsequent model execution that reaches a dumper hook. Upstream issue #44188 remains open, and the v0.5.23 tag still contains the eval-based filter path even though that tag is outside the CVE record's enumerated affected range. Do not enable or expose the debug dumper endpoint; restrict it at the network layer and verify an upstream fix before treating a later version as remediated.","operations":"Customer manages accelerator capacity, model artifacts, runtime compatibility, endpoint access, including isolation of debug and dumper routes, monitoring, and upgrades.","publisher":false,"reviewed":"2026-11-16","sources":[{"title":"Official installation and runtime","url":"https://docs.sglang.io/docs/get-started/install"},{"title":"Upstream project and capabilities","url":"https://github.com/sgl-project/sglang"},{"title":"Current upstream license","url":"https://raw.githubusercontent.com/sgl-project/sglang/main/LICENSE"},{"title":"CVE-2026-111391 debug dumper filter code injection","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-111391"},{"title":"Upstream SGLang dumper-filter RCE issue","url":"https://github.com/sgl-project/sglang/issues/44188"},{"title":"SGLang v0.5.23 debug dumper implementation","url":"https://github.com/sgl-project/sglang/blob/v0.5.23/python/sglang/srt/debug_utils/dumper.py#L1309-L1320"},{"title":"CVE-2026-111391 primary record and affected-version range","url":"https://cveawg.mitre.org/api/cve/CVE-2026-111391"}],"url":"https://launchinyourcloud.com/directory/sglang/","website":"https://sglang.io/"},{"architecture":"Customer-operated observability services, OpenTelemetry collection and persistent analytical storage","categories":["observability"],"category":"Observability","categoryFit":{"observability":"Application observability over OpenTelemetry traces, metrics and logs; applications must be instrumented and collection configured."},"cloudEvidence":[{"clouds":["aws"],"notes":"Official self-hosting instructions install SigNoz and its storage components on Amazon EKS; this is not the vendor-hosted SigNoz Cloud service.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"SigNoz self-hosting on Amazon EKS","url":"https://signoz.io/docs/install/kubernetes/aws/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Official self-hosting instructions install SigNoz and its storage components on Azure Kubernetes Service; this is not the vendor-hosted SigNoz Cloud service.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"SigNoz self-hosting on Azure Kubernetes Service","url":"https://signoz.io/docs/install/kubernetes/aks/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Official self-hosting instructions install SigNoz and its storage components on Google Kubernetes Engine; this is not the vendor-hosted SigNoz Cloud service.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"SigNoz self-hosting on Google Kubernetes Engine","url":"https://signoz.io/docs/install/kubernetes/gcp/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Maintenance and community contributor credits","url":"https://github.com/SigNoz/signoz/releases"},{"title":"Public upstream project","url":"https://github.com/SigNoz/signoz"}],"summary":"The active release stream records recent maintenance and multiple named contributors and first-time contributions across releases."},"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":"OpenTelemetry-based application observability platform for traces, metrics and logs.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Current supported Docker installation requirements; application, storage and collector roles require workload sizing","source":"https://signoz.io/docs/install/docker/","status":"documented","summary":"The supported Foundry/Docker installation requires at least 4 GB allocated to Docker for its local stack. Production ingestion rate, ClickHouse/Keeper topology, retention and replicas can raise capacity substantially; this is an installation baseline, not a 1 TB HA telemetry sizing guarantee."},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://signoz.io/docs/install/docker/","status":"documented","summary":"The supported Docker workflow uses Foundry to generate/manage the Compose deployment. The older install.sh and bundled deploy files are deprecated from v0.130.0; do not use them as the current installation artifact."},"licensePricing":{"reviewed":"2026-11-20","scope":"Published Community/Enterprise source boundary; not a hosted usage-price quote","source":"https://github.com/SigNoz/signoz/blob/v0.150.0/LICENSE","status":"documented","summary":"The v0.150.0 licence applies MIT terms to the core and explicitly excludes ee/ and cmd/enterprise/, which have separate Enterprise terms. Community source rights do not grant paid SAML/OIDC features or commercial support. Self-hosted licence, ingestion/storage infrastructure and SigNoz Cloud charges are separate."},"release":{"releasePublishedAt":"2026-11-13T13:47:26Z","releaseTag":"v0.150.0","reviewed":"2026-11-14","scope":"Upstream SigNoz/signoz release record; commercial editions and deployment packages may differ","source":"https://github.com/SigNoz/signoz/releases/tag/v0.150.0","status":"documented","summary":"The publisher-designated GitHub release checked was v0.150.0, published 2026-11-13. 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 SigNoz edition-specific protocols","source":"https://signoz.io/docs/manage/administrator-guide/sso/overview/","status":"documented","summary":"SAML and OIDC require Enterprise Self-Hosted. Google Workspace OAuth2 is also documented for Community Edition. Login-time account creation is distinct from automated deprovisioning."}},"id":"signoz","infrastructure":["servers"],"infrastructureNotes":"Customer-operated observability services, OpenTelemetry collection and persistent analytical storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. From v0.150.0, log bodies are dual-ingested during migration. The vendor recommends 25% OpenTelemetry Collector CPU and memory headroom, 15% ClickHouse CPU headroom, and log-disk growth approximately equal to the existing body column.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://signoz.io/docs/install/docker/","https://signoz.io/docs/operate/migration/upgrade-0-150/","https://signoz.io/guides/json-logs-migration/"],"install":"Use the supported Foundry workflow to generate and run the Docker Compose stack; the older bundled install script/deploy files are deprecated.","installMethods":["docker"],"kind":"product","license":"MIT Expat for core code; ee/ enterprise code has its own separate license.","licenseModel":"open-source","licenseModelNotes":"MIT Expat for core code; ee/ enterprise code has its own separate license. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.","licenseModelSources":["https://raw.githubusercontent.com/SigNoz/signoz/develop/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"SigNoz Self-Hosted","notes":"The reviewed guide is explicitly for self-hosted Community without a license. Commercial features require their stated terms. Instrumentation can capture sensitive payloads, so configure capture and retention according to the data being monitored. SigNoz v0.150.0 automatically migrates stored alert rules to v2alpha1 but removes the v1 rule APIs and GET /api/v2/rules. Update API scripts, move Terraform configurations from signoz_alert to signoz_rule, use SigNoz Operator v0.0.5 or newer, and back up the metastore before upgrading. The release also begins dual-ingesting log bodies into native JSON storage; plan additional collector, ClickHouse, and log-disk capacity before rollout.","operations":"Customer manages collectors, storage capacity, retention, authentication, backups, alert API and operator migrations, and platform upgrades.","publisher":false,"reviewed":"2026-11-16","sources":[{"title":"Official installation and runtime","url":"https://signoz.io/docs/install/docker/"},{"title":"Upstream project and capabilities","url":"https://github.com/SigNoz/signoz"},{"title":"Current upstream license","url":"https://raw.githubusercontent.com/SigNoz/signoz/develop/LICENSE"},{"title":"SigNoz v0.150.0 breaking changes","url":"https://github.com/SigNoz/signoz/releases/tag/v0.150.0"},{"title":"SigNoz v0.150.0 alert-rule upgrade guide","url":"https://signoz.io/docs/operate/migration/upgrade-0-150/"},{"title":"SigNoz JSON log migration capacity guidance","url":"https://signoz.io/guides/json-logs-migration/"}],"url":"https://launchinyourcloud.com/directory/signoz/","website":"https://signoz.io/"},{"architecture":"SimpleRisk application AMI or installed application stack plus the licensed supplier-risk extension.","categories":["vendor-supplier-document-management"],"category":"Vendor \u0026 supplier document management","categoryFit":{"vendor-supplier-document-management":"Self-hosted SimpleRisk with the separately licensed Vendor Risk Management Extra."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"SimpleRisk application AMI or installed application stack plus the licensed supplier-risk extension. The listed supplier workflow requires the commercial Extra; the core project's open-source licence does not include it. An AWS image is a deployment path, not a guarantee that software spend counts toward a buyer's commitment.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Cloud Install KB (AWS AMI)","url":"https://support.simplerisk.com/kb/01-04-installing-on-cloud","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":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Self-hosted SimpleRisk with the separately licensed Vendor Risk Management Extra.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"SimpleRisk current deployment-size starting points; not a fixed VRM/HA minimum","source":"https://support.simplerisk.com/kb/01-01-system-requirements","status":"documented","summary":"The system guide suggests small deployments at 1–2 vCPU/2 GB RAM/20 GB disk and mid-size deployments at 2–4 vCPU/4–8 GB/50–100 GB. Large programs separate database and web tiers with 4+ vCPU/8+ GB per tier. These workload examples require tuning for frameworks, imports, evidence, audit growth and HA."},"iac":{"artifactRef":"Current vendor Docker installation guide","artifactUrl":"https://support.simplerisk.com/kb/01-03-installing-via-docker","reviewed":"2026-11-21","scope":"SimpleRisk upstream Docker installation plus separately licensed Extras","source":"https://support.simplerisk.com/kb/01-03-installing-via-docker","status":"documented","summary":"The vendor documents Linux/cloud and Docker installation, with configuration, persistence and separately activated Extras. Select compatible base application/DB and licensed VRM/authentication components, then configure HTTPS, backups and updates; installing the base does not activate all Extras."},"licensePricing":{"reviewed":"2026-11-19","scope":"SimpleRisk (with Vendor Risk Management Extra); software terms only, excluding cloud charges, labour and separately licensed services","source":"https://www.simplerisk.com/pricing","status":"documented","summary":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-21","scope":"SimpleRisk SAML via separately enabled Custom Authentication Extra","source":"https://support.simplerisk.com/kb/custom-authentication-extra-installation-and-administration-guide","status":"documented","summary":"The Custom Authentication Extra adds SAML with provider metadata, trusted domain and mapped user type, alongside LDAP/AD. Licence/enable that Extra separately from Vendor Risk Management, configure the IdP and user lifecycle, and retain recovery access; base local login does not include the same identity integration."}},"id":"simplerisk-vrm","infrastructure":["servers"],"infrastructureNotes":"SimpleRisk application AMI or installed application stack plus the licensed supplier-risk extension. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://support.simplerisk.com/kb/01-04-installing-on-cloud"],"install":"VM image","installMethods":["vm-image"],"kind":"product","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.simplerisk.com/pricing"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"SimpleRisk (with Vendor Risk Management Extra)","notes":"The listed supplier workflow requires the commercial Extra; the core project's open-source licence does not include it. An AWS image is a deployment path, not a guarantee that software spend counts toward a buyer's commitment.","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":"Cloud Install KB (AWS AMI)","url":"https://support.simplerisk.com/kb/01-04-installing-on-cloud"},{"title":"VRM Extra","url":"https://www.simplerisk.com/extras/vendor-risk-management"},{"title":"Pricing \u0026 Editions","url":"https://www.simplerisk.com/pricing"},{"title":"SimpleRisk 20261105-001 Release","url":"https://www.simplerisk.com/product-releases/whats-new-simplerisk-20261105-001-release"},{"title":"GitHub Releases","url":"https://github.com/simplerisk/code/releases"}],"url":"https://launchinyourcloud.com/directory/simplerisk-vrm/","website":"https://www.simplerisk.com"},{"architecture":"Pipeline VM or Kubernetes resources run in the customer's cloud and load events to the customer's warehouse or lake. Snowplow hosts the management console and APIs.","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Collects, validates, enriches, and delivers behavioural event data to the customer's data warehouse or lake."},"cloudEvidence":[{"clouds":["aws"],"notes":"Snowplow uses delegated cross-account access to install and operate the pipeline in the customer's selected AWS region.","reviewed":"2026-11-21","sourceType":"vendor-documentation","title":"Snowplow Private Managed Cloud on AWS","url":"https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-aws/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The Azure guide uses an application service principal and role scoped to the customer's subscription.","reviewed":"2026-11-21","sourceType":"vendor-documentation","title":"Snowplow Private Managed Cloud on Azure","url":"https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-azure/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The customer enables billing and grants installation and maintenance roles in its Google Cloud project.","reviewed":"2026-11-21","sourceType":"vendor-documentation","title":"Snowplow Private Managed Cloud on Google Cloud","url":"https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-gcp/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-21","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"vendor-hosted","evidence":[0],"operator":"vendor"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"vendor-hosted","evidence":[1],"operator":"vendor"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"vendor-hosted","evidence":[2],"operator":"vendor"}],"description":"Vendor-managed behavioural event pipeline running in the customer's cloud account.","diligence":{"airGap":{"availability":"unavailable","reviewed":"2026-11-21","scope":"Snowplow CDI PMC operational connectivity; IP allowlisting is supported, full disconnection is not.","source":"https://docs.snowplow.io/restrictive-access-models/","status":"documented","summary":"PMC deployment and monitoring require Snowplow's direct public-internet access to the customer environment. The vendor explicitly excludes architectures that prohibit that access, even when customer-managed VPN or SSO gates would otherwise provide access. This managed model does not support a fully disconnected environment."},"footprint":{"reviewed":"2026-11-21","scope":"CDI Private Managed Cloud production sizing unresolved; separate self-hosted examples are not a PMC guarantee.","source":"https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-aws/","status":"inconclusive","summary":"The managed-cloud setup guides specify account access and dedicated networking, not a complete quantitative production CPU/RAM/storage baseline. Snowplow scales and operates the pipeline; obtain sizing against events per month, peak event rate, enrichment workloads, destinations, retention and HA/recovery objectives. Customer-console user count and warehouse data size do not establish event-pipeline capacity.","supportingSources":[{"title":"Dedicated-subnet and operational constraints","url":"https://docs.snowplow.io/restrictive-access-models/"}]},"iac":{"reviewed":"2026-11-21","scope":"Complete CDI PMC runtime artifact unresolved; AWS IAM-role bootstrap is documented separately.","source":"https://docs.snowplow.io/restrictive-access-models/","status":"inconclusive","summary":"Snowplow documents a proprietary IaC platform for PMC. Its AWS setup guide links a public CloudFormation template for the SnowplowAdmin IAM role and describes a separate deployment role; that access bootstrap does not expose the complete managed pipeline installer. Obtain the release-specific deployment configuration, full permissions and rollback/export procedure from Snowplow. Self-Hosted Terraform modules describe a different operating model.","supportingSources":[{"title":"AWS IAM role and CloudFormation access bootstrap","url":"https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-aws/"}]},"licensePricing":{"reviewed":"2026-11-21","scope":"CDI Private Managed Cloud quote-based commercial terms; no numeric public PMC rate established.","source":"https://snowplow.io/pricing","status":"documented","summary":"Private Managed Cloud is a commercial, custom-quote deployment inside the customer's AWS, Google Cloud or Azure account. The quote depends on events per month, deployment location and destinations. Confirm infrastructure, vendor service and support charges in the contract; the free hosted trial and production Self-Hosted license are separate options."},"sso":{"availability":"available","reviewed":"2026-11-21","scope":"Vendor-hosted Snowplow Console identity for CDI Private Managed Cloud.","source":"https://docs.snowplow.io/docs/account-management/managing-users/","status":"documented","summary":"Snowplow Console administrators can configure SSO using SAML or OpenID Connect. The PMC deployment uses the vendor-hosted Console and APIs; pricing lists SSO and user permissions on every plan. This does not establish SSO at event collectors, destination systems or the customer's cloud console.","supportingSources":[{"title":"PMC control-plane boundary","url":"https://docs.snowplow.io/docs/get-started/deployment-options/"},{"title":"Plan features including SSO","url":"https://snowplow.io/pricing"}]}},"id":"snowplow-private-managed-cloud","infrastructure":["servers"],"infrastructureNotes":"Pipeline VM or Kubernetes resources run in the customer's cloud and load events to the customer's warehouse or lake. Snowplow hosts the management console and APIs.","infrastructureReviewed":"2026-11-21","infrastructureSources":["https://docs.snowplow.io/restrictive-access-models/"],"install":"Provide a dedicated AWS account, Azure subscription, or Google Cloud project and grant the permissions in the provider guide.","installMethods":["vendor-assisted"],"kind":"platform","license":"Commercial Private Managed Cloud plan with quote-based pricing.","licenseModel":"commercial-only","licenseModelNotes":"Commercial Private Managed Cloud plan with quote-based pricing.","licenseModelSources":["https://snowplow.io/pricing"],"licenseReviewed":"2026-11-21","model":"BYOC","modelLabel":"Vendor-operated BYOC","name":"Snowplow CDI Private Managed Cloud","notes":"Snowplow requires dedicated subnets and remote operational access. Certain restricted environments, including AWS GovCloud and Azure Government, are outside the documented support scope. Agree how to preserve schema and configuration records and revoke Snowplow's access at offboarding.","operationReview":{"controlPlane":"vendor-hosted","modelLabel":"Vendor-operated BYOC","operator":"vendor","reviewed":"2026-11-21","source":"https://docs.snowplow.io/docs/get-started/deployment-options/","summary":"Snowplow operates, monitors and upgrades the pipeline in the customer's dedicated cloud environment. Snowplow hosts the management Console and APIs outside that data plane; the customer supplies the cloud account, permissions and warehouse or lake.","supportingSources":[{"title":"Operational access and deployment restrictions","url":"https://docs.snowplow.io/restrictive-access-models/"}]},"operations":"Snowplow provisions, monitors, patches, and upgrades the pipeline. The customer supplies the cloud environment, access permissions, and data destination.","publisher":false,"reviewed":"2026-11-21","sources":[{"title":"Deployment options and control-plane boundary","url":"https://docs.snowplow.io/docs/get-started/deployment-options/"},{"title":"Infrastructure and access requirements","url":"https://docs.snowplow.io/restrictive-access-models/"},{"title":"Private Managed Cloud pricing","url":"https://snowplow.io/pricing"},{"title":"Customer account boundaries and operation","url":"https://support.snowplow.io/articles/4431218364-learn-about-snowplow-bdp"},{"title":"Snowplow Private Managed Cloud on AWS","url":"https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-aws/"},{"title":"Snowplow Private Managed Cloud on Azure","url":"https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-azure/"},{"title":"Snowplow Private Managed Cloud on Google Cloud","url":"https://docs.snowplow.io/docs/get-started/private-managed-cloud/setup-guide-gcp/"}],"url":"https://launchinyourcloud.com/directory/snowplow-private-managed-cloud/","website":"https://snowplow.io/"},{"architecture":"Customer-managed archival platform and data storage","categories":["legacy-system-archive-access"],"category":"Legacy system archive \u0026 access","categoryFit":{"legacy-system-archive-access":"Dedicated application retirement and historical-data archival access using the customer-managed enterprise option. Vendor-assisted enterprise installation; no public installer was verified. Confirm package, deployment topology and responsibility split."},"cloudEvidence":[{"clouds":["aws","azure","gcp","oci","ibm"],"notes":"The parent company's 2024-25 annual report, printed page 46/PDF page 48, describes CDP Private on an organization's existing cloud instances with in-house application management. Its Enterprise Archiving architecture includes Application Retirement above named AWS, Azure, Google Cloud, Oracle Cloud and IBM Cloud infrastructure, and states that the bundle is offered privately as well as as SaaS. This is a platform compatibility disclosure, not a release-specific installation guide; confirm the current private package, topology, licenses and operating agreement.","reviewed":"2026-11-12","sourceType":"corporate-disclosure","title":"Solix private deployment and enterprise archiving platform disclosure","url":"https://bsmedia.business-standard.com/_media/bs/data/announcements/bse/06092025/3528499d-78aa-4f75-9656-074933f4ddc2.pdf","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The vendor case documents Application Retirement on a Google Cloud private tenant, delivered collaboratively with Kyndryl. It corroborates a real private deployment; it does not by itself establish customer account ownership or customer operations. Use the separate CDP Private disclosure for the customer-operated option and agree the exact contract and support boundaries.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Solix Application Retirement customer case on a Google Cloud private tenant","url":"https://www.solix.com/documents/case-studies/how-a-clean-energy-utility-saved-millions-with-solixcloud.pdf","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp","oci","ibm"],"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,1],"operator":"customer"},{"boundary":"cloud-account","cloud":"oci","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"ibm","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Archive retired applications while retaining searchable access to historical business information.","diligence":{"compliance":{"reviewed":"2026-11-14","scope":"Customer-managed application versus vendor cloud scope unresolved","source":"https://www.solix.com/products/application-retirement-solution/","status":"inconclusive","summary":"The product page mentions SOC 2 and ISO 27001 alongside SolixCloud options. It does not establish an assessed scope for the customer-managed Application Retirement installation."},"footprint":{"reviewed":"2026-11-21","scope":"Customer-managed application retirement sizing remains unconfirmed","source":"https://www.solix.com/products/enterprise-edition/","status":"inconclusive","summary":"The reviewed enterprise/product material does not establish numeric customer-managed CPU/RAM/storage or HA requirements. Size ingestion, source formats, indexed archive volume, retrieval concurrency and retention separately from the vendor-operated cloud service."},"iac":{"reviewed":"2026-11-21","scope":"Customer-managed Solix installation artifact remains unconfirmed","source":"https://www.solix.com/products/enterprise-edition/","status":"inconclusive","summary":"Solix advertises implementation services and multiple deployment options, but the reviewed public material does not expose a release-specific installer, chart or infrastructure artifact for customer-managed retirement. Obtain the supported delivery package and deployment procedure."},"licensePricing":{"reviewed":"2026-11-21","scope":"Current Enterprise Edition commercial model; negotiated customer-managed entitlement and price remain order-specific","source":"https://www.solix.com/products/enterprise-edition/","status":"documented","summary":"Solix describes Enterprise Edition as a consumption-based commercial bundle including preservation products and application retirement, with on-premises, hybrid and cloud options. Obtain the applicable customer-managed order, consumption metric, support and non-production/DR rights; no SOLIXCloud SaaS rate is substituted for that agreement."},"sso":{"reviewed":"2026-11-21","scope":"Solix customer-managed application retirement SSO remains unconfirmed","source":"https://www.solix.com/products/application-retirement-solution/","status":"inconclusive","summary":"The reviewed product and Enterprise Edition pages describe governance and deployment options but do not establish the customer-managed retirement application identity integration, provider protocol or account mapping. A hosted-service SSO statement cannot settle the selected customer-hosted edition."}},"id":"solix-application-retirement","infrastructure":["unspecified"],"infrastructureNotes":"Customer-hosted installation is documented, but the reviewed public material does not specify enough runtime detail to classify it. Confirm the supported server or container topology with the vendor.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://www.solix.com/products/application-retirement-solution/"],"install":"Vendor-assisted customer-managed enterprise deployment; confirm supported package/topology","installMethods":["package","vendor-assisted"],"kind":"product","license":"Commercial Enterprise Edition","licenseModel":"commercial-only","licenseModelNotes":"This entry covers the licensed Enterprise Edition customer-managed application retirement option. Self-management and public-cloud deployment do not imply open-source rights.","licenseModelSources":["https://www.solix.com/products/enterprise-edition/","https://www.solix.com/solixcloud/"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Solix Application Retirement — Customer-Managed","notes":"Solix documents application retirement and separately describes customer-managed and self-managed on-premises/private/public-cloud options. This entry excludes fully managed SOLIXCloud SaaS. Public installation commands and specific customer-account hyperscaler deployment paths were not verified.","operations":"Customer-managed deployment is available; agree implementation, support, upgrades and infrastructure ownership with Solix.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Application retirement functionality","url":"https://www.solix.com/products/application-retirement-solution/"},{"title":"Explicit customer-managed deployment option","url":"https://www.solix.com/solixcloud/"},{"title":"Enterprise Edition deployment options","url":"https://www.solix.com/products/enterprise-edition/"},{"title":"Official self-managed private/public-cloud deployment statement","url":"https://www.solix.com/documents/datasheets/solix-cloud-data-management-for-sap.pdf"}],"url":"https://launchinyourcloud.com/directory/solix-application-retirement/","website":"https://www.solix.com/"},{"advisories":[{"action":"Apply -XX:-UseBASE64Intrinsics to Web, Compute Engine, and Search as documented, and move to a patched Sonar build when the vendor names one.","conditions":"OpenJDK 17.0.6 or later, including Java 21 and 25, on x86-64 with AVX-512 VBMI. Sonar reported no known exploitation when publishing the notice.","disclosedOn":"2026-11-17","id":"sonarqube-cve-2026-114938-java4shell","listingIds":["sonarqube-data-center"],"reviewed":"2026-11-18","scope":"Potentially affects supported SonarQube Server 2026.5, 2026.1 LTA, 2025.4 LTA, Community Build, and older versions when the affected Java and CPU conditions are present. ARM is unaffected.","source":"https://community.sonarsource.com/t/security-advisory-java4shell-workaround-for-sonarqube/191330","summary":"Sonar reports that CVE-2026-114938 may permit unauthenticated RCE in affected OpenJDK runtimes on x86-64 AVX-512 VBMI systems.","title":"SonarQube Java4Shell workaround","type":"security-advisory"}],"architecture":"Clustered application and search nodes with load balancing, persistent volumes and an external production database","categories":["devops"],"category":"DevOps","categoryFit":{"devops":"Provides high-availability self-managed code-quality and security analysis integrated with source-control and CI workflows."},"cloudEvidence":[{"clouds":["gcp"],"notes":"Sonar documents deploying Data Center Edition through Google Cloud Marketplace into an existing customer GKE cluster, using either Click to Deploy or the advanced command-line path.","reviewed":"2026-11-15","sourceType":"vendor-documentation","title":"SonarQube Data Center Edition on GKE","url":"https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/installing-from-gcp","vendorSupport":"not-assessed"},{"applicableEdition":"Data Center Edition","applicableVersions":["2026.1"],"clouds":["azure"],"notes":"Sonar provides a Data Center Edition deployment procedure for primary and replica AKS clusters using its Helm chart, an external PostgreSQL writer endpoint and Azure ingress. This is an active-cold standby example; cluster sizing must be assessed separately.","reviewed":"2026-11-15","sourceType":"vendor-documentation","title":"SonarQube DCE deployment on Azure Kubernetes Service","url":"https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/set-up-clusters-on-aks","vendorSupport":"not-assessed"},{"applicableEdition":"Data Center Edition","applicableVersions":["2026.1 architecture; select a compatible Helm chart"],"clouds":["aws"],"notes":"Sonar explicitly says its DCE Kubernetes disaster-recovery architecture can be adapted to AWS with modifications. The upstream DCE Helm chart separately documents AWS ingress migration settings. This is an architecture adaptation path, not an AWS one-click package or a support commitment.","reviewed":"2026-11-15","sourceType":"vendor-documentation","title":"SonarQube DCE cloud architecture and AWS chart guidance","url":"https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/architecture-example","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-15","clouds":["gcp","azure","aws"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Commercial high-availability SonarQube Server edition with Google Cloud deployment, Azure Kubernetes instructions and documented AWS architecture guidance.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Current five-node Data Center topology and vendor validation example","source":"https://docs.sonarsource.com/sonarqube-server/server-installation/data-center-edition/installation-requirements.md","status":"documented","summary":"Current Data Center requirements call for at least two application nodes and three search nodes, plus a separate database and load balancer. The validated example uses 4-vCPU/16-GB application nodes and 8-vCPU/32-GB search nodes. Code/issue volume, storage, database and optional agentic features require additional sizing."},"iac":{"reviewed":"2026-11-16","scope":"SonarSource sonarqube-dce chart README on moving master branch","source":"https://github.com/SonarSource/helm-chart-sonarqube/blob/master/charts/sonarqube-dce/README.md","status":"documented","summary":"The upstream sonarqube-dce Helm chart installs Data Center Edition and requires an external database. It explicitly excludes Community, Developer and Enterprise Editions. Pin and validate the chart/application versions instead of assuming a moving chart matches the versioned cloud guide."},"licensePricing":{"reviewed":"2026-11-20","scope":"Commercial Data Center edition; LOC-based annual model","source":"https://www.sonarsource.com/plans-and-pricing/sonarqube/","status":"documented","summary":"Self-hosted editions are priced per instance per year by lines of code; Data Center is the commercial clustered edition. Obtain the required LOC tier and support quote. Optional agentic features require separate subscriptions; the Community licence and Cloud price do not cover Data Center.","supportingSources":[{"title":"Optional feature subscriptions","url":"https://docs.sonarsource.com/sonarqube-server/server-installation/data-center-edition/installation-requirements.md"}]},"securityControls":{"reviewed":"2026-11-18","scope":"Potentially affects supported SonarQube Server 2026.5, 2026.1 LTA, 2025.4 LTA, Community Build, and older versions when the affected Java and CPU conditions are present. ARM is unaffected.","source":"https://community.sonarsource.com/t/security-advisory-java4shell-workaround-for-sonarqube/191330","status":"documented","summary":"Current advisory review: Sonar reports that CVE-2026-114938 may permit unauthenticated RCE in affected OpenJDK runtimes on x86-64 AVX-512 VBMI systems. Apply -XX:-UseBASE64Intrinsics to Web, Compute Engine, and Search as documented, and move to a patched Sonar build when the vendor names one."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"SonarQube Server 2026.5 SAML; selected Data Center entitlement requires review","source":"https://docs.sonarsource.com/sonarqube-server/instance-administration/authentication/saml/overview","status":"documented","summary":"SonarQube Server 2026.5 documents SP-initiated SAML 2.0 federation and optional SCIM provisioning with configured identity providers. This applies to the licensed Server deployment; verify the chosen Data Center licence and identity-provider mapping."}},"id":"sonarqube-data-center","infrastructure":["servers"],"infrastructureNotes":"Data Center Edition runs clustered application and search services on customer Kubernetes infrastructure with persistent storage and an external production database.","infrastructureReviewed":"2026-11-15","infrastructureSources":["https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/installing-from-gcp","https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/set-up-clusters-on-aks","https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/architecture-example"],"install":"Google Cloud Marketplace on GKE or DCE Helm chart; documented AKS deployment and AWS architecture adaptation","installMethods":["platform-template","helm","kubernetes"],"kind":"product","license":"Commercial Data Center Edition license.","licenseModel":"commercial-only","licenseModelNotes":"SonarQube Server Data Center Edition is a paid, per-instance commercial edition priced by licensed lines of code.","licenseModelSources":["https://www.sonarsource.com/plans-and-pricing/sonarqube/"],"licenseReviewed":"2026-11-15","model":"Fully in your account","modelLabel":"Customer-operated","name":"SonarQube Server Data Center Edition","notes":"This entry covers self-managed Data Center Edition. Google Cloud has a Marketplace path; Azure has a concrete AKS deployment example, while the AWS architecture requires adaptation. For 2026.1, use an external production database, compatible Helm values and an appropriate storage class on AKS; the documentation warns about Azure Fileshare permissions. Confirm chart and package versions independently. CVE-2026-114938 is reported to allow unauthenticated RCE in affected OpenJDK 17.0.6+ runtimes, including Java 21 and 25, on x86-64 CPUs with AVX-512 VBMI. Until Sonar publishes patched builds, set -XX:-UseBASE64Intrinsics for Web, Compute Engine, and Search; ARM is unaffected, and Sonar reported no evidence of exploitation.","operations":"Customer manages the Kubernetes cluster, namespaces, database, persistent volumes, secrets, TLS, identity, load balancing, backups, autoscaling, upgrades and the SonarQube license.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"SonarQube Data Center Edition on Google Cloud","url":"https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/installing-from-gcp"},{"title":"SonarQube Server plans and licensing","url":"https://www.sonarsource.com/plans-and-pricing/sonarqube/"},{"title":"SonarQube DCE deployment on Azure Kubernetes Service","url":"https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/set-up-clusters-on-aks"},{"title":"SonarQube DCE cloud architecture and AWS chart guidance","url":"https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/architecture-example"},{"title":"Upstream SonarQube DCE Helm chart and AWS ingress settings","url":"https://github.com/SonarSource/helm-chart-sonarqube/blob/master/charts/sonarqube-dce/README.md"},{"title":"DCE Kubernetes prerequisites and AKS storage limitation","url":"https://docs.sonarsource.com/sonarqube-server/2026.1/server-installation/data-center-edition/on-kubernetes-or-openshift/before-you-start"},{"title":"SonarQube Java4Shell workaround advisory","url":"https://community.sonarsource.com/t/security-advisory-java4shell-workaround-for-sonarqube/191330"}],"url":"https://launchinyourcloud.com/directory/sonarqube-data-center/","website":"https://www.sonarsource.com/products/sonarqube/server/"},{"advisories":[{"action":"Upgrade to 3.98.0 or later. The upgrade retains existing Rut Auth capabilities and repository-group memberships: remove unused Rut Auth capabilities and realms, confirm intended capabilities were administrator-created, and remove group members that group editors are not allowed to read. Review disabled or locked SSO users' sign-ins and affected reindex tasks; rotate potentially exposed signing keys and passphrases.","conditions":"Rut Auth, SSO, YUM or repository signing, the optional reindex task, OCI attestations, and repository groups determine applicability.","id":"nexus-repository-3-98-0-security-update","listingIds":["nexus-repository-pro-self-hosted"],"reviewed":"2026-11-18","scope":"Affected ranges vary from 3.0.0 through 3.97.x to narrower 3.86–3.97, 3.90–3.97, 3.93–3.97, and 3.94–3.97 ranges. All are fixed in 3.98.0.","source":"https://support.sonatype.com/hc/en-us/articles/56614238092947-CVE-2026-113373-Nexus-Repository-3-Disabled-or-Locked-Single-Sign-On-Users-Can-Sign-In-Again-2026-11-04","summary":"Seven November advisories cover privilege escalation, SSO account reactivation, exposed signing credentials, SQL injection, stored XSS, and repository-member authorization bypass.","supportingSources":[{"title":"CVE-2026-113374","url":"https://support.sonatype.com/hc/en-us/articles/56616522124435-CVE-2026-113374-Nexus-Repository-3-Privilege-Escalation-via-Rut-Auth-Capability-Creation-2026-11-04"},{"title":"CVE-2026-113372","url":"https://support.sonatype.com/hc/en-us/articles/56612283547539-CVE-2026-113372-Nexus-Repository-3-Insufficiently-Protected-Credentials-in-YUM-Repository-Signing-Key-2026-11-04"},{"title":"CVE-2026-113371","url":"https://support.sonatype.com/hc/en-us/articles/56609541356051-CVE-2026-113371-Nexus-Repository-3-Insufficiently-Protected-Credentials-in-Repository-Signing-Passphrase-2026-11-04"},{"title":"CVE-2026-113370","url":"https://support.sonatype.com/hc/en-us/articles/56603207226131-CVE-2026-113370-Nexus-Repository-3-SQL-Injection-in-Reindex-Search-by-Pattern-Task-2026-11-04"},{"title":"CVE-2026-113369","url":"https://support.sonatype.com/hc/en-us/articles/56597339691027-CVE-2026-113369-Nexus-Repository-3-Stored-Cross-Site-Scripting-in-OCI-Attestations-Tab-2026-11-04"},{"title":"CVE-2026-113368","url":"https://support.sonatype.com/hc/en-us/articles/56599581299987-CVE-2026-113368-Nexus-Repository-3-Group-Repository-Member-Authorization-Bypass-2026-11-04"}],"title":"Nexus Repository 3.98.0 security update","type":"security-advisory"},{"action":"Upgrade the installed supported branch to its fixed release, including 3.98.2 or later on 3.98. Restart and verify affected processes. If an immediate upgrade is unavailable, follow Sonatype’s temporary JVM mitigation and runtime-compatibility guidance. Do not downgrade to match an older maintenance backport.","conditions":"Installed branch, bundled JDK, CPU and process restart determine applicability.","id":"nexus-repository-java4shell-maintenance-backports","listingIds":["nexus-repository-pro-self-hosted"],"reviewed":"2026-11-19","scope":"Self-hosted Nexus Repository: 3.98.2 on the 3.98 line. The FAQ also lists 3.97.4, 3.95.6, 3.94.4, 3.93.4 and 3.92.5; the linked November 19 notes identify 3.90.7 and 3.88.2.","source":"https://support.sonatype.com/hc/en-us/articles/57683907326355-Java4Shell-FAQ-for-Sonatype-Products","summary":"Nexus Repository 3.98.2 includes Java4Shell mitigation; 3.90.7 and 3.88.2 are separate older-line backports, not substitutes for the current 3.98-line fix.","supportingSources":[{"title":"3.90.7 release notes","url":"https://help.sonatype.com/en/sonatype-nexus-repository-3-90-0-release-notes.html"},{"title":"3.88.2 release notes","url":"https://help.sonatype.com/en/sonatype-nexus-repository-3-88-0-release-notes.html"},{"title":"3.98.2 current-line fix, released November 18, 2026","url":"https://help.sonatype.com/en/sonatype-nexus-repository-3-98-0-release-notes.html"}],"title":"Nexus Repository Java4Shell fixes for current and maintained branches","type":"security-advisory"}],"architecture":"Standalone node or active-active Nexus Repository Pro cluster with persistent storage, external PostgreSQL, load balancing and cloud blob storage","categories":["devops"],"category":"DevOps","categoryFit":{"devops":"Provides a self-managed repository for packages, containers and other build artifacts used by software-delivery pipelines."},"cloudEvidence":[{"applicableEdition":"Nexus Repository Pro","clouds":["aws","azure","gcp"],"notes":"Sonatype explicitly lists AWS, Azure and Google Cloud as supported providers for Nexus Repository Pro HA and names EKS, AKS and GKE together with provider-specific databases, storage and blob services.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Supported Nexus Repository Pro high-availability infrastructure","url":"https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html","vendorSupport":"not-assessed"},{"applicableEdition":"Nexus Repository Pro","clouds":["gcp"],"notes":"Sonatype provides a concrete Google Cloud deployment path for Nexus Repository Pro using its resiliency and high-availability Helm chart, GKE ingress, persistent storage and license management.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Nexus Repository Pro deployment on Google Cloud","url":"https://help.sonatype.com/en/deploy-nexus-repository-to-google-cloud.html","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,1],"operator":"customer"}],"description":"Commercial self-hosted artifact repository with supported high-availability deployment across customer cloud infrastructure.","diligence":{"airGap":{"reviewed":"2026-11-16","scope":"Current self-hosted Pro telemetry policy, including 3.97+ onboarding; not Community or SAGE","source":"https://help.sonatype.com/en/nexus-repository-telemetry.html","status":"inconclusive","summary":"The current telemetry policy requires base usage reporting and directs commercially entitled customers needing disconnected operation to Sonatype Support. It does not publish an unconditional Pro exemption or a complete disconnected procedure; obtain entitlement-specific terms before relying on air-gapped operation."},"footprint":{"reviewed":"2026-11-16","scope":"Per-node example for the documented workload; not an HA total or performance guarantee","source":"https://help.sonatype.com/en/sonatype-nexus-repository-system-requirements.html","status":"documented","summary":"The current cloud-native XS profile recommends one node with 4 vCPU and 16 GiB RAM for its stated 100 requests/second workload. Larger profiles increase node count and resources; Pro HA additionally needs a load balancer, shared blob storage and external PostgreSQL.","supportingSources":[{"title":"HA infrastructure requirements","url":"https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html"}]},"iac":{"artifactRef":"main (moving branch)","artifactUrl":"https://github.com/sonatype/nxrm3-ha-repository/tree/main/nxrm-ha","reviewed":"2026-11-16","scope":"Nexus Repository Pro HA; not the standalone Community Edition topology","source":"https://help.sonatype.com/en/deploy-nexus-repository-to-google-cloud.html","status":"documented","summary":"Sonatype publishes the nxrm-ha Helm chart for resilient and high-availability deployments. Pro HA requires an external PostgreSQL database and persistent storage; choose a supported chart, application and database combination.","supportingSources":[{"title":"HA requirements","url":"https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html"}]},"licensePricing":{"reviewed":"2026-11-16","scope":"Sonatype Nexus Repository Pro Self-Hosted: software license terms; infrastructure and operating costs are separate","source":"https://help.sonatype.com/en/license-management.html","status":"documented","summary":"A Sonatype license file unlocks Nexus Repository Pro capabilities; unlicensed self-hosted instances operate as Community Edition, while the selected high-availability deployment requires Pro.","supportingSources":[{"title":"Edition and license conditions","url":"https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html"}]},"marketplace":{"availability":"edition-dependent","offers":[{"cloud":"aws","delivery":"Self-hosted license contract; AWS delivery classification SaaS","id":"prodview-444trrzad4z56","publisher":"Sonatype","url":"https://aws.amazon.com/marketplace/pp/prodview-444trrzad4z56"}],"reviewed":"2026-11-16","scope":"Vendor-published AWS offer; procurement and application hosting are distinct","source":"https://aws.amazon.com/marketplace/pp/prodview-444trrzad4z56","status":"documented","summary":"Sonatype publishes an AWS Marketplace offer explicitly named Nexus Repository Pro (Self-Hosted). It is a contract/license procurement listing classified as SaaS, not a vendor-run Repository Cloud deployment or an infrastructure installer. Confirm usage, renewal and support terms."},"release":{"releasePublishedOn":"2026-11-18","releaseTag":"3.98.2","reviewed":"2026-11-19","scope":"Self-hosted Nexus Repository release; commercial edition and HA compatibility still govern use; source supplies a publication day, not a timestamp","source":"https://help.sonatype.com/en/sonatype-nexus-repository-3-98-0-release-notes.html","status":"documented","summary":"Nexus Repository 3.98.2 was released November 18, 2026 and includes Java4Shell mitigation for CVE-2026-114938. This is the reviewed 3.98-line snapshot; 3.90.7 and 3.88.2 are separate maintenance backports. Check commercial-edition, runtime, Helm and HA compatibility before upgrading.","supportingSources":[{"title":"3.90.7 maintenance-line mitigation","url":"https://help.sonatype.com/en/sonatype-nexus-repository-3-90-0-release-notes.html"},{"title":"3.88.2 maintenance-line mitigation","url":"https://help.sonatype.com/en/sonatype-nexus-repository-3-88-0-release-notes.html"},{"title":"Sonatype Java4Shell product and maintained-branch guidance","url":"https://support.sonatype.com/hc/en-us/articles/57683907326355-Java4Shell-FAQ-for-Sonatype-Products"}]},"scim":{"availability":"unavailable","reviewed":"2026-11-16","scope":"Nexus Repository direct SCIM integration","source":"https://help.sonatype.com/en/authentication.html","status":"documented","summary":"Sonatype explicitly states that direct SCIM is unsupported. SSO does not automatically synchronize user lifecycle or group changes; manual management or custom API integrations are required.","supportingSources":[{"title":"Separate SAML-user management REST API","url":"https://help.sonatype.com/en/security-management-api.html"}]},"securityControls":{"reviewed":"2026-11-19","scope":"Nexus Repository maintenance lines explicitly covered by the November 19 release notes","source":"https://support.sonatype.com/hc/en-us/articles/57683907326355-Java4Shell-FAQ-for-Sonatype-Products","status":"documented","summary":"The policy requires base usage telemetry and administrator acknowledgment starting in 3.97.0. Pro has a stated 45-day telemetry-delivery grace period; customers requiring disconnected operation need entitlement-specific support review. This is an egress requirement, not a security attestation. Current advisory review: Seven November advisories cover privilege escalation, SSO account reactivation, exposed signing credentials, SQL injection, stored XSS, and repository-member authorization bypass. Upgrade to 3.98.0 or later. The upgrade retains existing Rut Auth capabilities and repository-group memberships: remove unused Rut Auth capabilities and realms, confirm intended capabilities were administrator-created, and remove group members that group editors are not allowed to read. Review disabled or locked SSO users' sign-ins and affected reindex tasks; rotate potentially exposed signing keys and passphrases. Current review: Nexus Repository 3.98.2, released November 18, 2026, includes Java4Shell mitigation for CVE-2026-114938 on the 3.98 line. Sonatype also identifies fixes for other maintained branches, including 3.97.4, 3.95.6, 3.94.4, 3.93.4 and 3.92.5; the November 19 notes separately document 3.90.7 and 3.88.2 backports. Use the fixed release for the installed supported branch, restart affected processes and verify the active Java runtime or mitigation; do not downgrade to an older branch to match a backport.","supportingSources":[{"title":"Prior security-controls source","url":"https://support.sonatype.com/hc/en-us/articles/56614238092947-CVE-2026-113373-Nexus-Repository-3-Disabled-or-Locked-Single-Sign-On-Users-Can-Sign-In-Again-2026-11-04"},{"title":"Prior security-controls source","url":"https://help.sonatype.com/en/nexus-repository-telemetry.html"},{"title":"CVE-2026-113374","url":"https://support.sonatype.com/hc/en-us/articles/56616522124435-CVE-2026-113374-Nexus-Repository-3-Privilege-Escalation-via-Rut-Auth-Capability-Creation-2026-11-04"},{"title":"CVE-2026-113372","url":"https://support.sonatype.com/hc/en-us/articles/56612283547539-CVE-2026-113372-Nexus-Repository-3-Insufficiently-Protected-Credentials-in-YUM-Repository-Signing-Key-2026-11-04"},{"title":"CVE-2026-113371","url":"https://support.sonatype.com/hc/en-us/articles/56609541356051-CVE-2026-113371-Nexus-Repository-3-Insufficiently-Protected-Credentials-in-Repository-Signing-Passphrase-2026-11-04"},{"title":"CVE-2026-113370","url":"https://support.sonatype.com/hc/en-us/articles/56603207226131-CVE-2026-113370-Nexus-Repository-3-SQL-Injection-in-Reindex-Search-by-Pattern-Task-2026-11-04"},{"title":"CVE-2026-113369","url":"https://support.sonatype.com/hc/en-us/articles/56597339691027-CVE-2026-113369-Nexus-Repository-3-Stored-Cross-Site-Scripting-in-OCI-Attestations-Tab-2026-11-04"},{"title":"CVE-2026-113368","url":"https://support.sonatype.com/hc/en-us/articles/56599581299987-CVE-2026-113368-Nexus-Repository-3-Group-Repository-Member-Authorization-Bypass-2026-11-04"},{"title":"3.90.7 release notes","url":"https://help.sonatype.com/en/sonatype-nexus-repository-3-90-0-release-notes.html"},{"title":"3.88.2 release notes","url":"https://help.sonatype.com/en/sonatype-nexus-repository-3-88-0-release-notes.html"},{"title":"3.98.2 current-line Java4Shell mitigation","url":"https://help.sonatype.com/en/sonatype-nexus-repository-3-98-0-release-notes.html"}]},"sso":{"availability":"edition-dependent","reviewed":"2026-11-16","scope":"Nexus Repository Pro self-hosted UI; not Community or a repository-content SAML protocol","source":"https://help.sonatype.com/en/saml.html","status":"documented","summary":"Licensed self-hosted Nexus Repository supports SAML 2.0 browser SSO, including IdP group attributes for authorization. SAML authenticates the UI; repository clients use other supported credentials such as user tokens."}},"id":"nexus-repository-pro-self-hosted","infrastructure":["servers"],"infrastructureNotes":"Nexus Repository Pro runs on persistent VM or Kubernetes capacity with durable node storage, blob storage and, for resilient or HA deployments, an external PostgreSQL database.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://help.sonatype.com/en/install-nexus-repository.html","https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html"],"install":"Official Helm chart for resilient or high-availability Kubernetes deployments, or supported standalone and Docker installation paths","installMethods":["helm","docker","package"],"kind":"product","license":"Commercial Nexus Repository Pro license required for high availability and other Pro capabilities.","licenseModel":"commercial-only","licenseModelNotes":"A Sonatype license file unlocks Nexus Repository Pro capabilities; unlicensed self-hosted instances operate as Community Edition, while the selected high-availability deployment requires Pro.","licenseModelSources":["https://help.sonatype.com/en/license-management.html","https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"Sonatype Nexus Repository Pro Self-Hosted","notes":"This entry covers Nexus Repository Pro self-hosted deployments, not Nexus Repository Cloud or the unlicensed Community Edition. High availability requires Pro, an external PostgreSQL database and customer expertise in Kubernetes, Helm and cloud infrastructure. Sonatype states that its support expertise is strongest on AWS even though Azure and Google Cloud infrastructure are supported. Container deployments must persist both nexus-data and Java preferences so license state survives restarts. Nexus Repository 3.98.0 fixes seven November advisories covering Rut Auth privilege escalation, disabled or locked SSO users regaining access, exposed signing material, SQL injection in the optional reindex task, stored XSS, and group-member authorization bypass. After upgrading, remove unused Rut Auth capabilities and realms, confirm intended capabilities were administrator-created, and remove existing group members that group editors are not allowed to read; the upgrade does not clean these up. Review affected sign-ins and tasks, and rotate potentially exposed signing keys or passphrases. Nexus Repository 3.98.2, released November 18, 2026, includes Java4Shell mitigation for CVE-2026-114938 on the 3.98 line. Sonatype also identifies fixes for other maintained branches, including 3.97.4, 3.95.6, 3.94.4, 3.93.4 and 3.92.5; the November 19 notes separately document 3.90.7 and 3.88.2 backports. Use the fixed release for the installed supported branch, restart affected processes and verify the active Java runtime or mitigation; do not downgrade to an older branch to match a backport.","operations":"Customer manages compute or Kubernetes, PostgreSQL, blob and node storage, ingress and load balancing, TLS, secrets, backups, monitoring, upgrades and license persistence.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Install self-hosted Nexus Repository","url":"https://help.sonatype.com/en/install-nexus-repository.html"},{"title":"Nexus Repository high-availability requirements","url":"https://help.sonatype.com/en/system-requirements-for-high-availability-deployments.html"},{"title":"Deploy Nexus Repository to Google Cloud","url":"https://help.sonatype.com/en/deploy-nexus-repository-to-google-cloud.html"},{"title":"Nexus Repository license management","url":"https://help.sonatype.com/en/license-management.html"},{"title":"Nexus Repository CVE-2026-113373 advisory","url":"https://support.sonatype.com/hc/en-us/articles/56614238092947-CVE-2026-113373-Nexus-Repository-3-Disabled-or-Locked-Single-Sign-On-Users-Can-Sign-In-Again-2026-11-04"},{"title":"Nexus Repository Rut Auth cleanup after upgrade","url":"https://support.sonatype.com/hc/en-us/articles/56616522124435-CVE-2026-113374-Nexus-Repository-3-Privilege-Escalation-via-Rut-Auth-Capability-Creation-2026-11-04"},{"title":"Nexus Repository existing group-member cleanup after upgrade","url":"https://support.sonatype.com/hc/en-us/articles/56599581299987-CVE-2026-113368-Nexus-Repository-3-Group-Repository-Member-Authorization-Bypass-2026-11-04"},{"title":"Nexus Repository 3.90.7 release notes","url":"https://help.sonatype.com/en/sonatype-nexus-repository-3-90-0-release-notes.html"},{"title":"Nexus Repository 3.88.2 release notes","url":"https://help.sonatype.com/en/sonatype-nexus-repository-3-88-0-release-notes.html"},{"title":"Sonatype Java4Shell FAQ","url":"https://support.sonatype.com/hc/en-us/articles/57683907326355-Java4Shell-FAQ-for-Sonatype-Products"},{"title":"Nexus Repository 3.98.2 Java4Shell mitigation and publication date","url":"https://help.sonatype.com/en/sonatype-nexus-repository-3-98-0-release-notes.html"}],"url":"https://launchinyourcloud.com/directory/nexus-repository-pro-self-hosted/","website":"https://www.sonatype.com/products/sonatype-nexus-repository"},{"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":"Standalone or distributed customer-operated search heads, indexers and management components, with local storage or optional SmartStore object storage","categories":["observability","data-analytics"],"category":"Observability","categoryFit":{"data-analytics":"Provides search, dashboards, reports and statistical analysis over indexed machine-generated data.","observability":"Ingests, indexes and searches machine data for operational monitoring, troubleshooting, dashboards and alerting."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Splunk explicitly states that Splunk Enterprise can be deployed on Amazon Web Services, Microsoft Azure and Google Cloud Platform, including named government, local and distributed variants. Customers must still select supported host specifications and size each deployment for its workload.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Splunk Enterprise reference hardware for AWS, Azure and Google Cloud","url":"https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware","vendorSupport":"not-assessed"},{"clouds":["aws","azure","gcp"],"notes":"Splunk describes customer-managed cloud deployments as BYOL on AWS, Google Cloud or Azure and provides provider-specific SmartStore architecture guidance. This evidence concerns customer-operated Splunk Enterprise, not Splunk Cloud Platform; validate instance, network, object-store and cache requirements for the selected topology.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Customer-managed Splunk Enterprise BYOL architecture","url":"https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-16","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-managed platform for ingesting, indexing, searching and visualizing machine data.","diligence":{"airGap":{"availability":"available","reviewed":"2026-11-16","scope":"Commercial Splunk Enterprise deployment option; not Splunk Cloud or every add-on","source":"https://www.splunk.com/en_us/products/pricing.html","status":"documented","summary":"Splunk explicitly offers Enterprise for private-cloud/on-premises deployment, including air-gapped environments. This establishes the vendor’s deployment option; the selected apps, license delivery, updates, trust material and data integrations still need a disconnected operating procedure."},"compliance":{"reviewed":"2026-11-16","scope":"Splunk 10.6 documented module plus NIST validation status checked 2026-11-16","source":"https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/establish-and-maintain-compliance-with-fips-and-common-criteria-in-splunk-enterprise/secure-splunk-enterprise-with-fips","status":"documented","summary":"Splunk’s 10.6 guide identifies OpenSSL FIPS Provider certificate 4985 for FIPS 140-3. NIST lists that module as active, with sunset 2030-03-10 and approved-mode conditions. This is a cryptographic-module validation; deployment OS, mode, TLS and app prerequisites remain essential and it is not a blanket Splunk deployment attestation.","supportingSources":[{"title":"NIST CMVP certificate 4985","url":"https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4985"}]},"footprint":{"reviewed":"2026-11-16","scope":"S1 single-instance production reference; not a multi-tier total or operating-cost estimate","source":"https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware","status":"documented","summary":"The Enterprise 10.6 single-instance reference specifies 12 physical cores or 24 vCPU at 2 GHz+, 12 GB RAM and a 1 Gb NIC. Storage, search concurrency, ingest volume and distributed roles require separate sizing."},"iac":{"reviewed":"2026-11-16","scope":"Splunk Enterprise 10.6 installation guidance; topology and platform determine the artifact","source":"https://help.splunk.com/en/splunk-enterprise/administer/install-and-upgrade/10.6/plan-your-splunk-enterprise-installation/installation-overview","status":"documented","summary":"Splunk supplies operating-system-specific Enterprise installers. Select the required platform/version and verify the published checksum. The installation guide limits Docker to supported standalone and single-server uses; a download is not a complete distributed infrastructure template.","supportingSources":[{"title":"Enterprise packages and checksums","url":"https://www.splunk.com/en_us/download/splunk-enterprise.html"}]},"licensePricing":{"reviewed":"2026-11-16","scope":"Splunk Enterprise: software license terms; infrastructure and operating costs are separate","source":"https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.6/configure-splunk-licenses/types-of-splunk-enterprise-licenses","status":"documented","summary":"Splunk Enterprise is proprietary software. Production customers purchase commercial end-user licenses based on indexed data volume or licensed infrastructure. Trial, developer and Free licenses are restricted alternatives and do not establish an open-source edition.","supportingSources":[{"title":"Edition and license conditions","url":"https://help.splunk.com/en/splunk-enterprise/get-started/install-and-upgrade/10.6/install-a-splunk-enterprise-license/install-a-license"}]},"marketplace":{"availability":"available","offers":[{"cloud":"aws","delivery":"EC2 AMI with trial; commercial license purchased outside Marketplace","id":"prodview-l6oos72bsyaks","publisher":"Splunk","url":"https://aws.amazon.com/marketplace/pp/prodview-l6oos72bsyaks"}],"reviewed":"2026-11-16","scope":"Vendor-published AWS offer; procurement and application hosting are distinct","source":"https://aws.amazon.com/marketplace/pp/prodview-l6oos72bsyaks","status":"documented","summary":"Splunk publishes an AWS AMI with a 60-day Enterprise trial. Continued paid software use requires an external license; the AMI is not a paid Enterprise subscription or proof of software-spend commitment credit. Verify its packaged version separately from upstream releases."},"release":{"releasePublishedOn":"2026-10-16","releaseTag":"10.6.1","reviewed":"2026-11-18","scope":"Splunk Enterprise 10.6 release line; advance notice is not a final CVE matrix","source":"https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.6/whats-new/welcome-to-splunk-enterprise-10.6","status":"documented","summary":"Splunk Enterprise 10.6.1 was released October 16, 2026. The release page warns against Universal Forwarder 10.6.0, while SVD-2026-1101 names 10.6.1 and maintained parallel branches as forthcoming November fix targets.","supportingSources":[{"title":"November 2026 advance notice","url":"https://advisory.splunk.com/advisories/SVD-2026-1101"}]},"scim":{"reviewed":"2026-11-16","scope":"Splunk Enterprise 10.6 SAML user-removal workflow; identity-provider and availability conditions apply","source":"https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/use-saml-as-an-authentication-scheme-for-single-sign-on/configure-sso-with-okta-as-your-identity-provider","status":"documented","summary":"Enterprise 10.6 documents SCIM-based deletion of SAML users with a compatible Okta integration. Its release notes identify Entra ID de-provisioning as controlled availability. These sources establish scoped de-provisioning, not unrestricted SCIM user creation, updates or group synchronization.","supportingSources":[{"title":"10.6 controlled-availability Entra ID feature","url":"https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.6/whats-new/welcome-to-splunk-enterprise-10.6"}]},"securityControls":{"reviewed":"2026-11-16","scope":"Enterprise 10.6 FIPS configuration prerequisites; not automatic security or regulatory compliance","source":"https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/establish-and-maintain-compliance-with-fips-and-common-criteria-in-splunk-enterprise/secure-splunk-enterprise-with-fips","status":"documented","summary":"FIPS mode requires a supported x86-64 OS running in FIPS mode, TLS 1.2+ between nodes and compatible apps. The guide lists the older FIPS 140-2 certificate as expired in September 2026; select the supported 140-3 path and validate the full configuration."},"sso":{"availability":"available","reviewed":"2026-11-16","scope":"Customer-managed Splunk Enterprise 10.6 SAML configuration","source":"https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/use-saml-as-an-authentication-scheme-for-single-sign-on/configure-single-sign-on-with-saml","status":"documented","summary":"Enterprise 10.6 documents SAML 2.0 SSO, supported IdP connectivity, role/realName/mail attributes and administrator change_authentication capability. Encrypted assertions can be decrypted when configured; this does not establish SCIM provisioning."}},"id":"splunk-enterprise","infrastructure":["servers"],"infrastructureNotes":"Splunk Enterprise runs persistent standalone or distributed search, indexing and management services on customer-managed hosts. SmartStore can move indexed data to customer object storage, but the search and indexing tiers remain long-running server workloads.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://help.splunk.com/en/splunk-enterprise/administer/install-and-upgrade/10.6/plan-your-splunk-enterprise-installation/installation-overview","https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware","https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform"],"install":"Splunk Enterprise installation package on supported Linux or Windows hosts; Docker is limited to supported standalone and single-server topologies.","installMethods":["package"],"kind":"product","license":"Commercial end-user license based on data volume or infrastructure; limited trial, developer and Free licenses have separate restrictions.","licenseModel":"commercial-only","licenseModelNotes":"Splunk Enterprise is proprietary software. Production customers purchase commercial end-user licenses based on indexed data volume or licensed infrastructure. Trial, developer and Free licenses are restricted alternatives and do not establish an open-source edition.","licenseModelSources":["https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.6/configure-splunk-licenses/types-of-splunk-enterprise-licenses","https://help.splunk.com/en/splunk-enterprise/get-started/install-and-upgrade/10.6/install-a-splunk-enterprise-license/install-a-license"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"Splunk Enterprise","notes":"This entry covers customer-managed Splunk Enterprise, not Splunk Cloud Platform. Splunk documents customer-managed BYOL architectures on AWS, Azure and Google Cloud. Current installation documentation limits supported container deployments to standalone and single-server topologies, so distributed production deployments should follow supported package-based validated architectures. Confirm supported operating systems, instance types, object-store throughput, cache sizing and clustering requirements. Splunk advance notice SVD-2026-1101 says forthcoming November disclosures are fixed in Enterprise 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 and strongly recommends those or later releases. Final CVE-specific disclosures were not live during this review; 10.6.0 Universal Forwarder users should move to 10.6.1 or later.","operations":"Customer manages compute, networking, storage, data inputs, certificates, clustering, capacity, backups, license configuration, monitoring and upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Splunk Enterprise installation overview","url":"https://help.splunk.com/en/splunk-enterprise/administer/install-and-upgrade/10.6/plan-your-splunk-enterprise-installation/installation-overview"},{"title":"Splunk Enterprise reference hardware","url":"https://help.splunk.com/en/splunk-enterprise/get-started/deployment-capacity-manual/10.6/performance-reference/reference-hardware"},{"title":"Customer-managed BYOL SmartStore architectures","url":"https://help.splunk.com/en/splunk-enterprise/splunk-validated-architectures/splunk-platform-indexing-and-search/smartstore-for-splunk-platform"},{"title":"Splunk Enterprise license types","url":"https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.6/configure-splunk-licenses/types-of-splunk-enterprise-licenses"},{"title":"Splunk November 2026 advance notice","url":"https://advisory.splunk.com/advisories/SVD-2026-1101"},{"title":"Splunk Enterprise 10.6 release notes","url":"https://help.splunk.com/en/splunk-enterprise/release-notes-and-updates/release-notes/10.6/whats-new/welcome-to-splunk-enterprise-10.6"}],"url":"https://launchinyourcloud.com/directory/splunk-enterprise/","website":"https://www.splunk.com/en_us/products/splunk-enterprise.html"},{"architecture":"Squidex application, database and asset storage using provider-specific instructions.","categories":["content-management"],"category":"Content management \u0026 CMS","categoryFit":{"content-management":"Self-hosted headless CMS with structured content, APIs and assets."},"cloudEvidence":[{"clouds":["aws"],"notes":"Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"AWS EC2 Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Azure Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"GCP Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp","vendorSupport":"not-assessed"},{"clouds":["render"],"notes":"Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Render Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render","vendorSupport":"not-assessed"},{"clouds":["heroku"],"notes":"Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Install on Heroku | Squidex","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku","vendorSupport":"not-assessed"},{"clouds":["vultr"],"notes":"Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Install on Vultr | Squidex","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","azure","gcp","render","heroku","vultr"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/Squidex/squidex/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/Squidex/squidex"}],"summary":"The reviewed upstream contributor history includes SebastianStehle, kamushadenes, seamys, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-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"},{"boundary":"platform-workspace","cloud":"render","controlPlane":"not-assessed","evidence":[3],"operator":"customer"},{"boundary":"platform-workspace","cloud":"heroku","controlPlane":"not-assessed","evidence":[4],"operator":"customer"},{"boundary":"cloud-account","cloud":"vultr","controlPlane":"not-assessed","evidence":[5],"operator":"customer"}],"description":"Self-hosted headless CMS with structured content, APIs and assets.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Upstream deployment topology; no workload-tested minimum established","source":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-docker","status":"inconclusive","summary":"The official Compose stack establishes application, MongoDB and proxy dependencies, but no quantitative CPU/RAM/storage production floor was established in the reviewed installation materials. Confirm content volume, database replication, caches and concurrency before sizing.","supportingSources":[{"title":"Reviewed Compose services","url":"https://raw.githubusercontent.com/Squidex/squidex-hosting/master/docker-compose/docker-compose.yml"}]},"iac":{"artifactRef":"master (moving branch); Squidex major 7 / MongoDB major 6 in reviewed example","artifactUrl":"https://github.com/Squidex/squidex-hosting/tree/master/docker-compose","reviewed":"2026-11-20","scope":"Upstream Squidex 7 Compose example; assess database support and image versions separately","source":"https://raw.githubusercontent.com/Squidex/squidex-hosting/master/docker-compose/docker-compose.yml","status":"documented","summary":"The upstream hosting repository supplies a Compose stack with Squidex 7, MongoDB 6 and a Caddy proxy, persistent mounts and environment-based identity settings. These moving examples need compatible supported image versions, secrets and backups; the stack is not a replicated database/HA design."},"licensePricing":{"reviewed":"2026-11-19","scope":"Squidex; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://github.com/Squidex/squidex/blob/master/LICENSE","status":"documented","summary":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"release":{"releasePublishedAt":"2026-09-28T09:30:35Z","releaseTag":"7.24.0","reviewed":"2026-11-19","scope":"Squidex upstream application; verify compatibility with the selected package","source":"https://github.com/Squidex/squidex/releases/tag/7.24.0","status":"documented","summary":"Reviewed upstream 7.24.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Self-hosted Squidex external-provider configuration; not the deprecated Squidex.Identity server","source":"https://docs.squidex.io/id-01-getting-started/installation/external-identity-providers","status":"documented","summary":"The official external-identity guide documents configuring an external Azure AD/OAuth identity provider for self-hosted Squidex. The Compose example also exposes Google/GitHub/Microsoft credentials. The separately documented Squidex.Identity project is deprecated and must not be presented as a maintained SSO service.","supportingSources":[{"title":"Upstream Compose identity configuration","url":"https://raw.githubusercontent.com/Squidex/squidex-hosting/master/docker-compose/docker-compose.yml"}]}},"id":"squidex","infrastructure":["servers"],"infrastructureNotes":"Squidex application, database and asset storage using provider-specific instructions. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2","https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure","https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp","https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render","https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku","https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr"],"install":"Application platform deployment","installMethods":["platform-template"],"kind":"product","license":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://github.com/Squidex/squidex/blob/master/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Squidex","notes":"The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.","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 EC2 Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2"},{"title":"Azure Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure"},{"title":"GCP Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp"},{"title":"Render Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render"},{"title":"Install on Heroku | Squidex","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku"},{"title":"Install on Vultr | Squidex","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr"},{"title":"MIT LICENSE","url":"https://github.com/Squidex/squidex/blob/master/LICENSE"},{"title":"Releases v7.24.0","url":"https://github.com/Squidex/squidex/releases"}],"url":"https://launchinyourcloud.com/directory/squidex/","website":"https://squidex.io"},{"advisories":[{"action":"Upgrade the installed maintained branch to its fixed or later patch.","conditions":"Exposure depends on the bundled Brotli decoder and reachable processing paths.","id":"starburst-enterprise-cve-2026-111497","listingIds":["starburst-enterprise"],"reviewed":"2026-11-18","scope":"Fixed in 482-e.6, 480-e.13, 479-e.20, and 477-e.24; branch-specific affected ranges follow the vendor advisory.","source":"https://docs.starburst.io/security/advisories.html","summary":"Starburst documents fixed builds for critical Brotli CVE-2026-111497.","title":"Starburst Enterprise Brotli security update","type":"security-advisory"}],"architecture":"Coordinator, worker and supporting services on Kubernetes with external service database and data-source connections.","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Distributed SQL query, federation and governed analytics across cloud data stores and lakehouse systems."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Starburst documents its Enterprise Helm deployment on customer Kubernetes and explicitly supports Amazon EKS, Azure AKS and Google GKE with provider-specific ecosystem guidance. Customers operate the cluster and data services.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Starburst Enterprise Kubernetes deployment on EKS, AKS and GKE","url":"https://docs.starburst.io/latest/k8s/requirements.html","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":"Commercial distributed SQL and analytics platform deployed by Helm into customer-operated Kubernetes.","diligence":{"airGap":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Starburst Enterprise; unresolved within this edition/deployment","source":"https://docs.starburst.io/latest/k8s/requirements.html","status":"inconclusive","summary":"SEP requires entitled images/charts and a licence. The reviewed Kubernetes requirements do not establish complete isolated licence renewal, connector dependencies and upgrades."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Starburst Enterprise; unresolved within this edition/deployment","source":"https://docs.starburst.io/latest/ecosystems/aws/marketplace/","status":"inconclusive","summary":"SEP Marketplace deployment is documented, but the reviewed procurement guides do not establish qualifying fees and contract-specific commitment treatment. Galaxy claims were excluded."},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://docs.starburst.io/latest/security/authentication-types.html","status":"inconclusive","summary":"The reviewed Starburst Enterprise material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage."},"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.starburst.io/latest/k8s/requirements.html","status":"inconclusive","summary":"Confirm coordinator failover, worker concurrency, backend database, data-source storage and licensed cores. The documented dedicated-node minimum does not by itself establish the required HA query architecture. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"SEP Kubernetes node requirements; workload and HA counts still need design","source":"https://docs.starburst.io/latest/k8s/requirements.html","status":"documented","summary":"The Kubernetes guide specifies identical dedicated nodes with 16–64 cores and 64–256 GB RAM, one coordinator/worker per node, plus an externally managed service database. This is substantially more than a small general-purpose app cluster."},"iac":{"reviewed":"2026-11-17","scope":"Supported Kubernetes SEP installation","source":"https://docs.starburst.io/latest/k8s/requirements.html","status":"documented","summary":"SEP supplies licensed Helm charts and images in its Harbor registry. Obtain customer credentials and configure the coordinator, workers and backend database; the legacy AWS CloudFormation path is deprecated."},"licensePricing":{"reviewed":"2026-11-17","scope":"Starburst Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://docs.starburst.io/latest/k8s.html","status":"documented","summary":"Starburst Enterprise requires a commercial license and access to authenticated container and Helm registries. The open-source Trino project is separate."},"marketplace":{"availability":"available","reviewed":"2026-11-17","scope":"Starburst Enterprise Marketplace, not Galaxy SaaS","source":"https://docs.starburst.io/latest/ecosystems/aws/marketplace/","status":"documented","summary":"SEP documents AWS EKS Marketplace deployment and Google Cloud Marketplace subscriptions. The Google Click to Deploy path is recommended only for small proofs of concept; prefer the documented command-line customization path.","supportingSources":[{"title":"Google Cloud Marketplace limits and support","url":"https://docs.starburst.io/latest/ecosystems/google/gcp-marketplace.html"}]},"release":{"reviewed":"2026-11-17","scope":"SEP support policy and month-level release table; not a patch timestamp","source":"https://docs.starburst.io/latest/versions.html","status":"documented","summary":"The version policy distinguishes LTS and STS. The reviewed table lists 482-e.x LTS through 2027-08-31 and 483-e STS from October 2026 until the next release; select a supported line and review breaking changes."},"scim":{"availability":"available","reviewed":"2026-11-17","scope":"SEP self-managed SCIM configuration","source":"https://docs.starburst.io/latest/security/scim-provisioning.html","status":"documented","summary":"SEP documents SCIM user/group synchronization with its internal group provider and a configured secret token. Configure a supported external provider and network reachability; authorization to data remains separate."},"securityControls":{"reviewed":"2026-11-18","scope":"Starburst Enterprise authentication requirements Fixed in 482-e.6, 480-e.13, 479-e.20, and 477-e.24; branch-specific affected ranges follow the vendor advisory.","source":"https://docs.starburst.io/security/advisories.html","status":"documented","summary":"Authentication requires TLS/HTTPS and a shared secret. Apply the selected authenticator plus access-control system and restrict coordinator exposure; provisioning identities does not grant unrestricted data access. Current advisory review: Starburst documents fixed builds for critical Brotli CVE-2026-111497. Upgrade the installed maintained branch to its fixed or later patch.","supportingSources":[{"title":"Prior security-controls source","url":"https://docs.starburst.io/latest/security/authentication-types.html"}]},"sso":{"availability":"available","reviewed":"2026-11-17","scope":"Starburst Enterprise, not Galaxy or upstream Trino","source":"https://docs.starburst.io/latest/security/saml.html","status":"documented","summary":"SEP supports SAML 2.0 SSO configured on the coordinator. TLS is required; authentication is separate from the access-control rules that grant data permissions."}},"id":"starburst-enterprise","infrastructure":["servers"],"infrastructureNotes":"Starburst Enterprise runs persistent coordinator, worker and supporting containers on Kubernetes and requires an external service database plus production capacity planning.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://docs.starburst.io/latest/k8s.html","https://docs.starburst.io/latest/k8s/requirements.html"],"install":"Authenticated Starburst Enterprise Helm charts on EKS, AKS or GKE","installMethods":["helm","kubernetes"],"kind":"platform","license":"Commercial Starburst Enterprise license and entitled registry access required.","licenseModel":"commercial-only","licenseModelNotes":"Starburst Enterprise requires a commercial license and access to authenticated container and Helm registries. The open-source Trino project is separate.","licenseModelSources":["https://docs.starburst.io/latest/k8s.html"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"Starburst Enterprise","notes":"This entry covers Starburst Enterprise, not Starburst Galaxy or the upstream Trino project. Production Kubernetes deployment requires entitled images and charts, a Starburst license, dedicated adequately sized nodes and an external service database. The older AWS CloudFormation path is deprecated and is not presented as the current installation method. Starburst's November advisory fixes critical Brotli CVE-2026-111497 in 482-e.6, 480-e.13, 479-e.20, and 477-e.24. Upgrade the installed maintained branch to its fixed or later patch.","operations":"Customer manages Kubernetes, dedicated node capacity, storage, networking, service database, catalogs, secrets, backups and upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Starburst Enterprise on Kubernetes","url":"https://docs.starburst.io/latest/k8s.html"},{"title":"Kubernetes requirements","url":"https://docs.starburst.io/latest/k8s/requirements.html"},{"title":"AWS ecosystem and deployment","url":"https://docs.starburst.io/latest/ecosystems/aws/"},{"title":"Microsoft Azure ecosystem","url":"https://docs.starburst.io/latest/ecosystems/microsoft/"},{"title":"Google Cloud ecosystem","url":"https://docs.starburst.io/latest/ecosystems/google/"},{"title":"Starburst security advisories","url":"https://docs.starburst.io/security/advisories.html"}],"url":"https://launchinyourcloud.com/directory/starburst-enterprise/","website":"https://www.starburst.io/platform/starburst-enterprise/"},{"advisories":[{"action":"Upgrade to 4.1.7 or a later maintained build and review diagnostic endpoint permissions.","conditions":"Applicability depends on the affected functions, web and diagnostic endpoints, and bundled dependencies.","id":"starrocks-4-1-7-security-hardening","listingIds":["starrocks"],"reviewed":"2026-11-18","scope":"Upstream 4.1.7 release notes; no CVE, severity, or universal affected-version range is specified.","source":"https://github.com/StarRocks/starrocks/releases/tag/4.1.7","summary":"StarRocks 4.1.7 hardens lookup_string SQL handling, web-console output, diagnostic endpoints, credential display, and security dependencies.","title":"StarRocks 4.1.7 security hardening","type":"security-advisory"}],"architecture":"Distributed front-end, back-end and compute-node services with persistent disks or object storage","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Provides a distributed analytical database and query engine for real-time analytics, data warehousing and lakehouse workloads."},"cloudEvidence":[{"clouds":["aws","gcp"],"notes":"StarRocks documents creating an Amazon EKS or Google GKE cluster, installing its Kubernetes Operator and deploying a StarRocks cluster through customer-applied custom resources.","reviewed":"2026-11-15","sourceType":"vendor-documentation","title":"StarRocks Operator on EKS or GKE","url":"https://docs.starrocks.io/docs/deployment/sr_operator/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-15","clouds":["aws","gcp"],"communityAcceptance":{"reviewed":"2026-11-15","sources":[{"title":"Reviewed release 4.1.7","url":"https://github.com/StarRocks/starrocks/releases/tag/4.1.7"},{"title":"Upstream contributor history","url":"https://github.com/StarRocks/starrocks/graphs/contributors"}],"summary":"StarRocks release 4.1.7 was published on November 3, 2026, and the public contributor history records sustained upstream participation. This evidence does not establish commercial support for a particular cloud configuration."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Open-source distributed analytical database deployed through the StarRocks Kubernetes Operator.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Alibaba EMR StarRocks node recommendation; other deployment modes differ","source":"https://www.alibabacloud.com/help/en/emr/emr-on-ecs/user-guide/faq-about-starrocks","status":"documented","summary":"Alibaba Cloud recommends FE nodes with at least 8 cores/16 GB and BE nodes with at least 16 cores/64 GB for its EMR StarRocks deployment. It recommends three data replicas and workload-specific disk sizing. This provider-specific production guidance is not a universal minimum for upstream, shared-data or other-cloud installations."},"iac":{"reviewed":"2026-11-16","scope":"StarRocks Kubernetes Operator documentation, Latest-4.1 branch","source":"https://docs.starrocks.io/docs/deployment/sr_operator/","status":"documented","summary":"The official Kubernetes Operator automates StarRocks cluster deployment and management on an existing cluster. Its documentation covers EKS and GKE and identifies it as a level-2 operator; it does not provision every underlying dependency or establish production sizing."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/StarRocks/starrocks/main/LICENSE.txt","status":"documented","summary":"The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate."},"release":{"releasePublishedAt":"2026-11-03T03:51:07Z","releaseTag":"4.1.7","reviewed":"2026-11-18","scope":"Upstream StarRocks 4.1 release","source":"https://github.com/StarRocks/starrocks/releases/tag/4.1.7","status":"documented","summary":"StarRocks 4.1.7 has an upstream release date of October 26, 2026, and was published on GitHub November 3. It includes SQL, web-console, diagnostic-endpoint, credential-masking, and dependency hardening."},"securityControls":{"reviewed":"2026-11-18","scope":"Upstream 4.1.7 release notes; no CVE, severity, or universal affected-version range is specified.","source":"https://github.com/StarRocks/starrocks/releases/tag/4.1.7","status":"documented","summary":"Current advisory review: StarRocks 4.1.7 hardens lookup_string SQL handling, web-console output, diagnostic endpoints, credential display, and security dependencies. Upgrade to 4.1.7 or a later maintained build and review diagnostic endpoint permissions."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"StarRocks 3.5+ Web UI and SQL-client OAuth2","source":"https://docs.starrocks.io/docs/administration/user_privs/authentication/oauth2_authentication/","status":"documented","summary":"From 3.5.0, StarRocks documents OAuth2 authorization-code sign-in for its Web UI and JDBC clients. Client plugins or a browser authentication step are needed for SQL access. Configure the security integration and validate identity-provider/client compatibility; this is distinct from LDAP binds."}},"id":"starrocks","infrastructure":["servers"],"infrastructureNotes":"StarRocks runs persistent distributed database services and operator-managed pods on Kubernetes.","infrastructureReviewed":"2026-11-15","infrastructureSources":["https://docs.starrocks.io/docs/deployment/sr_operator/","https://docs.starrocks.io/docs/deployment/"],"install":"Official Kubernetes Operator on Amazon EKS or Google GKE","installMethods":["kubernetes","helm"],"kind":"product","license":"Apache License 2.0","licenseModel":"open-source","licenseModelNotes":"The reviewed StarRocks repository uses the Apache License 2.0.","licenseModelSources":["https://github.com/StarRocks/starrocks/blob/main/LICENSE.txt"],"licenseReviewed":"2026-11-15","model":"Fully in your account","modelLabel":"Customer-operated","name":"StarRocks","notes":"This entry covers the open-source StarRocks deployment, not a vendor-hosted service. Size front-end, back-end and compute nodes for the selected shared-nothing or shared-data topology, and validate object-storage, persistent-volume and upgrade compatibility. StarRocks 4.1.7 escapes lookup_string arguments, runs its internal query as the caller, encodes web-console output, validates proc_profile input, restricts diagnostic endpoints to administrators, masks credentials, and updates security dependencies. Upstream does not publish a CVE, severity, or universal affected range for these fixes.","operations":"Customer manages Kubernetes, StarRocks custom resources, storage, networking, credentials, scaling, backups, monitoring and upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"StarRocks Kubernetes Operator","url":"https://docs.starrocks.io/docs/deployment/sr_operator/"},{"title":"StarRocks deployment overview","url":"https://docs.starrocks.io/docs/deployment/"},{"title":"StarRocks Apache 2.0 license","url":"https://github.com/StarRocks/starrocks/blob/main/LICENSE.txt"},{"title":"StarRocks 4.1.7 release","url":"https://github.com/StarRocks/starrocks/releases/tag/4.1.7"},{"title":"Upstream contributor history","url":"https://github.com/StarRocks/starrocks/graphs/contributors"},{"title":"StarRocks 4.1 release notes","url":"https://docs.starrocks.io/releasenotes/release-4.1/"}],"url":"https://launchinyourcloud.com/directory/starrocks/","website":"https://www.starrocks.io/"},{"architecture":"Customer-operated Node.js CMS, admin panel and database","categories":["content-management"],"category":"Content management \u0026 CMS","categoryFit":{"content-management":"Headless content management with content modeling, editorial administration and APIs; paid governance features depend on plan."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"The vendor explicitly identifies AWS, Azure and Google Cloud for self-hosted Strapi. This is its Node.js application in customer infrastructure, not Strapi Cloud; production database, backups and updates remain customer responsibilities.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Strapi self-hosting compatibility","url":"https://strapi.io/hosting","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","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":"Headless CMS for managing structured content and delivering it through APIs.","diligence":{"footprint":{"reviewed":"2026-11-14","scope":"Strapi deployment-guide baseline; not an end-to-end infrastructure bill","source":"https://docs.strapi.io/cms/deployment","status":"documented","summary":"The deployment guide lists a minimum of 1 CPU core, 2 GB RAM and 8 GB disk, with 2+ cores, 4 GB+ and 32 GB+ recommended. Database and workload sizing remain separate."},"iac":{"artifactRef":"Current Strapi 5 Dockerfile/Compose examples; pin project dependencies and base images","artifactUrl":"https://docs.strapi.io/cms/installation/docker","reviewed":"2026-11-20","scope":"Upstream courtesy examples for a custom Strapi 5 project","source":"https://docs.strapi.io/cms/installation/docker","status":"documented","summary":"The Strapi 5 Docker guide supplies development/production Dockerfile and Compose examples for building your own application image. Strapi explicitly does not publish an official container image; do not label a third-party image as upstream-supported."},"licensePricing":{"reviewed":"2026-11-20","scope":"Self-hosted CMS software plans; not Strapi Cloud hosting","source":"https://strapi.io/pricing-self-hosted","status":"documented","summary":"Community is free under MIT. Growth is listed at $45/month including three admin users, with additional users at $15/month. SSO is a separate priced add-on; Enterprise is quoted. Hosting is separate."},"release":{"releasePublishedAt":"2026-11-18T09:11:35Z","releaseTag":"v5.63.0","reviewed":"2026-11-18","scope":"Upstream Strapi 5 release","source":"https://github.com/strapi/strapi/releases/tag/v5.63.0","status":"documented","summary":"Strapi v5.63.0 was published November 18, 2026. It changes invalid-filter, array-limit, null, locale-permission, and AI-job behavior; test queries and rolling upgrades before rollout."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-20","scope":"CMS self-hosted admin-user authentication; paid-plan/add-on scope","source":"https://strapi.io/pricing-self-hosted","status":"documented","summary":"The self-hosted pricing page offers SSO as a paid Growth add-on and includes it in Enterprise. The listed identity options include SAML 2.0 and OAuth2 providers; Community does not gain those entitlements."}},"id":"strapi","infrastructure":["servers"],"infrastructureNotes":"Classified for the documented long-running Node.js application/server deployment with a database; headless APIs do not imply a function-based or static-only deployment.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.strapi.io/cms/deployment"],"install":"Node.js production deployment with a supported SQL database; container/Kubernetes options","installMethods":["source"],"kind":"product","license":"MIT core; commercial Growth/Enterprise features and terms differ","licenseModel":"open-source","licenseModelNotes":"The broad self-hosted listing includes the MIT core and separately licensed Enterprise feature code under ee/ directories; paid hosting alone is not the reason for this classification.","licenseModelSources":["https://github.com/strapi/strapi/blob/develop/packages/core/content-manager/LICENSE","https://docs.strapi.io/cms/deployment"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Strapi Self-Hosted","notes":"This entry covers self-hosted Strapi, not Strapi Cloud. Review workflows, audit logs and other editorial controls are plan-dependent. Confirm supported database/runtime versions and storage requirements for the selected release. Strapi 5.62.0, released November 12, 2026, includes a security patch whose detailed disclosure was delayed to allow operators time to upgrade. It also changes invalid boolean-filter handling, so self-hosted operators should review compatibility and upgrade promptly. Strapi v5.63.0 changes filter behavior: invalid or previously dropped conditions now return errors or no results, arrays are limited to 100 items, null semantics change, locale permissions are not automatically restored, and AI jobs require rolling-upgrade care. Test existing queries, permissions, and mixed-version nodes before rollout.","operations":"Customer operates application servers, database, media storage, backups and upgrades.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Self-hosted deployment requirements","url":"https://docs.strapi.io/cms/deployment"},{"title":"Project functionality and core license","url":"https://github.com/strapi/strapi"},{"title":"Licensing and edition terms","url":"https://github.com/strapi/strapi/blob/develop/packages/core/content-manager/LICENSE"},{"title":"Strapi 5.62.0 security release","url":"https://github.com/strapi/strapi/releases/tag/v5.62.0"},{"title":"Strapi v5.63.0 release","url":"https://github.com/strapi/strapi/releases/tag/v5.63.0"}],"url":"https://launchinyourcloud.com/directory/strapi/","website":"https://strapi.io/"},{"architecture":"Dedicated containerized Strategy services in a customer-licensed VPC or VNet, administered and maintained by Strategy.","categories":["data-analytics","ai-tools"],"category":"Data \u0026 analytics","categoryFit":{"ai-tools":"Enterprise includes customizable AI agents and AI-assisted analysis capabilities; exact features and model integrations follow the contracted platform.","data-analytics":"Enterprise business intelligence, dashboards, reporting, embedded analytics and governed data exploration in a dedicated environment."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"Strategy documents a dedicated single-tenant deployment in a customer-licensed AWS, Azure or GCP environment and states that its cloud team administers and maintains the service on the customer's behalf. The pricing page separately limits own-cloud deployment to Enterprise.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Strategy Enterprise in customer-licensed AWS, Azure or Google Cloud","url":"https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise","vendorSupport":"not-assessed"},{"clouds":["stackit"],"notes":"The current pricing FAQ explicitly lists STACKIT alongside AWS, Azure and Google Cloud for Enterprise deployment in the customer cloud environment. Standard is vendor-hosted; contract-specific regions, account access, support and commitment eligibility remain procurement checks.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Strategy Enterprise customer-cloud deployment on STACKIT","url":"https://software.strategy.com/pricing","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-17","clouds":["aws","azure","gcp","stackit"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"vendor"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0],"operator":"vendor"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"vendor"},{"boundary":"cloud-account","cloud":"stackit","controlPlane":"not-assessed","evidence":[1],"operator":"vendor"}],"description":"Vendor-managed enterprise analytics and AI platform deployed as a dedicated single-tenant environment in the customer's public-cloud account.","diligence":{"airGap":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Strategy Enterprise in Your Cloud; unresolved within this edition/deployment","source":"https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise","status":"inconclusive","summary":"Customer-account/VPC custody and dedicated vendor management do not establish no-internet operation, offline licensing or isolated vendor administration."},"commitments":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"Enterprise customer-cloud procurement statement, conditional eligibility","source":"https://software.strategy.com/pricing","status":"documented","summary":"The Enterprise pricing FAQ states usage can count toward cloud commitments/credits for the supported customer-cloud deployment. Confirm the provider agreement, offer and eligible charges; Standard is a different deployment tier."},"compliance":{"reviewed":"2026-11-17","scope":"Enterprise marketing claims versus scoped current attestation","source":"https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise","status":"inconclusive","summary":"The Enterprise security page names SOC 2, ISO 27001 and other frameworks, but the actual report/certificate scope, audit period and applicability to the purchased customer-account deployment were not available in the reviewed page."},"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://software.strategy.com/pl/research-and-reports/cloud-security-enterprise","status":"inconclusive","summary":"Obtain the managed Enterprise HA deployment/region bill of materials, user roles, service fees, data-processing profile and cloud-resource billing boundary from the vendor. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Strategy Enterprise in Your Cloud; unresolved within this edition/deployment","source":"https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise","status":"inconclusive","summary":"The managed Enterprise page does not publish a complete HA bill of materials for 100 users/1 TB. Obtain the service topology, regional availability, capacity and responsibility split in the quote."},"iac":{"reviewed":"2026-11-17","scope":"Vendor-operated Enterprise deployment, not Standard hosted service","source":"https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise","status":"documented","summary":"Enterprise is vendor-managed in the customer cloud account. Obtain the approved provisioning/access design and region/topology with the Enterprise order; a public self-service Terraform/Helm artifact is not established."},"licensePricing":{"reviewed":"2026-11-17","scope":"Strategy Enterprise in Your Cloud: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://software.strategy.com/pricing","status":"documented","summary":"The customer-cloud option is a commercial Strategy Enterprise service. Strategy Standard is vendor-hosted and does not include deployment into the customer's cloud; exact entitlements and cloud-credit treatment follow the Enterprise contract."},"marketplace":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Strategy Enterprise in Your Cloud; unresolved within this edition/deployment","source":"https://software.strategy.com/pricing","status":"inconclusive","summary":"The Enterprise FAQ permits customer-cloud deployment and conditional commitment usage, but does not identify the offer/delivery terms for each provider. Confirm the managed Enterprise order."},"release":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Strategy Enterprise in Your Cloud; unresolved within this edition/deployment","source":"https://www2.strategy.com/producthelp/Current/Workstation/en-us/Content/config_lib_server_scim.htm","status":"inconclusive","summary":"Strategy One Library feature dates do not establish the release installed or upgrade cadence in the contracted Enterprise managed service. Obtain its maintenance and version policy."},"scim":{"reviewed":"2026-11-17","scope":"Strategy One feature evidence; managed Enterprise delivery/entitlement unconfirmed","source":"https://www2.strategy.com/producthelp/Current/Workstation/en-us/Content/config_lib_server_scim.htm","status":"inconclusive","summary":"Strategy One Library documents SCIM 2.0 from September 2025, but the reviewed material does not establish which Library release, enablement and entitlement are supplied in the purchased managed Enterprise environment. Confirm these before treating it as included."},"securityControls":{"reviewed":"2026-11-17","scope":"Enterprise account/network boundary; certification scope reviewed separately","source":"https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise","status":"documented","summary":"The Enterprise architecture describes a dedicated, single-tenant customer-account boundary with vendor administration and VPC configuration. Review the operational access and responsibility split in the contract."},"sso":{"reviewed":"2026-11-17","scope":"Strategy One identity features versus purchased Enterprise service","source":"https://www2.strategy.com/producthelp/Current/WorkstationWeb/en-us/Content/config_lib_server_scim.htm","status":"inconclusive","summary":"Strategy Library documents SAML/OIDC interaction with SCIM, but the reviewed guide does not establish the managed Enterprise package, IdP configuration and contractual entitlement for this listing."}},"id":"strategy-enterprise","infrastructure":["servers"],"infrastructureNotes":"Strategy describes a dedicated single-tenant, containerized environment using cloud virtual networks and provider infrastructure in the customer's licensed cloud, with Strategy operating the platform.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise","https://software.strategy.com/pricing"],"install":"Vendor-assisted, fully managed deployment into the customer's licensed AWS, Azure Google Cloud or STACKIT environment","installMethods":["vendor-assisted","other"],"kind":"platform","license":"Commercial Strategy Enterprise subscription; customer-cloud deployment is not available with the Standard plan.","licenseModel":"commercial-only","licenseModelNotes":"The customer-cloud option is a commercial Strategy Enterprise service. Strategy Standard is vendor-hosted and does not include deployment into the customer's cloud; exact entitlements and cloud-credit treatment follow the Enterprise contract.","licenseModelSources":["https://software.strategy.com/pricing","https://software.strategy.com/company/product-listing"],"licenseReviewed":"2026-11-17","model":"BYOC","modelLabel":"Vendor-operated BYOC","name":"Strategy Enterprise in Your Cloud","notes":"This entry covers the Strategy Enterprise customer-cloud option, not Strategy Standard in the vendor's managed environment. Strategy describes the service as fully managed despite its deployment in a customer-licensed AWS, Azure Google Cloud or STACKIT environment, so it is classified as BYOC rather than fully customer-operated. Confirm contract-specific account ownership, cloud-resource billing, service availability, support boundaries and cloud-commitment eligibility before procurement.","operationReview":{"controlPlane":"not-assessed","modelLabel":"Vendor-operated BYOC","operator":"vendor","reviewed":"2026-11-20","source":"https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise","summary":"Strategy Enterprise is fully managed in the customer's selected cloud environment. The customer administers the analytics solution while Strategy maintains platform infrastructure and application upgrades.","supportingSources":[{"title":"Enterprise customer-cloud eligibility, including STACKIT","url":"https://software.strategy.com/pricing"}]},"operations":"Strategy administers and maintains the platform; the customer supplies the cloud environment, data sources, identity, network approvals and shared governance responsibilities.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Strategy plans, customer-cloud option and named providers","url":"https://software.strategy.com/pricing"},{"title":"Strategy Managed Cloud Enterprise security and operating model","url":"https://software.strategy.com/pl/research-and-reports/cloud-security-enterprise"},{"title":"Strategy on AWS and customer-licensed cloud environments","url":"https://software.strategy.com/ecosystems/aws"},{"title":"Strategy product licensing list","url":"https://software.strategy.com/company/product-listing"},{"title":"Strategy for regulated industries and customer-cloud custody","url":"https://software.strategy.com/ecosystems/regulated-industries"}],"url":"https://launchinyourcloud.com/directory/strategy-enterprise/","website":"https://software.strategy.com/pricing"},{"architecture":"Sunbird RC services, database and identity/storage dependencies deployed by AWS CDK/Helm or GKE Terraform/Helm.","categories":["backend-platforms"],"category":"Backend platforms","categoryFit":{"backend-platforms":"Open-source registries and verifiable-credential building blocks with named-cloud deployments."},"cloudEvidence":[{"clouds":["aws"],"notes":"Sunbird RC services, database and identity/storage dependencies deployed by AWS CDK/Helm or GKE Terraform/Helm. The product is a registry and credential platform. Municipal permitting or licence-renewal workflows require a separate configured application. Deployment packaging and individual registry-component releases have independent versions and licences.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"AWS CDK","url":"https://raw.githubusercontent.com/Sunbird-RC/aws-cdk/main/README.md","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Sunbird RC services, database and identity/storage dependencies deployed by AWS CDK/Helm or GKE Terraform/Helm. The product is a registry and credential platform. Municipal permitting or licence-renewal workflows require a separate configured application. Deployment packaging and individual registry-component releases have independent versions and licences.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"GCP Terraform","url":"https://raw.githubusercontent.com/Sunbird-RC/gcp-devops/main/README.md","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","gcp"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/Sunbird-RC/sunbird-rc-core/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/Sunbird-RC/sunbird-rc-core"}],"summary":"The reviewed upstream contributor history includes tejash-jl, jyotsnaraveendran, dileepbapat, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee."},"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"}],"description":"Open-source registries and verifiable-credential building blocks with named-cloud deployments.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Registry component scope; current numeric workload and HA sizing remains unconfirmed","source":"https://rc.sunbird.org/registry/technical-overview/high-level-architecture","status":"inconclusive","summary":"The official architecture and deployment recipes span registry, PostgreSQL, identity, search and optional workflow/queue services, but do not establish a current whole-stack CPU/RAM/storage minimum for this workload. Enabled services, registry records, credentials, query rate and replicas must be sized separately; a sample cluster is not a 1 TB HA capacity guarantee.","supportingSources":[{"title":"Official AWS CDK/Helm deployment collection","url":"https://github.com/Sunbird-RC/aws-cdk/blob/main/README.md"}]},"iac":{"artifactRef":"main (moving branch)","artifactUrl":"https://github.com/Sunbird-RC/aws-cdk/tree/main","reviewed":"2026-11-19","scope":"Reviewed deployment source collection; application images and infrastructure components have separate versions","source":"https://raw.githubusercontent.com/Sunbird-RC/aws-cdk/main/README.md","status":"documented","summary":"The reviewed source supplies deployment configuration for Sunbird RC services, database and identity/storage dependencies deployed by AWS CDK/Helm or GKE Terraform/Helm. Set organization-specific secrets, networking, storage and compatible image versions before use."},"licensePricing":{"reviewed":"2026-11-19","scope":"Sunbird RC (Registries \u0026 Credentials); software terms only, excluding cloud charges, labour and separately licensed services","source":"https://raw.githubusercontent.com/Sunbird-RC/sunbird-rc-core/main/LICENSE","status":"documented","summary":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"release":{"releasePublishedAt":"2026-08-10T13:20:43Z","releaseTag":"v2.1.0","reviewed":"2026-11-19","scope":"Sunbird RC (Registries \u0026 Credentials) upstream application; verify compatibility with the selected package","source":"https://github.com/Sunbird-RC/sunbird-rc-core/releases/tag/v2.1.0","status":"documented","summary":"Reviewed upstream v2.1.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence."},"sso":{"reviewed":"2026-11-20","scope":"Documented custom integration and old dependency boundary; current release/installation-wide federation remains unconfirmed","source":"https://rc.sunbird.org/use/developer-guide/custom-keycloak-build","status":"inconclusive","summary":"The registry architecture uses Keycloak for authentication and its entity API documents token generation. A separate guide describes Meripehchaan SSO using a custom Keycloak 14-based build with configurable nonce validation. This does not confirm a currently supported, version-matched external IdP/browser-login path for every RC 2.1 deployment or frontend; verify broker/client, claims/roles and dependency compatibility.","supportingSources":[{"title":"Registry identity component scope","url":"https://rc.sunbird.org/registry/technical-overview/high-level-architecture"},{"title":"Entity authentication is a separate token path","url":"https://rc.sunbird.org/registry/api-reference/registry/authenticating-as-an-entity"}]}},"id":"sunbird-rc","infrastructure":["servers"],"infrastructureNotes":"Sunbird RC services, database and identity/storage dependencies deployed by AWS CDK/Helm or GKE Terraform/Helm. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://raw.githubusercontent.com/Sunbird-RC/aws-cdk/main/README.md","https://raw.githubusercontent.com/Sunbird-RC/gcp-devops/main/README.md"],"install":"CloudFormation; Terraform; Helm / Kubernetes operator; Kubernetes manifests","installMethods":["cloudformation","terraform","helm","kubernetes"],"kind":"platform","license":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://raw.githubusercontent.com/Sunbird-RC/sunbird-rc-core/main/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Sunbird RC (Registries \u0026 Credentials)","notes":"The product is a registry and credential platform. Municipal permitting or licence-renewal workflows require a separate configured application. Deployment packaging and individual registry-component releases have independent versions and licences.","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 CDK","url":"https://raw.githubusercontent.com/Sunbird-RC/aws-cdk/main/README.md"},{"title":"GCP Terraform","url":"https://raw.githubusercontent.com/Sunbird-RC/gcp-devops/main/README.md"},{"title":"MIT","url":"https://raw.githubusercontent.com/Sunbird-RC/sunbird-rc-core/main/LICENSE"},{"title":"Releases","url":"https://github.com/Sunbird-RC/sunbird-rc-core/releases"}],"url":"https://launchinyourcloud.com/directory/sunbird-rc/","website":"https://rc.sunbird.org"},{"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/"},{"architecture":"Customer-operated management server container with persistent repositories, database data, proxy services and managed-system connections.","categories":["devops"],"category":"DevOps","categoryFit":{"devops":"Automates Linux provisioning, patching, configuration, monitoring, inventory and compliance operations across managed systems."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"SUSE states that its public-cloud requirements and procedures were tested on Amazon EC2, Microsoft Azure and Google Compute Engine. The customer operates the instance, DNS, private networking and durable storage; billing and image availability differ by provider.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"SUSE Multi-Linux Manager public-cloud installation on EC2, Azure and GCE","url":"https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/pubcloud-requirements.html","vendorSupport":"not-assessed"},{"clouds":["aws","azure"],"notes":"The public-cloud guide documents BYOS on AWS and Azure and PAYG on AWS. This evidence qualifies procurement models; it does not extend PAYG availability to Azure or Google Cloud.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"SUSE Multi-Linux Manager BYOS and PAYG public-cloud models","url":"https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-17","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],"operator":"customer"}],"description":"Open-source Linux infrastructure management and automation platform deployed as a customer-operated container or cloud virtual machine.","diligence":{"airGap":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for SUSE Multi-Linux Manager 5.2; unresolved within this edition/deployment","source":"https://documentation.suse.com/multi-linux-manager/5.2/pdf/en/suse_multi_linux_manager_administration_guide.pdf","status":"inconclusive","summary":"The reviewed 5.2 administration PDF identifies itself as Beta 1 and describes disconnected repository synchronization. It does not settle the supported GA installation, subscription renewal, container updates and client-content transfer workflow."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for SUSE Multi-Linux Manager 5.2; unresolved within this edition/deployment","source":"https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html","status":"inconclusive","summary":"AWS PAYG and BYOS variants have different entitlement/billing terms. The public-cloud guide does not establish qualifying charges under a buyer commitment agreement."},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://documentation.suse.com/multi-linux-manager/5.2/en/docs/administration/auth-methods-sso.html","status":"inconclusive","summary":"The reviewed SUSE Multi-Linux Manager 5.2 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://documentation.suse.com/multi-linux-manager/5.2/en/docs/installation-and-upgrade/hardware-requirements.html","status":"inconclusive","summary":"Specify managed clients, OS repositories/proxies, subscription units and a supported HA/recovery design. The guide requires local PostgreSQL, so substituting RDS Multi-AZ is not established. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"5.2 storage and database requirements; not an approved active-active HA design","source":"https://documentation.suse.com/multi-linux-manager/5.2/en/docs/installation-and-upgrade/hardware-requirements.html","status":"documented","summary":"Size the server and proxy for managed clients and mirrored repositories, not human users. PostgreSQL must be local; remote PostgreSQL and NFS database storage are unsupported. Separate persistent repository/database devices and supported filesystems are recommended."},"iac":{"reviewed":"2026-11-17","scope":"Multi-Linux Manager container deployment","source":"https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/container-deployment/mlm/server-deployment-mlm.html","status":"documented","summary":"The 5.2 server workflow deploys containers using mgradm on the supported host OS, with persistent volumes and separately prepared repository/database storage. Select the matching BYOS/PAYG cloud image and entitlements."},"licensePricing":{"reviewed":"2026-11-17","scope":"SUSE Multi-Linux Manager 5.2: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://documentation.suse.com/releasenotes/legacy/multi-linux-manager/5.2/index.html","status":"documented","summary":"SUSE describes Multi-Linux Manager as an open-source infrastructure-management solution based on Uyuni and publishes corresponding GPL source. SUSE-provided images, updates, support, host entitlements and trademarks remain governed by the selected subscription and commercial terms."},"marketplace":{"availability":"edition-dependent","reviewed":"2026-11-17","scope":"Product-specific public-cloud delivery variants","source":"https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html","status":"documented","summary":"The public-cloud guide documents AWS BYOS/PAYG and Azure BYOS routes. Google Cloud is tested but a corresponding Marketplace offer is not established by the guide; proxies are BYOS only."},"release":{"reviewed":"2026-11-17","scope":"5.2 Server release notes; document revision time is not a software release timestamp","source":"https://documentation.suse.com/releasenotes/legacy/multi-linux-manager/5.2/index.html","status":"documented","summary":"The reviewed 5.2 Server notes include 5.2.1 updates, PostgreSQL 18, platform changes and security fixes. Kubernetes deployment remains a Technology Preview; the notes document host/feature support separately from container and proxy versions."},"scim":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for SUSE Multi-Linux Manager 5.2; unresolved within this edition/deployment","source":"https://documentation.suse.com/multi-linux-manager/5.2/en/docs/administration/auth-methods-sso.html","status":"inconclusive","summary":"The SAML guide requires the Manager user to exist before enabling SSO. It does not establish a SCIM endpoint or automatic lifecycle provisioning."},"securityControls":{"reviewed":"2026-11-17","scope":"Manager identity trust; not SCIM or a certification","source":"https://documentation.suse.com/multi-linux-manager/5.2/en/docs/administration/auth-methods-sso.html","status":"documented","summary":"The SSO workflow requires mapping the IdP uid to an existing Manager user and protecting signing/encryption material. SSO does not automatically provision accounts or grant other SUSE products the same identity support."},"sso":{"availability":"available","reviewed":"2026-11-17","scope":"SUSE Multi-Linux Manager 5.2 server authentication","source":"https://documentation.suse.com/multi-linux-manager/5.2/en/docs/administration/auth-methods-sso.html","status":"documented","summary":"Multi-Linux Manager supports SAML 2 SSO with signed/encrypted assertions and SP metadata. The corresponding Manager user must exist before enabling SSO; selecting an IdP and its support remain customer responsibilities."}},"id":"suse-multi-linux-manager","infrastructure":["servers"],"infrastructureNotes":"The supported 5.2 deployment runs persistent server and proxy containers on customer virtual machines with large durable repository and database volumes.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/container-deployment/mlm/server-deployment-mlm.html","https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/pubcloud-requirements.html"],"install":"SUSE Multi-Linux Manager 5.2 container with mgradm on SL Micro 6.2 or SLES 15 SP7, or a SUSE-provided cloud VM image","installMethods":["docker","vm-image","package"],"kind":"platform","license":"Open-source product based on Uyuni with component open-source licenses; SUSE subscriptions, support, images and trademarks use separate commercial terms.","licenseModel":"open-source","licenseModelNotes":"SUSE describes Multi-Linux Manager as an open-source infrastructure-management solution based on Uyuni and publishes corresponding GPL source. SUSE-provided images, updates, support, host entitlements and trademarks remain governed by the selected subscription and commercial terms.","licenseModelSources":["https://documentation.suse.com/releasenotes/legacy/multi-linux-manager/5.2/index.html","https://www.suse.com/products/multi-linux-manager/"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"SUSE Multi-Linux Manager 5.2","notes":"SUSE documents public-cloud installation tested on Amazon EC2, Google Compute Engine and Microsoft Azure. Keep the server on a restricted private network with working forward-confirmed reverse DNS and external persistent disks for repositories and database data. AWS supports PAYG and BYOS; Azure supports BYOS, while the public guide's GCP path is a tested customer-operated installation rather than a confirmed marketplace billing offer. Public-cloud proxies are BYOS-only.","operations":"Customer manages the cloud VM, private networking, DNS, storage, server and proxy containers, repository synchronization, backups, upgrades and registered systems.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"SUSE Multi-Linux Manager 5.2 documentation","url":"https://documentation.suse.com/multi-linux-manager/5.2/"},{"title":"Public-cloud requirements for EC2, GCE and Azure","url":"https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/pubcloud-requirements.html"},{"title":"Public Cloud Guide and subscription models","url":"https://documentation.suse.com/multi-linux-manager/5.2/en/docs/specialized-guides/public-cloud-guide/overview.html"},{"title":"SUSE Multi-Linux Manager 5.2 container deployment","url":"https://documentation.suse.com/suma/5.2/en/docs/installation-and-upgrade/container-deployment/mlm/server-deployment-mlm.html"},{"title":"SUSE Multi-Linux Manager 5.2 release notes","url":"https://documentation.suse.com/releasenotes/legacy/multi-linux-manager/5.2/index.html"},{"title":"Product and subscription overview","url":"https://www.suse.com/products/multi-linux-manager/"}],"url":"https://launchinyourcloud.com/directory/suse-multi-linux-manager/","website":"https://www.suse.com/products/multi-linux-manager/"},{"architecture":"Persistent observability services, ingestion and storage components on a dedicated customer Kubernetes cluster.","categories":["observability"],"category":"Observability","categoryFit":{"observability":"Collects, correlates and visualizes Kubernetes topology, metrics, events and related operational signals in a customer-operated deployment."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"The server-installation guide explicitly covers the Observability server on EKS, AKS and GKE and supplies the Helm installation. The customer operates the dedicated server cluster, default storage class, persistent volumes and ingress; monitored-cluster agent integrations are separate.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"SUSE Observability on EKS, AKS and GKE","url":"https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html","vendorSupport":"not-assessed"},{"clouds":["alibaba"],"notes":"The server guide supplies ACK-specific Helm values for stateful backend PVCs, each at least 20 GiB. This is server deployment evidence, distinct from monitoring an ACK cluster with an agent. Apply the selected HA sizing profile and provider storage requirements.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"SUSE Observability server installation on Alibaba ACK","url":"https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/kubernetes_openshift/ack.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-17","clouds":["aws","azure","gcp","alibaba"],"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":"cloud-account","cloud":"alibaba","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Commercial observability platform installed by Helm into a dedicated customer Kubernetes cluster.","diligence":{"airGap":{"availability":"available","reviewed":"2026-11-17","scope":"Licensed self-hosted Observability server, not agents only","source":"https://documentation.suse.com/cloudnative/suse-observability/latest/en/k8s-suse-rancher-prime-air-gapped.html","status":"documented","summary":"SUSE supplies an air-gapped server installation workflow: download the charts/images, transfer them to the isolated network, load a private registry and apply the licensed Helm configuration. Configure registry credentials and preserve the chosen sizing profile."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for SUSE Observability Self-Hosted; unresolved within this edition/deployment","source":"https://www.suse.com/products/subscription_terms.pdf","status":"inconclusive","summary":"The self-hosted SUSE subscription and Helm installation do not establish an eligible offer or contract-specific 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://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html","status":"inconclusive","summary":"The reviewed SUSE Observability 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":{"estimate":{"currency":"USD","exclusions":["Software licence and support","Operating labor","Backups and recovery testing","Load balancing, NAT/endpoints, IPv4 and all data transfer","Monitoring, mail and other services","Taxes and discounts","Observed-node count, ingestion and retention above the 150-ha profile","Storage beyond default PVC requests; profile is not a promise of 1 TB retained source data"],"kind":"partial-infrastructure","period":"month","region":"AWS us-east-1","rows":[{"description":"3 Linux m6i.8xlarge VMs × 730 hours; capacity is an editorial planning choice, not a vendor 100-user benchmark","id":"compute","quantity":2190,"rate":1.536},{"description":"2745 GB provisioned gp3 capacity, including stated boot/data allowance; base IOPS/throughput only","id":"storage","quantity":2745,"rate":0.08},{"description":"One EKS cluster on standard version support; Auto Mode, paid add-ons and observability excluded","id":"external","quantity":730,"rate":0.1},{"description":"Unpriced; include if required by the selected topology","id":"database","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"backup","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"network","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"license","quantity":1,"rate":""},{"description":"Unpriced; see scope/exclusions; do not assume zero","id":"labor","quantity":1,"rate":""}],"workload":"100 internal users; 1 TB (1,000 GB) logical data; HA target; average usage unmeasured; 730 h/month. See reviewed scope for topology, replication, retention and sizing assumptions."},"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":"Smallest documented HA profile, not a conversion from 100 users/1 TB into monitored-node capacity. It exceeds a 1 TB storage allowance before boot volumes. 96 vCPU/384 GiB fleet leaves nominal CPU/memory capacity after one worker loss; scheduling, AZ/storage failover and rolling updates still need validation.","source":"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","status":"inconclusive","summary":"Illustrative priced infrastructure subtotal: USD 3,656.44/month. Three 32-vCPU/128-GiB workers price the minimum 150-ha profile, plus its 2,595 GiB default PVC request and 150 GB boot allowance. For this illustration each requested GiB is budgeted as one EBS billing GB. This is not a complete operating-cost estimate or a validated capacity/SLA claim.","supportingSources":[{"title":"Product topology/sizing basis","url":"https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/requirements.html"},{"title":"Current AWS documentation: us-east-1 gp3 capacity example","url":"https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html"},{"title":"EBS performance and charging qualifications","url":"https://aws.amazon.com/ebs/pricing/"},{"title":"EKS standard versus extended support pricing","url":"https://aws.amazon.com/eks/pricing/"}]},"footprint":{"reviewed":"2026-11-17","scope":"Observability 150-ha resource requests, not CPU limits or physical-node counts","source":"https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/requirements.html","status":"documented","summary":"The smallest HA profile (150-ha) requests 49.8 CPU and 130.7 GiB RAM across at least three workers, with 2,595 GiB default storage. It is based on observed default-node capacity, not users; spare rolling-update capacity is additional."},"iac":{"reviewed":"2026-11-17","scope":"Self-hosted server Helm installation","source":"https://documentation.suse.com/cloudnative/suse-observability/latest/en/installing-suse-obs.html","status":"documented","summary":"The server installer uses the SUSE Observability Helm repository, licence key and a selected sizing profile. It provisions the Observability backend on EKS/AKS/GKE; agent installation is a separate workflow."},"licensePricing":{"reviewed":"2026-11-17","scope":"SUSE Observability Self-Hosted: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://www.suse.com/products/subscription_terms.pdf","status":"documented","summary":"The self-hosted SUSE Observability product requires a commercial subscription and license key. SUSE Cloud Observability is a separate hosted offering."},"marketplace":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for SUSE Observability Self-Hosted; unresolved within this edition/deployment","source":"https://documentation.suse.com/cloudnative/suse-observability/latest/en/installing-suse-obs.html","status":"inconclusive","summary":"The reviewed server guide supplies a licensed Helm repository, not a cloud-provider billing offer. A current Marketplace offer for this self-hosted server was not established."},"release":{"releasePublishedOn":"2026-11-12","releaseTag":"2.13.0","reviewed":"2026-11-18","scope":"Dated SUSE Observability self-hosted Helm release snapshot; the deprecated Values helper chart is not a universal installation requirement","source":"https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/release-notes/v2.13.0.html","status":"documented","summary":"The self-hosted Helm chart v2.13.0 release notes are dated November 12, 2026. They list SUSE Observability 2.13.0, Values helper chart 1.4.13 (deprecated since 2.8.0), Agent 1.7.64 and CLI 3.9.0. Component versions are separate; apply every version-specific upgrade step from the installed version through 2.13.0, including the changed scheduling precedence."},"scim":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for SUSE Observability Self-Hosted; unresolved within this edition/deployment","source":"https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html","status":"inconclusive","summary":"The server supports selected OIDC/LDAP authentication and role mappings, but a SCIM provisioning endpoint and lifecycle operations were not established."},"securityControls":{"reviewed":"2026-11-17","scope":"Server identity and role hardening; not monitored-cluster agent settings","source":"https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html","status":"documented","summary":"The default shared administrator password is explicitly not production-ready. Configure an external identity method, limit administrator roles and review RBAC before production use."},"sso":{"availability":"available","reviewed":"2026-11-17","scope":"SUSE Observability server authentication","source":"https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/security/authentication/authentication_options.html","status":"documented","summary":"The server supports OIDC, including Rancher and Keycloak configurations, or LDAP as the selected authentication mechanism. Only one mechanism is configured at a time; map external groups to the intended server roles."}},"id":"suse-observability-self-hosted","infrastructure":["servers"],"infrastructureNotes":"SUSE Observability runs persistent stateful services on a dedicated Kubernetes cluster with durable storage and substantial capacity requirements.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html"],"install":"SUSE Observability server Helm chart on EKS, AKS, GKE or Alibaba ACK, with provider-specific storage configuration","installMethods":["helm","kubernetes"],"kind":"platform","license":"Commercial SUSE Observability self-hosted subscription and license key required.","licenseModel":"commercial-only","licenseModelNotes":"The self-hosted SUSE Observability product requires a commercial subscription and license key. SUSE Cloud Observability is a separate hosted offering.","licenseModelSources":["https://www.suse.com/products/subscription_terms.pdf","https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"SUSE Observability Self-Hosted","notes":"This entry covers the self-hosted server product, not SUSE Cloud Observability SaaS. Installation requires a license key, compatible Helm and Kubernetes versions, persistent storage and dedicated sizing. High-availability and non-high-availability profiles are not interchangeable after installation, so choose the production topology before deployment. SUSE Observability 2.13.0 includes authentication, disk, and backup fixes and requires the documented sequential upgrade path. Version 2.10 reached end of support on November 12, 2026; move through supported intermediate releases as required.","operations":"Customer manages the Kubernetes cluster, persistent storage, sizing, ingress, certificates, backups, upgrades and monitored-system access.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Install SUSE Observability self-hosted","url":"https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/installing-suse-obs.html"},{"title":"Kubernetes quick start and named-cloud integrations","url":"https://documentation.suse.com/en-us/cloudnative/suse-observability/latest/en/k8s-quick-start-guide.html"},{"title":"SUSE subscription terms","url":"https://www.suse.com/products/subscription_terms.pdf"},{"title":"Alibaba ACK server Helm installation and PVC minimums","url":"https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/install-stackstate/kubernetes_openshift/ack.html"},{"title":"SUSE Observability 2.13.0 release notes","url":"https://documentation.suse.com/cloudnative/suse-observability/latest/en/setup/release-notes/v2.13.0.html"},{"title":"SUSE product lifecycle","url":"https://www.suse.com/lifecycle/"}],"url":"https://launchinyourcloud.com/directory/suse-observability-self-hosted/","website":"https://www.suse.com/products/observability/"},{"advisories":[{"action":"Follow the 5.6.4 scanner restart and database-update instructions, including the transfer process in isolated environments.","conditions":"Older scanners cache the controller capability response. SUSE also calls for current scanner/CVE database content for PHP vulnerability checks.","id":"neuvector-5-6-4-scanner-upgrade","listingIds":["suse-security-neuvector"],"reviewed":"2026-11-18","scope":"Upgrades from pre-5.6.0 controllers with existing scanner pods; not a claim of a new exploitable vulnerability in every NeuVector installation.","source":"https://documentation.suse.com/cloudnative/security/5.6/en/5x.html","summary":"SUSE requires existing scanner pods to restart or redeploy when upgrading from before 5.6.0 to 5.6.4 or later, so cached capabilities recognize critical CVE severity.","title":"NeuVector scanner restart required for critical-severity results","type":"security-advisory"}],"architecture":"Manager, controller and scanner services plus an enforcer DaemonSet inside the customer Kubernetes cluster.","categories":["devops","observability"],"category":"DevOps","categoryFit":{"devops":"Adds runtime security, vulnerability scanning and policy enforcement to customer Kubernetes delivery environments.","observability":"Provides workload, network and security-event visibility for Kubernetes clusters."},"cloudEvidence":[{"clouds":["aws","azure","gcp","ibm","alibaba","oci"],"notes":"SUSE explicitly names AWS EKS, Azure AKS, Google Cloud, IBM Cloud Kubernetes, Alibaba Cloud and Oracle Cloud and links full Kubernetes/Helm application deployment. Confirm tested platform versions and privileges. GKE Autopilot requires allowlists; AWS ECS is no longer supported in the requirements guide.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"SUSE Security on six named public-cloud Kubernetes services","url":"https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-18","clouds":["aws","azure","gcp","ibm","alibaba","oci"],"communityAcceptance":{"reviewed":"2026-11-18","sources":[{"title":"Official maintenance and adoption evidence","url":"https://github.com/neuvector/neuvector/blob/main/CONTRIBUTING.md"},{"title":"Official maintenance and adoption evidence","url":"https://github.com/neuvector/neuvector/releases/tag/v5.6.4"},{"title":"Official maintenance and adoption evidence","url":"https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4"}],"summary":"NeuVector publishes contribution/governance instructions and maintained public application and Helm releases. This is sustained upstream participation rather than a star-count threshold; commercial SUSE support remains a separately purchased entitlement."},"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":"cloud-account","cloud":"ibm","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"alibaba","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"oci","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Open-source Kubernetes security platform with documented customer-operated deployment on AWS, Azure, Google Cloud, IBM Cloud, Alibaba Cloud and OCI.","diligence":{"airGap":{"availability":"available","reviewed":"2026-11-18","scope":"SUSE Security (NeuVector): selected customer-operated edition","source":"https://documentation.suse.com/cloudnative/security/5.6/en/airgap.html","status":"documented","summary":"The air-gap guide mirrors charts and images using Skopeo/zstd, transfers them and deploys from an internal registry. Its example versions are older than the current 5.6 line; resolve matching current application/chart/scanner versions and arrange offline vulnerability-database updates."},"commitments":{"reviewed":"2026-11-18","scope":"SUSE Security (NeuVector): selected customer-operated edition","source":"https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw","status":"inconclusive","summary":"The multi-product private-offer route does not settle the buyer’s commitment eligibility or whether SUSE Security is included in the selected contract. Confirm exact entitlement, billable dimensions and cloud agreement.","supportingSources":[{"title":"AWS commitment qualification is product/agreement-specific","url":"https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html"}]},"compliance":{"reviewed":"2026-11-18","scope":"SUSE organisational management systems including the scheduled NeuVector entity; not a customer-deployment attestation","source":"https://www.suse.com/support/security/certifications/SUSE-ISO-27001-ISO-27701.pdf","status":"documented","summary":"LRQA certificate 10726335 covers SUSE’s ISO/IEC 27001:2022 ISMS and ISO/IEC 27701:2019 PIMS; schedule page 28 explicitly includes NeuVector, LLC. Issued November 4, 2025, it expires November 3, 2028. This is organisational information/privacy management assurance, not certification of a customer’s NeuVector cluster, protected workloads, configuration or operations.","supportingSources":[{"title":"Official SUSE certificate index","url":"https://www.suse.com/support/security/certifications/isoiec-certification/"}]},"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://documentation.suse.com/cloudnative/security/5.6/en/requirements.html","status":"inconclusive","summary":"Size by protected Kubernetes node count, network throughput, container/image scan volume, registry retention and HA controller/scanner design, not directory users. Include per-node enforcers, scan capacity, persistent configuration and any SUSE support subscription. The manager redundancy conflict also needs resolution.","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":"SUSE Security (NeuVector): selected customer-operated edition","source":"https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html","status":"documented","summary":"The requirements recommend three controllers for HA, an enforcer on each worker and separate scanner/manager resources. Controller minimum is 1 CPU/2 GB; an enforcer needs 1+ CPU/1 GB and a scanner 1 CPU/2 GB before workload growth. The public-cloud guide warns against multiple managers behind a load balancer because of session state, while requirements suggest manager redundancy; resolve that design before claiming full HA.","supportingSources":[{"title":"Manager scaling caveat and cloud topology","url":"https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html"}]},"iac":{"artifactRef":"NeuVector Helm chart v2.11.4","artifactUrl":"https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4","reviewed":"2026-11-18","scope":"SUSE Security (NeuVector): selected customer-operated edition","source":"https://documentation.suse.com/cloudnative/security/latest/en/helm.html","status":"documented","summary":"NeuVector maintains a Helm chart for manager/controller/enforcer/scanner deployment. The reviewed chart release is v2.11.4, separate from application v5.6.4. Pin image tags and check values/privileges; air-gap documentation’s historical chart example is not a current version pin."},"licensePricing":{"reviewed":"2026-11-18","scope":"SUSE Security (NeuVector): selected customer-operated edition","source":"https://github.com/neuvector/neuvector/blob/main/LICENSE","status":"documented","summary":"Upstream NeuVector is Apache 2.0 licensed. SUSE subscription-delivered images, support and Rancher Prime integrations may require commercial entitlements. The multi-product AWS order is distinct from the free upstream code licence.","supportingSources":[{"title":"SUSE commercial procurement path","url":"https://documentation.suse.com/cloudnative/security/5.6/en/awsmarketplace.html"}]},"marketplace":{"availability":"edition-dependent","offers":[{"cloud":"aws","delivery":"SaaS-labelled multi-product private-offer subscription","id":"prodview-b6es6ar6n4siw","publisher":"SUSE","url":"https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw"}],"reviewed":"2026-11-18","scope":"SUSE Security (NeuVector): selected customer-operated edition","source":"https://documentation.suse.com/cloudnative/security/5.6/en/awsmarketplace.html","status":"documented","summary":"SUSE’s security guide routes AWS procurement through its multi-product Rancher/SUSE subscription offer. The current offer is a private-offer commercial contract labelled SaaS delivery; it is not a standalone upstream OSS AMI or proof of included NeuVector support. Confirm the Security entitlement in the order.","supportingSources":[{"title":"Actual SUSE Cloud Marketplace Program offer","url":"https://aws.amazon.com/marketplace/pp/prodview-b6es6ar6n4siw"}]},"release":{"releasePublishedAt":"2026-10-27T16:32:44Z","releaseTag":"v5.6.4","reviewed":"2026-11-18","scope":"SUSE Security (NeuVector): selected customer-operated edition","source":"https://github.com/neuvector/neuvector/releases/tag/v5.6.4","status":"documented","summary":"NeuVector v5.6.4 was published October 27, 2026; chart v2.11.4 is a separate release. When upgrading from before v5.6.0, SUSE requires restarting/redeploying existing scanner pods for critical CVE severity handling. Maintenance releases on older branches are not a newer major-line snapshot.","supportingSources":[{"title":"5.6.4 upgrade and scanner requirements","url":"https://documentation.suse.com/cloudnative/security/5.6/en/5x.html"},{"title":"Separate chart release","url":"https://github.com/neuvector/neuvector-helm/releases/tag/v2.11.4"}]},"scim":{"reviewed":"2026-11-18","scope":"SUSE Security (NeuVector): selected customer-operated edition","source":"https://documentation.suse.com/cloudnative/security/5.6/en/saml.html","status":"inconclusive","summary":"SAML group-to-role mapping does not establish a SCIM server or provisioning/deprovisioning operations. Confirm a current endpoint and user-removal behavior for the selected OSS or subscription-delivered edition."},"securityControls":{"reviewed":"2026-11-18","scope":"SUSE Security (NeuVector): selected customer-operated edition","source":"https://documentation.suse.com/cloudnative/security/5.6/en/saml.html","status":"documented","summary":"NeuVector documents SAML role mapping and signed-assertion requirements. Enforcers run on cluster nodes and controllers coordinate security policy, so deployment needs the documented privileged access and network visibility. Scope cluster roles and protect console/controller access.","supportingSources":[{"title":"Runtime and component requirements","url":"https://documentation.suse.com/cloudnative/security/5.6/en/requirements.html"},{"title":"Cloud network and topology requirements","url":"https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html"}]},"sso":{"availability":"available","reviewed":"2026-11-18","scope":"SUSE Security (NeuVector): selected customer-operated edition","source":"https://documentation.suse.com/cloudnative/security/5.6/en/saml.html","status":"documented","summary":"The v5.6 guide documents SAML 2.0 SSO, including Okta and group-to-role mapping. Signed assertions are required; encrypted assertions are not supported by this documented configuration. Set a deliberate default role rather than assuming group import grants appropriate access."}},"id":"suse-security-neuvector","infrastructure":["servers"],"infrastructureNotes":"SUSE Security runs controller, scanner and enforcement workloads on customer Kubernetes nodes.","infrastructureReviewed":"2026-11-18","infrastructureSources":["https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html"],"install":"SUSE Security Helm chart or manifests on public-cloud Kubernetes","installMethods":["helm","kubernetes"],"kind":"platform","license":"Apache License 2.0 for NeuVector; Rancher Prime delivery and commercial support have separate subscription terms.","licenseModel":"open-source","licenseModelNotes":"NeuVector is Apache-2.0 licensed. SUSE subscriptions can add entitled delivery, integrations and support.","licenseModelSources":["https://github.com/neuvector/neuvector/blob/main/LICENSE"],"licenseReviewed":"2026-11-18","model":"Fully in your account","modelLabel":"Customer-operated","name":"SUSE Security (NeuVector)","notes":"This entry covers upstream NeuVector/SUSE Security deployment; subscription images/support can require commercial entitlements. SUSE names six public-cloud Kubernetes targets. Resolve the conflicting manager-redundancy guidance before HA design, and apply GKE Autopilot allowlists where required. Scan-policy/compliance functions do not certify the customer installation.","operations":"Customer manages Kubernetes, registry access, Helm values, storage, certificates, policies, upgrades, monitoring and cluster privileges.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Deploy SUSE Security on public-cloud Kubernetes","url":"https://documentation.suse.com/external-tree/en-us/cloudnative/security/5.6/en/publick8s.html"},{"title":"Deploy SUSE Security with Helm","url":"https://documentation.suse.com/cloudnative/security/latest/en/helm.html"},{"title":"SUSE Security support matrix","url":"https://www.suse.com/suse-neuvector/support-matrix/all-supported-versions/neuvector-v-all-versions/"},{"title":"NeuVector Apache 2.0 license","url":"https://github.com/neuvector/neuvector/blob/main/LICENSE"}],"url":"https://launchinyourcloud.com/directory/suse-security-neuvector/","website":"https://www.suse.com/products/security/"},{"architecture":"Customer-operated Tableau Server on cloud virtual machines in a single-node or distributed topology.","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Enterprise analytics, governed data exploration, dashboards and business-intelligence publishing on a customer-operated server."},"cloudEvidence":[{"clouds":["aws"],"notes":"Tableau documents customer-managed EC2 installation as the production-ready AWS path. The provider guide is archived, but Tableau states the deployment remains supported.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Tableau Server on Amazon Web Services","url":"https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Tableau documents customer-managed Azure VM installation as the production-ready path. The provider guide is archived, but Tableau states the deployment remains supported.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Tableau Server on Microsoft Azure","url":"https://help.tableau.com/current/server/en-us/ts_azure_deployment_options.htm","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Tableau documents production-ready self-deployment on customer Google Compute Engine virtual machines with BYOL operation. The provider guide is archived.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Tableau Server on Google Cloud","url":"https://help.tableau.com/current/server/en-us/ts_gcp_deployment_options.htm","vendorSupport":"not-assessed"},{"clouds":["alibaba"],"notes":"Tableau documents production-ready self-deployment on customer Alibaba Elastic Compute Service virtual machines with BYOL operation. The provider guide is archived.","reviewed":"2026-11-17","sourceType":"vendor-documentation","title":"Tableau Server on Alibaba Cloud","url":"https://help.tableau.com/current/server/en-us/ts_alibaba_deployment_options.htm","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-17","clouds":["aws","azure","gcp","alibaba"],"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":"alibaba","controlPlane":"not-assessed","evidence":[3],"operator":"customer"}],"description":"Commercial analytics and business-intelligence server installed and operated on customer cloud virtual machines.","diligence":{"airGap":{"reviewed":"2026-11-17","scope":"Offline activation versus complete air-gapped operation","source":"https://help.tableau.com/current/server/en-us/activate_off.htm","status":"inconclusive","summary":"Offline Server activation is documented, but this alone does not establish isolation for every connector, extension, update and identity dependency. Confirm the selected full deployment and licence workflow."},"commitments":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Tableau Server; unresolved within this edition/deployment","source":"https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm","status":"inconclusive","summary":"The reviewed Server deployment/licensing material does not establish a qualifying software Marketplace offer and buyer commitment treatment."},"compliance":{"reviewed":"2026-11-17","scope":"Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited","source":"https://help.tableau.com/current/server/en-us/activate_off.htm","status":"inconclusive","summary":"The reviewed Tableau Server 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://help.tableau.com/current/server/en-us/server_hardware_min.htm","status":"inconclusive","summary":"Obtain the supported multi-node/HA design, user-role licence mix, extract/refresh workload, repository/file-store sizing and any Windows licences. Single-node production recommendations do not price an HA farm. A complete monthly operating estimate is not established."},"footprint":{"reviewed":"2026-11-17","scope":"Production single-node recommendation, not the complete HA design","source":"https://help.tableau.com/current/server/en-us/server_hardware_min.htm","status":"documented","summary":"The production single-node recommendation is 8 physical cores/16 vCPU, 128 GB RAM for 2022.3+ and at least 50 GB disk. Multi-node/HA design needs Tableau guidance; extracts, refresh scratch space and backups add storage."},"iac":{"reviewed":"2026-11-17","scope":"Customer-managed Server; archived automation warnings retained","source":"https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm","status":"documented","summary":"Vendor cloud guides describe installing Server on customer VMs. Archived AWS/Azure Quick Start and Marketplace routes carry production-readiness warnings; use a supported self-deployment design and installation media."},"licensePricing":{"reviewed":"2026-11-17","scope":"Tableau Server: software entitlement and edition boundary; infrastructure and operating costs are separate","source":"https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm","status":"documented","summary":"Tableau Server requires a commercial product key and the applicable user-, core- or subscription-based entitlement. Tableau Cloud is a separate hosted offering."},"marketplace":{"reviewed":"2026-11-17","scope":"Reviewed public evidence for Tableau Server; unresolved within this edition/deployment","source":"https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm","status":"inconclusive","summary":"Archived AWS/Azure deployment guides identify Marketplace paths with production-readiness warnings. A current production-ready offer and entitlement were not confirmed."},"release":{"releasePublishedOn":"2026-10-23","releaseTag":"2026.3","reviewed":"2026-11-17","scope":"Tableau Server vendor release record","source":"https://www.tableau.com/support/releases/server/2026.3","status":"documented","summary":"Tableau Server 2026.3 was released 2026-10-23. The release page warns Windows Server 2016/Windows 10 users to review installation issue W-24614917 before upgrading; this is Server, not Tableau Cloud/Desktop."},"scim":{"availability":"available","reviewed":"2026-11-17","scope":"Tableau Server SCIM; not Tableau Cloud-only documentation","source":"https://help.tableau.com/current/server/en-us/scim_config_online.htm","status":"documented","summary":"Server supports site-level SCIM from 2025.3. Site-specific SAML works from 2025.3.0; TSM-configured authentication and identity pools require 2025.3.1+. Entra/Okta may need an on-premises provisioning connector through the server firewall."},"securityControls":{"reviewed":"2026-11-17","scope":"Server offline activation and licence handling","source":"https://help.tableau.com/current/server/en-us/activate_off.htm","status":"documented","summary":"The offline activation guide distinguishes product keys and ATR workflows. Protect transferred activation files and configure server identity and permissions separately; disconnected activation does not confer a security attestation."},"sso":{"availability":"available","reviewed":"2026-11-17","scope":"Server identity methods applicable to SCIM","source":"https://help.tableau.com/current/server/en-us/scim_config_online.htm","status":"documented","summary":"The Server SCIM guide explicitly supports site-specific SAML, TSM authentication and identity pools with version qualifications. Configure the chosen Server identity method and network reachability separately from provisioning."}},"id":"tableau-server","infrastructure":["servers"],"infrastructureNotes":"The production self-managed path installs Tableau Server on persistent cloud virtual machines; distributed deployments use multiple nodes and external cloud services.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://help.tableau.com/current/server-linux/en-us/ts_tableau_server_cloud_overview.htm","https://help.tableau.com/current/server/en-us/admin.htm"],"install":"Native server installer on customer virtual machines; optional AWS CloudFormation, Azure Resource Manager or marketplace BYOL paths","installMethods":["package","cloudformation","platform-template","vm-image"],"kind":"product","license":"Commercial Tableau Server product-key licensing with user-, core- or subscription-based entitlements.","licenseModel":"commercial-only","licenseModelNotes":"Tableau Server requires a commercial product key and the applicable user-, core- or subscription-based entitlement. Tableau Cloud is a separate hosted offering.","licenseModelSources":["https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm"],"licenseReviewed":"2026-11-17","model":"Fully in your account","modelLabel":"Customer-operated","name":"Tableau Server","notes":"Tableau's provider-specific public-cloud guides are archived and no longer updated, although Tableau states that these deployments remain supported. Native virtual-machine self-deployment is the consistently documented production-ready path; marketplace and Quick Start options are convenience paths and should not be treated as the preferred production architecture. Tableau recommends Tableau Cloud where it meets the customer's requirements.","operations":"Customer manages the virtual machines, operating system, Tableau services, identity, networking, storage, backups, upgrades and availability.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Tableau Server public-cloud overview","url":"https://help.tableau.com/current/server-linux/en-us/ts_tableau_server_cloud_overview.htm"},{"title":"Tableau Server administrator overview","url":"https://help.tableau.com/current/server/en-us/admin.htm"},{"title":"AWS deployment options","url":"https://help.tableau.com/current/server/en-us/ts_aws_deployment_options.htm"},{"title":"Azure deployment options","url":"https://help.tableau.com/current/server/en-us/ts_azure_deployment_options.htm"},{"title":"Google Cloud deployment options","url":"https://help.tableau.com/current/server/en-us/ts_gcp_deployment_options.htm"},{"title":"Alibaba Cloud deployment options","url":"https://help.tableau.com/current/server/en-us/ts_alibaba_deployment_options.htm"},{"title":"AWS prerequisites and licensing","url":"https://help.tableau.com/current/server/en-us/ts_aws_prerequisites.htm"}],"url":"https://launchinyourcloud.com/directory/tableau-server/","website":"https://www.tableau.com/products/server"},{"architecture":"Customer-operated Teleport Auth and Proxy services with provider databases, object storage, DNS and load balancing.","categories":["identity-access-management"],"category":"Identity \u0026 access management","categoryFit":{"identity-access-management":"Provides identity-aware access to servers, Kubernetes, databases and applications through customer-operated authentication and proxy services."},"cloudEvidence":[{"clouds":["aws"],"notes":"Teleport documents a full HA Auth and Proxy deployment on customer EKS with AWS backing services.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"Teleport Enterprise on AWS EKS","url":"https://goteleport.com/docs/installation/self-hosted/helm-deployments/aws/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Teleport documents a full HA deployment on customer AKS.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"Teleport Enterprise on Azure AKS","url":"https://goteleport.com/docs/installation/self-hosted/helm-deployments/azure/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Teleport documents a full HA deployment on customer GKE.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"Teleport Enterprise on Google GKE","url":"https://goteleport.com/docs/installation/self-hosted/helm-deployments/gcp/","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":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Commercial access platform deployed as a high-availability Teleport cluster in the customer's cloud.","diligence":{"airGap":{"availability":"edition-dependent","reviewed":"2026-11-18","scope":"Fully self-hosted Teleport Enterprise with a valid local licence and internally reachable dependencies","source":"https://goteleport.com/docs/reference/deployment/networking/","status":"documented","summary":"Teleport explicitly supports fully air-gapped clusters, including privately reachable Auth and Proxy services. Enterprise uses a local licence file. Automatic licence updates require api.teleport.sh, but the cluster continues without that access while its local licence remains valid. Transfer renewed licences and release artifacts deliberately, and provide internal IdP, DNS, certificates, audit/storage backends and client access.","supportingSources":[{"title":"Offline licence behavior and expiry boundary","url":"https://goteleport.com/docs/installation/self-hosted/license/"},{"title":"Vendor statement of air-gapped self-hosting","url":"https://goteleport.com/use-cases/data-centers/"}]},"commitments":{"reviewed":"2026-11-18","scope":"Teleport Enterprise Self-Hosted: selected customer-operated edition","source":"https://aws.amazon.com/marketplace/pp/prodview-fnmgbsyr3kwko","status":"inconclusive","summary":"The linked AWS public offer prices Cloud only; it does not establish eligible spend for Enterprise Self-Hosted. Confirm a self-hosted private offer, its billed entitlement/support dimensions and the buyer’s applicable AWS commitment terms. Do not transfer the public Cloud offer’s procurement or credits to a self-hosted order.","supportingSources":[{"title":"AWS commitment qualification is product/agreement-specific","url":"https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html"}]},"compliance":{"availability":"edition-dependent","reviewed":"2026-11-18","scope":"Enterprise FIPS-build cryptographic-module boundary; operating environment and approved-mode conditions still require assessment","source":"https://github.com/gravitational/teleport/blob/v18.11.10/docs/pages/zero-trust-access/compliance-frameworks/fedramp.mdx","status":"documented","summary":"Teleport’s v18.11.10 documentation identifies BoringCrypto fips-20220613, CMVP 4735, in Enterprise FIPS builds from 17.7.3/18.0.0. NIST lists the FIPS 140-3 Level 1 module as active, with a July 22, 2029 sunset and approved-mode/tested-configuration conditions. This validates the cryptographic module, not Teleport as a whole, every OS/CPU combination or a customer’s FedRAMP authorisation.","supportingSources":[{"title":"NIST module status, caveats and tested configurations","url":"https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4735"}]},"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://goteleport.com/api/files/teleport-pricing-guide.pdf","status":"inconclusive","summary":"The current pricing guide defines MAUs and hourly/monthly averaged Protected Resources but gives no rates. One hundred internal users is at most a user assumption, not a resource or machine-identity count; 1 TB is not a session-recording retention model. Supply MAUs, protected resources/bots, recording volume/retention, auth/proxy/backend HA design and a self-hosted licence quote before completing the AWS us-east-1 budget.","supportingSources":[{"title":"Self-hosted topology and backend sizing","url":"https://goteleport.com/docs/reference/deployment/scaling/"},{"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":"Teleport Enterprise Self-Hosted: selected customer-operated edition","source":"https://goteleport.com/docs/reference/deployment/scaling/","status":"documented","summary":"Teleport publishes an illustrative HA configuration for up to 10,000 SSH nodes: two Proxy instances at 4 vCPU/8 GB and two Auth at 8 vCPU/16 GB, with appropriate external storage. It is a scale example, not the minimum for 100 users. Kubernetes API request rate, sessions, registered clusters and recording volume require measurement."},"iac":{"artifactRef":"Teleport v18.11.10 chart source","artifactUrl":"https://github.com/gravitational/teleport/tree/v18.11.10/examples/chart/teleport-cluster","reviewed":"2026-11-18","scope":"Teleport Enterprise Self-Hosted: selected customer-operated edition","source":"https://goteleport.com/docs/reference/helm-reference/teleport-cluster/","status":"documented","summary":"The upstream teleport-cluster Helm chart configures Enterprise images using enterprise: true and a customer licence secret. The reviewed chart source is pinned to v18.11.10. Follow the separate EKS/AKS/GKE backend and network configuration guides."},"licensePricing":{"reviewed":"2026-11-18","scope":"Teleport Enterprise Self-Hosted: selected customer-operated edition","source":"https://goteleport.com/api/files/teleport-pricing-guide.pdf","status":"documented","summary":"The June 16, 2026 Enterprise guide bills Monthly Active Users and Teleport Protected Resources, with Standard/Premium feature bundles; Priority Support is included for self-hosted deployments. It publishes metric definitions, not numeric rates. Request a self-hosted quote with protected resources, machine identities and entitlements; public Cloud Marketplace prices are not self-hosted rates.","supportingSources":[{"title":"Public offer explicitly prices Cloud only","url":"https://aws.amazon.com/marketplace/pp/prodview-fnmgbsyr3kwko"}]},"marketplace":{"reviewed":"2026-11-18","scope":"Current linked public AWS offer versus separately negotiated Enterprise Self-Hosted entitlement","source":"https://aws.amazon.com/marketplace/pp/prodview-fnmgbsyr3kwko","status":"inconclusive","summary":"Teleport’s Marketplace announcement describes cloud or self-hosted deployment, but the linked current AWS offer prodview-fnmgbsyr3kwko prices its dimension as Cloud only and excludes support. It does not establish self-hosted licence terms. Obtain a self-hosted order/private-offer identifier, entitlement and support terms rather than transferring the public Cloud price to this deployment.","supportingSources":[{"title":"Broader vendor Marketplace announcement","url":"https://goteleport.com/about/newsroom/press-releases/teleport-infrastructure-identity-platform-in-aws-marketplace-ai-agents-tools/"}]},"release":{"releasePublishedAt":"2026-11-16T16:31:54Z","releaseTag":"v18.11.10","reviewed":"2026-11-18","scope":"Teleport Enterprise Self-Hosted: selected customer-operated edition","source":"https://github.com/gravitational/teleport/releases/tag/v18.11.10","status":"documented","summary":"Teleport v18.11.10 was published November 16, 2026. Match Enterprise images, cluster chart, clients and Terraform provider to the supported upgrade path. Community repository publication does not itself establish the buyer’s commercial support term.","supportingSources":[{"title":"Teleport application change log","url":"https://goteleport.com/docs/changelog/"}]},"scim":{"availability":"edition-dependent","reviewed":"2026-11-18","scope":"Teleport Enterprise Self-Hosted: selected customer-operated edition","source":"https://goteleport.com/docs/identity-governance/integrations/scim/","status":"documented","summary":"Teleport Enterprise Identity Governance documents SCIM 2.0 for users/groups with SAML SSO, OAuth client credentials and matching Access Lists. It requires v17.6.1 or v18.0.3+; the IdP pushes changes into Teleport, not the reverse. Confirm the Identity Governance entitlement and tested deactivation/session-lock behavior."},"securityControls":{"reviewed":"2026-11-18","scope":"Teleport Enterprise Self-Hosted: selected customer-operated edition","source":"https://goteleport.com/docs/reference/helm-reference/teleport-cluster/","status":"documented","summary":"The chart separates Auth/Proxy services and configures TLS, backing storage and Enterprise licence secrets. Avoid treating standalone local storage as HA. Authentication, roles, short-lived certificates, audit/session storage and backup protection need an explicit deployment policy.","supportingSources":[{"title":"HA scaling and service separation","url":"https://goteleport.com/docs/reference/deployment/scaling/"},{"title":"Identity governance provisioning controls","url":"https://goteleport.com/docs/identity-governance/integrations/scim/"}]},"sso":{"availability":"edition-dependent","reviewed":"2026-11-18","scope":"Teleport Enterprise Self-Hosted: selected customer-operated edition","source":"https://goteleport.com/docs/feature-matrix/","status":"documented","summary":"The feature matrix assigns SAML and OIDC SSO to Enterprise Self-Hosted. Configure the IdP connector, roles and login policy; the Community GitHub-login option is a separate edition boundary."}},"id":"teleport-enterprise-self-hosted","infrastructure":["servers"],"infrastructureNotes":"Teleport runs persistent authentication and proxy services with provider-backed state and network dependencies.","infrastructureReviewed":"2026-11-18","infrastructureSources":["https://goteleport.com/docs/installation/self-hosted/deployments/"],"install":"Teleport Helm charts on EKS, AKS or GKE; official Terraform deployment paths are also documented","installMethods":["helm","kubernetes","terraform"],"kind":"platform","license":"Commercial Teleport Enterprise Self-Hosted subscription and license file required.","licenseModel":"commercial-only","licenseModelNotes":"The selected Enterprise Self-Hosted edition requires a commercial subscription and license file.","licenseModelSources":["https://goteleport.com/docs/installation/self-hosted/","https://goteleport.com/docs/feature-matrix/"],"licenseReviewed":"2026-11-18","model":"Fully in your account","modelLabel":"Customer-operated","name":"Teleport Enterprise Self-Hosted","notes":"This entry covers Enterprise Self-Hosted, not Teleport Enterprise Cloud. Community licensing and feature availability differ; confirm the purchased edition and current upgrade compatibility.","operations":"Customer manages Kubernetes or VMs, backend state, storage, DNS, TLS, upgrades, capacity, backups and the Enterprise license.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Self-hosting Teleport","url":"https://goteleport.com/docs/installation/self-hosted/"},{"title":"Teleport deployment guides","url":"https://goteleport.com/docs/installation/self-hosted/deployments/"},{"title":"Teleport on AWS EKS","url":"https://goteleport.com/docs/installation/self-hosted/helm-deployments/aws/"},{"title":"Teleport on Azure AKS","url":"https://goteleport.com/docs/installation/self-hosted/helm-deployments/azure/"},{"title":"Teleport on Google GKE","url":"https://goteleport.com/docs/installation/self-hosted/helm-deployments/gcp/"}],"url":"https://launchinyourcloud.com/directory/teleport-enterprise-self-hosted/","website":"https://goteleport.com/"},{"architecture":"Containerized Terraform Enterprise application with customer-managed runtime, data storage and worker capacity","categories":["devops"],"category":"DevOps","categoryFit":{"devops":"Provides self-hosted infrastructure-as-code runs, workspaces, policy controls, private registry and team workflows."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"HashiCorp lists official Terraform Enterprise modules for AWS EC2 and EKS, Azure VMs and AKS, and Google GCE and GKE, together with provider-specific deployment guidance for customer environments.","reviewed":"2026-11-15","sourceType":"vendor-documentation","title":"Official Terraform Enterprise modules and provider guidance","url":"https://developer.hashicorp.com/terraform/enterprise/deploy","vendorSupport":"not-assessed"},{"clouds":["ibm"],"notes":"HashiCorp explicitly directs IBM Cloud Kubernetes Service users to its Kubernetes deployment workflow, and Red Hat OpenShift users to its OpenShift workflow. It also links the IBM Cloud deployable architecture. This is separate from the EC2, Azure and Google Cloud validated modules.","reviewed":"2026-11-15","sourceType":"vendor-documentation","title":"Terraform Enterprise on IBM Cloud","url":"https://developer.hashicorp.com/terraform/enterprise/deploy","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-15","clouds":["aws","azure","gcp","ibm"],"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":"cloud-account","cloud":"ibm","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Commercial self-hosted Terraform collaboration and infrastructure-automation platform.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Vendor validated-design baseline; execution workers and HA topology additional","source":"https://developer.hashicorp.com/validated-designs/terraform/installation-guide/detailed-design","status":"documented","summary":"The validated design gives per-node application baseline 4 vCPUs/32 GB/1 TB, PostgreSQL 4 cores/32 GB/2 TB, and Redis 4 cores/16 GB/500 GB. It notes larger initial application nodes are common. Execution concurrency, per-run memory, availability and object storage require separate sizing."},"iac":{"reviewed":"2026-11-16","scope":"Terraform Enterprise flexible deployment overview and HashiCorp Validated Designs","source":"https://developer.hashicorp.com/terraform/enterprise/deploy","status":"documented","summary":"HashiCorp links official deployment modules for AWS EC2/EKS, Azure VM/AKS and Google Cloud GCE/GKE. Select a supported Enterprise version, runtime and storage arrangement before using the appropriate module. A module is not a software license."},"licensePricing":{"reviewed":"2026-11-20","scope":"Terraform Enterprise commercial licensing; CLI and HCP pricing excluded","source":"https://developer.hashicorp.com/terraform/docs/glossary","status":"documented","summary":"HashiCorp identifies Terraform Enterprise as closed-source commercial software. It requires Enterprise entitlement; Terraform CLI source-available terms do not license the Enterprise service. The reviewed product documentation does not establish a numeric price; obtain a current licence/support quote."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Terraform Enterprise SAML login and metadata connectivity","source":"https://developer.hashicorp.com/validated-designs/terraform/installation-guide/air-gapped-configuration","status":"documented","summary":"The vendor validates SAML 2.0 integration and requires connectivity to the identity provider metadata endpoint at login. Configure the Enterprise identity integration and recovery access; an air-gapped deployment needs a reachable internal IdP."}},"id":"terraform-enterprise","infrastructure":["servers"],"infrastructureNotes":"Terraform Enterprise runs as persistent containers on VM or Kubernetes runtimes with durable database and object-storage dependencies.","infrastructureReviewed":"2026-11-15","infrastructureSources":["https://developer.hashicorp.com/terraform/enterprise/deploy"],"install":"Official HashiCorp Terraform modules for EC2, EKS, Azure VMs, AKS, GCE or GKE; Kubernetes or OpenShift workflow on IBM Cloud","installMethods":["terraform","helm","kubernetes"],"kind":"product","license":"Commercial Terraform Enterprise license required.","licenseModel":"commercial-only","licenseModelNotes":"Terraform Enterprise is a commercial self-hosted product and requires a valid license file or license server configuration.","licenseModelSources":["https://developer.hashicorp.com/terraform/enterprise/deploy/configuration/license"],"licenseReviewed":"2026-11-15","model":"Fully in your account","modelLabel":"Customer-operated","name":"Terraform Enterprise","notes":"This entry covers Terraform Enterprise, the self-hosted distribution, not HCP Terraform. Match the selected runtime to the current compatibility matrix and review the module's IAM, managed-identity, database, object-storage and network requirements before applying it.","operations":"Customer manages compute or Kubernetes, PostgreSQL and object storage, cache, networking, TLS, identity, worker images, backups, scaling, upgrades and licensing.","publisher":false,"reviewed":"2026-11-15","sources":[{"title":"Terraform Enterprise deployment overview and cloud modules","url":"https://developer.hashicorp.com/terraform/enterprise/deploy"},{"title":"Terraform Enterprise license configuration","url":"https://developer.hashicorp.com/terraform/enterprise/deploy/configuration/license"}],"url":"https://launchinyourcloud.com/directory/terraform-enterprise/","website":"https://developer.hashicorp.com/terraform/enterprise"},{"architecture":"ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths.","categories":["data-analytics","observability"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Source-available IoT device, telemetry and dashboard platform.","observability":"Source-available IoT device, telemetry and dashboard platform."},"cloudEvidence":[{"clouds":["aws"],"notes":"ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"AWS","url":"https://thingsboard.io/docs/installation/aws/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Azure","url":"https://thingsboard.io/docs/installation/azure/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"GCP","url":"https://thingsboard.io/docs/installation/gcp/","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":"Source-available IoT device, telemetry and dashboard platform.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Current single-host tier recommendations; not a 1 TB microservice/HA sizing guarantee","source":"https://thingsboard.io/docs/user-guide/install/ubuntu/","status":"documented","summary":"The Ubuntu guide distinguishes a 1-core/4 GB/20 GB proof of concept from small production at 2 cores/8 GB/50 GB SSD and a larger starting tier at 4+ cores/16+ GB/100+ GB SSD. Queue/database choices add resources; the heap example is not total host capacity. Device/message rate, retention and HA require separate sizing."},"iac":{"artifactRef":"v4.4.0.2 application package release; match provider image/manifests separately","artifactUrl":"https://github.com/thingsboard/thingsboard/releases/tag/v4.4.0.2","reviewed":"2026-11-20","scope":"Official native package installation; AWS reference topologies and provider images have separate versions","source":"https://thingsboard.io/docs/user-guide/install/ubuntu/","status":"documented","summary":"The current Ubuntu guide installs a versioned application package, Java and database, then initializes the schema and starts the service. AWS guidance separates single-VM, EKS monolith and microservice topologies. Select matching application/manifests and dependencies, replace sample secrets, and configure TLS, persistence, mail and licence activation.","supportingSources":[{"title":"Official AWS deployment choices","url":"https://thingsboard.io/docs/installation/aws/"}]},"licensePricing":{"availability":"edition-dependent","reviewed":"2026-11-19","scope":"ThingsBoard Self-Hosted; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://github.com/thingsboard/thingsboard/blob/master/LICENSE","status":"documented","summary":"Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions."},"release":{"releasePublishedAt":"2026-10-30T14:15:12Z","releaseTag":"v4.4.0.2","reviewed":"2026-11-19","scope":"ThingsBoard Self-Hosted upstream application; verify compatibility with the selected package","source":"https://github.com/thingsboard/thingsboard/releases/tag/v4.4.0.2","status":"documented","summary":"Reviewed upstream v4.4.0.2 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Current self-hosted ThingsBoard user login and identity mapping, distinct from device authentication","source":"https://thingsboard.io/docs/user-guide/oauth-2-support/","status":"documented","summary":"The ThingsBoard guide configures OAuth2/OIDC clients and domain-specific callbacks for Web UI or mobile login, including Keycloak, Okta, Azure and social providers. Configure issuer/JWKS, trusted claims, tenant/customer mapping and account-creation policy. Device transport credentials and API tokens are separate; the selected release licence still applies."}},"id":"thingsboard","infrastructure":["servers"],"infrastructureNotes":"ThingsBoard monolith or microservices, database and messaging/cache services on the documented cloud VM/Kubernetes paths. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://thingsboard.io/docs/installation/aws/","https://thingsboard.io/docs/installation/azure/","https://thingsboard.io/docs/installation/gcp/"],"install":"Kubernetes manifests","installMethods":["kubernetes"],"kind":"product","license":"Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions.","licenseModel":"source-available","licenseModelNotes":"Business Source License 1.1 for ThingsBoard 4.4+; production grants and a licence key are subject to device, server and attribution conditions.","licenseModelSources":["https://github.com/thingsboard/thingsboard/blob/master/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"ThingsBoard Self-Hosted","notes":"Current 4.4+ code uses BUSL-1.1 with a usage grant; do not label it Apache-licensed Community merely because older versions used that licence. Device monitoring and energy dashboards do not establish regulated environmental filings or evidence workflows.","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","url":"https://thingsboard.io/docs/installation/aws/"},{"title":"Azure","url":"https://thingsboard.io/docs/installation/azure/"},{"title":"GCP","url":"https://thingsboard.io/docs/installation/gcp/"},{"title":"v4.4 Unification","url":"https://thingsboard.io/docs/pe/installation/upgrade-from-ce/"},{"title":"Smart Energy","url":"https://thingsboard.io/use-cases/smart-energy/"},{"title":"BUSL-1.1","url":"https://github.com/thingsboard/thingsboard/blob/master/LICENSE"},{"title":"Releases","url":"https://github.com/thingsboard/thingsboard/releases"}],"url":"https://launchinyourcloud.com/directory/thingsboard/","website":"https://thingsboard.io"},{"advisories":[{"action":"Review the fixed PD/TiKV/optional component versions, restrict management endpoints and follow the matching LTS upgrade procedure.","conditions":"Exposure depends on component versions, PD endpoint accessibility and configured dependencies. Community, Cloud and unrelated LTS branches must not be treated as identical deployments.","id":"tidb-8-5-8-security-review","listingIds":["tidb-community"],"reviewed":"2026-11-18","scope":"The v8.5.8 component release notes; a complete affected-version range and a universal exposure claim are not established.","source":"https://docs.pingcap.com/tidb/stable/release-8.5.8","summary":"The release fixes potential SSRF/upstream response exposure in PD metric endpoints, GlobalConfig namespace access and dependency vulnerabilities in TiKV/DM.","title":"TiDB v8.5.8 PD endpoint and component security review","type":"security-advisory"}],"architecture":"TiDB, PD and TiKV services on customer Kubernetes node pools with persistent storage, or a separately reviewed third-party single-VM bundle; optional analytics and monitoring depend on the deployment.","categories":["databases-vector","data-analytics"],"category":"Databases \u0026 vector","categoryFit":{"data-analytics":"Supports scalable transactional and analytical SQL workloads on a customer-operated cluster.","databases-vector":"Provides a distributed SQL database with horizontally scaled storage and query services."},"cloudEvidence":[{"clouds":["aws"],"notes":"PingCAP documents customer EKS node pools, storage and TiDB Operator deployment.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"TiDB on Amazon EKS","url":"https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-aws-eks/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"PingCAP documents customer GKE node pools, persistent disks and TiDB Operator deployment.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"TiDB on Google Kubernetes Engine","url":"https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-gcp-gke/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"PingCAP provides a full AKS deployment guide with customer node pools, PD/TiKV/TiDB and monitoring manifests. A deployment guide establishes a documented path, not a commercial support contract.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"TiDB Community on Azure AKS","url":"https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/","vendorSupport":"not-assessed"},{"applicableVersions":["TiDB Operator guide v1.4"],"clouds":["alibaba"],"notes":"PingCAP’s v1.4 guide deploys a full cluster into customer ACK using Terraform and TiDB Operator and is scoped to development/testing. The current deployment FAQ still names ACK; old Terraform/image examples need a current-version production review.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"TiDB on Alibaba Cloud ACK","url":"https://docs.pingcap.com/tidb-in-kubernetes/v1.4/deploy-on-alibaba-cloud/","vendorSupport":"not-assessed"},{"applicableEdition":"Repackaged open-source TiDB bundle","applicableVersions":["Seller package 1.0.2; embedded database versions unreported"],"clouds":["aws"],"notes":"The seller guide subscribes to exact AWS offer prodview-ddl3tqewcoko4 and launches into the customer region/VPC/EC2 account. TiDB and its monitoring interfaces run on the VM. This is a separately packaged single-node option, not the Kubernetes HA path; package 1.0.2 leaves embedded database versions unreported. Restrict SSH/RDP and set the documented initial credentials.","reviewed":"2026-11-18","sourceType":"third-party-package","title":"Techlatest TiDB OSS single-VM bundle in customer EC2","url":"https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-18","clouds":["aws","gcp","azure","alibaba"],"communityAcceptance":{"reviewed":"2026-11-18","sources":[{"title":"Official maintenance and adoption evidence","url":"https://github.com/pingcap/tidb/releases/tag/v8.5.8"},{"title":"Official maintenance and adoption evidence","url":"https://www.pingcap.com/case-studies/"},{"title":"Official maintenance and adoption evidence","url":"https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-operator-overview/"}],"summary":"PingCAP maintains the Apache-licensed database and operator with public contribution activity and supported LTS releases. Its named customer case-study catalog demonstrates adoption, while TiDB Cloud stories are kept separate from Community cloud evidence."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0,4],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[2],"operator":"customer"},{"boundary":"cloud-account","cloud":"alibaba","controlPlane":"not-assessed","evidence":[3],"operator":"customer"}],"description":"Open-source distributed SQL database with customer-operated cloud Kubernetes guides and a separately packaged third-party AWS VM option.","diligence":{"airGap":{"availability":"available","reviewed":"2026-11-18","scope":"Operator-based Kubernetes offline procedure only; the third-party VM’s offline lifecycle is not established","source":"https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-general-kubernetes/","status":"documented","summary":"The Kubernetes guide explicitly describes transferring container images to a server without external network access and loading them locally. Include operator, PD/TiKV/TiDB, optional TiFlash/TiCDC, monitoring and initialization images; its v8.5.7 example is not a complete current-version image lockfile."},"commitments":{"reviewed":"2026-11-18","scope":"TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope","source":"https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4","status":"inconclusive","summary":"The upstream Community Apache licence has no subscription charge. The alternative Techlatest VM has a separately billed seller-support charge on AWS Marketplace, but its exact commitment eligibility is not established by the offer. Confirm the selected offer/contract and buyer’s AWS agreement; neither the free licence nor TiDB Cloud SaaS terms settle that transaction.","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":"Community licence","url":"https://github.com/pingcap/tidb/blob/master/LICENSE"}]},"compliance":{"reviewed":"2026-11-18","scope":"TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope","source":"https://www.pingcap.com/trust-hub/compliance/","status":"inconclusive","summary":"PingCAP’s Trust Hub advertises ISO and SOC assurances and requests certificate/report access. Its specific ISO announcement identifies TiDB Cloud, a managed service, rather than this customer-operated Community cluster. A current certificate/report covering the relevant Community development/support boundary and buyer controls was not established; do not inherit TiDB Cloud attestations.","supportingSources":[{"title":"Explicit TiDB Cloud ISO certification boundary","url":"https://www.pingcap.com/press-release/announcing-iso-27001-certification-for-tidb-cloud/"}]},"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.pingcap.com/tidb/stable/hardware-and-software-requirements/","status":"inconclusive","summary":"Define SQL QPS, transaction mix, concurrency, indexes, TiKV replication, usable versus raw 1 TB, compaction headroom, TiFlash/TiCDC needs, monitoring and recovery targets. Price EKS and stateful nodes/storage across failure domains after benchmarking; the user count alone does not size this distributed database. The seller’s single-VM bundle does not provide the requested HA architecture.","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/"},{"title":"Single-VM price/topology is a different cost scope","url":"https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4"}]},"footprint":{"reviewed":"2026-11-18","scope":"Upstream v8.5 production component recommendations; not the third-party VM’s capacity or HA guarantee","source":"https://docs.pingcap.com/tidb/stable/hardware-and-software-requirements/","status":"documented","summary":"The v8.5 production hardware baseline lists two TiDB nodes at 16 cores/48 GB each, three PD at 8 cores/16 GB, and three TiKV at 16 cores/64 GB, plus SSD and network requirements. Optional analytics/changefeed/monitoring add components. These are component recommendations, not exact pod requests or a benchmark for 100 users. The seller’s t2.large VM example is not this production multi-node baseline.","supportingSources":[{"title":"Different single-VM baseline","url":"https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html"}]},"iac":{"artifactRef":"TiDB Operator v1.6.6 AKS example","artifactUrl":"https://raw.githubusercontent.com/pingcap/tidb-operator/v1.6.6/examples/aks/tidb-cluster.yaml","reviewed":"2026-11-18","scope":"Operator v1.6.6 Kubernetes manifest; the third-party VM is a separate delivery","source":"https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/","status":"documented","summary":"The AKS guide provides a versioned TiDB custom-resource manifest from TiDB Operator v1.6.6, together with separate monitoring/dashboard manifests. The operator version and TiDB image versions are independent; review requests, storage classes and all example defaults. The optional seller VM has a separate AMI/image inventory; do not treat the Operator manifest as its installation artifact.","supportingSources":[{"title":"Separate single-VM deployment artifact","url":"https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html"}]},"licensePricing":{"reviewed":"2026-11-18","scope":"TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope","source":"https://github.com/pingcap/tidb/blob/master/LICENSE","status":"documented","summary":"TiDB Community is Apache 2.0 licensed. PingCAP support and TiDB Cloud are separate commercial purchases. Review the licences of optional monitoring tools and other bundled components. The alternative Techlatest AMI bills USD 0.13/hour for seller support on its reviewed t2.large option, with AWS resources separate.","supportingSources":[{"title":"Separately transacted seller bundle pricing","url":"https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4"}]},"marketplace":{"availability":"available","offers":[{"cloud":"aws","delivery":"Amazon Machine Image (AMI), x86; single-VM bundle","id":"prodview-ddl3tqewcoko4","publisher":"Techlatest.net","url":"https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4","version":"Seller package 1.0.2; embedded database versions unreported"}],"reviewed":"2026-11-18","scope":"Optional third-party TiDB Community VM delivery in the customer AWS account; independent from Operator/Kubernetes topology, package versions and support","source":"https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4","status":"documented","summary":"Techlatest.net publishes TiDB with Grafana/Prometheus as AWS AMI prodview-ddl3tqewcoko4: a repackaged open-source single-VM bundle, package 1.0.2 on CentOS Stream 9. The reviewed t2.large option charges USD 0.13/hour for seller support plus AWS resources. This is an alternative to the Operator-based Kubernetes path, not that HA topology. The seller does not name embedded TiDB/TiKV/PD versions; inspect and pin them before production rather than inheriting the upstream release snapshot.","supportingSources":[{"title":"Seller single-VM installation and initial credentials","url":"https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html"},{"title":"TiDB Community upstream licence","url":"https://github.com/pingcap/tidb/blob/master/LICENSE"}]},"release":{"releasePublishedAt":"2026-08-27T09:06:37Z","releaseTag":"v8.5.8","reviewed":"2026-11-18","scope":"Upstream TiDB v8.5 LTS snapshot; not a confirmed version for the third-party AWS image","source":"https://github.com/pingcap/tidb/releases/tag/v8.5.8","status":"documented","summary":"TiDB v8.5.8 was published August 27, 2026 and is the reviewed v8.5 LTS snapshot. Its notes include PD endpoint and TiKV dependency security fixes. The later v7.5.8 publication belongs to an older branch. Match Operator, TiKV, PD and optional component versions rather than treating the chart version as the database version. Techlatest’s AMI package 1.0.2 does not disclose its embedded database versions, so this upstream snapshot must not be inherited by that VM.","supportingSources":[{"title":"Component fixes in v8.5.8","url":"https://docs.pingcap.com/tidb/stable/release-8.5.8"},{"title":"Separate seller package/version boundary","url":"https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4"}]},"scim":{"reviewed":"2026-11-18","scope":"TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope","source":"https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql/","status":"inconclusive","summary":"JWT and LDAP authentication do not establish SCIM user/group management or automatic SQL-account deprovisioning. A current Community endpoint and supported operations were not confirmed; review provisioning and token revocation separately.","supportingSources":[]},"securityControls":{"reviewed":"2026-11-18","scope":"TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope","source":"https://docs.pingcap.com/tidb/stable/enable-tls-between-components/","status":"documented","summary":"PingCAP documents certificates and TLS between components, plus client TLS and privileged-user/network controls. JWT SQL authentication requires trusted issuer/JWKS configuration and client TLS because the client sends the token through a clear-password plugin. Database token/LDAP authentication alone does not establish SSO or SCIM. Techlatest’s VM guide starts TiDB root with a blank password and Grafana with admin/admin; set new credentials and restrict SSH/RDP before use. Its component patch levels remain unconfirmed. Optional Dashboard OIDC SSO stores an encrypted SQL password for impersonation; use the documented least-privileged account and network/TLS controls, and reauthorize after SQL password rotation.","supportingSources":[{"title":"Self-managed security configuration","url":"https://docs.pingcap.com/tidb/stable/best-practices-for-security-configuration/"},{"title":"SQL authentication and JWT TLS requirements","url":"https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql/"},{"title":"Seller-specific initial credential requirements","url":"https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html"},{"title":"Dashboard OIDC credential-handling boundary","url":"https://docs.pingcap.com/tidb/stable/dashboard-session-sso/"},{"title":"Least-privileged Dashboard SQL users","url":"https://docs.pingcap.com/tidb/stable/dashboard-user/"}]},"sso":{"availability":"available","reviewed":"2026-11-18","scope":"TiDB Community/Self-Managed v8.5 Dashboard web UI, including its documented Kubernetes deployment; SQL-client SSO and the versions inside the third-party VM are assessed separately","source":"https://docs.pingcap.com/tidb/stable/dashboard-session-sso/","status":"documented","summary":"TiDB Self-Managed v8.5 documents OIDC SSO for the TiDB Dashboard web UI, with Okta, Auth0 and self-hosted Casdoor examples. Dashboard encrypts/stores a SQL account password to complete an impersonated SQL sign-in after OIDC authentication. SQL password rotation requires reauthorization; disabling SSO erases the stored password. This establishes Dashboard sign-in only. A selected SQL client’s federated login and SCIM lifecycle require separate confirmation.","supportingSources":[{"title":"Dashboard access on customer-operated Kubernetes","url":"https://docs.pingcap.com/tidb-in-kubernetes/stable/access-dashboard/"},{"title":"Least-privileged Dashboard SQL users","url":"https://docs.pingcap.com/tidb/stable/dashboard-user/"},{"title":"Protect Dashboard and privileged PD interfaces","url":"https://docs.pingcap.com/tidb/stable/dashboard-ops-security/"},{"title":"Separate SQL JWT/LDAP authentication boundary","url":"https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql/"}]}},"id":"tidb-community","infrastructure":["servers"],"infrastructureNotes":"TiDB runs persistent database/storage services on customer Kubernetes node pools, or as a separately packaged single-VM OSS bundle. The seller VM is not the Operator-based production HA topology.","infrastructureReviewed":"2026-11-18","infrastructureSources":["https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-operator-overview/","https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html"],"install":"TiDB Operator and versioned Kubernetes resources on EKS/GKE/AKS; the Alibaba ACK Terraform recipe has older development/test version constraints; optional Techlatest AWS single-VM bundle is separately packaged and does not supply the Operator HA topology","installMethods":["helm","kubernetes","terraform","vm-image"],"kind":"product","license":"Apache License 2.0.","licenseModel":"open-source","licenseModelNotes":"The TiDB repository is Apache-2.0 licensed. Managed TiDB Cloud services have separate terms.","licenseModelSources":["https://github.com/pingcap/tidb/blob/master/LICENSE"],"licenseReviewed":"2026-11-18","model":"Fully in your account","modelLabel":"Customer-operated","name":"TiDB Community Self-Hosted","notes":"This entry covers TiDB Community, not TiDB Cloud. AKS has a complete current guide even though the deployment FAQ omits it; that difference does not negate the documented path. The ACK guide is an older development/test recipe, while the current FAQ still names ACK. Match operator/database versions and validate production permissions, storage and HA before use. An alternative Techlatest AWS image packages TiDB OSS with Grafana/Prometheus on one VM. Package 1.0.2 does not identify the database components’ versions and is not an HA cluster or PingCAP support entitlement. Do not transfer Operator sizing, offline procedures or the upstream v8.5.8 snapshot to this image.","operations":"Customer manages the chosen Kubernetes cluster or VM, operating system/node pools, persistent storage, networking, database identities, backups, monitoring, upgrades, scaling and database operations.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"TiDB Operator overview","url":"https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-operator-overview/"},{"title":"Deploy TiDB on AWS EKS","url":"https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-aws-eks/"},{"title":"Deploy TiDB on Google Cloud GKE","url":"https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-gcp-gke/"},{"title":"TiDB Apache 2.0 license","url":"https://github.com/pingcap/tidb/blob/master/LICENSE"},{"title":"TiDB Community on Azure AKS","url":"https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/"},{"title":"TiDB on Alibaba Cloud ACK","url":"https://docs.pingcap.com/tidb-in-kubernetes/v1.4/deploy-on-alibaba-cloud/"},{"title":"Current TiDB deployment FAQ","url":"https://docs.pingcap.com/tidb/stable/deploy-and-maintain-faq/"},{"title":"Exact third-party TiDB OSS AWS image","url":"https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4"},{"title":"Seller customer-account VM deployment","url":"https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html"}],"url":"https://launchinyourcloud.com/directory/tidb-community/","website":"https://www.pingcap.com/tidb/"},{"architecture":"Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack.","categories":["incident-investigation-management"],"category":"Incident \u0026 investigation management","categoryFit":{"incident-investigation-management":"Open-source collaborative forensic timeline analysis application."},"cloudEvidence":[{"clouds":["gcp"],"notes":"Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack. Azure packaging is supplied by SecureAnyCloud, not Google. The upstream release and image stack versions are separate. Timeline analysis complements acquisition and incident-intake tools; it does not replace every investigation or case-management function.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"OSDFIR Getting Started","url":"https://google.github.io/osdfir-infrastructure/docs/getting-started.html","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack. Azure packaging is supplied by SecureAnyCloud, not Google. The upstream release and image stack versions are separate. Timeline analysis complements acquisition and incident-intake tools; it does not replace every investigation or case-management function.","reviewed":"2026-11-19","sourceType":"third-party-package","title":"SecureAnyCloud Azure","url":"https://secureanycloud.com/stacks/timesketch/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["gcp","azure"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/google/timesketch/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/google/timesketch"}],"summary":"The reviewed upstream contributor history includes berggren, kiddinn, jaegeral, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Open-source collaborative forensic timeline analysis application.","diligence":{"footprint":{"reviewed":"2026-11-21","scope":"Timesketch published entry baseline and search-scaling guidance","source":"https://timesketch.org/guides/admin/scaling-and-limits/","status":"documented","summary":"The upstream scaling guide gives at least 8 GB RAM for its described Ubuntu environment and stresses fast local storage and OpenSearch sizing/shard limits. This is an entry baseline, not capacity for arbitrary timelines/events or an HA cluster; separately size indexes, imports, workers, replicas and backups."},"iac":{"artifactRef":"Current OSDFIR Timesketch chart guide reviewed on this date","artifactUrl":"https://google.github.io/osdfir-infrastructure/charts/timesketch/","reviewed":"2026-11-21","scope":"Maintainer Timesketch Kubernetes/Helm deployment; chart and application versions separate","source":"https://google.github.io/osdfir-infrastructure/charts/timesketch/","status":"documented","summary":"Google maintains OSDFIR Helm charts with Timesketch values and production installation guidance. Select compatible chart/application/OpenSearch versions, expose ingress deliberately and configure secrets, persistent storage and backups. Local Minikube instructions and default port-forward access are not production deployment."},"licensePricing":{"reviewed":"2026-11-19","scope":"Timesketch; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://github.com/google/timesketch/blob/master/LICENSE","status":"documented","summary":"Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"release":{"releasePublishedAt":"2026-10-14T15:06:04Z","releaseTag":"20261014","reviewed":"2026-11-19","scope":"Timesketch upstream application; verify compatibility with the selected package","source":"https://github.com/google/timesketch/releases/tag/20261014","status":"documented","summary":"Reviewed upstream 20261014 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence."},"sso":{"availability":"available","reviewed":"2026-11-21","scope":"Timesketch 20261014 configured user SSO/OIDC/IAP paths","source":"https://github.com/google/timesketch/blob/20261014/data/timesketch.conf","status":"documented","summary":"The versioned configuration supports trusted web-server REMOTE_USER SSO and separately Google OIDC/Cloud IAP options, with actual token/authentication implementation. Configure the selected mode, trusted proxy boundary, identity claims and group policy; these mechanisms are not interchangeable and must not trust spoofed headers.","supportingSources":[{"title":"Google token validation","url":"https://github.com/google/timesketch/blob/20261014/timesketch/lib/google_auth.py"},{"title":"Application authentication views","url":"https://github.com/google/timesketch/blob/20261014/timesketch/views/auth.py"}]}},"id":"timesketch","infrastructure":["servers"],"infrastructureNotes":"Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://google.github.io/osdfir-infrastructure/docs/getting-started.html","https://secureanycloud.com/stacks/timesketch/"],"install":"Helm / Kubernetes operator; Kubernetes manifests; VM image","installMethods":["helm","kubernetes","vm-image"],"kind":"product","license":"Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://github.com/google/timesketch/blob/master/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Timesketch","notes":"Azure packaging is supplied by SecureAnyCloud, not Google. The upstream release and image stack versions are separate. Timeline analysis complements acquisition and incident-intake tools; it does not replace every investigation or case-management function.","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":"OSDFIR Getting Started","url":"https://google.github.io/osdfir-infrastructure/docs/getting-started.html"},{"title":"SecureAnyCloud Azure","url":"https://secureanycloud.com/stacks/timesketch/"},{"title":"OSDFIR Timesketch","url":"https://google.github.io/osdfir-infrastructure/charts/timesketch/"},{"title":"Apache-2.0","url":"https://github.com/google/timesketch/blob/master/LICENSE"},{"title":"Releases","url":"https://github.com/google/timesketch/releases"}],"url":"https://launchinyourcloud.com/directory/timesketch/","website":"https://github.com/google/timesketch"},{"advisories":[{"action":"Review the selected LTS line and apply its supported patch; validate webhook limits and token administration.","conditions":"Configured workflow webhooks, personal access tokens and bundled dependencies determine applicability.","id":"tooljet-3-21-96-lts-security-review","listingIds":["tooljet"],"reviewed":"2026-11-17","scope":"ToolJet v3.21.96-lts release review; this is security maintenance, not a named product-wide vulnerability or a cross-branch support claim.","source":"https://github.com/ToolJet/ToolJet/releases/tag/v3.21.96-lts","summary":"The release fixes dependency findings, extends webhook rate limits and adds administrator token revocation.","title":"ToolJet LTS security maintenance review","type":"security-advisory"}],"architecture":"Customer-operated app services, PostgreSQL and optional cache","categories":["internal-tools"],"category":"Internal tools","categoryFit":{"internal-tools":"Visual internal app development with database/API connections, dashboards and workflows; access and governance depend on edition."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"The current vendor Docker guide links optional Terraform VM provisioning on AWS, Azure and Google Cloud, followed by ToolJet server deployment. Configure the application databases, image edition and production settings separately; AI features can use vendor endpoints.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"ToolJet application deployment on cloud VMs","url":"https://docs.tooljet.com/docs/setup/docker/","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"The vendor guide creates an Ubuntu Droplet, configures its firewall and installs Docker and Compose, then follows the ToolJet Docker deployment. The current instructions include LTS and enterprise image guidance; license and AI endpoint requirements remain edition-dependent.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"ToolJet on a customer DigitalOcean Droplet","url":"https://docs.tooljet.com/docs/setup/digitalocean/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","cloudScope":"Documented customer-operated deployment guides for AWS, Azure and Google Cloud","clouds":["aws","azure","gcp","digitalocean"],"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":"cloud-account","cloud":"digitalocean","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Build internal tools and business applications with a customer-hosted app builder.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Application, database and Redis requirements are separate; ARM64 is not supported by the reviewed guide and these are not HA capacity guarantees","source":"https://docs.tooljet.com/docs/setup/system-requirements/","status":"documented","summary":"The self-hosted requirements specify an x86 VM with 1 vCPU, 4 GB RAM and at least 8 GiB disk. PostgreSQL is separately sized at 2 vCPU, 8 GB RAM and 20 GB disk, and Redis at 1 vCPU, 512 MB RAM and 1 GB disk (1 GB RAM recommended for production)."},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://docs.tooljet.com/docs/setup/docker/","status":"documented","summary":"The server guide documents Compose with PostgreSQL and links optional VM Terraform examples. Multi-instance workers need external Redis; ToolJet AI also requires separately documented outbound endpoints."},"licensePricing":{"reviewed":"2026-11-20","scope":"Current self-hosted Basic/paid licensing; not an unlimited 100-user entitlement or hosted-plan quote","source":"https://docs.tooljet.com/docs/tj-setup/licensing/self-hosted/","status":"documented","summary":"The self-hosted licensing guide distinguishes free Basic, 14-day Trial and paid plans. Since v3.5.20-ee-lts, Basic is limited to 2 builders including the super admin, 50 end users, 2 apps, 2 workflows and 1 workspace. Paid features require a vendor-issued key; confirm a quote for larger deployments."},"release":{"releasePublishedAt":"2026-11-13T07:47:16Z","releaseTag":"v3.21.96-lts","reviewed":"2026-11-17","scope":"Upstream ToolJet/ToolJet release record; commercial editions, LTS branches and provider packages can differ","source":"https://github.com/ToolJet/ToolJet/releases/tag/v3.21.96-lts","status":"documented","summary":"The reviewed upstream release is v3.21.96-lts, published 2026-11-13. This is a dated release snapshot, not a support designation, a future cadence promise or approval to replace a provider package."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-20","scope":"Self-hosted login; OpenID entitlement is paid and protocol availability must not imply every provider is included in Basic","source":"https://docs.tooljet.com/docs/tj-setup/licensing/self-hosted/","status":"documented","summary":"Self-hosted workspace login documents Google, GitHub, OIDC, LDAP and SAML. The licensing guide explicitly says OpenID SSO is lost when a paid/trial key expires and the instance reverts to Basic; confirm the selected plan for other identity providers.","supportingSources":[{"title":"Self-hosted workspace login","url":"https://docs.tooljet.com/docs/user-management/authentication/self-hosted/workspace-login/"}]}},"id":"tooljet","infrastructure":["servers"],"infrastructureNotes":"Reviewed topology uses long-lived application containers on a VM or Kubernetes cluster with PostgreSQL. Classified servers rather than function-based serverless.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.tooljet.com/docs/setup/docker/"],"install":"Docker Compose or Kubernetes; optional Terraform provisioning for AWS/Azure/GCP VMs","installMethods":["terraform","docker","vendor-assisted"],"kind":"product","license":"AGPL-3.0 open-source foundation; commercial self-hosted editions/plans","licenseModel":"open-source","licenseModelNotes":"The self-hosted product combines an AGPL-3.0 open-source foundation with commercially licensed/gated self-hosted Enterprise capabilities; Basic/free plan access does not include all premium features.","licenseModelSources":["https://github.com/ToolJet/ToolJet","https://docs.tooljet.com/docs/tj-setup/licensing/self-hosted/"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"ToolJet Self-Hosted","notes":"The self-hosted Basic tier and paid editions have different limits and governance features. Official Docker documentation includes customer VM provisioning paths for AWS, Azure and Google Cloud. AI features require additional outbound vendor endpoints; self-hosting does not imply air-gapped operation. ToolJet v3.21.96-lts lets administrators revoke any workspace personal access token, applies configured rate limits to workflow webhooks, and updates vulnerable dependencies. Self-hosted operators should use v3.21.96-lts or later.","operations":"Customer operates application, database, credentials, backups and upgrades; vendor license activation applies to paid features.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Server Docker Compose deployment and cloud VM provisioning","url":"https://docs.tooljet.com/docs/setup/docker/"},{"title":"Self-hosted license types and limits","url":"https://docs.tooljet.com/docs/tj-setup/licensing/self-hosted/"},{"title":"System requirements","url":"https://docs.tooljet.com/docs/setup/system-requirements/"},{"title":"Project functionality and license","url":"https://github.com/ToolJet/ToolJet"},{"title":"ToolJet on a customer DigitalOcean Droplet","url":"https://docs.tooljet.com/docs/setup/digitalocean/"},{"title":"ToolJet v3.21.96 LTS security hardening","url":"https://github.com/ToolJet/ToolJet/releases/tag/v3.21.96-lts"}],"url":"https://launchinyourcloud.com/directory/tooljet/","website":"https://www.tooljet.com/"},{"architecture":"Tyk Gateway, Dashboard, Pump and Developer Portal services with Redis and MongoDB or supported SQL data stores","categories":["backend-platforms"],"category":"Backend platforms","categoryFit":{"backend-platforms":"Provides a self-managed API gateway, management dashboard, analytics, developer portal and lifecycle controls for application APIs."},"cloudEvidence":[{"clouds":["aws"],"notes":"Tyk documents creating an Amazon EC2 instance in the customer's AWS account and deploying the licensed Tyk Self-Managed platform with Docker.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Tyk Self-Managed on AWS","url":"https://tyk.io/deploying-on-aws/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Tyk documents creating an Azure virtual machine and installing the Tyk Self-Managed stack with Docker in the customer's Azure environment.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Tyk Self-Managed on Microsoft Azure","url":"https://tyk.io/deploying-on-azure/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Tyk documents deploying its licensed Self-Managed platform on customer Google Cloud infrastructure.","reviewed":"2026-11-16","sourceType":"vendor-documentation","title":"Tyk Self-Managed on Google Cloud","url":"https://tyk.io/deploying-on-gcp/","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":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Commercial self-managed API management platform with documented AWS, Azure and Google Cloud deployments.","diligence":{"airGap":{"reviewed":"2026-11-16","scope":"Documented self-managed offline installation workflow; selected integrations and license terms still require deployment-specific review","source":"https://tyk.io/docs/api-management/air-gapped-deployment","status":"documented","summary":"Tyk documents mirroring all chart images, packaging the Helm chart and installing from private registries; Linux deployments can use local package mirrors. Include optional-component images and arrange the correct commercial licenses and compatible versions."},"footprint":{"reviewed":"2026-11-16","scope":"Self-managed Kubernetes tutorial prerequisites, not a universal production minimum","source":"https://tyk.io/docs/tyk-self-managed/install/kubernetes","status":"documented","summary":"The current Kubernetes tutorial requires at least 4 GB RAM available to the cluster, but explicitly deploys a trial-ready configuration. Production sizing must include Gateway traffic, Redis, PostgreSQL and optional components; 4 GB is not a production capacity guarantee."},"iac":{"artifactRef":"main (moving branch; select compatible chart release)","artifactUrl":"https://github.com/TykTechnologies/tyk-charts/tree/main/tyk-stack","reviewed":"2026-11-16","scope":"Full self-managed platform; not the standalone open-source gateway","source":"https://tyk.io/docs/tyk-self-managed/install/kubernetes","status":"documented","summary":"Tyk publishes the tyk-stack Helm chart and a trial-ready installation wrapper. Use the current tyk-charts repository; the former tyk-helm-chart repository is archived and deprecated. Select compatible chart/component versions, configure the required Dashboard license and production databases, and review trial defaults before production.","supportingSources":[{"title":"Archived chart repository and replacement notice","url":"https://github.com/TykTechnologies/tyk-helm-chart"}]},"licensePricing":{"reviewed":"2026-11-16","scope":"Tyk Self-Managed: software license terms; infrastructure and operating costs are separate","source":"https://tyk.io/docs/5.7/tyk-self-managed/","status":"documented","summary":"The selected full Tyk Self-Managed platform requires a commercial license. Tyk Gateway and Pump are separately available as open-source components, but they do not constitute the complete listed platform.","supportingSources":[{"title":"Edition and license conditions","url":"https://tyk.io/self-managed/"}]},"marketplace":{"availability":"edition-dependent","offers":[{"cloud":"aws","delivery":"SaaS contract listing covering multiple deployment modes; self-managed terms require confirmation","id":"prodview-pboluroscnqro","publisher":"Tyk Technologies Ltd","url":"https://aws.amazon.com/marketplace/pp/prodview-pboluroscnqro"}],"reviewed":"2026-11-16","scope":"Vendor-published AWS offer; procurement and application hosting are distinct","source":"https://aws.amazon.com/marketplace/pp/prodview-pboluroscnqro","status":"documented","summary":"The vendor AWS offer explicitly covers Cloud, Hybrid and Self-Managed. Its delivery classification is a SaaS contract and its public dimensions price Tyk Cloud; request terms that specifically license the self-managed deployment rather than treating it as an application AMI."},"release":{"reviewed":"2026-11-16","scope":"Published Gateway/Dashboard LTS policy as reviewed; not a single version or support guarantee for the entire platform","source":"https://tyk.io/docs/developer-support/release-types/long-term-support","status":"documented","summary":"The reviewed vendor policy lists 5.13 as its current LTS line. Gateway/Dashboard LTS receives 12 months of full support with eight-week patches, then 12 months of critical maintenance. Other components and non-LTS releases have separate compatibility and lifecycle rules."},"securityControls":{"reviewed":"2026-11-16","scope":"Dashboard 5.7+ audit-log configuration and storage responsibilities","source":"https://tyk.io/docs/5.7/tyk-self-managed/","status":"documented","summary":"The self-managed guide documents database-backed Dashboard audit-log storage from v5.7 onward. Operators must configure it, size the database and set retention/archive policies; example log sizes are workload assumptions, not a default retention guarantee or an attestation."},"sso":{"availability":"available","reviewed":"2026-11-16","scope":"Commercial self-managed Dashboard with internal TIB","source":"https://support.tyk.io/hc/en-gb/articles/8568981329564-SSO-access-using-internal-TIB-SAML-OKTA","status":"documented","summary":"Tyk documents Dashboard SAML login through its internal Identity Broker with Okta, and an OIDC integration with AWS Cognito. Configure the identity profile and user mapping for the licensed Dashboard; API-consumer authentication is a separate concern.","supportingSources":[{"title":"Dashboard OIDC with Cognito","url":"https://support.tyk.io/hc/en-gb/articles/21540673255836--Setting-Up-SSO-with-AWS-Cognito-as-IdP-for-Tyk-Dashboard"}]}},"id":"tyk-self-managed","infrastructure":["servers"],"infrastructureNotes":"Tyk Self-Managed runs persistent gateway, management, analytics, portal and database services on customer virtual machines or Kubernetes.","infrastructureReviewed":"2026-11-16","infrastructureSources":["https://tyk.io/docs/5.7/tyk-self-managed/","https://tyk.io/self-managed/"],"install":"Docker, Helm, Linux packages or Ansible on customer cloud infrastructure","installMethods":["helm","docker","package","other"],"kind":"product","license":"Commercial Tyk Self-Managed license required for the full platform; Gateway and Pump are available without that license.","licenseModel":"commercial-only","licenseModelNotes":"The selected full Tyk Self-Managed platform requires a commercial license. Tyk Gateway and Pump are separately available as open-source components, but they do not constitute the complete listed platform.","licenseModelSources":["https://tyk.io/docs/5.7/tyk-self-managed/","https://tyk.io/self-managed/"],"licenseReviewed":"2026-11-16","model":"Fully in your account","modelLabel":"Customer-operated","name":"Tyk Self-Managed","notes":"This entry covers the full Tyk Self-Managed platform, not Tyk Cloud or the standalone OSS Gateway. The Dashboard and other full-platform components require a commercial license, and Kubernetes installation requires a multi-node license. Provider tutorials are starter deployments rather than production sizing or high-availability guarantees.","operations":"Customer manages hosts or Kubernetes, data stores, networking, TLS, identities, secrets, monitoring, backups, scaling, upgrades and the Tyk license.","publisher":false,"reviewed":"2026-11-16","sources":[{"title":"Install Tyk Self-Managed","url":"https://tyk.io/docs/5.7/tyk-self-managed/"},{"title":"Deploy Tyk on AWS","url":"https://tyk.io/deploying-on-aws/"},{"title":"Deploy Tyk on Azure","url":"https://tyk.io/deploying-on-azure/"},{"title":"Deploy Tyk on Google Cloud","url":"https://tyk.io/deploying-on-gcp/"},{"title":"Tyk Self-Managed product and pricing model","url":"https://tyk.io/self-managed/"}],"url":"https://launchinyourcloud.com/directory/tyk-self-managed/","website":"https://tyk.io/self-managed/"},{"architecture":"High-availability Vault Enterprise VM cluster with integrated storage, load balancing, TLS and cloud key-management dependencies","categories":["identity-access-management"],"category":"Identity \u0026 access management","categoryFit":{"identity-access-management":"Provides centrally governed secrets, encryption, authentication methods, dynamic credentials and identity-based access policies."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"HashiCorp provides official validated-design modules for AWS EC2, Azure VMs and Google GCE and states that the modules deploy a complete Vault Enterprise environment inside the customer's own cloud account.","reviewed":"2026-11-15","sourceType":"vendor-documentation","title":"Vault Enterprise inside a customer cloud account","url":"https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-15","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 self-managed secrets and identity security platform deployed as a customer-operated high-availability cluster.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Official Vault integrated-storage per-server and cluster reference; not an application-data storage estimate","source":"https://developer.hashicorp.com/vault/tutorials/day-one-raft/raft-reference-architecture","status":"documented","summary":"The integrated-storage reference recommends 2–4 cores, 8–16 GB RAM and 100+ GB SSD at 3,000+ IOPS per small-cluster server; larger workloads have higher tiers. Its resilient topology uses five nodes across three zones. Audit-log I/O, replication and secret/request rates need separate sizing; these figures are not a complete 1 TB HA design."},"iac":{"reviewed":"2026-11-16","scope":"Vault Enterprise VM installation, HashiCorp Validated Designs","source":"https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform","status":"documented","summary":"HashiCorp publishes validated Terraform modules for Vault Enterprise on AWS EC2, Azure VMs and Google Cloud. Provider-specific networking, encryption keys, TLS material and a valid Enterprise license are prerequisites. These modules do not include an Enterprise entitlement."},"licensePricing":{"reviewed":"2026-11-20","scope":"Current Vault Enterprise self-managed licence-key policy; no public numeric quote established","source":"https://developer.hashicorp.com/vault/docs/license","status":"documented","summary":"Vault Enterprise requires a commercial licence key governing feature access and use dates. The current policy distinguishes expiration from termination: release date and termination conditions affect restart, unseal and security-upgrade eligibility. Obtain the applicable self-managed quote, feature/replication entitlements and term; HCP Vault Dedicated uses a separate commercial model."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Self-managed Vault user authentication via the JWT/OIDC auth method","source":"https://developer.hashicorp.com/vault/docs/auth/jwt","status":"documented","summary":"Vault documents OIDC browser login from the UI and CLI, using configured identity providers, callback URLs, roles and claim-bound policies. OIDC authentication is distinct from Kubernetes/JWT machine login and from downstream applications consuming secrets. Configure authorization and the selected Enterprise feature entitlements separately.","supportingSources":[{"title":"Identity-provider configuration examples","url":"https://developer.hashicorp.com/vault/docs/auth/jwt/oidc-providers"}]}},"id":"vault-enterprise","infrastructure":["servers"],"infrastructureNotes":"The validated design deploys a persistent high-availability Vault Enterprise VM cluster with integrated storage and provider key-management services.","infrastructureReviewed":"2026-11-15","infrastructureSources":["https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform"],"install":"Official HashiCorp Validated Design Terraform modules for AWS EC2, Azure VMs or Google GCE","installMethods":["terraform"],"kind":"product","license":"Commercial Vault Enterprise license required.","licenseModel":"commercial-only","licenseModelNotes":"The selected Vault Enterprise edition requires a commercial license and supports license autoloading or explicit license configuration.","licenseModelSources":["https://developer.hashicorp.com/vault/docs/license","https://developer.hashicorp.com/vault/tutorials/get-started/available-editions"],"licenseReviewed":"2026-11-15","model":"Fully in your account","modelLabel":"Customer-operated","name":"Vault Enterprise Self-Managed","notes":"This entry covers Vault Enterprise self-managed, not HCP Vault Dedicated or the separately licensed Community edition. Protect recovery and root credentials, design unseal and disaster-recovery procedures, and review the Terraform modules' requested permissions before deployment.","operations":"Customer manages VPC or VNet infrastructure, VMs, load balancers, storage, cloud KMS or Key Vault, TLS, initialization and unseal controls, audit logs, backups, replication, upgrades and licensing.","publisher":false,"reviewed":"2026-11-15","sources":[{"title":"Deploy Vault Enterprise with official Terraform modules","url":"https://developer.hashicorp.com/validated-designs/vault/installation-guide/vms/deploying-vault-using-terraform"},{"title":"Vault Enterprise license keys","url":"https://developer.hashicorp.com/vault/docs/license"},{"title":"Vault editions","url":"https://developer.hashicorp.com/vault/tutorials/get-started/available-editions"}],"url":"https://launchinyourcloud.com/directory/vault-enterprise/","website":"https://developer.hashicorp.com/vault"},{"architecture":"Customer-operated model-serving process, model weights and inference hardware","categories":["ai-inference-gateways","ai-tools"],"category":"AI inference \u0026 gateways","categoryFit":{"ai-inference-gateways":"Model inference engine and OpenAI-compatible serving API for compatible model weights. Distinct from an API gateway that forwards calls to proprietary hosted models.","ai-tools":"Self-hosted model inference and serving engine with OpenAI-compatible APIs."},"cloudEvidence":[{"clouds":["aws"],"notes":"The project publishes Amazon EKS provisioning and vLLM deployment scripts in its versioned Production Stack guide. Verify current chart versions, model licenses, accelerator availability, GPU quotas and storage; this is customer-hosted inference, not a hosted model API.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"vLLM Production Stack deployment on Amazon EKS","url":"https://docs.vllm.ai/projects/production-stack/en/vllm-stack-0.1.4/deployment/cloud-deployment/aws.html","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The project publishes Azure Kubernetes Service provisioning and vLLM deployment scripts in its versioned Production Stack guide. Verify current chart versions, model licenses, accelerator availability, GPU quotas and storage; this is customer-hosted inference, not a hosted model API.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"vLLM Production Stack deployment on Azure Kubernetes Service","url":"https://docs.vllm.ai/projects/production-stack/en/vllm-stack-0.1.4/deployment/cloud-deployment/azure.html","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The project publishes Google Kubernetes Engine provisioning and vLLM deployment scripts in its versioned Production Stack guide. Verify current chart versions, model licenses, accelerator availability, GPU quotas and storage; this is customer-hosted inference, not a hosted model API.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"vLLM Production Stack deployment on Google Kubernetes Engine","url":"https://docs.vllm.ai/projects/production-stack/en/vllm-stack-0.1.4/deployment/cloud-deployment/gcp.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","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":"Self-hosted model inference and serving engine with OpenAI-compatible APIs.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Model-specific inference sizing; no universal numeric footprint established","source":"https://docs.vllm.ai/en/stable/configuration/conserving_memory/","status":"inconclusive","summary":"The stable memory guide sizes serving around model weights, precision/quantization, tensor parallelism, context length, batch size and cache. A supported accelerator alone does not establish sufficient memory. Select the exact model and target throughput/latency, then benchmark VRAM/RAM and HA replica requirements."},"iac":{"artifactRef":"select a stable version and architecture tag; latest is moving","artifactUrl":"https://hub.docker.com/r/vllm/vllm-openai","reviewed":"2026-11-14","scope":"Stable upstream CUDA image path; not the latest developer-preview guide or a GPU sizing guarantee","source":"https://docs.vllm.ai/en/stable/deployment/docker/","status":"documented","summary":"The stable deployment guide links the official vllm/vllm-openai image for a CUDA-backed OpenAI-compatible server. Select a release/architecture tag and compatible GPU drivers; model memory, credentials and optional dependencies need separate review."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/vllm-project/vllm/main/LICENSE","status":"documented","summary":"The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Model weights and external model APIs require their own review."},"release":{"releasePublishedAt":"2026-11-16T23:22:00Z","releaseTag":"v0.34.0","reviewed":"2026-11-17","scope":"Upstream vllm-project/vllm release record; commercial editions, LTS branches and provider packages can differ","source":"https://github.com/vllm-project/vllm/releases/tag/v0.34.0","status":"documented","summary":"The reviewed upstream release is v0.34.0, published 2026-11-16. This is a dated release snapshot, not a support designation, a future cadence promise or approval to replace a provider package."},"sso":{"reviewed":"2026-11-20","scope":"Upstream inference-server auth surface; federated user integration unresolved","source":"https://docs.vllm.ai/en/latest/usage/security/","status":"inconclusive","summary":"The security guide documents API-key protection for specified HTTP path prefixes and warns that other sensitive endpoints remain unprotected. It does not establish a native SAML/OIDC user sign-on workflow. Use a reviewed gateway/network design; an API bearer key alone is not corporate SSO or complete endpoint protection."}},"id":"vllm","infrastructure":["servers"],"infrastructureNotes":"vLLM is a running inference-server workload. Hardware support and capacity depend on the model and selected backend; the documented container paths include accelerator-specific images, and CPU support is separately documented. In v0.34.0, the KV-cache allocator sizes from free memory after warmup and defaults to gpu_memory_utilization=1.0; revalidate GPU headroom, and set 0.9 or disable extensible cache to retain prior sizing. ROCm 10.0 replaces 7.2 for published images and wheels.","infrastructureReviewed":"2026-11-17","infrastructureSources":["https://docs.vllm.ai/en/latest/deployment/docker/","https://github.com/vllm-project/vllm/releases/tag/v0.34.0"],"install":"Official vLLM Docker image or supported Python installation; choose a compatible hardware/backend configuration.","installMethods":["docker","source"],"kind":"product","license":"Apache 2.0 for vLLM; model weights and supporting dependencies have independent licenses and access conditions.","licenseModel":"open-source","licenseModelNotes":"The reviewed inference runtime is Apache-2.0 licensed. Its license does not grant rights to the model weights served by that runtime; check model and dependency terms separately.","licenseModelSources":["https://github.com/vllm-project/vllm/blob/main/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"vLLM Self-Hosted","notes":"This entry covers the inference server, not a hosted model service. It can run supported model weights on customer infrastructure, but those weights may need external downloads or access approval and are not licensed by vLLM. Review default usage telemetry and optional outbound integrations; hosting inference does not automatically create an air-gapped system. vLLM v0.34.0 removes Model Runner V1; configurations setting VLLM_USE_V2_MODEL_RUNNER=0 now fail at startup. It changes the default block size from 16 to 64, enables extensible KV cache by default with gpu_memory_utilization defaulting to 1.0, drops ROCm 7.2 wheels and images in favor of ROCm 10.0, requires huggingface_hub 2.0.0 or later, and removes QuTLASS/fp_quant and Marlin W4A8 support. Review the upstream breaking-change table and test model, quantization, memory, and accelerator compatibility before rollout.","operations":"Customer manages model acquisition, hardware capacity, endpoint protection, availability, upgrades and model/runtime compatibility.","publisher":false,"reviewed":"2026-11-17","sources":[{"title":"Official Docker serving images","url":"https://docs.vllm.ai/en/latest/deployment/docker/"},{"title":"Online serving","url":"https://docs.vllm.ai/en/latest/serving/online_serving/"},{"title":"Usage statistics and opt-out","url":"https://docs.vllm.ai/en/latest/usage/usage_stats/"},{"title":"Apache 2.0 license","url":"https://github.com/vllm-project/vllm/blob/main/LICENSE"},{"title":"vLLM v0.34.0 breaking upgrade notes","url":"https://github.com/vllm-project/vllm/releases/tag/v0.34.0"}],"url":"https://launchinyourcloud.com/directory/vllm/","website":"https://vllm.ai/"},{"architecture":"Customer-operated vector database, persistent storage and optional model integrations","categories":["databases-vector","ai-tools"],"category":"Databases \u0026 vector","categoryFit":{"ai-tools":"Self-hosted vector-search database for retrieval and AI applications.","databases-vector":"Vector database supporting pre-vectorized search and configurable model integrations. Connected embedding/generation modules and enterprise features are separate dependencies."},"cloudEvidence":[{"clouds":["aws"],"notes":"The vendor documents a self-managed EKS deployment path. Use that path for this listing: the same page also describes Shared Cloud marketplace SaaS, which is a separate deployment option.","reviewed":"2026-11-21","sourceType":"vendor-documentation","title":"Weaviate self-managed AWS deployment options","url":"https://docs.weaviate.io/deploy/production/aws","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Google documents provisioning a private GKE Standard or Autopilot cluster in the customer’s project with Terraform and installing Weaviate with Helm. The customer operates the database.","reviewed":"2026-11-21","sourceType":"provider-guide","title":"Deploy self-hosted Weaviate on Google Kubernetes Engine","url":"https://docs.cloud.google.com/kubernetes-engine/docs/tutorials/deploy-weaviate","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-21","clouds":["aws","gcp"],"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"}],"description":"Self-hosted vector-search database for retrieval and AI applications.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Upstream vector-index memory example; full workload/topology sizing additional","source":"https://docs.weaviate.io/weaviate/concepts/resources","status":"documented","summary":"The resource-planning guide estimates roughly 3 GB memory for one million uncompressed 384-dimensional float32 vectors using its two-times rule. HNSW connectivity, compression, payloads, replicas and concurrency change requirements; CPU affects query/import throughput. This is an index-sizing example, not a complete minimum or 1-TB/HA guarantee."},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://docs.weaviate.io/deploy/installation-guides/docker-installation","status":"documented","summary":"The Docker guide supplies an official image and configurable Compose recipe. Its default example enables anonymous access; configure authentication, persistent volumes and required modules before exposing the service."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/weaviate/weaviate/main/LICENSE","status":"documented","summary":"Code outside the wl directory is BSD-3-Clause; wl contains separately licensed Enterprise functionality enabled by a licence key. The core licence does not grant those features. Obtain Enterprise pricing and support terms separately from infrastructure."},"release":{"releasePublishedAt":"2026-11-10T13:52:39Z","releaseTag":"v1.40.5","reviewed":"2026-11-19","scope":"Upstream weaviate/weaviate release record; commercial editions and deployment packages may differ","source":"https://github.com/weaviate/weaviate/releases/tag/v1.40.5","status":"documented","summary":"The publisher-designated GitHub release checked was v1.40.5, published 2026-11-10. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. The maintained v1.39 branch has a separate v1.39.17 runtime-reindex restart fix; this does not replace the newer v1.40.5 primary snapshot.","supportingSources":[{"title":"v1.39.17 maintenance release","url":"https://github.com/weaviate/weaviate/releases/tag/v1.39.17"},{"title":"Runtime reindex fix","url":"https://github.com/weaviate/weaviate/pull/13755"}]},"securityControls":{"reviewed":"2026-11-14","scope":"Weaviate database/API controls; not a vendor compliance attestation","source":"https://docs.weaviate.io/deploy/configuration/authentication","status":"documented","summary":"The self-managed authentication guide supports API keys and OIDC and also permits anonymous access. Configure authentication and authorization together; an anonymous quickstart is not a protected production endpoint."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Self-hosted database OIDC authentication","source":"https://docs.weaviate.io/deploy/configuration/authentication","status":"documented","summary":"Self-hosted Weaviate supports OpenID Connect alongside API keys, with Docker and Kubernetes configuration examples. Authentication and RBAC authorization are separate; configure issuer/client settings and role mapping, and disable anonymous access for production."}},"id":"weaviate","infrastructure":["servers"],"infrastructureNotes":"Docker/Compose or Kubernetes runs a provisioned persistent database service. Data-plane ownership does not include optional external model integrations; choose and size those separately.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.weaviate.io/deploy/installation-guides/docker-installation"],"install":"Docker or Docker Compose, or a Kubernetes deployment using Helm. Google’s GKE guide uses Terraform to provision the cluster.","installMethods":["docker","helm","terraform"],"kind":"product","license":"BSD-3-Clause core outside the wl directory; wl code and associated enterprise features require a separate enterprise license/key.","licenseModel":"open-source","licenseModelNotes":"The current repository distinguishes BSD-3-Clause code outside wl/ from enterprise-licensed wl/ code and features enabled by a license key. The complete current product is therefore classified as open-core, not uniformly BSD licensed.","licenseModelSources":["https://github.com/weaviate/weaviate/blob/main/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Weaviate Self-Hosted","notes":"The Docker defaults include anonymous access and default telemetry; production installations must configure the intended controls. Pre-vectorized data can be searched without an external vectorizer, but enabled embedding, reranking or generation integrations may call external providers. Telemetry is enabled by default and has a documented opt-out; the entire current codebase must not be described as uniformly BSD-licensed. Weaviate v1.39.17 fixes a v1.39 runtime-reindex restart bug in which writes arriving before reindex resumed could be absent from the new property index, or an incomplete index could be swapped in after partial files disappeared. Operators remaining on v1.39 should update and verify filter/search results; the primary reviewed release remains the newer v1.40.5 line.","operations":"Customer manages authentication, storage, backup, scaling, configuration and upgrades.","publisher":false,"reviewed":"2026-11-21","sources":[{"title":"Docker and persistent-storage deployment","url":"https://docs.weaviate.io/deploy/installation-guides/docker-installation"},{"title":"Default telemetry and configuration","url":"https://docs.weaviate.io/deploy/configuration/telemetry"},{"title":"Core and enterprise license split","url":"https://github.com/weaviate/weaviate/blob/main/LICENSE"},{"title":"Weaviate v1.39.17 maintenance release","url":"https://github.com/weaviate/weaviate/releases/tag/v1.39.17"},{"title":"Runtime reindex restart fix","url":"https://github.com/weaviate/weaviate/pull/13755"},{"title":"Deploy self-hosted Weaviate on Google Kubernetes Engine","url":"https://docs.cloud.google.com/kubernetes-engine/docs/tutorials/deploy-weaviate"}],"url":"https://launchinyourcloud.com/directory/weaviate/","website":"https://weaviate.io/"},{"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/"},{"advisories":[{"action":"Use the current reviewed plugin, enable PKCE after IdP testing and review linking without verified email. Check callback, account linking and recovery behavior rather than assuming upgrade changes all existing settings.","conditions":"Existing sites that link users have Link Users Without Verified Email enabled during upgrade and receive an admin notice. The changelog provides no universal affected-version range or CVE.","id":"wordpress-oidc-generic-3-11-4-security-settings","listingIds":["wordpress-self-hosted"],"reviewed":"2026-11-18","scope":"Only WordPress sites using the optional OpenID Connect Generic Client plugin; this is not a WordPress core or every-provider-image advisory.","source":"https://wordpress.org/plugins/daggerhart-openid-connect-generic/","summary":"OpenID Connect Generic Client 3.11.4 changes login state, nonce and verified-email linking checks. PKCE defaults on for new installs but stays off on existing sites until enabled.","title":"Optional WordPress OIDC plugin security settings need review","type":"security-advisory"},{"action":"Update immediately to 7.1.5 or the corresponding supported backport and verify the exact provider-image version.","conditions":"Multisite administration, block-editor/media workflows and the installed core branch determine applicability.","disclosedOn":"2026-11-18","id":"wordpress-7-1-5-security-release","listingIds":["wordpress-self-hosted"],"reviewed":"2026-11-19","scope":"WordPress core 7.1 and eligible supported backport branches; themes and plugins remain separate.","source":"https://wordpress.org/news/2026/11/wordpress-7-1-5-release/","summary":"WordPress 7.1.5 fixes multisite privilege escalation to Super Admin, stored and reflected XSS paths and media-type hardening.","title":"WordPress 7.1.5 security release","type":"security-advisory"}],"architecture":"PHP application with a customer-controlled MySQL or MariaDB database and persistent media storage.","categories":["content-management"],"category":"Content management \u0026 CMS","categoryFit":{"content-management":"Publishes websites, blogs and extensible structured content with themes, plugins and a browser-based editorial interface."},"cloudEvidence":[{"clouds":["aws"],"notes":"AWS documents selecting a region, launching the WordPress blueprint and operating the instance in the customer's Lightsail account.","reviewed":"2026-11-18","sourceType":"provider-guide","title":"WordPress in the customer's Amazon Lightsail account","url":"https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Microsoft's quickstart deploys the WordPress Marketplace item and backing Azure resources into the customer's selected subscription and resource group.","reviewed":"2026-11-18","sourceType":"provider-guide","title":"WordPress on Azure App Service","url":"https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Google documents customer deployments of WordPress on Google Cloud, including a Compute Engine path. Provider packaging and support scope must be reviewed.","reviewed":"2026-11-18","sourceType":"provider-guide","title":"WordPress on Google Cloud","url":"https://cloud.google.com/wordpress","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"DigitalOcean installs the full WordPress application and database on a customer Droplet. Confirm the resolved image version and production/HA design.","reviewed":"2026-11-18","sourceType":"provider-guide","title":"WordPress DigitalOcean 1-Click application","url":"https://docs.digitalocean.com/products/marketplace/catalog/wordpress/","vendorSupport":"not-assessed"},{"clouds":["oci"],"notes":"Oracle lists a Resource Manager quickstart that deploys a WordPress instance into OCI. It is a provider application template, not a WordPress support contract or HA guarantee.","reviewed":"2026-11-18","sourceType":"provider-guide","title":"OCI Resource Manager WordPress template","url":"https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Reference/templates.htm","vendorSupport":"not-assessed"},{"clouds":["linode"],"notes":"Akamai documents full application/database deployment on a customer Compute Instance using StackScript 401697, with Cloud Manager and API/CLI inputs.","reviewed":"2026-11-18","sourceType":"provider-guide","title":"WordPress on Akamai Cloud (Linode)","url":"https://techdocs.akamai.com/quick-deploy-apps/docs/wordpress","vendorSupport":"not-assessed"},{"clouds":["vultr"],"notes":"Vultr documents launching the full WordPress application on the customer’s selected server size/location and configuring its administrator, domain and TLS.","reviewed":"2026-11-18","sourceType":"provider-guide","title":"Vultr One-Click WordPress","url":"https://docs.vultr.com/one-click-wordpress","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-18","clouds":["aws","azure","gcp","digitalocean","oci","linode","vultr"],"communityAcceptance":{"reviewed":"2026-11-18","sources":[{"title":"Official maintenance and adoption evidence","url":"https://wordpress.org/documentation/article/wordpress-versions/"},{"title":"Official maintenance and adoption evidence","url":"https://wordpress.org/showcase/nasa/"}],"summary":"The project maintains a dated core release history and documents NASA’s WordPress-based web properties. This establishes maintained software and named adoption, not the cloud account or suitability of a particular plugin stack."},"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":"cloud-account","cloud":"oci","controlPlane":"not-assessed","evidence":[4],"operator":"customer"},{"boundary":"cloud-account","cloud":"linode","controlPlane":"not-assessed","evidence":[5],"operator":"customer"},{"boundary":"cloud-account","cloud":"vultr","controlPlane":"not-assessed","evidence":[6],"operator":"customer"}],"description":"Open-source content management system with documented customer-account deployments across major clouds and application-provider images.","diligence":{"airGap":{"reviewed":"2026-11-18","scope":"WordPress Self-Hosted: selected customer-operated edition","source":"https://developer.wordpress.org/reference/classes/wp_http/block_request/","status":"inconclusive","summary":"WordPress documents manual updates and WP_HTTP_BLOCK_EXTERNAL for requests made through its HTTP API. The latter allows local/site requests and does not govern arbitrary PHP networking by plugins. These controls do not validate a disconnected lifecycle for a selected theme/plugin stack. Confirm offline packages, licences, mail, IdP, media/CDN and update dependencies for that stack.","supportingSources":[{"title":"Manual core update procedure","url":"https://wordpress.org/documentation/article/updating-wordpress/"}]},"commitments":{"reviewed":"2026-11-18","scope":"WordPress Self-Hosted: selected customer-operated edition","source":"https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress","status":"inconclusive","summary":"The Azure quickstart creates App Service and database resources, but does not establish software-offer commitment credit. Check the selected provider charges and the buyer’s agreement; WordPress core’s free license is not a transactable commitment claim.","supportingSources":[{"title":"AWS commitment qualification is product/agreement-specific","url":"https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html"}]},"compliance":{"reviewed":"2026-11-18","scope":"WordPress Self-Hosted: selected customer-operated edition","source":"https://wordpress.org/about/security/","status":"inconclusive","summary":"The WordPress security paper describes project practices, not an independent attestation covering the buyer’s site, plugins, hosting and operations. Obtain the deployment-specific control and audit scope."},"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://wordpress.org/about/requirements/","status":"inconclusive","summary":"100 internal users and 1 TB do not determine page requests, PHP workers, database I/O or media delivery. Specify traffic/concurrency, plugin stack, cache/CDN, media versus database storage, HA database and application design, backups, egress and paid extensions before estimating AWS us-east-1 operations.","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":"WordPress Self-Hosted: selected customer-operated edition","source":"https://wordpress.org/about/requirements/","status":"documented","summary":"The project recommends PHP 8.3+, MariaDB 10.11+ or MySQL 8.4+, and HTTPS; Apache or Nginx is recommended. It does not give a universal CPU/RAM minimum. PHP 7.4/MySQL 5.5.5 compatibility is a legacy fallback, not a recommendation to use those EOL runtimes."},"iac":{"reviewed":"2026-11-18","scope":"WordPress Self-Hosted: selected customer-operated edition","source":"https://techdocs.akamai.com/quick-deploy-apps/docs/wordpress","status":"documented","summary":"Akamai documents WordPress StackScript 401697 and maps its database, administrator and web-server inputs to Cloud Manager and API/CLI deployment. AWS supplies a Lightsail blueprint and OCI lists a Resource Manager WordPress template. These are provider-managed moving packages, not a pinned upstream application release.","supportingSources":[{"title":"Lightsail blueprint","url":"https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html"},{"title":"OCI Resource Manager application templates","url":"https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Reference/templates.htm"}]},"licensePricing":{"reviewed":"2026-11-18","scope":"WordPress Self-Hosted: selected customer-operated edition","source":"https://wordpress.org/about/license/","status":"documented","summary":"WordPress core is GPLv2 or later, without a core software subscription. Themes, plugins, commercial support and provider packaging may introduce separate terms and charges. Hosting and operations are additional."},"marketplace":{"availability":"available","offers":[{"cloud":"digitalocean","delivery":"Droplet 1-Click application","id":"wordpress","publisher":"DigitalOcean","url":"https://marketplace.digitalocean.com/apps/wordpress","version":"WordPress 7.1.4; package label latest"}],"reviewed":"2026-11-18","scope":"WordPress Self-Hosted: selected customer-operated edition","source":"https://docs.digitalocean.com/products/marketplace/catalog/wordpress/","status":"documented","summary":"DigitalOcean offers a WordPress 1-Click Droplet, currently including WordPress 7.1.4, PHP 8.3.36 and MySQL 8.0.46. That database version is below WordPress’s current MySQL 8.4 recommendation. Microsoft also documents an App Service Marketplace item. Packaging and infrastructure charges are separate from WordPress.com.","supportingSources":[{"title":"Microsoft WordPress deployment","url":"https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress"},{"title":"Lightsail WordPress blueprint","url":"https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html"},{"title":"Upstream runtime/database recommendations","url":"https://wordpress.org/about/requirements/"}]},"release":{"releasePublishedOn":"2026-11-18","releaseTag":"7.1.5","reviewed":"2026-11-19","scope":"WordPress.org self-hosted core; themes, plugins and provider images require separate version review","source":"https://wordpress.org/news/2026/11/wordpress-7-1-5-release/","status":"documented","summary":"WordPress 7.1.5 was released November 18, 2026. It is a security release fixing multisite privilege escalation, stored and reflected XSS paths and media-type hardening. Eligible older branches received backports; provider packages may lag.","supportingSources":[{"title":"Prior reviewed release context","url":"https://wordpress.org/documentation/article/wordpress-versions/"},{"title":"Version-specific documentation","url":"https://wordpress.org/documentation/wordpress-version/version-7-1-5/"}]},"scim":{"availability":"edition-dependent","reviewed":"2026-11-18","scope":"Third-party miniOrange WordPress provisioning plugin; inbound users, with Premium lifecycle operations; not native core SCIM","source":"https://wordpress.org/plugins/scim-user-provisioning/","status":"documented","summary":"miniOrange supplies an optional inbound SCIM endpoint: the IdP sends users to WordPress using a base URL and bearer token. Free creation is documented; profile updates, deletion/deactivation and reactivation require Premium. Enhanced group push/import are listed as future work. Soft deactivation retains the account and blocks login, but the guides do not establish revocation of existing sessions. Public package 1.2.0 is separate from the licensed Premium delivery.","supportingSources":[{"title":"Provisioning operations, Premium boundary and group limitations","url":"https://plugins.miniorange.com/wordpress-scim-user-provisioning"}]},"securityControls":{"reviewed":"2026-11-19","scope":"WordPress core 7.1 and eligible backported branches; third-party themes and plugins are outside this advisory","source":"https://wordpress.org/news/2026/11/wordpress-7-1-5-release/","status":"documented","summary":"The hardening guide covers restricted database privileges, file permissions, protecting wp-config.php, disabling dashboard file editing, backups and logging. Core, theme and plugin updates remain customer responsibilities; a provider image does not complete this work. Current review: WordPress 7.1.5 fixes multisite privilege escalation to Super Admin, stored and reflected XSS paths and media-type hardening. Update immediately or use the corresponding supported backport, and verify the exact provider image version.","supportingSources":[{"title":"Prior security-controls source","url":"https://developer.wordpress.org/advanced-administration/security/hardening/"},{"title":"Optional OIDC plugin 3.11.4 security settings and upgrade behavior","url":"https://wordpress.org/plugins/daggerhart-openid-connect-generic/"}]},"sso":{"artifactRef":"OpenID Connect Generic Client 3.11.4","artifactUrl":"https://downloads.wordpress.org/plugin/daggerhart-openid-connect-generic.3.11.4.zip","availability":"available","reviewed":"2026-11-18","scope":"Optional OpenID Connect Generic Client 3.11.4; WordPress user login, not every theme/plugin or external application","source":"https://wordpress.org/plugins/daggerhart-openid-connect-generic/","status":"documented","summary":"OpenID Connect Generic Client 3.11.4 provides authorization-code SSO and optional account creation/linking for WordPress logins. It is a separately installed community plugin, not bundled core or a provider-image entitlement. It requires PHP 8.0+; configure the IdP, redirect URI and linking policy. Version 3.11.4 changes state/nonce validation and requires review of PKCE and existing-user linking settings."}},"id":"wordpress-self-hosted","infrastructure":["servers"],"infrastructureNotes":"WordPress runs on provisioned application and database capacity with durable media and database state, even when a provider manages parts of the substrate.","infrastructureReviewed":"2026-11-18","infrastructureSources":["https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html","https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress"],"install":"Provider application images/blueprints, Azure App Service quickstart, OCI Resource Manager template, or Akamai StackScript; package and topology vary by provider","installMethods":["platform-template","vm-image","terraform","package"],"kind":"product","license":"GPLv2 or later; themes, plugins and provider packaging may have separate terms.","licenseModel":"open-source","licenseModelNotes":"WordPress core is released under GPLv2 or later. Themes, plugins and provider images can add separate licenses or charges.","licenseModelSources":["https://wordpress.org/about/license/"],"licenseReviewed":"2026-11-18","model":"Fully in your account","modelLabel":"Customer-operated","name":"WordPress Self-Hosted","notes":"This entry covers WordPress.org self-hosting, not WordPress.com SaaS. Provider blueprints accelerate installation but do not replace application hardening, backup, patching and plugin review. Provider packages can lag upstream. The current recommended PHP/database versions and application/plugin stack need a separate patch and HA review. WordPress 7.1.5 is a security release fixing multisite privilege escalation to Super Admin, stored and reflected XSS paths and media-type hardening. Security fixes were backported to eligible older branches. Update immediately, and verify provider images that still advertise 7.1.4 or earlier rather than assuming the platform package is current.","operations":"Customer manages WordPress core, themes and plugins, application security, identities, content, database, media, backups, scaling and upgrades.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Launch and configure WordPress on Amazon Lightsail","url":"https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress.html"},{"title":"Create a WordPress site on Azure App Service","url":"https://learn.microsoft.com/en-us/azure/app-service/quickstart-wordpress"},{"title":"WordPress on Google Cloud","url":"https://cloud.google.com/wordpress"},{"title":"WordPress GPL license","url":"https://wordpress.org/about/license/"},{"title":"WordPress DigitalOcean 1-Click application","url":"https://docs.digitalocean.com/products/marketplace/catalog/wordpress/"},{"title":"OCI Resource Manager WordPress template","url":"https://docs.oracle.com/en-us/iaas/Content/ResourceManager/Reference/templates.htm"},{"title":"WordPress on Akamai Cloud (Linode)","url":"https://techdocs.akamai.com/quick-deploy-apps/docs/wordpress"},{"title":"Vultr One-Click WordPress","url":"https://docs.vultr.com/one-click-wordpress"},{"title":"WordPress 7.1.5 security release","url":"https://wordpress.org/news/2026/11/wordpress-7-1-5-release/"},{"title":"WordPress 7.1.5 documentation","url":"https://wordpress.org/documentation/wordpress-version/version-7-1-5/"}],"url":"https://launchinyourcloud.com/directory/wordpress-self-hosted/","website":"https://wordpress.org/"},{"architecture":"Customer-operated management control plane and distributed database universe nodes","categories":["databases-vector"],"category":"Databases \u0026 vector","categoryFit":{"databases-vector":"Provides a self-managed control plane for deploying and operating distributed YugabyteDB database clusters across customer cloud infrastructure."},"cloudEvidence":[{"clouds":["aws"],"notes":"Yugabyte documents customer AWS credentials, regions, networks and VM provisioning for YBA-managed database universes.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"YugabyteDB Anywhere AWS provider","url":"https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/aws/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Yugabyte documents customer Azure subscription credentials, resource groups, networks and VM provisioning for YBA-managed universes.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"YugabyteDB Anywhere Azure provider","url":"https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/azure/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Yugabyte documents customer GCP service accounts, projects, regions and instance provisioning for YBA-managed universes.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"YugabyteDB Anywhere Google Cloud provider","url":"https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/gcp/","vendorSupport":"not-assessed"},{"clouds":["oci"],"notes":"Yugabyte documents customer OCI credentials, regions, availability domains and VM provisioning for YBA-managed universes.","reviewed":"2026-11-14","sourceType":"vendor-documentation","title":"YugabyteDB Anywhere OCI provider","url":"https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/oci/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-14","clouds":["aws","azure","gcp","oci"],"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":"oci","controlPlane":"not-assessed","evidence":[3],"operator":"customer"}],"description":"Commercial self-managed database-as-a-service control plane for YugabyteDB clusters.","diligence":{"airGap":{"reviewed":"2026-11-14","scope":"Documented YBA offline release-management path","source":"https://docs.yugabyte.com/stable/yugabyte-platform/manage-deployments/ybdb-releases/","status":"documented","summary":"YBA documents manual database-release upload for air-gapped instances and additional software prerequisites for offline database nodes. Prepare dependencies and the management/data-plane network; this is not the default connected installation.","supportingSources":[{"title":"Offline database-node prerequisites","url":"https://docs.yugabyte.com/stable/yugabyte-platform/prepare/server-nodes-software/"}]},"footprint":{"reviewed":"2026-11-14","scope":"YugabyteDB Anywhere management VM only; a license file is required","source":"https://docs.yugabyte.com/stable/yugabyte-platform/prepare/server-yba/","status":"documented","summary":"The YBA management-server VM requires 4 cores, 8 GB RAM and 215 GB disk on x86 Linux. Database universes run on separate nodes and need separate sizing; these figures are not a complete database footprint."},"iac":{"artifactRef":"Current stable vendor YBA Installer documentation","artifactUrl":"https://docs.yugabyte.com/stable/yugabyte-platform/install-yugabyte-platform/install-software/installer/","reviewed":"2026-11-21","scope":"YugabyteDB Anywhere management-platform installer, not the whole managed database estate","source":"https://docs.yugabyte.com/stable/yugabyte-platform/install-yugabyte-platform/install-software/installer/","status":"documented","summary":"The vendor YBA Installer deploys and manages YugabyteDB Anywhere using a downloaded release, YAML configuration and installer lifecycle commands. Provision the management host and permissions separately from database universe nodes; pin a supported release and configure storage, TLS and backups."},"licensePricing":{"reviewed":"2026-11-21","scope":"April 2026 installed-software commercial terms for YugabyteDB Anywhere","source":"https://www.yugabyte.com/legal/installed-software-terms/","status":"documented","summary":"The installed-software terms explicitly include YugabyteDB Anywhere and license executable use under an Order Form with capacity metrics such as vCPU/CPU cores. Monitor contracted usage and review support, increases and renewal terms; the open-source database core licence is a different entitlement."},"sso":{"availability":"available","reviewed":"2026-11-21","scope":"YugabyteDB Anywhere administrator console; database identities separate","source":"https://docs.yugabyte.com/stable/yugabyte-platform/administer-yugabyte-platform/oidc-authentication/","status":"documented","summary":"YugabyteDB Anywhere documents OIDC authentication for its management console with IdP/client configuration and user/role mapping. This is management-platform SSO, distinct from database-user OIDC and from the vendor-operated Aeon service."}},"id":"yugabytedb-anywhere","infrastructure":["servers"],"infrastructureNotes":"YugabyteDB Anywhere and the database universe run as persistent control-plane and database-server workloads on VMs or Kubernetes.","infrastructureReviewed":"2026-11-14","infrastructureSources":["https://docs.yugabyte.com/stable/yugabyte-platform/","https://docs.yugabyte.com/stable/yugabyte-platform/prepare/"],"install":"Installer or Helm deployment, followed by customer-cloud provider configuration","installMethods":["helm","package"],"kind":"product","license":"Commercial installed-software license; YugabyteDB core components have separate source licenses.","licenseModel":"commercial-only","licenseModelNotes":"YugabyteDB Anywhere is commercial installed software. The open-source YugabyteDB database and evaluation packages have separate terms and do not replace the production YBA entitlement.","licenseModelSources":["https://www.yugabyte.com/legal/installed-software-terms/","https://docs.yugabyte.com/stable/faq/general/"],"licenseReviewed":"2026-11-14","model":"Fully in your account","modelLabel":"Customer-operated","name":"YugabyteDB Anywhere","notes":"This entry covers YugabyteDB Anywhere, not the managed YugabyteDB Aeon service or a manual deployment of only the open-source database. Cloud provider configurations require customer credentials, network access and supported machine images.","operations":"Customer operates YugabyteDB Anywhere and its database nodes while the software automates provisioning, scaling, backups and upgrades.","publisher":false,"reviewed":"2026-11-14","sources":[{"title":"YugabyteDB Anywhere overview","url":"https://docs.yugabyte.com/stable/yugabyte-platform/"},{"title":"Provider configurations","url":"https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/"},{"title":"Deployment planning","url":"https://docs.yugabyte.com/stable/yugabyte-platform/create-deployments/create-universes-overview/"},{"title":"Installed software license terms","url":"https://www.yugabyte.com/legal/installed-software-terms/"}],"url":"https://launchinyourcloud.com/directory/yugabytedb-anywhere/","website":"https://www.yugabyte.com/yugabytedb-anywhere/"},{"architecture":"Customer-operated Zabbix server, web frontend and database on a cloud virtual machine.","categories":["observability"],"category":"Observability","categoryFit":{"observability":"Monitors infrastructure, networks, applications, logs and service availability through a customer-operated server and agents."},"cloudEvidence":[{"clouds":["aws"],"notes":"Zabbix documents launching the official server image into the customer's selected AWS VPC and subnet.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"Zabbix Server on AWS","url":"https://www.zabbix.com/documentation/current/en/manual/installation/install/aws_deployment_guide","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The current Azure deployment guide launches the server appliance in the customer subscription. Its 7.4 example does not include infrastructure redundancy and is distinct from current upstream 8.0.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"Zabbix Server on Azure","url":"https://www.zabbix.com/documentation/current/en/manual/installation/install/azure_deployment_guide","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Zabbix documents deployment from Google Cloud Marketplace into the customer's project.","reviewed":"2026-11-18","sourceType":"vendor-documentation","title":"Zabbix Server on Google Cloud","url":"https://www.zabbix.com/documentation/current/en/manual/installation/install/cloud_google","vendorSupport":"not-assessed"},{"clouds":["digitalocean"],"notes":"DigitalOcean lists full Zabbix Server Droplet packages, including 6.0.17 (image 131398452, slug zabbix-zabbixserver60). These older images require supported-branch/patch/OS review; they are not current upstream 8.0 packages.","reviewed":"2026-11-18","sourceType":"provider-guide","title":"Official Zabbix DigitalOcean image","url":"https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-18","clouds":["aws","azure","gcp","digitalocean"],"communityAcceptance":{"reviewed":"2026-11-18","sources":[{"title":"Official maintenance and adoption evidence","url":"https://www.zabbix.com/users"},{"title":"Official maintenance and adoption evidence","url":"https://www.zabbix.com/release_notes"}],"summary":"Zabbix maintains a named user/case-study catalog and dated current/LTS release histories, providing adoption and maintenance evidence beyond downloads. Provider images retain their own versions, licences and support terms."},"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"}],"description":"Open-source monitoring platform deployed from official Zabbix cloud images into customer accounts.","diligence":{"airGap":{"availability":"available","reviewed":"2026-11-18","scope":"Self-hosted Zabbix with prepared packages and local monitoring/database dependencies; not every optional external integration","source":"https://blog.zabbix.com/showcasing-our-potential-at-europol-industry-and-research-days/32733/","status":"documented","summary":"Zabbix explicitly describes fully on-premises, air-gapped monitoring without external cloud services. The current server setting AllowSoftwareUpdateCheck=0 disables software-update checks. Stage OS/application packages, database, agents, templates and updates for the isolated network; external notification channels and cloud integrations need reachable internal replacements or must be omitted.","supportingSources":[{"title":"Current update-check setting and server configuration","url":"https://www.zabbix.com/documentation/current/en/manual/concepts/server/server_params"}]},"commitments":{"reviewed":"2026-11-18","scope":"Zabbix Server: selected customer-operated edition","source":"https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4","status":"inconclusive","summary":"The paid AWS image does not establish the buyer’s software commitment eligibility. Direct source/package installation, support contracts and provider images have different charging paths; verify the chosen order and agreement.","supportingSources":[{"title":"AWS commitment qualification is product/agreement-specific","url":"https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html"}]},"compliance":{"reviewed":"2026-11-18","scope":"Vendor-reported renewal plus an older issuer certificate; current certificate/issuer validity and assessed scope remain unconfirmed","source":"https://blog.zabbix.com/zabbix-in-2025-a-year-of-growth-community-and-innovation/32470/","status":"inconclusive","summary":"Zabbix’s year-in-review reports three-year ISO 27001/27017 recertification in 2025. Its public BM PDF MSC-27-849 still expires December 27, 2025. These sources distinguish a renewal claim from the older certificate; neither supplies the renewed issuer record and current assessed scope here. Obtain that document/status before relying on current supplier assurance, and assess the customer monitoring environment separately. The old PDF is not proof that certification lapsed.","supportingSources":[{"title":"Current vendor security-policy statement","url":"https://www.zabbix.com/zabbix_security_policy"},{"title":"Older published issuer certificate","url":"https://assets.zabbix.com/img/about/Zabbix_ISO_27001_ISO_27017_Certificate_EN_2024.pdf"},{"title":"Issuer directs management-system checks to IAF CertSearch","url":"https://bmcertification.com/about-us/certificate-check/"}]},"cost":{"estimate":{"currency":"USD","exclusions":["Entire HA database and all monitoring/history/trend data storage","Frontend, proxies, agents and paid Marketplace AMI surcharges","Backup and restore testing","Networking, IPv4 and all data transfer","Software/image licence and support","Operating labor, monitoring, taxes and discounts"],"kind":"partial-infrastructure","period":"month","region":"AWS us-east-1","rows":[{"description":"2 Linux m6i.large VMs × 730 h; editorial capacity choice, not a vendor 100-user benchmark","id":"compute","quantity":1460,"rate":0.096},{"description":"2 × 30 GB application boot gp3 only; all 1 TB monitoring/database data excluded","id":"storage","quantity":60,"rate":0.08},{"description":"Unpriced: the entire HA database, including its compute, licences and storage for all 1 TB of monitoring/history data","id":"database","quantity":1,"rate":""},{"description":"Unpriced: Backup capacity, retention, restore testing and recovery services","id":"backup","quantity":1,"rate":""},{"description":"Unpriced: Load balancers, NAT/endpoints, IPv4 and all transfer, including cross-AZ replication","id":"network","quantity":1,"rate":""},{"description":"Unpriced: Software/image licences, commercial support and entitlement for failover","id":"license","quantity":1,"rate":""},{"description":"Unpriced: Operation, patching, monitoring and incident/recovery labor","id":"labor","quantity":1,"rate":""}],"workload":"100 internal users; 1 TB (1,000 GB) logical data; HA target; average usage unmeasured; 730 h/month. Only the explicitly identified layer is priced; see scope and excluded components."},"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":"Editorial Zabbix native-server HA application layer across two AZs, with a separately designed reachable HA database. Two CPUs/8 GiB mirrors the small 1,000-metric illustration, not a 100-user or throughput benchmark. No data volume or database service is included.","source":"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","status":"inconclusive","summary":"Illustrative priced infrastructure subtotal: USD 144.96/month. Only two 2-vCPU/8-GiB application VMs and 30 GB boot gp3 each are priced. Native server HA is active/standby and shares a database. The HA database, all 1 TB monitoring/history data, frontend and proxies are unpriced; this is not the paid appliance AMI price. This is not a complete operating-cost estimate or validated capacity/SLA claim.","supportingSources":[{"title":"Product topology/sizing basis","url":"https://www.zabbix.com/documentation/current/en/manual/concepts/server/ha"},{"title":"Current AWS us-east-1 gp3 capacity example","url":"https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html"},{"title":"EBS performance and charging qualifications","url":"https://aws.amazon.com/ebs/pricing/"},{"title":"Metric-count sizing illustrations","url":"https://www.zabbix.com/documentation/current/en/manual/installation/requirements"}]},"footprint":{"reviewed":"2026-11-18","scope":"Zabbix Server: selected customer-operated edition","source":"https://www.zabbix.com/documentation/current/en/manual/installation/requirements","status":"documented","summary":"The requirements table gives an illustrative small installation at 1,000 metrics with 2 CPUs/8 GiB RAM and medium at 10,000 metrics with 4 CPUs/16 GiB. History/trend retention, polling frequency and database design dominate storage. These are metric-count examples, not user-count or fully redundant database sizing."},"iac":{"reviewed":"2026-11-18","scope":"Zabbix Server: selected customer-operated edition","source":"https://www.zabbix.com/documentation/current/en/manual/installation/install/azure_deployment_guide","status":"documented","summary":"The Azure guide deploys a Zabbix appliance VM into the customer subscription but uses a 7.4 example without infrastructure redundancy. AWS and DigitalOcean provide separately versioned images. Pin the actual image ID/version and supply database/HA automation rather than treating an appliance as a complete HA artifact.","supportingSources":[{"title":"AWS image/package","url":"https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4"},{"title":"DigitalOcean image IDs","url":"https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/"}]},"licensePricing":{"reviewed":"2026-11-18","scope":"Zabbix Server: selected customer-operated edition","source":"https://www.zabbix.com/license","status":"documented","summary":"Zabbix 7.0+ is AGPLv3; older releases including the DigitalOcean 6.x images use GPLv2. Direct open-source software, paid support and provider-image usage charges are separate. The reviewed AWS AMI is usage-priced despite open-source upstream licensing.","supportingSources":[{"title":"AWS image usage terms","url":"https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4"},{"title":"Older DigitalOcean release packages","url":"https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/"}]},"marketplace":{"availability":"available","offers":[{"cloud":"aws","delivery":"Amazon Machine Image (AMI)","id":"prodview-jf4elxhe5llj4","publisher":"Zabbix","url":"https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4","version":"v7.4.16"}],"reviewed":"2026-11-18","scope":"Zabbix Server: selected customer-operated edition","source":"https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4","status":"documented","summary":"Zabbix publishes an AWS Server AMI, currently package v7.4.16 on Rocky Linux 10.2, with usage pricing after its trial. DigitalOcean’s catalog separately lists older 6.0/6.2/6.4 images. Neither package should be represented as the current upstream 8.0.0 release.","supportingSources":[{"title":"DigitalOcean image IDs and versions","url":"https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/"}]},"release":{"releasePublishedOn":"2026-11-05","releaseTag":"8.0.0","reviewed":"2026-11-18","scope":"Zabbix Server: selected customer-operated edition","source":"https://www.zabbix.com/release_notes","status":"documented","summary":"Zabbix 8.0.0 was released November 5, 2026. The reviewed AWS AMI remains v7.4.16 and DigitalOcean offers older 6.x images. A current upstream release does not mean every provider package has been refreshed.","supportingSources":[{"title":"AWS packaged version","url":"https://aws.amazon.com/marketplace/pp/prodview-jf4elxhe5llj4"},{"title":"DigitalOcean packaged versions","url":"https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/"}]},"scim":{"availability":"available","reviewed":"2026-11-18","scope":"Zabbix Server: selected customer-operated edition","source":"https://www.zabbix.com/documentation/current/en/manual/web_interface/frontend_sections/users/authentication/saml","status":"documented","summary":"SCIM 2.0 is documented with SAML just-in-time provisioning enabled, a Super admin API token and api_scim.php. Only users provisioned through the SAML/JIT path are continuously updated; existing local users are not automatically imported. Review deprovisioned-group mapping and the privileged token."},"securityControls":{"reviewed":"2026-11-18","scope":"Zabbix Server: selected customer-operated edition","source":"https://www.zabbix.com/documentation/current/en/manual/web_interface/frontend_sections/users/authentication/saml","status":"documented","summary":"The frontend provides SAML role/group mappings and privileged-token controls for SCIM. Zabbix separately documents certificate/PSK encryption for component connections. Configure each transport and access boundary; SSO does not secure agent/proxy traffic by itself.","supportingSources":[{"title":"Component encryption guide","url":"https://www.zabbix.com/documentation/current/en/manual/encryption"}]},"sso":{"availability":"available","reviewed":"2026-11-18","scope":"Zabbix Server: selected customer-operated edition","source":"https://www.zabbix.com/documentation/current/en/manual/web_interface/frontend_sections/users/authentication/saml","status":"documented","summary":"Zabbix documents SAML 2.0 frontend authentication with IdP mapping and optional just-in-time provisioning. Configure group/role mappings and login permissions. This is distinct from agent/proxy authentication."}},"id":"zabbix","infrastructure":["servers"],"infrastructureNotes":"Zabbix runs persistent monitoring and database services on customer virtual-machine capacity.","infrastructureReviewed":"2026-11-18","infrastructureSources":["https://www.zabbix.com/cloud_images"],"install":"Official Zabbix VM images from AWS, Azure, Google Cloud or DigitalOcean marketplaces","installMethods":["vm-image","package"],"kind":"product","license":"AGPLv3 for Zabbix 7.0+; older releases such as the reviewed DigitalOcean 6.x packages use GPLv2. Provider images/support can be separately charged.","licenseModel":"open-source","licenseModelNotes":"Zabbix 7.0 and later are AGPLv3; professional support is optional and separate.","licenseModelSources":["https://www.zabbix.com/license"],"licenseReviewed":"2026-11-18","model":"Fully in your account","modelLabel":"Customer-operated","name":"Zabbix Server","notes":"Provider packages differ: the reviewed AWS AMI is v7.4.16, the Azure guide uses a 7.4 example, and DigitalOcean lists older 6.x images. Upstream 8.0.0 does not make those images current. Recheck supported branches/OS and patch before use; single appliances do not establish HA or retention sizing.","operations":"Customer manages VM, database, storage, agents, networking, TLS, retention, backups, upgrades and monitoring capacity.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Zabbix cloud images","url":"https://www.zabbix.com/cloud_images"},{"title":"AWS deployment guide","url":"https://www.zabbix.com/documentation/current/en/manual/installation/install/aws_deployment_guide"},{"title":"Azure deployment guide","url":"https://www.zabbix.com/documentation/current/en/manual/installation/install/azure_deployment_guide"},{"title":"Google Cloud deployment guide","url":"https://www.zabbix.com/documentation/current/en/manual/installation/install/cloud_google"},{"title":"Zabbix license","url":"https://www.zabbix.com/license"},{"title":"DigitalOcean Droplet package catalog","url":"https://docs.digitalocean.com/products/marketplace/droplet-1-click-apps/"}],"url":"https://launchinyourcloud.com/directory/zabbix/","website":"https://www.zabbix.com/"}],"relatedQuestions":[{"id":"software-on-google-cloud","json":"https://launchinyourcloud.com/api/v1/questions/software-on-google-cloud.json","markdown":"https://launchinyourcloud.com/questions/software-on-google-cloud/index.md","question":"What self-hosted software runs on Google Cloud?","url":"https://launchinyourcloud.com/questions/software-on-google-cloud/"}],"schemaVersion":1,"url":"https://launchinyourcloud.com/clouds/gcp/"}