ObjectOSBuild
How apps come to life in ObjectOS — by chatting with AI, by clicking in Console, or by forking a template.
Build
In ObjectOS the customer doesn't write metadata. They describe what they want and the AI builds it. Three paths exist, in order of how most people actually use the platform:
| Path | Who's it for | Output |
|---|---|---|
| AI Builder (primary) | Business users, product owners, anyone | Live metadata in your tenant, queued for approval |
| Console click-build (fallback) | Admins who prefer forms | The same live metadata |
| Template fork (dev path) | Engineers who want code under source control | A TypeScript package shipped via the marketplace |
All three paths produce the same artifact shape — packages of objects, fields, views, actions, flows, permissions. The platform doesn't care how the metadata got there.
The platform vocabulary
Every app is composed from the same primitives. Learn these once.
| Concept | What it is | Doc |
|---|---|---|
| Package | The unit of organization — com.acme.crm, versioned, installable | Packages |
| Data model | Objects + fields + relationships + state machines | Data Model |
| Actions | Named operations callable from REST, Console buttons, flows, or AI agents | Actions |
| Flows | Declarative business logic (autolaunched / scheduled / manual) | Flows |
| Agents | End-user AI assistants — Agent → Skill → Tool | Agents |
| Marketplace | Ready-made packages anyone can install in one click | Marketplace |
Where to start
-
Just exploring? → Open Console, start the AI Builder, say "I need to track customer support tickets with priority, status, and assignee." You'll have a working object in under 30 seconds.
-
Building a real product on top? → Read Packages and Data Model so you understand what the AI is generating. Use the AI to draft, refine by hand or by chat, commit the result.
-
Replacing a Salesforce/Retool app? → Fork the closest marketplace template, strip what you don't need, ask the AI to fill in the gaps.
What you'll never have to do
- Write a REST endpoint. The platform generates one per object.
- Wire a Console form. The form renders from the schema.
- Write RBAC checks. Permissions are declared, not coded.
- Build an admin UI. Console + Console cover both system and business admin.
- Generate types.
@objectstack/specderives them from the schema.
ObjectOS is opinionated about this on purpose: once metadata exists, every surface (REST, Console, ObjectQL, audit, AI tools) appears for free. That's why the AI Builder works — it only needs to produce metadata, and the platform handles the rest.