Unified Object Registry

Every business app is built on data objects. Customers, orders, products, invoices, contacts, projects, tickets — the list varies by business but the pattern is universal. These objects have fields, they relate to each other, and the entire application is a set of operations on them.

In most platforms, these objects live in scattered places: some in a database schema tool, some in configuration files, some implied by the application's structure. Understanding your data model requires looking in multiple places.

The unified object registry brings everything together.

One Place for All Data Types

Every object type in your app is defined in the registry. Open it and you see the complete data model for your app: every type, with its fields, its relationships, and its metadata.

Creating a new object type is a single action. Name it, define its fields, set up the relationships to other types, configure any metadata about how it should behave. The object becomes available immediately across the platform — in screens, in automations, in exports, everywhere.

Field Management

Each object's field list is editable directly from the registry. Add a field, choose its type — text, number, date, relation, file, status — and configure its properties. Change the order fields appear in forms. Mark fields as required. Add options to choice fields.

Changes to fields propagate automatically. A field added to the Customer object appears in customer forms, customer detail views, customer list columns, and anywhere else customer fields are used.

Relationship Definition

Relationships between objects are defined in the registry alongside fields. An Order relates to a Customer. A Product relates to a Category. A Task relates to a Project.

These aren't just visual annotations — they drive actual behavior. A relation field on a form shows a searchable picker for the related type. Related records components on detail pages show the linked records. Reports can traverse relationships to aggregate across types.

Structured at a Glance

The registry view shows you the data model as a whole: all object types, their field counts, their relationship connections. It's the architectural view of your app's data — useful for understanding what exists, planning new additions, and spotting inconsistencies before they become problems.

For teams working collaboratively on an app, the registry is the shared reference point. Everyone can see the data model. Everyone can see where a field lives. No one needs to trace through scattered configuration to answer "does this object have that field?"

The unified object registry is where data modeling happens — cleanly, visibly, and in one place.