
# No-code databases on AWS

Compare documented No-code databases deployments on AWS, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/aws/no-code-databases/
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: AWS account
- 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.aws.amazon.com/accounts/latest/reference/getting-started.html (checked 2026-11-20).
- Network: VPC
- Identity and access: IAM roles and policies
- Installation guidance: CloudFormation or Terraform; review stack changes and requested IAM permissions.
- Guidance source: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html
- Guidance reviewed: 2026-11-10


### Private offers

AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge.
Source: https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-private-offers-subscribing.html (reviewed 2026-11-14).

### Private connectivity

PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service.
Source: https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html (reviewed 2026-11-14).

### Cross-account operations

Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access.
Source: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html (reviewed 2026-11-14).

### Government environments

AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there.
Source: https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/whatis.html (reviewed 2026-11-14).

The listings below have evidence for Amazon Web Services. Read each cloud evidence note for the applicable package, edition and support qualifications.

3 listings.


## Baserow Self-Hosted

Self-hosted no-code database for organizing, relating and collaborating on business data.

- Listing: https://launchinyourcloud.com/directory/baserow/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, digitalocean, railway, render, heroku
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT-licensed core with paid premium features and subscription terms
- Licensing model: open-source
- Installation: Docker, Docker Compose or official Helm chart
- Architecture: Customer-operated application services with PostgreSQL, Redis and file storage
- Operations: Customer operates the application, database and storage, applies updates and configures backups.
- Product website: https://baserow.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

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.

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.


Cloud evidence scope: Official documentation establishes AWS deployments; other provider compatibility is not inferred.

### Category fit

- no-code-databases: No-code relational tables, views and APIs for collaborative business data; premium capabilities require the applicable license.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation%2Finstall-on-aws (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation/install-with-docker (checked 2026-11-12). 

- digitalocean: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation%2Finstall-on-digital-ocean (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation%2Finstall-on-railway (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation%2Finstall-on-render (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation%2Finstall-on-heroku (checked 2026-11-12). 


### Cloud deployment evidence

- Baserow AWS installation options (aws): https://baserow.io/docs/installation%2Finstall-on-aws
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Baserow Docker image compatibility with Google Cloud Run (gcp): https://baserow.io/docs/installation/install-with-docker
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Baserow on DigitalOcean App Platform (digitalocean): https://baserow.io/docs/installation%2Finstall-on-digital-ocean
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Baserow Railway installation (railway): https://baserow.io/docs/installation%2Finstall-on-railway
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Baserow Render application template (render): https://baserow.io/docs/installation%2Finstall-on-render
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Baserow Heroku application template (heroku): https://baserow.io/docs/installation%2Finstall-on-heroku
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Product and licensing FAQ: https://baserow.io/faq

- Docker installation: https://baserow.io/docs/installation/install-with-docker

- AWS installation paths: https://baserow.io/docs/installation%2Finstall-on-aws

- Licensing and edition terms: https://raw.githubusercontent.com/baserow/baserow/develop/LICENSE

- Licensing and edition terms: https://raw.githubusercontent.com/baserow/baserow/develop/premium/LICENSE

- Licensing and edition terms: https://raw.githubusercontent.com/baserow/baserow/develop/enterprise/LICENSE

- Baserow on DigitalOcean App Platform: https://baserow.io/docs/installation%2Finstall-on-digital-ocean

- Baserow Railway installation: https://baserow.io/docs/installation%2Finstall-on-railway

- Baserow Render application template: https://baserow.io/docs/installation%2Finstall-on-render

- Baserow Heroku application template: https://baserow.io/docs/installation%2Finstall-on-heroku

### Licensing sources

- 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

### Infrastructure sources

- https://baserow.io/docs/installation/install-with-docker

- https://baserow.io/docs/installation%2Finstall-on-aws


### 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. 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. Scope: Self-hosted Advanced/Enterprise authentication. Source: https://baserow.io/user-docs/enable-single-sign-on-sso (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://baserow.io/docs/installation/install-with-docker (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. 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. 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 (reviewed 2026-11-20).

- License pricing: Documented. 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. Scope: Versioned open-source versus paid-edition software rights; excludes hosting and support. Source: https://github.com/baserow/baserow/blob/2.4.3/LICENSE (reviewed 2026-11-20). Supporting source: Premium edition licence — https://github.com/baserow/baserow/blob/2.4.3/premium/LICENSE. Supporting source: Enterprise edition licence — https://github.com/baserow/baserow/blob/2.4.3/enterprise/LICENSE.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: Upstream baserow/baserow release record; commercial editions and deployment packages may differ. Source: https://github.com/baserow/baserow/releases/tag/2.4.3 (reviewed 2026-11-14).







## Grist Self-Hosted

Relational spreadsheet platform for collaborative business data and configurable operational applications.

- Listing: https://launchinyourcloud.com/directory/grist/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for grist-core; Grist Labs sells an edition with additional features under separate terms.
- Licensing model: open-source
- Installation: Run the documented Grist server container and configure persistent storage, authentication and production settings.
- Architecture: Customer-operated Grist web service with document storage and configured authentication/storage services
- Operations: Customer manages authentication, access rules, document and metadata storage, backups, sandboxing and upgrades.
- Product website: https://www.getgrist.com/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The listing covers the self-hosted server and its configured edition. Hosted billing features and commercial additions are not automatically part of grist-core. External widgets, integrations and AI services require separate review. Grist v1.7.22 is the first numbered release whose Docker images include Node.js 22.23.4, fixing CVE-2026-111497 remote code execution through Brotli-compressed responses, removing trust for compromised eMudhra certificate authorities, and updating vulnerable dependencies. Images pulled since October 22 already included these fixes; otherwise upgrade to v1.7.22 or later and refresh the deployed image.

Apache License 2.0 for grist-core; Grist Labs sells an edition with additional features under separate terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated Grist web service with document storage and configured authentication/storage services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- no-code-databases: Relational spreadsheet with linked tables, formulas, record views and access rules.

- internal-tools: Configurable data applications such as a team CRM combine linked tables, custom layouts and record access rules; advanced commercial features are separate.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.getgrist.com/install/grist-builder-edition/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.getgrist.com/install/grist-builder-edition/ (checked 2026-11-12). 


### Cloud deployment evidence

- Grist Builder Edition cloud installation (aws, azure): https://support.getgrist.com/install/grist-builder-edition/
  The project provides its self-hosted Builder Edition VM image through AWS and Azure Marketplace. Review the selected image, edition terms and authentication setup; this is not an assurance that every Marketplace component is under the grist-core license.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The project documents significant code contributions by French government organizations ANCT and DINUM alongside Grist Labs. Its public release history continues through v1.7.22 in October 2026, including a Node.js remote-code-execution fix and dependency security updates.

Reviewed 2026-11-16.

- Named institutional contributors and edition boundaries: https://github.com/gristlabs/grist-core

- Current Grist release history: https://github.com/gristlabs/grist-core/releases

- Grist v1.7.22 security release: https://github.com/gristlabs/grist-core/releases/tag/v1.7.22

### Sources

- Official installation and runtime: https://support.getgrist.com/self-managed/

- Upstream project and capabilities: https://github.com/gristlabs/grist-core

- Current upstream license: https://raw.githubusercontent.com/gristlabs/grist-core/main/LICENSE.txt

- Example internal CRM application: https://support.getgrist.com/lightweight-crm/

- Grist v1.7.22 security release: https://github.com/gristlabs/grist-core/releases/tag/v1.7.22

### Licensing sources

- https://raw.githubusercontent.com/gristlabs/grist-core/main/LICENSE.txt

### Infrastructure sources

- https://support.getgrist.com/self-managed/


### 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. OIDC sign-in is fully supported in the full edition with an activation key. Free activation keys are available only for qualifying users/organizations; configure the issuer, client and callback settings. Scope: Full self-managed Grist with activation; not an unconditional Community entitlement. Source: https://support.getgrist.com/install/oidc/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The self-managed guide documents container deployment, persistent document storage and authentication configuration. Full-edition activation and identity features must be distinguished from Community and the desktop app. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://support.getgrist.com/self-managed/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The self-hosted guide gives a known-good Linux-container configuration of 2 CPUs, 8 GB RAM and 20 GB disk for moderate workloads. Its much smaller template test is per-document evidence, not a host minimum; simultaneous documents and sandboxing affect capacity. HA requires full-edition activation and a separate design. Scope: Moderate-workload container guidance, not a 100-user/1-TB or HA guarantee. Source: https://support.getgrist.com/self-managed/ (reviewed 2026-11-20).

- License pricing: Documented. The v1.7.22 Community core is Apache-2.0. The full self-managed edition is a licensed application enabled by activation key, with additional governance/identity features and support; obtain the applicable full-edition terms rather than treating every feature as included in Community. Scope: Community source versus full self-managed edition; excludes infrastructure and optional services. Source: https://github.com/gristlabs/grist-core/blob/v1.7.22/LICENSE.txt (reviewed 2026-11-20). Supporting source: Self-hosted editions and activation — https://support.getgrist.com/self-managed/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v1.7.22, published 2026-10-29. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream gristlabs/grist-core release record; commercial editions and deployment packages may differ. Source: https://github.com/gristlabs/grist-core/releases/tag/v1.7.22 (reviewed 2026-11-14).







## 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.



