NocoDB Self-Hosted
Spreadsheet-style database platform with linked records, views and optional licensed internal app interfaces.
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
NocoDB 2026.10.2 access-control hardening
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.
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.
Primary source · Reviewed 2026-11-19
What lands where
Supplied by
Vendor or project
Run the official Docker image with persistent storage or use its documented Compose-based server installer.
Runs in
Documented customer environment
Customer-operated application with persistent metadata/database services and optional connected databases
- AWS: Customer cloud account
- Google Cloud: Customer cloud account
- DigitalOcean: Customer platform workspace
- Railway: Customer platform workspace
- AWS
- Google Cloud
- DigitalOcean
- Railway
Servers / containers
Operated by
Your team
Customer manages app services, databases, access rules, secrets, backups, upgrades and any paid license.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
NocoDB community cloud installation methods ↗ · Source checked 2026-11-12
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
NocoDB community cloud installation methods ↗ · Source checked 2026-11-12
- DigitalOcean: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
NocoDB community cloud installation methods ↗ · Source checked 2026-11-12
- Railway: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
NocoDB community cloud installation methods ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Run the official Docker image with persistent storage or use its documented Compose-based server installer. |
|---|---|
| Infrastructure | Servers / containers 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. |
| Licensing model | Source Available 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. |
| 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. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
6 of 12 fields researched (50%) · 6 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Edition-dependentEvidence and scope for Single sign-on
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.
Paid self-hosted user federation; verify the selected Business/Scale/Enterprise entitlement rather than assuming Community includes SSO · Source ↗ · Self-hosted plans and licensing ↗ · Reviewed 2026-11-20
Edition-dependent · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
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.
NocoDB self-hosted access controls documented in the 2026.10.2 release; no broader affected-version range was published · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
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.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Deployment artifact ↗ (develop installer (moving)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
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.
Single-server starting guidance; not a complete HA design or 1-TB storage allowance · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
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.
Reviewed source-available terms; confirm commercial use and paid features for the intended deployment · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
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.
Upstream NocoDB self-hosted release; paid-feature and license behavior remains edition-dependent · Source ↗ · Prior reviewed release context ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (6 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
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.
Community & 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.
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.
Compare within No-code databases
- ActivityInfo (Self-Managed Server)Commercial self-managed data collection, relational records and program-reporting platform.
- Azure
- Baserow Self-HostedSelf-hosted no-code database for organizing, relating and collaborating on business data.
- AWS
- Google Cloud
- DigitalOcean
- Railway
- Render
- Heroku
- Grist Self-HostedRelational spreadsheet platform for collaborative business data and configurable operational applications.
- AWS
- Azure
These products address related workflows; read their category-fit notes before comparing scope. See all of No-code databases →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Upstream project and capabilities ↗github.com
- Current upstream license ↗raw.githubusercontent.com
- Internal Interfaces and self-hosted plan availability ↗nocodb.com
- Product functionality ↗nocodb.com
- NocoDB 2026.10.2 release ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- NocoDB community cloud installation methods ↗ · AWS, Google Cloud, DigitalOcean, Railway
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- NocoDB community cloud installation methods ↗ · AWS, Google Cloud, DigitalOcean, Railway
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked