Connect Metabase, Tableau, or DBeaver to your AI-built app's database

Every White Ghost app runs on a managed PostgreSQL database, and the console gives you real development credentials for it: host, user, and password, ready to paste into Metabase, Tableau, DBeaver, or any other PostgreSQL-compatible tool. Open the app's Settings tab and click "Show development credentials".

This is one of the clearest differences between deploying an AI-built app as a real application and sharing it as an artifact or platform-hosted site. A link shows people the app. A database connection lets you analyze what the app is collecting.

Production closed, development open

The rule is simple:

• The production database is not reachable from outside the platform. No connection string exists for it.
• The development database is: the credentials from the console point only at the app's development database, over an SSL-required connection.

That split is deliberate. You get a real analytical surface without production data ever being exposed to an external connection. The development database is the same one local development uses, so what you inspect is what you and your assistant have been building against.

What you can do with it

1. Point Metabase at it and build a dashboard over the data your app manages.
2. Open it in DBeaver or psql and inspect the schema the assistant created, table by table.
3. Connect a notebook and pull the data into a quick analysis.

Why this matters for AI-built apps

When an assistant builds your app, the database schema is something it designed for you. Being able to open that schema in a real SQL client keeps you in control: you can verify what is stored, correct course early, and answer questions the app's own UI does not answer yet. On White Ghost the database is managed (provisioned with the app, no setup), but never a black box.

Frequently asked questions