
# Internal tools on Google Cloud

Compare documented Internal tools deployments on Google Cloud, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/gcp/internal-tools/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Google Cloud project
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects (checked 2026-11-20).
- Network: VPC network
- Identity and access: IAM policies and service accounts
- Installation guidance: Terraform, optionally using Infrastructure Manager for resource provisioning; deploy the application separately.
- Guidance source: https://docs.cloud.google.com/infrastructure-manager/docs/overview
- Guidance reviewed: 2026-11-10


### Private offers

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

### Private connectivity

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

### External workload access

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

### Regulated environments

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

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

6 listings.


## Appsmith Self-Hosted

Build internal applications with visual widgets, queries and JavaScript on customer-operated infrastructure.

- Listing: https://launchinyourcloud.com/directory/appsmith/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache-2.0 Community core; commercial edition and plan-dependent features
- Licensing model: open-source
- Installation: Docker Compose or Kubernetes; documented cloud VM/managed-container installation guides
- Architecture: Customer-operated application and supporting databases/cache; vendor licensing/template endpoint
- Operations: Customer manages deployment, persistent databases, backups, networking and upgrades; confirm edition-specific vendor connectivity.
- Product website: https://www.appsmith.com/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-17

### Scope and qualifications

Community and commercial images differ. Documentation requires outbound HTTPS to cs.appsmith.com for self-hosted license/template services and describes separate air-gapped arrangements. Official setup guides name AWS, Azure and Google Cloud. Fargate and Cloud Run are long-running container hosting options, not evidence that the entire stack is function-based. Appsmith v2.7.0 fixes app and datasource authorization issues, extends restricted-host enforcement to S3-compatible and DynamoDB sources, and updates vulnerable dependencies.

The broad self-hosted listing spans Apache-2.0 Community code and commercially licensed Enterprise functionality requiring an enterprise key. Match the selected image and plan to these terms.

Classified as servers under this directory convention: the application is a long-running container/service. Official Fargate/Cloud Run paths reduce host management but retain application, database and persistence operations. For Helm upgrades, partial probe overrides now inherit new 10-second period and 5-second timeout defaults; invalid probe values fail installation or upgrade. Review custom probe settings before rollout.


Cloud evidence scope: Documented customer-operated deployment guides for AWS, Azure and Google Cloud

### Category fit

- internal-tools: Low-code development of dashboards, admin panels and internal apps connected to databases/APIs; not a turnkey business application.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.appsmith.com/getting-started/setup/installation-guides (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.appsmith.com/getting-started/setup/installation-guides (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.appsmith.com/getting-started/setup/installation-guides (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.appsmith.com/getting-started/setup/installation-guides/digitalocean (checked 2026-11-12). 


### Cloud deployment evidence

- Appsmith provider-specific installation index (aws, azure, gcp): https://docs.appsmith.com/getting-started/setup/installation-guides
  The vendor documents AWS AMI and ECS, Azure Container Instances and Google Cloud Run installation of the application. These are self-hosted installations, with edition-specific licensing and vendor connectivity requirements described separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Appsmith on a customer DigitalOcean Droplet (digitalocean): https://docs.appsmith.com/getting-started/setup/installation-guides/digitalocean
  The vendor walks through choosing the Appsmith Marketplace image, creating a Droplet in the customer account and registering its application administrator. Free and licensed features have separate entitlements; configure domain, TLS, email and recovery for production.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosted Docker installation: https://docs.appsmith.com/getting-started/setup/installation-guides/docker

- Deployment architecture and vendor connectivity: https://docs.appsmith.com/getting-started/setup/deployment-architecture

- Provider-specific installation guides: https://docs.appsmith.com/getting-started/setup/installation-guides

- Community project and license: https://github.com/appsmithorg/appsmith

- Licensing and edition terms: https://www.appsmith.com/terms-and-conditions

- Appsmith on a customer DigitalOcean Droplet: https://docs.appsmith.com/getting-started/setup/installation-guides/digitalocean

- Appsmith v2.7.0 security and upgrade notes: https://github.com/appsmithorg/appsmith/releases/tag/v2.7.0

### Licensing sources

- https://www.appsmith.com/terms-and-conditions

- https://github.com/appsmithorg/appsmith

- https://docs.appsmith.com/getting-started/setup/installation-guides/docker

### Infrastructure sources

- https://docs.appsmith.com/getting-started/setup/installation-guides/docker

- https://github.com/appsmithorg/appsmith/releases/tag/v2.7.0


### Buyer diligence


Research coverage: 7/12 fields (58%); 7 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The self-hosting authentication guides document SAML and OIDC SSO as Enterprise features. SAML can migrate from the bundled Keycloak broker to native server handling starting in v2.7; configure the provider and migration for the selected release. Scope: Self-hosted Enterprise user login; Google/GitHub login and enterprise federation are different options. Source: https://docs.appsmith.com/getting-started/setup/instance-configuration/authentication/security-assertion-markup-language-saml (reviewed 2026-11-20). Supporting source: Enterprise OIDC SSO — https://docs.appsmith.com/getting-started/setup/instance-configuration/authentication/openid-connect-oidc.

- SCIM provisioning: Edition-dependent. Self-hosted Enterprise documents SCIM v2 user and group provisioning. The identity provider must reach the instance SCIM endpoint over HTTPS. Scope: Self-hosted Enterprise; identity-provider and network requirements apply. Source: https://docs.appsmith.com/advanced-concepts/user-provisioning-group-sync (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Edition-dependent. A separate Airgapped Edition is obtained through sales. Offline operation limits templates, SaaS integrations and third-party libraries; disabling telemetry alone is not air-gapped deployment. Scope: Separately arranged Airgapped Edition, not every Appsmith installation. Source: https://docs.appsmith.com/getting-started/setup/installation-guides/air-gapped (reviewed 2026-11-14).

- Deployment artifact / IaC: Documented. The official Docker guide supplies run and Compose configurations using an Appsmith image and persistent /appsmith-stacks storage. Choose the Community or commercial image deliberately, pin the intended release and configure the host, secrets, HTTPS and backups. Scope: Official all-in-one installation example; choose the edition and a compatible pinned container release. Source: https://docs.appsmith.com/getting-started/setup/installation-guides/docker (reviewed 2026-11-20).

- Minimum footprint / sizing: Documented. The all-in-one Docker installation guidance calls for at least 8 GB host RAM because supporting services run inside the container. Externalized services require a different capacity plan. Scope: All-in-one Docker host; not a universal per-application requirement. Source: https://docs.appsmith.com/getting-started/setup/installation-guides/docker (reviewed 2026-11-14).

- License pricing: Documented. The v2.7.0 core is Apache-2.0. The vendor distinguishes free Community from paid Business and Enterprise plans; SAML/OIDC, provisioning and air-gapped add-ons have separate commercial entitlements. Confirm self-hosted feature, user and support terms with the vendor. Scope: Versioned core versus commercially licensed features; displayed Cloud limits and prices are not applied as a self-hosted quote. Source: https://github.com/appsmithorg/appsmith/blob/v2.7.0/LICENSE (reviewed 2026-11-20). Supporting source: Edition and feature pricing — https://www.appsmith.com/pricing.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The Airgapped Edition documentation specifies quarterly packaged updates transferred manually into the isolated environment. This is separate from the normal upstream release stream. Scope: Airgapped Edition update policy; not the cadence of all Appsmith editions. Source: https://docs.appsmith.com/getting-started/setup/installation-guides/air-gapped (reviewed 2026-11-14).




### Security and lifecycle reviews

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

- Appsmith 2.7.0 access and datasource hardening (security-advisory): The release adds missing app-access checks and extends restricted-host rules to S3-compatible and DynamoDB datasources. Scope: Upstream Appsmith 2.7.0 release; Airgapped Edition packaging follows its separate update policy. Conditions: Applicability depends on custom JS-library access, fork permissions and configured datasource endpoints; no complete affected range is asserted. Action: Review the security changes and Helm probe defaults before applying a compatible update. Source: https://github.com/appsmithorg/appsmith/releases/tag/v2.7.0; reviewed 2026-11-17.




## Decisions Self-Hosted

Commercial rules and workflow platform with provider-specific container deployments.

- Listing: https://launchinyourcloud.com/directory/decisions-platform/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Docker / Compose; Kubernetes manifests
- Architecture: Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- workflow-automation: Commercial rules and workflow platform with provider-specific container deployments.

- internal-tools: Commercial rules and workflow platform with provider-specific container deployments.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.decisions.com/docs/deploying-containers-on-azure-1.md (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://documentation.decisions.com/docs/deploying-containers-on-gcp-1.md (checked 2026-11-19). 


### Cloud deployment evidence

- AWS ECS Deploy (aws): https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md
  Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Deploy (azure): https://documentation.decisions.com/docs/deploying-containers-on-azure-1.md
  Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Deploy (gcp): https://documentation.decisions.com/docs/deploying-containers-on-gcp-1.md
  Licensed Decisions application containers and required database/cache services on AWS, Azure or GCP. The platform can implement lending workflows, but deployment of the platform does not install a complete loan-origination product. Container licences, application versions and cloud infrastructure are separate scopes.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS ECS Deploy: https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md

- Azure Deploy: https://documentation.decisions.com/docs/deploying-containers-on-azure-1.md

- GCP Deploy: https://documentation.decisions.com/docs/deploying-containers-on-gcp-1.md

- AWS EKS Deploy: https://documentation.decisions.com/docs/deploying-an-aws-kubernetes-cluster.md

- Azure AKS Deploy: https://documentation.decisions.com/docs/deploying-azure-kubernetes-services-aks.md

- Financial Services: https://decisions.com/solutions/industry/financial-services

- Terms of Use: https://decisions.com/terms-of-use

- Container Licensing: https://documentation.decisions.com/docs/licensing-a-container.md

- v10.4.x Release Notes: https://documentation.decisions.com/v99/docs/version-104x-release-notes.md

### Licensing sources

- https://decisions.com/terms-of-use

- https://documentation.decisions.com/docs/licensing-a-container.md

### Infrastructure sources

- https://documentation.decisions.com/docs/deploying-containers-on-aws-1.md

- https://documentation.decisions.com/docs/deploying-containers-on-azure-1.md

- https://documentation.decisions.com/docs/deploying-containers-on-gcp-1.md


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The vendor documents SAML login through an installed identity-provider module, certificate and IdP settings, with accounts updated before enforcement and at least one working admin SSO account. It warns that Active Directory Sync cannot run simultaneously with SAML/OpenID SSO modules. Scope: Self-hosted application user SSO; module/release and IdP configuration required. Source: https://documentation.decisions.com/docs/saml (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The installation guide provides the v10.x installer and supported database setup. The ECS guide documents task definitions using the vendor container image, environment variables and persistent file storage; it is a console recipe rather than a supplied Terraform/CloudFormation stack. Pin a compatible released image rather than copying latest. Scope: Licensed self-hosted installer/container workflow; application, database and HA setup are separate. Source: https://documentation.decisions.com/docs/deploying-containers-on-aws-1 (reviewed 2026-11-20). Supporting source: v10 installation guide and release download — https://documentation.decisions.com/version-10/docs/installation-guide.

- Minimum footprint / sizing: Documented. The installation requirements list an AWS production example using t3.xlarge (4 vCPU, 16 GB RAM) and 100 GB storage. Database requirements are separate, and enterprise/HA topology and workload can require larger or multiple servers. This server example does not include 1 TB of application data. Scope: General self-hosted application-server guidance; not a cost estimate or validated reference-workload HA design. Source: https://documentation.decisions.com/docs/installation-requirements (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Decisions Self-Hosted; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://decisions.com/terms-of-use (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Mendix on Kubernetes

Commercial low-code application runtime operated in customer Kubernetes infrastructure.

- Listing: https://launchinyourcloud.com/directory/mendix-private-cloud/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, stackit
- Operating model: Customer-operated · vendor control plane
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Mendix Operator, application runtimes, database and file storage on the documented managed-Kubernetes providers.
- Operations: Customer operates the application runtime; the documented connected deployment also depends on the Mendix management portal and its configured access.
- Product website: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The selected connected deployment registers the cluster with the external Mendix Portal control plane. A customer cluster is not a packaged insurance-claims application. Runtime licences, operator versions and application versions have different lifecycles; standalone modes need their own review.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Mendix Operator, application runtimes, database and file storage on the documented managed-Kubernetes providers. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- internal-tools: Commercial low-code application runtime operated in customer Kubernetes infrastructure.

- workflow-automation: Commercial low-code application runtime operated in customer Kubernetes infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

- stackit: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

Operating responsibility: In the selected Connected mode the customer supplies and operates the Kubernetes runtime, database, storage and backups. The Mendix Portal controls deployments through an in-cluster agent. This is not a vendor-operated application service. Source: https://docs.mendix.com/developerportal/deploy/private-cloud/ (checked 2026-11-20).


### Cloud deployment evidence

- Supported Clouds (aws, azure, gcp, stackit): https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/
  Mendix Operator, application runtimes, database and file storage on the documented managed-Kubernetes providers. The selected connected deployment registers the cluster with the external Mendix Portal control plane. A customer cluster is not a packaged insurance-claims application. Runtime licences, operator versions and application versions have different lifecycles; standalone modes need their own review.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Supported Clouds: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/

- Private Cloud Deploy: https://docs.mendix.com/developerportal/deploy/private-cloud-deploy/

- Insurance Claims: https://www.mendix.com/industries/insurance/

- Outside-Cloud Licensing: https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/

- Mendix Legal: https://www.mendix.com/legal/

- Mendix on K8s RN: https://docs.mendix.com/releasenotes/developer-portal/mendix-for-private-cloud/

### Licensing sources

- https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/

- https://www.mendix.com/legal/

### Infrastructure sources

- https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Mendix documents SAML and OIDC modules for end-users of deployed apps, with module/runtime compatibility and app-level configuration. The SAML guide explicitly addresses apps outside Mendix Cloud and requires external file storage. This is separate from developer-portal or Private Mendix Platform login. Scope: Application end-user federation on a compatible Mendix runtime; verify module dependencies and app configuration. Source: https://docs.mendix.com/appstore/modules/saml/ (reviewed 2026-11-20). Supporting source: OIDC module and supported runtime versions — https://docs.mendix.com/appstore/modules/oidc/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Kubernetes deployment guides register a cluster/namespace, install the Mendix Operator and deploy app environments from the Mendix Portal or Kubernetes custom resources. Database, file storage, registry, network access and licensed runtime configuration remain deployment inputs. Scope: Mendix on Kubernetes deployment workflow; operator, runtime and application releases are separate. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-deploy/ (reviewed 2026-11-20). Supporting source: Cluster and operator setup — https://docs.mendix.com/developerportal/deploy/private-cloud-cluster/.

- Minimum footprint / sizing: Documented. The supported-provider guide requires at least 2 CPU cores, 2 GB memory and 3 GB ephemeral storage available on a node for one simple app, excluding Kubernetes core components. Production databases, file storage, image building and multiple replicas need additional sizing; experimental ARM64 support is limited to non-production Connected Mode. Scope: One simple app baseline, excluding cluster overhead and HA/1-TB workload capacity. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Mendix on Kubernetes; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## NocoDB Self-Hosted

Spreadsheet-style database platform with linked records, views and optional licensed internal app interfaces.

- Listing: https://launchinyourcloud.com/directory/nocodb/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, digitalocean, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Current upstream master/develop code uses the Sustainable Use License: internal business or noncommercial/personal use is permitted, with distribution and other restrictions. Paid self-hosted features require a separate license.
- Licensing model: source-available
- Installation: Run the official Docker image with persistent storage or use its documented Compose-based server installer.
- Architecture: Customer-operated application with persistent metadata/database services and optional connected databases
- Operations: Customer manages app services, databases, access rules, secrets, backups, upgrades and any paid license.
- Product website: https://nocodb.com/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The upstream license changed in January 2026; this is classified as source-available. Internal-tool Interfaces are a licensed feature, while AI apps have separate availability. Connected databases, AI providers and integrations can send data outside the account. NocoDB 2026.10.2 restricts shared views and dashboards to displayed fields, limits forms to their own fields, prevents Editors from reading workflow-step secrets and caps workflow webhook bodies at 1 MB. It also restores NC_SSO=oidc, requires unchanged RelayState for SAML IdP-initiated login and repairs air-gapped license refresh. Retest public shares, forms, workflow permissions and SSO after upgrading.

Current upstream master/develop code uses the Sustainable Use License: internal business or noncommercial/personal use is permitted, with distribution and other restrictions. Paid self-hosted features require a separate license. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Official Docker images run the NocoDB application on a customer-controlled host with persistent storage and a configured SQLite or PostgreSQL metadata backend; the server installer adds supporting services.


### Category fit

- no-code-databases: Spreadsheet-style database interface with linked records, views, forms and programmatic access.

- internal-tools: Interfaces build focused internal pages, dashboards and approval views on base data. The reviewed release limits Interfaces to licensed self-hosted Business plans and above.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 

- digitalocean: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 


### Cloud deployment evidence

- NocoDB community cloud installation methods (aws, gcp, digitalocean, railway): https://nocodb.com/docs/self-hosting/installation/community-methods
  The upstream community-methods guide includes full application deployment on DigitalOcean App Platform and a Railway template alongside AWS ECS/Fargate and Google Cloud Run. NocoDB explicitly does not maintain these methods or give them first-class installation support. Review image licensing, database configuration, persistence and production requirements.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

NocoDB's published adopter list names Accenture, Bosch and American Express. Its official GitHub discussion records actual exchanges between named users and maintainer o1lab about the 2026 license change, including critical feedback, while the release history shows continuing maintenance. These are adoption and participation signals; they do not establish which edition or hosting model any named organization uses.

Reviewed 2026-11-10.

- Vendor-published named organization adoption claims: https://nocodb.com/

- Observed user/maintainer discussion of the license change: https://github.com/nocodb/nocodb/discussions/12891

- Current maintenance releases: https://github.com/nocodb/nocodb/releases

### Sources

- Upstream project and capabilities: https://github.com/nocodb/nocodb

- Current upstream license: https://raw.githubusercontent.com/nocodb/nocodb/develop/LICENSE.md

- Internal Interfaces and self-hosted plan availability: https://nocodb.com/docs/changelog/2026.08.0

- Product functionality: https://nocodb.com/docs/product

- NocoDB 2026.10.2 release: https://github.com/nocodb/nocodb/releases/tag/2026.10.2

### Licensing sources

- https://raw.githubusercontent.com/nocodb/nocodb/develop/LICENSE.md

### Infrastructure sources

- https://github.com/nocodb/nocodb


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The authentication guide documents SAML and OIDC providers and explicitly describes on-premises SSO configuration without Cloud DNS-domain verification. SSO is associated with paid self-hosted plans; optional password login alongside SSO has a separate on-premises setting. Scope: Paid self-hosted user federation; verify the selected Business/Scale/Enterprise entitlement rather than assuming Community includes SSO. Source: https://nocodb.com/docs/product-docs/account-settings/authentication (reviewed 2026-11-20). Supporting source: Self-hosted plans and licensing — https://nocodb.com/docs/self-hosting.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. NocoDB 2026.10.2 prevents shared views and dashboards from returning hidden fields, prevents forms from writing unrelated fields, hides workflow secrets from Editors and limits webhook request bodies. Upgrade and retest shares, forms, workflows and SSO. Scope: NocoDB self-hosted access controls documented in the 2026.10.2 release; no broader affected-version range was published. Source: https://github.com/nocodb/nocodb/releases/tag/2026.10.2 (reviewed 2026-11-19).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream repository publishes an installer that generates a PostgreSQL/Redis/Traefik Compose stack. Re-running can upgrade the application; inspect the script, preserve secrets/data and control version changes. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/nocodb/nocodb (reviewed 2026-11-14). Deployment artifact: https://github.com/nocodb/nocodb/blob/develop/docker-compose/1_Auto_Upstall/noco.sh. Artifact reference: develop installer (moving).

- Minimum footprint / sizing: Documented. The self-hosting guide lists a minimum of 2 vCPU, 2 GB RAM and 10 GB disk, and a production recommendation of 4 vCPU, 8 GB RAM and 50 GB or more disk. Database, attachments, workload and replication require additional sizing. Scope: Single-server starting guidance; not a complete HA design or 1-TB storage allowance. Source: https://nocodb.com/docs/self-hosting (reviewed 2026-11-20).

- License pricing: Documented. The 2026.10.2 licence identifies the Sustainable Use License for the master/develop code: use and modification are limited to internal business, personal or non-commercial purposes, with restricted distribution. Commercial/self-hosted paid features require separate entitlements; this is not an unrestricted OSI open-source licence. Scope: Reviewed source-available terms; confirm commercial use and paid features for the intended deployment. Source: https://github.com/nocodb/nocodb/blob/2026.10.2/LICENSE.md (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. NocoDB 2026.10.2 was published November 19, 2026. It fixes shared-view, dashboard, form and workflow authorization boundaries, restores NC_SSO=oidc, changes SAML IdP-initiated RelayState handling and repairs air-gapped license refresh. Scope: Upstream NocoDB self-hosted release; paid-feature and license behavior remains edition-dependent. Source: https://github.com/nocodb/nocodb/releases/tag/2026.10.2 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/nocodb/nocodb/releases/tag/2026.10.1.




### Security and lifecycle reviews

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

- NocoDB 2026.10.2 access-control hardening (security-advisory): NocoDB 2026.10.2 prevents hidden-field disclosure in shares, unrelated form writes and workflow-secret disclosure to Editors, and caps webhook request bodies. Scope: NocoDB self-hosted behavior documented in the 2026.10.2 release; no universal affected-version range was published. Conditions: Public shares or dashboards, forms, Editor access to workflows, configured-key webhooks, OIDC or SAML determine exposure and upgrade impact. Action: Upgrade to 2026.10.2 or later and retest shares, forms, workflows, OIDC and SAML IdP-initiated login. Source: https://github.com/nocodb/nocodb/releases/tag/2026.10.2; reviewed 2026-11-19.




## Retool Self-Hosted, Self-Managed

Commercial single-tenant Retool deployment installed and operated on customer-managed Kubernetes infrastructure.

- Listing: https://launchinyourcloud.com/directory/retool-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Enterprise subscription with custom annual pricing and a self-hosted license key.
- Licensing model: commercial-only
- Installation: Official Terraform blueprints for Amazon EKS, Azure AKS or Google GKE, or Helm into an existing supported Kubernetes cluster
- Architecture: Distributed Retool containers on Kubernetes with external PostgreSQL, object storage, ingress and optional Temporal services
- Operations: Customer manages Kubernetes, PostgreSQL, object storage, DNS, TLS, secrets, networking, backups, capacity, upgrades and the Retool license.
- Product website: https://retool.com/self-hosted
- Source review: 2026-11-16; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers self-hosted, self-managed Retool, not Retool-managed hosting. Kubernetes with Helm is the supported production path for Retool 4.0 and later; Docker Compose is non-production only. EKS must use EC2-backed workers rather than Fargate for the agent sandbox. The standard deployment requires outbound access for license checks, authentication and usage reporting; Enterprise pricing separately offers air-gapped deployment, requiring the appropriate license and vendor-provided procedure. Workflows and Agents require Temporal, and Retool recommends its managed Temporal Cloud service unless the customer operates a compatible cluster.

Current pricing places self-hosted and air-gapped deployments in Enterprise with custom annual pricing. Product-specific subscription and license-key terms apply; cloud per-seat prices do not price this deployment.

Production deployments run persistent Retool services on customer EKS, AKS or GKE infrastructure with external database and object-storage dependencies.


### Category fit

- internal-tools: Provides a self-hosted low-code platform for building internal applications and operational interfaces.

- workflow-automation: Runs Retool Workflows and related automation services inside the customer-operated deployment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes (checked 2026-11-16). 


### Cloud deployment evidence

- Official Retool Terraform and Helm deployment paths (aws, azure, gcp): https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes
  Retool provides production Terraform blueprints for AWS, Azure and Google Cloud and explicitly targets Amazon EKS, Azure AKS and Google GKE. Customers may alternatively deploy with Helm into an existing supported cluster.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Self-hosted, self-managed Retool: https://docs.retool.com/self-hosted/self-managed

- Self-managed Retool quickstart: https://docs.retool.com/self-hosted/self-managed/quickstart

- Retool Kubernetes deployment tutorials: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes

- Deploy Retool on Kubernetes with Helm: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes/kubernetes-helm

- Retool product-specific terms: https://docs.retool.com/legal/product-specific-terms

- Enterprise deployment options and pricing: https://retool.com/pricing

### Licensing sources

- https://docs.retool.com/legal/product-specific-terms

- https://retool.com/pricing

### Infrastructure sources

- https://docs.retool.com/self-hosted/self-managed/quickstart

- https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes/kubernetes-helm


### Buyer diligence


Research coverage: 11/12 fields (92%); 10 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Edition-dependent. Retool’s AWS Marketplace listing explicitly describes self-hosted and Retool-managed AWS environments, with private-contract procurement. AWS classifies delivery as a SaaS contract; confirm the self-managed Enterprise entitlement rather than assuming an AMI installer or included infrastructure. Retool also announces Google Cloud private-offer purchasing with the same deployment options; the exact offer and agreement must match the self-hosted subscription. Scope: Vendor-published AWS offer; procurement and application hosting are distinct. Source: https://aws.amazon.com/marketplace/pp/prodview-cqgbgmrm63i4y (reviewed 2026-11-16). Supporting source: Google Cloud Marketplace procurement and commitment conditions — https://retool.com/blog/retool-google-cloud-marketplace-announcement. Offer prodview-cqgbgmrm63i4y: Retool; SaaS contract/private offer; select self-managed Enterprise entitlement; https://aws.amazon.com/marketplace/pp/prodview-cqgbgmrm63i4y.

- Cloud commitment eligibility: Edition-dependent. Retool states that eligible Google Cloud Marketplace purchases can draw down a Google Cloud commitment and that Marketplace procurement preserves deployment options. Purchases use a private offer; the amount credited depends on the buyer’s Google agreement and accepted offer. This is not a blanket credit promise for all purchases or providers. Scope: Google Cloud private-offer procurement; buyer agreement controls eligibility. Source: https://retool.com/blog/retool-google-cloud-marketplace-announcement (reviewed 2026-11-16).

- Single sign-on: Edition-dependent. Retool documents SAML and OIDC providers, including Entra ID and Okta, plus identity-provider group/role mapping. Apply the self-hosted instance configuration and subscription entitlements; Google Group sync is a separate integration. Scope: Retool organization SSO; protocol support does not establish every plan entitlement; current pricing includes this capability in Enterprise. Source: https://docs.retool.com/sso/quickstart (reviewed 2026-11-16). Supporting source: Enterprise entitlement matrix — https://retool.com/pricing.

- SCIM provisioning: Edition-dependent. SCIM provisioning is documented for self-hosted versions 2.32.1+, with bearer-token authentication and /api/scim/v2/* endpoints. The guide covers Okta and Entra ID; the identity provider must reach the instance through its firewall. Scope: Self-hosted technical configuration; selected subscription governs commercial entitlement; current pricing includes this capability in Enterprise. Source: https://docs.retool.com/sso/guides/scim-user-provisioning (reviewed 2026-11-16). Supporting source: Enterprise entitlement matrix — https://retool.com/pricing.

- Compliance attestations: Sources checked — unresolved. Retool’s legal security practices describe independent SOC 2/ISO audits and direct readers to its Trust Center. Those public practices alone do not establish report dates or coverage of the customer-operated self-managed environment. Scope: Vendor controls and audit availability; customer-environment scope/period needs the actual report. Source: https://docs.retool.com/legal/security (reviewed 2026-11-16).

- Security controls: Documented. The code-executor uses nsjail, which needs privileged container access. The documented fallback runs code without sandboxing if that access is unavailable. Review this specific container’s isolation separately from agent and JavaScript executors. Scope: Self-managed code-executor container; not an attestation for every Retool service. Source: https://docs.retool.com/self-hosted/self-managed/quickstart (reviewed 2026-11-16).

- Air-gapped operation: Edition-dependent. Retool’s current Enterprise pricing explicitly offers air-gapped deployments. The standard self-managed guide still requires outbound license/authentication/usage services, so obtain the separate air-gap license, artifacts and procedure from Retool rather than applying the standard online setup unchanged. Scope: Enterprise commercial air-gap option is confirmed; deployment-specific procedure and integration dependencies require account-team coordination. Source: https://retool.com/pricing (reviewed 2026-11-16). Supporting source: Standard deployment outbound requirements — https://docs.retool.com/self-hosted/self-managed/quickstart.

- Deployment artifact / IaC: Documented. Retool provides Terraform blueprints that provision EKS, AKS or GKE and deploy Helm. Kubernetes with Helm is the production path for 4.0 and later; Compose is for development and proofs of concept. AWS agent sandboxes require EC2-backed EKS workers rather than Fargate. Scope: Self-managed Retool 4.0+; select matching chart and application versions. Source: https://docs.retool.com/self-hosted/self-managed/quickstart (reviewed 2026-11-16). Deployment artifact: https://github.com/tryretool/terraform-retool-self-hosted-blueprints/tree/main. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The current Helm guide calls for at least 32 CPU cores and 64 GiB available across the workload-node pool. Agent sandbox pods scale with builder sessions; the external PostgreSQL database, storage and peak autoscaling capacity must also be planned. Scope: Current production Helm stack with app-builder/agent services; not the older Compose baseline. Source: https://docs.retool.com/self-hosted/self-managed/tutorials/kubernetes/kubernetes-helm (reviewed 2026-11-16).

- License pricing: Documented. Current pricing places self-hosted and air-gapped deployment in Enterprise, with custom annual pricing. Its published cloud per-seat prices do not price a self-hosted Enterprise installation. The subscription and license-key terms govern use. Scope: Self-hosted Enterprise procurement; excludes cloud infrastructure and operating labor. Source: https://retool.com/pricing (reviewed 2026-11-16). Supporting source: Self-hosted legal terms — https://docs.retool.com/legal/product-specific-terms.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed vendor release is 4.86.0, published 2026-11-11. This is a dated, scoped snapshot; it does not establish compatibility with another chart, cloud package or commercial edition. Retool documents quarterly stable releases and six months of support for each stable version. Scope: Self-hosted stable-channel release, separate from cloud/edge versions; source supplies a publication day, not a timestamp. Source: https://docs.retool.com/releases/stable/version/4.86 (reviewed 2026-11-16).







## ToolJet Self-Hosted

Build internal tools and business applications with a customer-hosted app builder.

- Listing: https://launchinyourcloud.com/directory/tooljet/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 open-source foundation; commercial self-hosted editions/plans
- Licensing model: open-source
- Installation: Docker Compose or Kubernetes; optional Terraform provisioning for AWS/Azure/GCP VMs
- Architecture: Customer-operated app services, PostgreSQL and optional cache
- Operations: Customer operates application, database, credentials, backups and upgrades; vendor license activation applies to paid features.
- Product website: https://www.tooljet.com/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The self-hosted Basic tier and paid editions have different limits and governance features. Official Docker documentation includes customer VM provisioning paths for AWS, Azure and Google Cloud. AI features require additional outbound vendor endpoints; self-hosting does not imply air-gapped operation. ToolJet v3.21.96-lts lets administrators revoke any workspace personal access token, applies configured rate limits to workflow webhooks, and updates vulnerable dependencies. Self-hosted operators should use v3.21.96-lts or later.

The self-hosted product combines an AGPL-3.0 open-source foundation with commercially licensed/gated self-hosted Enterprise capabilities; Basic/free plan access does not include all premium features.

Reviewed topology uses long-lived application containers on a VM or Kubernetes cluster with PostgreSQL. Classified servers rather than function-based serverless.


Cloud evidence scope: Documented customer-operated deployment guides for AWS, Azure and Google Cloud

### Category fit

- internal-tools: Visual internal app development with database/API connections, dashboards and workflows; access and governance depend on edition.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.tooljet.com/docs/setup/docker/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.tooljet.com/docs/setup/docker/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.tooljet.com/docs/setup/docker/ (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.tooljet.com/docs/setup/digitalocean/ (checked 2026-11-12). 


### Cloud deployment evidence

- ToolJet application deployment on cloud VMs (aws, azure, gcp): https://docs.tooljet.com/docs/setup/docker/
  The current vendor Docker guide links optional Terraform VM provisioning on AWS, Azure and Google Cloud, followed by ToolJet server deployment. Configure the application databases, image edition and production settings separately; AI features can use vendor endpoints.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- ToolJet on a customer DigitalOcean Droplet (digitalocean): https://docs.tooljet.com/docs/setup/digitalocean/
  The vendor guide creates an Ubuntu Droplet, configures its firewall and installs Docker and Compose, then follows the ToolJet Docker deployment. The current instructions include LTS and enterprise image guidance; license and AI endpoint requirements remain edition-dependent.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Server Docker Compose deployment and cloud VM provisioning: https://docs.tooljet.com/docs/setup/docker/

- Self-hosted license types and limits: https://docs.tooljet.com/docs/tj-setup/licensing/self-hosted/

- System requirements: https://docs.tooljet.com/docs/setup/system-requirements/

- Project functionality and license: https://github.com/ToolJet/ToolJet

- ToolJet on a customer DigitalOcean Droplet: https://docs.tooljet.com/docs/setup/digitalocean/

- ToolJet v3.21.96 LTS security hardening: https://github.com/ToolJet/ToolJet/releases/tag/v3.21.96-lts

### Licensing sources

- https://github.com/ToolJet/ToolJet

- https://docs.tooljet.com/docs/tj-setup/licensing/self-hosted/

### Infrastructure sources

- https://docs.tooljet.com/docs/setup/docker/


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. Self-hosted workspace login documents Google, GitHub, OIDC, LDAP and SAML. The licensing guide explicitly says OpenID SSO is lost when a paid/trial key expires and the instance reverts to Basic; confirm the selected plan for other identity providers. Scope: Self-hosted login; OpenID entitlement is paid and protocol availability must not imply every provider is included in Basic. Source: https://docs.tooljet.com/docs/tj-setup/licensing/self-hosted/ (reviewed 2026-11-20). Supporting source: Self-hosted workspace login — https://docs.tooljet.com/docs/user-management/authentication/self-hosted/workspace-login/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The server guide documents Compose with PostgreSQL and links optional VM Terraform examples. Multi-instance workers need external Redis; ToolJet AI also requires separately documented outbound endpoints. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.tooljet.com/docs/setup/docker/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The self-hosted requirements specify an x86 VM with 1 vCPU, 4 GB RAM and at least 8 GiB disk. PostgreSQL is separately sized at 2 vCPU, 8 GB RAM and 20 GB disk, and Redis at 1 vCPU, 512 MB RAM and 1 GB disk (1 GB RAM recommended for production). Scope: Application, database and Redis requirements are separate; ARM64 is not supported by the reviewed guide and these are not HA capacity guarantees. Source: https://docs.tooljet.com/docs/setup/system-requirements/ (reviewed 2026-11-20).

- License pricing: Documented. The self-hosted licensing guide distinguishes free Basic, 14-day Trial and paid plans. Since v3.5.20-ee-lts, Basic is limited to 2 builders including the super admin, 50 end users, 2 apps, 2 workflows and 1 workspace. Paid features require a vendor-issued key; confirm a quote for larger deployments. Scope: Current self-hosted Basic/paid licensing; not an unlimited 100-user entitlement or hosted-plan quote. Source: https://docs.tooljet.com/docs/tj-setup/licensing/self-hosted/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- ToolJet LTS security maintenance review (security-advisory): The release fixes dependency findings, extends webhook rate limits and adds administrator token revocation. Scope: ToolJet v3.21.96-lts release review; this is security maintenance, not a named product-wide vulnerability or a cross-branch support claim. Conditions: Configured workflow webhooks, personal access tokens and bundled dependencies determine applicability. Action: Review the selected LTS line and apply its supported patch; validate webhook limits and token administration. Source: https://github.com/ToolJet/ToolJet/releases/tag/v3.21.96-lts; reviewed 2026-11-17.



