{"catalog":"https://launchinyourcloud.com/api/v1/catalog.json","catalogRevision":"170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde","cloud":{"boundary":"Render workspace, project and services; platform-managed infrastructure","classificationReview":{"reviewed":"2026-11-20","source":"https://render.com/docs/deploys","summary":"Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account."},"defaultBoundary":"platform-workspace","diligence":[{"reviewed":"2026-11-14","source":"https://render.com/docs/private-network","summary":"Services in the same region can use Render private networking. Free web services can send but cannot receive private-network requests. Review the actual paid service and endpoint requirements.","topic":"Private networking"}],"id":"render","identity":"Workspace membership and deployment credentials","install":"Deploy application services and databases using a Blueprint or Docker/source build; configure persistent disks, secrets and recovery.","name":"Render","network":"Private services with separately exposed public endpoints","providerType":"application-platform","reviewed":"2026-11-12","short":"Render","source":"https://render.com/docs/deploys"},"kind":"cloud","listings":[{"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":"Dittofeed application, PostgreSQL, ClickHouse and supporting services.","categories":["marketing-automation"],"category":"Marketing automation","categoryFit":{"marketing-automation":"Self-hosted customer engagement and messaging orchestration platform."},"cloudEvidence":[{"clouds":["render"],"notes":"Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"\u003e ## Documentation Index\n\u003e Fetch the complete documentation index at: https://docs.dittofeed.com/llms.txt\n\u003e Use this fil","url":"https://docs.dittofeed.com/deployment/self-hosted/render.md","vendorSupport":"not-assessed"},{"clouds":["railway"],"notes":"Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.","reviewed":"2026-11-19","sourceType":"community-template","title":"Railway","url":"https://railway.com/deploy/dittofeed-2","vendorSupport":"not-assessed"},{"clouds":["hostinger"],"notes":"Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.","reviewed":"2026-11-19","sourceType":"provider-guide","title":"Hostinger","url":"https://www.hostinger.com/applications/dittofeed","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["render","railway","hostinger"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/dittofeed/dittofeed/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/dittofeed/dittofeed"}],"summary":"The reviewed upstream contributor history includes maxgurewitz, chandlercraig, neo773, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee."},"deploymentPaths":[{"boundary":"platform-workspace","cloud":"render","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"vps-account","cloud":"hostinger","controlPlane":"not-assessed","evidence":[2],"operator":"customer"}],"description":"Self-hosted customer engagement and messaging orchestration platform.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Documented chart component allocations, not total host or production capacity","source":"https://docs.dittofeed.com/deployment/self-hosted/kubernetes.md","status":"documented","summary":"The Helm guide lists application-container requests/limits of 1 CPU and 512 MiB RAM and ClickHouse memory requests/limits of 1 GiB. These are component configuration defaults, not a whole-stack minimum: PostgreSQL, Temporal, storage, replicas and traffic need separate capacity. They do not size 100 users, 1 TB or HA."},"iac":{"artifactRef":"main (moving branch; pin compatible application and dependency versions)","artifactUrl":"https://github.com/dittofeed/dittofeed/blob/main/docker-compose.lite.yaml","reviewed":"2026-11-20","scope":"Vendor community/lite deployment recipe, distinct from Enterprise image delivery","source":"https://docs.dittofeed.com/deployment/self-hosted/docker-compose.md","status":"documented","summary":"The official Docker guide links the lite Compose stack and documents replacing default credentials, secrets and dashboard URLs. It includes PostgreSQL, ClickHouse and workflow services; the vendor also publishes a Helm chart. Choose a compatible pinned release and configure storage, TLS, authentication and backups; Enterprise uses a separately entitled image.","supportingSources":[{"title":"Official Kubernetes/Helm recipe","url":"https://docs.dittofeed.com/deployment/self-hosted/kubernetes.md"}]},"licensePricing":{"reviewed":"2026-11-19","scope":"Dittofeed; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://raw.githubusercontent.com/dittofeed/dittofeed/main/LICENSE","status":"documented","summary":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"sso":{"availability":"edition-dependent","reviewed":"2026-11-20","scope":"Self-hosted Enterprise OIDC versus community/lite authentication; detailed mode restrictions override the general overview","source":"https://docs.dittofeed.com/deployment/self-hosted/auth-modes/multi-tenant.md","status":"documented","summary":"OIDC-based multi-tenant authentication is documented, but the detailed guide restricts that mode to dittofeed-ee and Dittofeed Cloud. The community lite deployment instead offers a shared-password single-tenant mode. Obtain the Enterprise image/entitlement and configure provider claims and workspace access; anonymous demo mode is unsuitable for production.","supportingSources":[{"title":"Authentication-mode overview","url":"https://docs.dittofeed.com/deployment/self-hosted/auth-modes.md"}]}},"id":"dittofeed","infrastructure":["servers"],"infrastructureNotes":"Dittofeed application, PostgreSQL, ClickHouse and supporting services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://docs.dittofeed.com/deployment/self-hosted/render.md","https://railway.com/deploy/dittofeed-2","https://www.hostinger.com/applications/dittofeed"],"install":"Application platform deployment; Docker / Compose","installMethods":["platform-template","docker"],"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://raw.githubusercontent.com/dittofeed/dittofeed/main/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Dittofeed","notes":"Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.","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":"\u003e ## Documentation Index\n\u003e Fetch the complete documentation index at: https://docs.dittofeed.com/llms.txt\n\u003e Use this fil","url":"https://docs.dittofeed.com/deployment/self-hosted/render.md"},{"title":"Railway","url":"https://railway.com/deploy/dittofeed-2"},{"title":"Hostinger","url":"https://www.hostinger.com/applications/dittofeed"},{"title":"Render Guide","url":"https://docs.dittofeed.com/deployment/self-hosted/render"},{"title":"GitHub LICENSE (MIT)","url":"https://raw.githubusercontent.com/dittofeed/dittofeed/main/LICENSE"},{"title":"GitHub Releases","url":"https://github.com/dittofeed/dittofeed/releases"}],"url":"https://launchinyourcloud.com/directory/dittofeed/","website":"https://dittofeed.com/"},{"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":"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":"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":"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/"},{"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":"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 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/"}],"relatedQuestions":[{"id":"apps-on-platforms","json":"https://launchinyourcloud.com/api/v1/questions/apps-on-platforms.json","markdown":"https://launchinyourcloud.com/questions/apps-on-platforms/index.md","question":"What apps can I deploy on Railway or Render?","url":"https://launchinyourcloud.com/questions/apps-on-platforms/"}],"schemaVersion":1,"url":"https://launchinyourcloud.com/clouds/render/"}