ShippedPostgreSQL
Keep application records in a database built for them. Shipped connects PostgreSQL to your services and manages its hosting.
Connect your app to its database
Add PostgreSQL to your project and bind it to the application services that need access. Keep connection credentials in protected configuration and use separate databases for staging and production. Your application can continue using its PostgreSQL driver, query library, or ORM, with migrations tracked as part of the application’s release process.
Grow the database on its own
A busy database does not always mean the web server needs a larger plan. Review database capacity, connections, and workload needs separately from application compute. Choose a compatible pooled or dedicated database tier and review the migration plan before changing it, including any connection changes, overlap costs, and interruption the move may require.
Treat recovery as a data operation
Use backups and a deliberate restore process to recover database state. Restoring an application release does not undo a schema migration or bring back a deleted record. Keep migrations compatible with the releases you may need to restore, and verify your application against recovered data before treating a database restore as complete.
A little more detail
Questions about PostgreSQL?
Does a dedicated app server include a dedicated database?
No. Application compute and PostgreSQL are separate resources. Choose a dedicated database tier when the database needs that capacity or isolation, independently of where the application server runs.
Does rolling back my app also roll back its database?
No. Application rollback restores a compatible application release. Database restore is a separate operation that must account for migrations, current records, and writes made since the recovery point.
Backups
Use backups and deliberate restores for Shipped data services. Understand recovery points, retained data, and the difference between restore and rollback.
Explore BackupsRollbacks
Restore a recorded application build in Shipped with release history and health checks, while keeping database recovery a separate deliberate operation.
Explore RollbacksStaging and production
Use separate staging and production environments in Shipped, each with its own services, data, secrets, addresses, and resource usage.
Explore Staging and production
Rails
Ship Ruby on Rails applications with PostgreSQL, job workers, file storage, email, and production configuration on Shipped.
Explore RailsFrom your workspace to the web