LUMIDEVKITdocs
Open app

Database Schemas & AI

Saved schemas

Saving keeps a schema on your LumiDevKit account so you can reopen it later, on any machine, with your diagram layout intact.

This is the one LumiDevKit feature that stores your data on our servers. Everything else happens in your browser. That is why it gets its own page.

What saving does

When you save a schema, LumiDevKit stores:

  • the schema itself: your user_types and option_sets
  • the name you gave it
  • the positions you dragged your nodes into

It is scoped to your account. Other users cannot see it.

It does not store the original file you uploaded. If you loaded a full Bubble application export, only the database part is kept; the pages, workflows, styles and settings are not saved anywhere.

Working with saved schemas

  • Save from the Database Visualizer once you have something worth keeping.
  • My Schemas in the portal lists everything you have saved.
My Schemas in the portal. Each saved schema is a card with its type and field counts, and buttons to open, rename, duplicate or delete it.
  • Open one and you land back on the canvas with your layout as you left it.
  • Duplicate to branch a design without losing the original.
  • Rename at any time.
  • Each schema has its own URL, so you can bookmark a specific one.

Why layout persistence matters

On a schema of any size, arranging the boxes so the relationships read clearly is real work. Reloading the file would scatter them again. Saving keeps that arrangement, which is what makes a saved schema worth returning to rather than just re-uploading the file.

If you would rather not store anything

You do not have to use this feature. The alternatives keep everything local:

  • Download JSON and keep the file yourself. Re-uploading it restores the schema, though not the layout.
  • Export as… to Postgres SQL, Markdown, Prisma or Drizzle. See export your schema.

Both are covered in build or edit a schema by hand.

View this page as plain markdown