Modeling manually

The visual canvas lets you build and edit your data model directly.

Creating entities

Click the New entity button on the canvas toolbar. A new entity card appears on the canvas. Click it to open the entity editor.

Entity properties

Each entity has:

  • Name / name plural — used in code (camelCase, e.g., blogPost / blogPosts).
  • Label / label plural — displayed in the UI (e.g., "Blog post" / "Blog posts").
  • Icon — a Lucide icon name shown in navigation.
  • Display field — the field used to represent this entity in dropdowns and links.
  • Archivable — enables soft-delete (archive/restore) instead of permanent deletion.
  • Show audit fields on list — displays createdAt, updatedAt, etc. in table views.

See entities for the full reference.

Adding fields

Inside the entity editor, click Add field to create a new field. Choose a field type and configure its validations and properties.

Repositioning

Drag entity cards anywhere on the canvas to organize your layout. Positions are saved automatically.

Relationships

Connect two entities by creating a relationship. Three types are available:

One-to-one

Each record in entity A links to exactly one record in entity B, and vice versa.

One-to-many

One record in entity A links to many records in entity B. For example, one Author has many Book records.

Many-to-many

Records on both sides can link to multiple records on the other side. For example, Student ↔ Course.

Relationship properties

Each side of a relationship has independent settings:

  • Editable — whether the relationship field can be set when creating/editing.
  • Required — whether the link is mandatory.
  • List — show the field in table views.
  • Filter — allow filtering by this relationship.
  • Export — include in CSV/Excel exports.
  • Order — display order among other fields.

Member relationship

A special relationship type that links an entity to the authenticated user. This restricts records so users only see their own data.

Schema operations

The toolbar provides several schema-level actions:

  • Duplicate — clone the current schema.
  • Download schema — save the schema as a JSON file.
  • Load schema — import a schema from a JSON file.
  • Copy schema — copy the schema JSON to clipboard.
  • Demo project — load a pre-built example schema to explore.
Modeling with AIPreview the project