Each Orbit app has its own Postgres database, rather than rows inside a database table shared with other apps.

## The database stores your app's records

Your data model describes the tables, fields, and links your app needs. The database holds the records that use that structure.

For example, a client request app can have a `requests` entity with a title and a status. A request titled *Replace the lobby sign* is one record. These names are an example, not built-in entities.

A page can display that request, but the page is not where the record lives. See [Entities and records](/concepts/entities-and-records) for the difference between the structure and the stored values.

## Records survive a deployment

[Orbit's product overview](https://orbitapps.io/) states that your rows survive a deployment. You do not need to recreate the example request because you deploy a new page layout.

Data persistence does not prove that a changed page reads or writes the correct fields. Test the page after a change.

## Database isolation is not a user access rule

A database for one app separates that app's storage from other apps. That separation does not define which people can read a request within your app.

For the example request, decide whether every signed-in person can read it or only the person who submitted it. Check that rule with separate test accounts before you add private client information.

[Authentication](/features/authentication) explains the difference between sign-in and access to private pages and records.

## Check the model and the app separately

Use the [Data Model workspace](/features/data-model-workspace) to inspect the tables, fields, and links.

Then [review the app before launch](/guides/review-an-app-before-launch). For the example request, confirm that the title and status remain correct when you reopen the app. Test who can read and change the request separately.

A correct model does not prove that the app's pages use the model correctly.