Build · Module
Apps Builder
Build tenant apps with objects, views, Actions and roles beside first-party apps
Apps Builder lets tenants build their own apps as Packs on the One3 kernel, with objects, fields, views, generated Actions, roles and workflows. It runs as an internal engine from W0 and is planned for tenants at W3 GA.
What it does
Apps Builder is the same metadata engine One3 uses to build its own Packs. From W0 it runs internally, compiling object, field, relation and view definitions into tables, Actions, events and views, and generating migrations, REST and OpenAPI, MCP tools, a TypeScript client and test scaffolds from a manifest. In Year 1 tenants get custom fields on first-party objects. The tenant-facing builder is planned for W3 GA in Year 2.
Designing an app
The app designer creates an app with navigation, icon, objects, fields, relations, record naming and codes. Field types cover text, number, money with currency, percent, dates, picklists, email, phone, URL, file, party and user references and more. Views include list, detail, form, kanban and calendar. Generated Actions and state machines give CRUD Actions with default risk tiers and reversibility, and statuses with guarded transitions. Roles and permissions combine app roles, record rules on owner, team, workspace and related party, and field-level visibility. Field classification encrypts sensitive fields and masks them by role.
From description or spreadsheet
Describe to build turns a description into a draft app with explanation and synthetic seed records, installed only in a sandbox until published. Spreadsheet to app infers objects, fields and relations from CSV or XLSX and imports data with dry-run and reconciliation. A solution planner turns requirements into a reviewable plan of process map, objects, forms, workflows, agent steps and open questions.
Safe change
Apps are built in a sandbox with synthetic or masked data and published with a migration preview. PackVersion and rollback restore previous views, Actions and policies; schema changes are expand-only so rollback never drops data. 3-way-merge upgrades reconcile the base Pack, the new version and tenant customisations with a conflict list and AI-suggested resolutions. Plain-language change requests produce a draft diff.
Connected to everything
Forms and Automations target app objects and events. App Actions can be exposed as MCP tools and agent skills under policy. Apps relate to first-party objects such as a CRM deal, appear in Portals and dashboards, export in an open format and install to agency sub-accounts. An agent activity feed shows what AI did in each app. Industry starter apps include dealer management, admissions, site inspections, asset issue registers and vendor onboarding.
Features
What Apps Builder includes
Metadata engine and codegen
Object, field, relation and view definitions compiled into tables, Actions, events, APIs, MCP tools and tests.
Custom fields on first-party objects
Tenant admins add fields, picklists and validation to One3 objects.
App designer
Navigation, icon, objects, fields, relations, record naming and codes.
Field types and views
Money, references, picklists and more, with list, detail, form, kanban and calendar views.
Generated Actions and state machines
CRUD Actions with default risk tiers and guarded status transitions.
Roles, record rules and field security
App roles, owner and team rules, field visibility and encrypted sensitive fields.
Describe to build
Description to draft app with seed records, installed only in a sandbox.
Spreadsheet to app
Infer objects and relations from CSV or XLSX and import with dry-run and reconciliation.
Sandbox, publish and rollback
Masked or synthetic sandbox data, migration preview and expand-only schema rollback.
3-way-merge upgrades
Base, new version and tenant changes merged with a conflict list and suggested resolutions.
Formula and rollup fields
Expression language and rollups over related records.
MCP tools and agent skills
App Actions exposed to agents and MCP clients under entitlement and policy.
Pack export and sub-account install
Open-format export and installation to agency sub-accounts and snapshots.
App templates and analytics
Dealer management, admissions, inspections, asset register and vendor onboarding starters, plus usage analytics.
Solution planner
Requirements to a reviewable plan of objects, forms, workflows and agent steps.
Workflow
Describe to published app
- 1
Describe the app or upload a spreadsheet
- 2
Review the draft objects, fields and views
- 3
Test in a sandbox with synthetic data
- 4
Add roles, forms and workflows
- 5
Publish with a migration preview
Workflow
Pack upgrade with tenant customisations
- 1
New base Pack version arrives
- 2
3-way merge compares base, new and tenant changes
- 3
Conflicts are listed with suggested resolutions
- 4
Upgrade is verified in a sandbox
- 5
Upgrade is published
AI
AI skills and Digital Employees
Describe to build
Draft app definitions with explanation and seed data.
Plain-language change requests
Draft diffs such as adding an approval step above a discount threshold.
Merge conflict suggestions
Suggested resolutions during upgrades.
Solution planner
Turns requirements into a reviewable build plan.
Digital Employees that use this module
- AI Developer (tenant apps)
- Tenant App Developer Agent
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
Can I build my own apps in Year 1?
Not yet. In Year 1 the engine is internal and tenants get custom fields, views and automations. The tenant-facing builder is planned for W3 GA in Year 2.
Will upgrades break my customisations?
Upgrades use a 3-way merge with a conflict list and sandbox verification, and rollback never drops data.
Is there a proprietary scripting language?
No. Apps are metadata-first Packs in an open format, with TypeScript extensions in a sandbox.
See Apps Builder in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.