Databases & Schema

Every Chrysai app is a fully isolated database. This page explains how your data is modelled and how schemas evolve over time.

Apps and entities

An app is a named database — for example, "Reading List" or "Work CRM". Each app contains one or more entities (similar to tables).

An entity has:

• A name (e.g. book, contact)
• A set of fields with types
• Optional links to other entities

Field types

Chrysai supports the following field types:

Type	Description
string	Text, up to 4–16 KB depending on plan
number	Integer or float
boolean	True/false
date	ISO 8601 date/time
json	Arbitrary JSON object

Links & relationships

Entities can be linked to each other. A link creates a one-to-many or many-to-many relationship. For example, a book can be linked to an author.

When you ask for related data ("Show me all books by this author"), Chrysai follows the links automatically.

Schema evolution

Your schema grows as you use it. When you ask your AI to track a new field or entity, it:

1. Validates the change won't break existing records
2. Adds the new field or entity to the schema
3. Confirms the update

Existing records are not affected — new fields default to null unless you specify otherwise.

Storage limits

Each plan has a storage quota that covers all apps in your workspace. See Plans & Limits for your tier's allowance.