# Apps

> Part of the NocoDB documentation (Apps). Index of all pages: https://nocodb.com/llms.txt. Any docs page is available as Markdown by adding `.md` to its URL.

URL: https://nocodb.com/docs/apps
Last updated: 2026-10-05

NocoDB Apps is an AI app builder for creating enterprise-grade work apps: describe the app, and NocoAI builds it on the data you already have, with teams, permissions, an API and an MCP server.

<AskNocoAI>
  <Prompt>
    Build an app where [the support team] can triage [tickets] and reply to [customers]
  </Prompt>

  <Prompt>
    Build an app for [event check-in] that lists [today's attendees] and marks them as [checked in]
  </Prompt>

  <Prompt>
    Add a page to this app that shows [overdue invoices] for [the finance team]
  </Prompt>

  <Prompt>
    Make the [booking] page public so [customers] can use it without signing in
  </Prompt>
</AskNocoAI>

NocoDB **Apps** is an AI app builder for creating enterprise-grade work apps. You describe the app in a chat, and [NocoAI](/docs/product/noco-ai) builds it on the data you already have. NocoAI writes the pages, the actions and the access rules, and adds tables when the app needs them. You test the app in a live preview. Then you deploy it to its own web address for your team and the people you invite.

This is vibe coding for the apps that a business runs on. From the first build, the app has a real database, teams and permissions, an API and an MCP server. You do not build a backend, and you do not add security later.

<img alt="A deployed NocoDB app" src={__img0} placeholder="blur" />

## Why build work apps with NocoDB

| What a work app needs                 | What NocoDB Apps gives you                                                                                                                                                                                                                                          |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Real data, not a demo database**    | Apps run on NocoDB tables, your own [Postgres or MySQL database](/docs/product/integrations/data-sources), or data that [syncs](/docs/product/sync/app-sync) from tools such as GitHub and HubSpot. There is no record limit. See [Data for apps](/docs/apps/data). |
| **A data model that fits the app**    | NocoAI designs the tables and fields too. **Build with AI** creates the base and the app from one description.                                                                                                                                                      |
| **Control of who does what**          | Teams, a list of the actions that each team can run, record rules for each team, and public pages that you choose. See [Secure vibe coding](/docs/apps/security).                                                                                                   |
| **Safe changes**                      | A live preview, a review before risky deploys, [environments](/docs/apps/environments) for tests, and a version history with one-click restore.                                                                                                                     |
| **Access for programs and AI agents** | Each app has its own [REST API and MCP server](/docs/apps/api-and-mcp).                                                                                                                                                                                             |
| **Costs that you can plan**           | Actions that only read or change the data of the base do not count as action runs. See [Availability](#availability).                                                                                                                                               |

An app is not limited to the layouts of an [interface](/docs/interfaces). NocoAI writes the app code, so each app can have its own screens, navigation and logic. For example:

* An internal tool for the operations team, on the company Postgres database.
* A client portal that shows each customer only their own records.
* A booking app for a clinic, with a public page where patients book a visit.
* A check-in app for an event team, used on phones at the door.

## How apps are structured

| Concept            | Description                                                                                                                                                                                               |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **App**            | A custom web app on the data of one base. Each base has at most one app. The app uses the name of the base.                                                                                               |
| **AI app builder** | The page where you build the app with AI: a live preview of the app and the NocoAI chat. See [AI app builder](/docs/apps/app-builder).                                                                    |
| **Action**         | An operation that the app can run, for example "create a booking" or "send a reminder". Actions are the only way that the app reads or changes data and calls other services. NocoAI creates the actions. |
| **Team**           | A group of people in the app. Each team has a list of the actions its members can run. Every app starts with the **Admin** and **Members** teams. See [Members and teams](/docs/apps/members-and-teams).  |
| **Deploy**         | Deploying saves the current build as a numbered version and makes it live at the app address. See [Deploy an app](/docs/apps/deploy-app).                                                                 |
| **App URL**        | The web address where people use the app. See [App URL](/docs/apps/app-url).                                                                                                                              |
| **Public pages**   | Pages that anyone can open without signing in. See [Public access](/docs/apps/public-access).                                                                                                             |

## Who can do what

| Action                | Who and how                                                                                                                                                                                                            |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Build**             | Base **Owner** and **Creator** roles build, change and deploy the app.                                                                                                                                                 |
| **Use**               | Base members open the app from the **App** tile in the mini sidebar, or at its address. You can also add people to the app only. They get no other access to the base. Their team controls which actions they can run. |
| **Visit**             | Anyone can open the pages that the app makes public.                                                                                                                                                                   |
| **Connect a program** | Programs and AI agents call the app actions through the app [API and MCP server](/docs/apps/api-and-mcp), with a token.                                                                                                |

## Get started

1. [Create an app](/docs/apps/create-app) in a base, or create a base and an app together with AI.
2. Describe the app to NocoAI in the [AI app builder](/docs/apps/app-builder).
3. [Deploy](/docs/apps/deploy-app) the app to its address.
4. Give people access in [Members and teams](/docs/apps/members-and-teams).

New to building apps with AI? Read [Vibe coding with NocoDB Apps](/docs/apps/vibe-coding).

## Availability

Apps are available on the paid plans of NocoDB Cloud: **Plus**, **Business**, **Scale** and **Enterprise**. Apps for self-hosted NocoDB are in private beta. To get early access, [talk to sales](https://cal.com/nocodb/sales).

Some capabilities need a higher plan:

| Capability                                                                                         | Plan            |
| -------------------------------------------------------------------------------------------------- | --------------- |
| Apps, the app API and MCP server, actions that use external data (SQL, HTTP and Redis connections) | Plus and above  |
| [Environments](/docs/apps/environments), per-user connections, record-level security for app teams | Scale and above |
| Clean URL                                                                                          | Enterprise      |

Each plan includes these action runs for each billing cycle:

| Plan       | Action runs per billing cycle |
| ---------- | ----------------------------- |
| Plus       | 30,000                        |
| Business   | 120,000                       |
| Scale      | 240,000                       |
| Enterprise | 600,000                       |

Only these runs count: actions that use external data, actions called with an API token, and actions that run custom code. Actions that only read or change the data of the base do not count.

## Related

* [Create an app](/docs/apps/create-app)
* [Data for apps](/docs/apps/data)
* [Secure vibe coding](/docs/apps/security)
* [Vibe coding with NocoDB Apps](/docs/apps/vibe-coding)
* [Credits](/docs/product/workspaces/credits)
* [Interfaces](/docs/interfaces)

---

## Related pages

- [Vibe Coding with NocoDB Apps](https://nocodb.com/docs/apps/vibe-coding.md): Vibe coding is making software by describing it to AI. NocoDB Apps bring vibe coding to enterprise-grade work apps, on your own data, with teams, permissions and safe deploys.
- [Create an App](https://nocodb.com/docs/apps/create-app.md): Create a NocoDB app with AI: describe the app, and NocoAI builds it on your data. Start from the App tile in a base, with Build with AI, or in the NocoAI chat.
- [AI App Builder](https://nocodb.com/docs/apps/app-builder.md): Build and change enterprise-grade work apps in NocoDB's AI app builder: describe a change to NocoAI in the chat, and test it in the live preview.
- [Data for Apps](https://nocodb.com/docs/apps/data.md): Build NocoDB apps on the data you already have: NocoDB tables, your own PostgreSQL or MySQL database, and data that syncs from tools such as GitHub and HubSpot, with no record limit.
- [Secure Vibe Coding](https://nocodb.com/docs/apps/security.md): How NocoDB Apps keep AI-built work apps safe: teams and action grants, record rules, reviewed public pages, secrets in connections, scoped API tokens, environments and version restore.
- [Members and Teams](https://nocodb.com/docs/apps/members-and-teams.md): Control who can use a NocoDB app and what they can do in it with app teams, members and action grants.
- [Public Access](https://nocodb.com/docs/apps/public-access.md): Make pages of a NocoDB app public, and choose which actions visitors can run without signing in.
- [Deploy an App](https://nocodb.com/docs/apps/deploy-app.md): Deploy a NocoDB app to make the current build live at its address, review risky changes before they go live, and restore an earlier version.
