App Builder

Create custom ERP data apps with natural language

What is the App Builder?

The App Builder is a specialized agent in Operator that lets you create small, focused ERP data applications — called Operator Apps — using natural language. Instead of writing code manually, you describe what you want—and the App Builder generates a fully functional app that integrates directly with ERP.net.

What Are Operator Apps?

Operator Apps are single-page applications (SPAs) designed for internal corporate users. They are lightweight, browser-based tools that run entirely on the client side — no server deployment or infrastructure is required.

Each app is purpose-built for a specific task: a dashboard, a data entry form, a lookup screen, a status monitor, or any other focused interface that works with your ERP data in real-time. They are not intended as public-facing websites or customer portals — they are internal productivity tools for your organization's employees.

ERP.net as the Default Data Model

The App Builder is built around the ERP.net data model. Every app you create can immediately work with real business objects — customers, products, sales orders, invoices, projects, and any other entity in your ERP.net instance — because the App Builder already understands ERP.net relationships, types, and conventions.

This means:

• Out-of-the-box data — apps are designed against proper ERP.net business objects, not anonymous spreadsheets or custom schemas.
• Zero setup integration — your apps connect to the same live ERP.net instance you are already using in Operator, so they work immediately for the current enterprise company and user permissions.
• Business-ready design — the AI knows how to build forms, dashboards, and workflows that match ERP.net entities and best practices.

At the same time, you are not limited to ERP.net. You can build any Operator App you want — including apps that use external APIs, combine ERP data with third-party services, or do not touch ERP.net at all.

Support Policy

The App Builder follows a self-service model. AI-powered assistance inside Operator replaces traditional support — AI-generated apps are not covered by ERP.net or Operator support. You build and run them at your own discretion.

By using the App Builder you accept the following principles:

• User Responsibility — You are solely responsible for testing, securing, and maintaining your app. Verify behavior with real data before relying on it for business-critical work.
• AI Error Liability — AI-generated code may contain mistakes, omissions, or unexpected behavior. You accept all risks arising from such errors. Always review the generated code and the live preview before deploying.
• Security — You must configure security (permission policies, sharing scope, data exposure) to protect your data. The AI does not guarantee a secure configuration by default. Apps that read or modify ERP data inherit the permissions of the user running them — design accordingly.
• Code Ownership — You own the code your apps generate. You can view it in the Code tab and export it to deploy elsewhere if you outgrow the App Builder.

If you need a guaranteed, supported solution, build it as a traditional ERP.net customization or engage an ERP.net partner. The App Builder is intended for fast, internal, self-managed productivity tools.

How It Works

The App Builder uses a conversational workflow:

1. Describe your app — Tell the App Builder what you want in plain language. For example: "Create a dashboard showing overdue invoices grouped by customer".

2. Iterative design — The App Builder generates the app and shows you a live preview. You can refine it by asking for changes: "Add a filter for date range" or "Make the table sortable by amount".

3. Deploy — Once satisfied, deploy your app through one of the available deployment modes.

Getting Started

Who can use the App Builder

The App Builder is available to:

• Global Power Users and above — always available, regardless of which instance (if any) is connected.
• Instance Power Users and above — available while an ERP.net instance where you have Power User or Admin role is connected. Disconnecting that instance (or switching to one where you only have Normal/External access) hides the App Builder.

Starting the App Builder

1. Open the agent selector in the header bar (next to the Operator logo).
2. Select App Builder from the dropdown.
3. You'll enter Creator Mode — a clean workspace ready for a new app.
4. Describe your app in the chat and watch it come to life.

The Agent Selector

The agent/app dropdown in the header serves dual purposes:

• Select App Builder — Switches to the App Builder agent in Creator Mode, ready to design a new app from scratch.
• Select an existing app — Opens the app in Execution Mode for day-to-day use. From there, you can switch to Design Mode to make changes.

Interface Modes

The App Builder interface has several modes, accessible via the tab bar:

Source files and stored files are different things: source files are the app's program code, stored files are data. When you mention a file by name in chat, the App Builder treats it as a stored file.

Design Mode

Design mode provides a 30/70 split view — the chat panel on the left and a live app preview on the right. As you describe changes, the preview updates in real-time. Use the Refresh preview button (right side of the tab bar) to force a reload if needed.

Execution Mode

Execution mode shows your app full-width, exactly as end users will see it. This is the default view when selecting an existing app from the agent dropdown. Operator opens existing apps directly in Execute mode for faster startup, and only loads the related design conversation when you switch to Design, Code, Properties, or Deploy.

What Apps Can Do

Apps built with the App Builder can work with live ERP.net data, call AI, and integrate with external services. See API Access in Apps for details on the ERP.net Domain API, data limits, error handling, and external REST API calls.

In short, apps can:

• Query data — Fetch and display records from any ERP entity
• Create records — Build forms that create new entries in the system
• Update records — Modify existing data with validation
• Display dashboards — Visualize data with charts, tables, and summary cards
• Filter and search — Add interactive controls for data exploration
• Respond to context — React to the connected instance and enterprise company
• Call AI — Invoke Pure AI for one-shot completions or run full Operator agents (built-in or user-defined) with tools and capabilities. See AI in Apps.
• Call external APIs — Integrate third-party services using fetch() or window.operator.corsFetch(). See API Access in Apps.

Best Practices

• Start simple — Describe the core function first, then iterate with refinements.
• Be specific — Mention exact entity names, fields, and filters you need.
• Test with real data — Connect your instance and verify the app works with actual records.
• Use descriptive names — Give your app a clear name and description for easy discovery.
• Accept refactor suggestions — If the App Builder suggests reorganising an existing app into smaller files, accept it. The refactor itself is a heavy operation and typically consumes 20–100 credits on its own (proportional to app size, since the AI rewrites many files across several turns). That upfront cost is quickly offset: every subsequent edit on the refactored app becomes noticeably cheaper because the AI no longer re-reads a monolithic file for each change. The only reason to decline is if you don't plan to keep developing the app.

Multiple Conversations per App

Each app supports multiple conversations — one per feature, screen, or sub-project. Splitting the work keeps context focused, cheaper, and easier to resume. Open the Conversations tab in the app panel to switch between them or start a new one.

See Conversations for the full mechanics, actions, and examples.

Next Steps

• Learn about Deployment Options for publishing your apps
• Manage your apps on the Apps Page
• Organize your work with Conversations