Data Apps · Beta

Generate data apps on the foundation you already trust

Prompt your AI agent for any data app or internal tool. It builds on your semantic layer, permissions, and auth, and lives in Metabase where you can audit usage and dependencies. Full customization, nothing to rebuild.

Trusted by 100,000+ companies
Hugging Face logoMcDonald's logoHUMA logoCapital One logoJLL logoLinear logoDeutsche Telekom logoKong logo

Build data experiences and internal apps with Metabase

MetaPumpkin is a pumpkin business app that a coding agent built on live data. Every number comes from saved metrics in Metabase, and with row and column security, each regional manager sees only their own region. Your team can build apps for the work they do every day:

  • Support: review complaints, and record refunds and credits back to your database.
  • Operations: find at-risk and undelivered orders, assign an owner, and mark them resolved.
  • Finance: flag accounts with unpaid invoices and pause their subscriptions.
  • Financial services: review loan applications against your own risk metrics, then approve or decline them.
  • IT and admin: handle access requests and role changes without building an admin tool from scratch.
  • People operations: track onboarding and offboarding tasks for every new hire and departure.
MetaPumpkin, a data app in Metabase, showing revenue, pumpkins sold, margin, and live sales for a pumpkin business

Any layout, on the same numbers

Live maps, feeds, forms, and approval queues: if your agent can build it in React, it can be a data app. MetaPumpkin's fleet view tracks every delivery van on live data, and every count on it comes from the same metrics your dashboards use.

MetaPumpkin's live fleet map, showing delivery vans, hubs, and store stock levels, with a detail card for one van

The guardrails that keep your agent on point

The constraints that matter are what an app builds with, who can do what, and where it lives. Metabase takes care of all three, so you don't have to build them yourself.

Same numbers as everywhere else

Apps read only published tables and Library metrics, through the query builder. Metabase rejects SQL questions, so the app and your dashboards can't disagree. What an app can read and write

Changes write back only through your actions

Apps write data back to your database only through the actions in their own collection, like updating or adding a row. Only admins can edit those actions, so you can see exactly what an app is allowed to change.

Your sign-in and permissions

People sign in with Metabase and see only what their groups allow. The same app shows each person their own slice.

Sandboxed inside your Metabase

Apps live at /apps/<name> behind your Metabase sign-in, and requests to other sites are blocked unless you allow them.

Code in your repo

Each app is code in your Remote Sync repository, so you can review the diff and any admin can pick it up. How to build and ship an app

Usage and dependencies in Monitor

Data app analytics logs every question and action an app runs, and the dependency graph shows which apps use a metric before you change it. Manage data apps

Your data deserves better than vibes

Vibe-coded apps rebuild the data connection, sign-in, and permissions, and write their own SQL. Data apps start from what you already have in Metabase.

Feature Vibe-coded app on the API Metabase Data Apps
Data connection Rebuilt for every app Already there
Sign-in Yours to build Metabase sign-in
Permissions API keys in the browser Metabase permissions
Numbers match your metrics Hand-rolled SQL Published metrics
Hosting Yours to set up Inside your Metabase
Audit and lineage None Monitor and dependency graph

Build it from your AI client

The whole thing happens in the coding agent you already use, like Claude Code or Codex.

1. Set up the CLI

Install the Metabase CLI, log it in to your development Metabase as an admin, and install the CLI's skill for your agent.

2. Prompt your agent

Start your agent in your Remote Sync repository and describe the app. For example: "Create a Metabase data app that lets people look up product info, and add, edit, or remove products."

3. Preview as it builds

Your agent saves the app's questions and actions, writes the code, and runs a local preview so you can try the app as it takes shape.

4. Ship it with Remote Sync

Push the app to production like the rest of your synced content, then choose which groups can open it.

Frequently asked questions

What are Metabase data apps?
Metabase data apps are custom apps that an AI coding agent builds on top of your Metabase semantic layer. Unlike a dashboard, a data app can have any layout and its own pages, and people can add, edit, and delete data from it. Data apps are in beta on Pro and Enterprise plans. See the data apps docs.
How do I build a data app with Metabase?
You build a Metabase data app by prompting an AI coding agent, like Claude Code or Codex, that uses the Metabase CLI. The agent creates the app on a development Metabase and writes its code, and you ship the app to production with Remote Sync. See how to build a data app.
What do I need to build a Metabase data app?
You need a Pro or Enterprise plan, an admin account, an AI coding agent, the Metabase CLI, Node.js 22.12 or later, and Remote Sync. Apps read the published tables and metrics in your Library, so you also need a semantic layer you trust.
Can Metabase data apps write data back to my database?
Yes. Metabase data apps write back to your database through actions, like adding, updating, or deleting a row. An app can only use the actions in its own collection, and only admins can edit them.
Are Metabase data apps secure?
Yes. A data app runs with the permissions of the person who opens it, including row and column security, and people sign in with their Metabase account. Apps are sandboxed inside Metabase, and requests to other sites are blocked unless you allow them.
Can a Metabase data app run SQL?
A data app can't read data with SQL. Apps read published tables and Library metrics through the query builder, and Metabase rejects SQL questions, so an app's numbers match your dashboards. Actions that write data can use SQL.
How are Metabase data apps different from vibe-coded apps or internal tool builders?
Metabase data apps start from the data connection, sign-in, permissions, and metrics you already have in Metabase. A vibe-coded app or a separate internal tool builder has to rebuild each of those, and its numbers can drift from your semantic layer.
Which AI coding agents work with Metabase data apps?
Metabase data apps work with any coding agent that can run commands and install skills, including Claude Code and Codex. There's no visual builder.
Which Metabase plans include data apps?
Data apps are available on Metabase Pro and Enterprise plans, and the 14-day free trial of Pro includes them. Data apps are in beta.
How do I see who uses a Metabase data app?
Data app analytics, in Metabase's Monitor section, logs every question and action an app runs, who ran it, and what failed. The dependency graph shows which tables, metrics, and actions each app depends on. See data app analytics.
Can I share a Metabase data app publicly?
Not yet. Data apps open behind Metabase sign-in, for the groups an admin chooses.