Apps vs Classic Apps

NocoDB has two ways to build apps on your project data: AI apps and classic apps. Classic apps were called Interfaces before. Both kinds live under Apps in the project sidebar, and a project can have both.

The two kinds of app use the same project data. They differ in how you build them, who can use them and how they go live.

	AI app	Classic app
In one sentence	You describe the app, and NocoAI writes it.	You put pages together from layouts, without code.
Best for	Portals, approvals, partner tools	Trackers, intake forms, dashboards
How many in a project	One	Any number, up to the limit of your plan
Docs	Apps	Classic apps

How you build

An AI app starts from a description in a chat. A classic app starts from a layout that you select for each page.

	AI app	Classic app
Builder	The AI app builder: a live preview and the NocoAI chat	The classic app builder: a canvas and a properties panel
How you make changes	Ask NocoAI in plain language. NocoAI writes the pages, the actions and the access rules.	Select an element on the canvas and configure it.
Screens	Custom screens, navigation and logic	Six page layouts: Table, Record review, Dashboard, Form, Overview and Record detail
Starting point	A description. NocoAI can also design new tables for the app.	Your existing tables. A page can copy settings from a view.
Learn more	Create an app	Create a classic app

Who can use it

Both kinds of app let you share project data with people who must not see the full project.

	AI app	Classic app
Builders	Project Owner and Creator roles	Project creators and owners
Access model	Teams. Each team has a list of the actions that its members can run.	Roles (Editor, Commenter, Read only) on the full classic app or on each page
People from outside the project	Add them to the app only	Invite them to the classic app only
Public use	Public pages that anyone can open without signing in	Not available yet. Public share-to-web for table and dashboard pages is planned.
Learn more	Secure vibe coding	Share a classic app

How it goes live

An AI app deploys to its own web address. A classic app publishes a draft inside NocoDB.

	AI app	Classic app
Release model	Deploy the current build as a numbered version	Publish the draft. You can keep single pages as draft.
Test before release	A live preview, and test environments	Preview and Preview as a role or a person
Version history	Each deploy is a numbered version. You can restore an earlier version with one click.	One draft and one published version of each page
Address	The app URL, its own web address	Inside NocoDB

Data and integrations

	AI app	Classic app
Data	Your databases (PostgreSQL, MySQL, SQL Server), any HTTP API and SaaS apps, live through connections, plus project data	Project data
How the app changes data	Through actions that NocoAI creates	Through the editing options of each page and buttons
Automations	Actions can call other services	Buttons can run a workflow through the When a button is clicked trigger
API and MCP server	Yes, one for each app	No
Learn more	Data for apps, API and MCP	Fields, buttons & filters

Which one to pick

Use the questions below to select the kind of app. You do not have to select only one: a project can have one AI app and many classic apps.

If you need	Use
A tracker, an intake form or a dashboard on tables you already have	Classic app
Several small tools, each for a different audience	Classic apps
Custom screens, logic or roles that the six layouts cannot give	AI app
Pages that people open without signing in	AI app
Access for other programs or AI agents	AI app
An app on self-hosted NocoDB today	Classic app. AI apps for self-hosted NocoDB are in private beta.

Availability

	AI app	Classic app
NocoDB Cloud	All plans, including Free. Building and running the app use the credits of the workspace.	All plans
Self-hosted	Private beta. To get early access, talk to sales.	Available. The Community Edition includes 2 classic apps with up to 2 pages each.