Choose capacity for your data
Give the database its own memory, CPU allocation and persistent storage. Database resources are separate from your application instance.
PostgreSQL
A solid foundation
for your application.
Keep your application data in PostgreSQL, alongside the services that use it. Choose a resource plan, connect privately and manage backups from your console.
Your code. Infrastructure included.
app-db / PostgreSQL
SELECT id, name FROM ideas;
| id | name | state |
|---|---|---|
| 01 | the next big thing | building |
| 02 | weekend project | growing |
| 03 | something useful | ready |
A little peace of mind.Daily backups · 7-day default retention
Private accessConnect from your Openstead services
Persistent dataStorage independent of the container
Daily backupsWith configurable retention
POSTGRESQL ON OPENSTEAD
A familiar database. A connected workflow.
Use PostgreSQL through the clients and frameworks you know. Openstead handles provisioning and keeps connection details, resource controls and recovery tools together.
Keep database traffic private
Use the internal hostname and credentials from the console to connect services in the same environment. PostgreSQL does not expose a public database port.
Make recovery part of the routine
Use scheduled or manual logical backups. Inspect backup status and restore a selected backup into a separate database before reconnecting your application.
MADE FOR YOUR STACK
Your connection string is all your app needs.
Use the standard PostgreSQL connection details with your database library. Application code stays portable, and credentials stay in the service environment.
- Persistent database storage is provisioned with the plan.
- Daily backups use seven-day retention by default.
- Restores create a separate database with its own resources.
PostgreSQL with Djangoopenstead / configuration
APPLICATION EXAMPLEimport os
import dj_database_url
DATABASES = {
"default": dj_database_url.config(
default=os.environ["DATABASE_URL"],
conn_max_age=60,
)
}This example uses dj-database-url. Copy the actual private connection string from your database service.
PUT IT TO WORK
Built for the work
your application does.
Application records
Store accounts, subscriptions, orders and other relational data with PostgreSQL transactions and constraints.
Framework backends
Connect Django, Rails, Node.js and other applications through their standard PostgreSQL drivers.
Recovery and migration
Create logical backups, download exports and restore data into an isolated database for inspection.
HOW IT WORKS
Create it. Connect it. Keep your data moving.
Create the database
Choose PostgreSQL in your project, select an instance and set the database name and version.
Connect your application
Reveal the private connection details and add them to your service environment. Use your framework’s migration command to initialize the schema.
Manage and recover
Inspect database status, use the SQL tools and review backups. Restore a backup separately when you need to recover or examine data.
Can I connect directly from my laptop?
PostgreSQL connections are private to services in the same Openstead environment. Use the console’s database tools to inspect data, or run database commands from an authorized application service.
Is PostgreSQL included with my web service?
PostgreSQL is a separate service with its own resource plan and storage. Your project can contain both, and the console shows each service’s cost.
How do backups and restores work?
Openstead creates logical database backups on a daily schedule when backups are enabled. You can also create one manually. Restoring provisions a separate database, so you can check the result before changing your application connection.
Which database architecture do the plans use?
PostgreSQL plans run a single database instance with persistent storage. Backups provide a recovery path; they are not replicas or automatic failover.
MAKE YOUR NEXT MOVE
Give your application data a home.
Your code. Infrastructure included.