ShippedManage your app
Connect databases and app settings
Give your app persistent data without tying it to one release.
Plan a managed database
Ask your agent to inspect the app and plan the database it needs. The current managed resource path supports PostgreSQL. Review the resource plan before deploying.
Resources shows provisioning state and database identity without exposing credentials. The runtime receives the approved connection binding. Database data is retained independently of application releases.
Keep configuration separate
Keep secrets out of your app source and source upload. Ask the operator to provision required secret bindings for the current approved environment; the portal does not yet provide a general secret editor.
When you create staging, configure test settings and resources for that project. Shipped does not automatically duplicate production credentials or customer data.
Review database changes
Run schema changes through your app’s supported migration process. Check compatibility with the release that remains live during an update.
Restoring a previous application image leaves the database as it is. Backups and a data recovery procedure are needed when a schema change cannot be reversed safely.