A schema you can rely on
Transactions, constraints and foreign keys help preserve relationships as your application grows.
Read the official guideAll database engines
Managed PostgreSQL
Managed PostgreSQLRelational where it matters. Flexible where you need it.
Keep your orders, accounts and application state in relational tables. Use JSONB for the fields that do not fit one fixed shape. PostgreSQL lets both live behind the same SQL connection.
PostgreSQL / a familiar starting pointSELECT account_id, SUM(total) AS revenue
FROM orders
WHERE status = 'paid'
GROUP BY account_id
ORDER BY revenue DESC;Working with PostgreSQL
Choose it for the work
it does well.
Documents alongside tables
Query JSONB values and index the paths your application actually searches.
Read the official guideIndexes for the workload
Explore B-tree, GIN and other index types. Choose based on your queries, not just your table size.
Read the official guideWhere it fits.
Application backends, SaaS products and reporting that benefits from joins and flexible data types.
Before you choose
Extensions and major-version compatibility need checking before migration. Remote read replicas can lag; they do not automatically become writers.
Your database.
The server work, covered.
The workspace brings connections, access and recovery together. Your application keeps its standard database client.
Connect with confidence
Find your endpoint, port, credentials and certificate together, with examples for standard clients.
Control who gets in
Set allowed IPs and give applications separate users. Review permissions before opening access.
Keep recovery separate
Full backups and recovery logs are stored off-server. Your workspace shows completed coverage.
Give PostgreSQL its own workspace.
Choose a published node type, region and storage. Review your monthly total before checkout.