nocodb

Why deploy nocodb on Render?

Deploy NocoDB, an open-source no-code database and spreadsheet interface, on Render with one click. This template provisions a Docker web service running the upstream NocoDB image, a PostgreSQL database for metadata, a Key Value instance for caching and job coordination, and a persistent disk for runtime data and attachments. Database, Key Value, and JWT secret environment variables are generated and wired automatically. After deploying, open the service URL at /dashboard to finish setup. Set NC_SITE_URL to your public URL for email links, webhooks, and OAuth redirects.

Deploy NocoDB, the fastest and easiest way to build databases online, with a single click.

This template runs the real upstream NocoDB Docker image and wires up every dependency for you. No manual configuration of databases, cache, or secrets required.

One deploy provisions:

• A Docker web service running upstream NocoDB.
• A persistent disk at /usr/app/data for runtime data and local attachments.
• A Render PostgreSQL database for NocoDB metadata.
• A Render Key Value instance for Redis-compatible cache and job coordination.
• Generated environment variables for the database, Key Value, and NC_AUTH_JWT_SECRET.

Render reads these resources from render.yaml, so the service, database, cache, secret, and disk come up connected on the first deploy.

• Managed PostgreSQL and Key Value instances instead of self-managed infrastructure.
• Persistent storage that survives restarts and redeploys.
• A generated JWT secret, so you skip manual secret handling.
• A public URL ready for the NocoDB dashboard right after deploy.

Click the Deploy to Render button above and follow the prompts. When the deploy finishes, open the web service URL and visit /dashboard to set up NocoDB.

For production email links, webhooks, OAuth redirects, and other public URL features, set NC_SITE_URL in the Render Dashboard to your public service URL.

Architecture

What you can build

Deploy NocoDB to turn your PostgreSQL database into a collaborative no-code spreadsheet interface. Teams can create tables and views, share bases publicly or privately, and automate workflows with built-in integrations for chat, email, and storage. Build data apps and back them with REST APIs, the NocoDB SDK, and role-based access control.

Key features

• One-Click NocoDB Deploy: Provisions the upstream NocoDB Docker web service on Render from render.yaml with no manual configuration.
• Managed PostgreSQL and Key Value: Includes a Render PostgreSQL database for metadata and a Render Key Value instance for Redis-compatible cache and job coordination.
• Persistent Storage: Mounts a persistent disk at /usr/app/data for NocoDB runtime data and local attachments.
• Pre-Wired Environment Variables: Generates and connects database, Key Value, and NC_AUTH_JWT_SECRET values so the service runs on first deploy.
• No-Code Spreadsheet Interface: Turns a database into grid, gallery, form, Kanban, and calendar views with sorting, filtering, grouping, and rich cell types.
• Sharing and Access Control: Share bases and views publicly, privately, or with password protection, and manage access with fine-grained roles.
• Workflow Automations: Connects chat, email, and storage integrations through the built-in App Store, including Slack, SMTP, and AWS S3.
• Programmatic Access: Exposes REST APIs and the NocoDB SDK with JWT or social auth token authentication.
• GitHub Template Ready: Use the Deploy to Render button directly or create your own copy first with GitHub's Use this template button.

Use cases

• Internal Team Database - Deploy a shared no-code spreadsheet interface for teams to manage projects, inventory, or CRM data backed by PostgreSQL without writing SQL.
• Airtable Self-Hosted Alternative - Run a self-hosted database with grid, gallery, form, Kanban, and calendar views on Render to keep data under your own control and avoid vendor lock-in.
• Backend for No-Code Apps - Use NocoDB's REST APIs and SDK to serve structured data to web and mobile front ends, with JWT authentication handled by the generated NC_AUTH_JWT_SECRET.
• Data Collection Forms - Create shareable form views to gather submissions from customers or team members and store responses directly in your PostgreSQL database.
• Workflow Automation Hub - Connect Slack, Discord, SMTP, AWS SES, S3, and other App Store integrations to trigger notifications and automate data-driven workflows.
• Attachment and File Management - Store local attachments on the persistent disk mounted at /usr/app/data or wire up S3, Google Cloud Storage, or MinIO for external file storage.
• Public Data Portals - Share bases and views publicly or with password protection to expose read-only datasets or catalogs to external users.
• Role-Based Data Access - Manage collaborator access with fine-grained roles and permissions so teams can edit, comment, or view specific bases and views.

Requirements

• Write concise developer-focused Render template copy
• Avoid fluff
• Avoid the word proof of concept
• Avoid em dashes
• Avoid semicolons in prose

Next steps

1. Open your service - Visit the web service URL from the Render Dashboard, then navigate to /dashboard to complete NocoDB setup and create your first admin account.
2. Set NC_SITE_URL - In the Render Dashboard, set NC_SITE_URL to your public service URL. This is required for email links, webhooks, OAuth redirects, and other public URL features.
3. Verify connected resources - Confirm the PostgreSQL database, Key Value instance, and persistent disk at /usr/app/data are provisioned and wired to the web service.
4. Configure integrations - Add chat, email, or storage integrations from the NocoDB App Store as needed. See the upstream App Store documentation for setup details.
5. Set up API access - Generate tokens and use the REST APIs or NocoDB SDK for programmatic access. Authenticate with JWT or social auth tokens.