Self-host Metabase in France, with its PostgreSQL database, with your AI (2026)
Your dashboards deserve better than a forgotten server. Connected to while over MCP, your AI deploys Metabase in France, with its settings in a PostgreSQL database backed up every day, and private to your colleagues if you want.
By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 19, 2026.
The short version. Over MCP, your AI deploys Metabase with while, in France, with its dashboards in a PostgreSQL database backed up every day. What matters, like deleting a database, waits for a person’s approval.
Prerequisites
- A new Metabase instance, or the database of a current instance.
- Your AI: Claude Code, Codex, Cursor or Gemini CLI.
Step 1: Ask your AI for Metabase
You, to your AI: Connect to while with my account (while.sh/agents), then deploy Metabase 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 Metabase account
Your AI gives you the address of your Metabase, for example https://metabase.while.cloud. The first startup takes about five minutes. You then create the admin account there, then your first questions.
What your AI does
It deploys the official Metabase image, without a Dockerfile3, with this while.yaml:
apiVersion: while/v1
project: metabase
services:
- name: web
image: docker.io/metabase/metabase:latest
port: 3000
health:
path: /api/health
startup_timeout_seconds: 600
command: ["sh", "-c", "MB_DB_TYPE=postgres MB_DB_CONNECTION_URI=\"$DATABASE_URL\" MB_JETTY_PORT=$PORT exec /app/run_metabase.sh"]
scale:
min: 1
max: 1
resources:
cpu: 2000m
memory: 1536Mi
databases:
- name: main
pool: session
Metabase keeps its settings, its questions and its dashboards in the PostgreSQL database1. The startup command gives it that database’s address and its port1,2. Three settings can’t be guessed, and without them Metabase doesn’t start:
pool: session, on the database. Metabase’s migrations take a lock that needs to keep the same connection to the database. Without this line, Metabase stops at startup.startup_timeout_seconds: 600. On its first startup, Metabase prepares its database for about three minutes. Without this line, while withdraws the version after 120 seconds.memory: 1536Mi. Metabase is a Java app: with the default memory, it falls over.
Two CPUs make startup shorter, and a single instance is enough: it fits within the Free plan’s CPU quota. If your AI leaves out one of these settings, show it this guide.

Connect Metabase to your app’s database
You, to your AI: Connect Metabase to our app’s database, read-only.
Your AI gives Metabase read-only access to your app’s database, even when it sits in another project of your organization. Metabase reads, and can never write.
Restrict Metabase to your colleagues
You, to your AI: Restrict Metabase to people in the company.
Your AI makes the service internal:
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 connected to while, on the Pro plan, your colleagues sign in with their usual account, then with Metabase’s own sign-in.
Move to your own domain
You, to your AI: Put Metabase on stats.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 Metabase
You, to your AI: Upgrade Metabase to the latest version.
Your AI deploys the latest Metabase image. If the new version disappoints, it rolls back to the previous one.
Put Metabase back the way it was yesterday
You, to your AI: Restore Metabase’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.
In the docs: PostgreSQL databases, Internal access and Prebuilt image.
Next steps
Sources
- Metabase, the application database (PostgreSQL), accessed November 2, 2026
- Metabase, environment variables, accessed November 2, 2026
- Metabase, the Docker image, accessed November 2, 2026