Data and recovery

Understand which data your project uses and which recovery point you are about to apply. Code, Postgres, and files are distinct parts of the application.

Choose the right store

Code-running templates receive Postgres connection settings. Static sites do not get a database. Follow the Postgres recipe for schema migrations and database access.

Use S3-compatible object storage for uploads and durable app files. Follow the file upload recipe. Do not treat a container's writable layer as a backup of your data.

Read usage at the right scope

The console's Usage area shows account resource measurements. Database usage has a soft allowance; file storage has an enforced limit. Measurements can lag recent writes. A member of a shared project cannot read the owner's account-wide resource totals. An unavailable measurement is not zero.

Review recovery points

Open the project's Data & recovery section. Check the channel and timestamp, whether code was recorded, and whether the file checkpoint is aligned with the database checkpoint. A checkpoint without an aligned file marker does not represent an atomic restore of the whole app.

Nightly snapshot retention differs by plan. Pre-deploy recovery points use a separate count policy. Read the current backup policy before relying on a particular recovery window.

Restore with an exact target

Database and file restores retain their own confirmation and permission rules. Review the project, channel, source checkpoint, and impact on current data. Copying a restore command is not approval to execute it.

After a restore, verify the application's behavior and its data. Deploying old code alone does not restore the database. See Deployments.

Export and download

Use the project's Exports page from Data & recovery for supported takeout flows. Checkpoint downloads and exports can have different availability and size restrictions. A disabled feature, unavailable archive, or incomplete export must not be treated as a successful backup.

Read the export reference for the operation's scope, status, and result. Keep downloaded data and credentials out of public bug reports.