Building Applications
Application data and demo content
DeplAI creates the application’s data model from the features you requested: products, bookings, tasks, customers, and similar records.
DeplAI creates the application’s data model from the features you requested: products, bookings, tasks, customers, and similar records.
You do not choose a database product. DeplAI manages how structured data is stored for the generated application.
Persistent data
Generated applications can store structured information so work survives a refresh in the preview: creating a task, placing an order, or booking an appointment can persist in that preview environment.
The generated source includes the application’s data structure so you can continue the product outside DeplAI after you download it.
Demonstration data
Preview applications often include demonstration data so you can explore screens that would otherwise be empty. Examples include sample products, customers, tasks, appointments, or inventory items.
Demonstration data exists for preview and review. It is not production customer data and does not become a production dataset if you later host the application yourself.
When you take the source elsewhere, treat preview data as sample content. Load your own production data through whatever process you use outside DeplAI.
What to expect
- The data shape follows the workflows you described.
- Empty-looking admin screens usually mean you still need to create records, or you are signed in as a role that should not see them.
- If a requested data type is missing, describe it in a Modify request rather than assuming a later hosting step will invent it.
Related: Authentication and roles | Files | FAQ