Incorta Applications
This content applies to Incorta Cloud deployments only.
Overview
Introduced in v8.2 - 2026.8, Incorta Applications is the first generally available (GA) version of Incorta AI Apps (v8.0.0 - 2026.8). Incorta Applications lets you build a working web application on top of your Incorta data.
You can build and refine applications with the Incorta Builder Agent through natural-language prompts. Developers can also use the AppKit command-line interface (CLI) to develop applications locally with their preferred code editors, tools, and AI coding agents.
An application is a complete web app built on your Incorta data, with its own pages, forms, logic, and database. Use applications to build whatever your team needs to act on data, not just view it. Common starting points include data entry and approval workflows, guided processes, and task tracking alongside live metrics, but the possibilities extend well beyond these.
Applications connect directly to your Incorta data using the signed-in user credentials, eliminating the need to export or synchronize data.
Feature availability
Incorta Applications is available on Incorta Cloud deployments only. Incorta Applications is a metered, pay-as-you-go capability. Incorta tracks Compute, memory, and data transfer per application and per tenant, and bills based on actual usage.
The feature is turned off by default. To enable it, contact your Incorta Account Executive.
Scope of operation
- Applications can only read Incorta data. Applications do not write to Incorta.
- Applications cannot bypass your permissions. Queries run as the signed-in user, under the same row-level security, access permissions, and masking rules as everywhere else in Incorta.
- Each application has its own dedicated database for application data, such as form submissions, workflow status, and application settings. Each database is isolated, with its own schemas and credentials, so applications cannot access each other's data.
- AI agents that build applications operate under the same restrictions as users. Agents do not access plaintext secrets, and every agent action is logged for auditing.
What you can build
The following are examples of applications that you can build with Incorta Applications:
- A departmental tool that combines a form, a workflow, and a report in one place
- An operational worklist over live Incorta data, where users record decisions
- An approval or review flow with status tracked per record
- A planning tool that combines Incorta figures with user-entered assumptions
Core concepts
| Concept | Description |
|---|---|
| Stack | The framework the application is built with. You select the stack when you create the application, and you cannot change it later. |
| Application | The unit you build, share, and publish. You can create an application within a tenant and share it with its users. |
| Version | A snapshot of the application. Every change the agent commits creates a version. Versions are numbered oldest-first and are never deleted. |
| Preview | A built, shareable copy of one specific version, at its own address |
| Dev server | The live, running application while you build it |
| Publishing | Promoting one version to a stable address |
How to build applications
To build an application, use the Builder Agent on the Application tab in the Incorta UI, or use the AppKit CLI.
The following table compares the two methods.
| Aspect | Builder Agent | AppKit CLI |
|---|---|---|
| Suitable persona | Users with limited or no coding experience | Developers comfortable with terminal commands and codebases |
| Local setup | Not required | Requires software development tools and a code editor |
| How you build | Describe the application to the Builder Agent, which builds it. Refine the application by chatting with the agent or by using the AppKit CLI. | Create and edit the application in your own code editor with your own tools and AI agent, and then push it to Incorta. Refine the application with the CLI or by chatting with the Builder Agent after you push it. |
| Best for | The fastest path from an idea to a working application | Custom code, deeper integrations, and work in your own local environment |
| More details | Guides → Build Applications via the Builder Agent? | References → AppKit CLI? |
Both methods work on the same application. You can build an application in the UI and then clone it locally, or create it with the AppKit CLI and then continue in the Builder Agent. Each application has one workspace and one version history, regardless of the method you use.
Supported frameworks
When you create an application in the UI, select one of the following options:
- Node.js (default): Builds the application with TanStack Start, a full-stack React meta-framework.
- Python: Builds the application with FastAPI, a Python web framework, and a React frontend.
Both options are full-stack. They handle the user interface, the server-side logic, and server-side rendering (SSR).
Additional frameworks in the AppKit CLI
When you create an application with the AppKit CLI, two additional Python frameworks are available. Both are well suited to dashboard-style data apps:
- Dash
- Streamlit
You cannot change the stack after you create an application. To use a different stack, create a new application.
Publish and manage applications
Before an application goes live, Incorta checks it automatically:
- Security scanning: Static code analysis, secret detection, and configuration checks
- Event auditing: Logging of publishes, approvals, and rollbacks
After you publish an application, you can manage it from the Builder Agent UI or the AppKit CLI:
- Roll back: Return the live application to an earlier version instantly, without code changes or a redeployment.
- Unpublish: Take the application offline immediately. Unpublishing does not affect your underlying Incorta data.
- Monitor: Review the console logs and backend logs in the Builder Agent UI, or stream live logs and review the version history with the AppKit CLI.
How to access applications
The address of an application depends on its status:
- While you build the application, you access it at a development address that is private to the build session.
- Each version has a preview address that you can share for review.
- After you publish the application, you access it at a stable address on the app domain of your Incorta environment.
- Users with access to the Content Manager can view and use shared applications; however, only a published application opens in the Content Manager.
- Users with the Application Manager role can preview a non-published application shared with Edit permission in the Application Manager.
Newly published applications are private. No other users can open a published application until you grant them access.
Access to an application is separate from access to data. Application access controls who can open the application, and data permissions control what each user sees. When two users open the same application, each user sees only the data that this user is entitled to view.
Users must authenticate with their Incorta account before the application responds.