---
title: "Self-host NocoDB in 2026: your tables in PostgreSQL, in France"
url: https://while.sh/en/guides/self-host-nocodb/
author: "Aloïs Oddon, co-founder of Nextmap"
updated: 2026-11-19
---

# Self-host NocoDB in France, with its PostgreSQL database, with your AI (2026)

An Airtable alternative of your own, hosted in France. Connected to while over MCP, your AI deploys NocoDB, with your tables in a PostgreSQL database backed up every day.

> **The short version.** Over MCP, your AI deploys NocoDB with while, in France, with your tables in a PostgreSQL database backed up every day. What matters, like deleting a database, waits for a person's approval.

## Prerequisites

- A new NocoDB instance, or your exported tables.
- Your AI: Claude Code, Codex, Cursor or Gemini CLI.

## Step 1: Ask your AI for NocoDB

> You, to your AI: Connect to while with my account (while.sh/agents), then deploy NocoDB with its PostgreSQL database.

Your AI adds while's MCP server itself. If it asks you to, restart it. On the first call to while, a page opens in your browser. In Claude Code, if it doesn't open, type /mcp, choose while, then Authenticate. On that page, choose "A new app", then click Authorize.

## Step 2: Create your NocoDB account

Your AI gives you the address of your NocoDB, for example `https://nocodb.while.cloud`. Open it right away: the first account created becomes NocoDB's administrator. You then create your tables there.

## What your AI does

It deploys the official NocoDB image as it is, without a Dockerfile, with this while.yaml:

```yaml titre="while.yaml"
apiVersion: while/v1
project: nocodb
services:
  - name: web
    image: docker.io/nocodb/nocodb:latest
    port: 8080
    health:
      path: /api/v1/health
    env:
      NC_TOOL_DIR: /tmp/nocodb/
    resources:
      memory: 1Gi
databases:
  - name: main
```

NocoDB reads its database from `DATABASE_URL`, which while gives it, and stores your tables and their data there (source 1). Two settings let it run without administrator rights: `NC_TOOL_DIR` gives it a working folder where it can write, and `memory: 1Gi` leaves it the memory it needs to start. The `/api/v1/health` route tells while that NocoDB is ready.


<figure class="illus"><img src="/illustrations/guide-heberger-1200.webp" srcset="/illustrations/guide-heberger-768.webp 768w, /illustrations/guide-heberger-1200.webp 1200w" sizes="(min-width: 48rem) 46rem, 100vw" width="1536" height="1024" loading="lazy" decoding="async" alt="Self-host NocoDB in France with no server to manage: the open-source tool and its PostgreSQL database backed up every day, served over HTTPS on while, put in production by your AI" /><figcaption>The open-source tool and its PostgreSQL database, backed up every day, in France, with no server to look after.</figcaption></figure>

## Restrict NocoDB to your colleagues

> You, to your AI: Restrict NocoDB to people in the company.

Your AI makes the service internal:

```yaml titre="while.yaml"
    access: internal
```

Then it asks for the Access role for your domain, @acme.com, on this app, and a person in your organization approves it.

Once your Google Workspace or Microsoft 365 is linked to while, on the Pro plan, your colleagues go through their usual account, then through NocoDB's sign-in.

## Move to your own domain

> You, to your AI: Put NocoDB on tables.acme.com.

Your AI declares the domain, you add the DNS records it gives you, and the HTTPS certificate follows.

## Upgrade to the latest version of NocoDB

> You, to your AI: Upgrade NocoDB to the latest version.

Your AI deploys the latest NocoDB image. If the new version disappoints, it rolls back to the previous one.

## Put NocoDB back the way it was yesterday

> You, to your AI: Restore NocoDB's database to yesterday at 6 pm.

Your AI prepares the restore, and you approve it: a safety backup is taken first, then the database goes back to the moment you asked for.

## Next steps

- [Restore your database to a precise moment](/en/guides/restore-postgresql/)
- [Deploy a Docker container](/en/guides/deploy-docker-container/)

## Sources

1. [NocoDB, environment variables](https://nocodb.com/docs/self-hosting/environment-variables), 2026-11-02
2. [NocoDB, installing with Docker](https://nocodb.com/docs/self-hosting/installation/quickstart), 2026-11-02

## Questions

### Are my tables backed up?

Yes: NocoDB keeps its tables and their data in the PostgreSQL database, which is backed up every day and can go back to a precise moment (source 1).

### Where do attached files go?

NocoDB keeps them in its working folder, which starts from scratch at every restart: keep your attachments elsewhere, or import them again after an update.

### Can my colleagues sign in with the company account?

Yes, with the Pro plan: they go through their usual account, then through NocoDB's sign-in.

### Where is my NocoDB hosted?

In France, by Nextmap, a French company.

### Does my AI see my credentials?

No. You paste them into while, the app uses them, and your AI never sees them. Every call is logged.
