We handle
- Engine configuration, autovacuum tuning, patching, and upgrades
- Backups, retention, restores, and dump exports
- Extension installation and upgrade compatibility review
- Storage capacity and connection limit management
Managed PostgreSQL
A PostgreSQL database with extensions, backups, and an operator.
What this tier is
PostgreSQL is our default recommendation for anything with interesting constraints, JSON documents, or full-text search. Running it well means paying attention to autovacuum, connection counts, and extension compatibility across upgrades, which is what you are buying here.
Extensions are available on request rather than universally pre-enabled, because every extension is a constraint on future version upgrades. We would rather have a short conversation than surprise you at upgrade time.
Specification
| Engine | PostgreSQL, current stable release |
|---|---|
| Storage | 5 GB, expandable |
| Connections | 25 concurrent |
| Extensions | Available on request, reviewed for upgrade impact |
| Access | Private in-cluster hostname; restricted external on request |
| Backups | Daily logical dump, 14-day retention |
| Restores | Operator-performed, restore point confirmed first |
| Upgrades | Major versions rehearsed before they are applied |
What is included
- Dedicated database and role with scoped privileges
- Extensions on request, including pgcrypto, uuid-ossp, and full-text tooling
- Autovacuum tuned for the tier and monitored
- Private in-cluster hostname; restricted external access on request
- Daily logical dump, fourteen-day retention
- Operator-assisted restore, dump export, and migration
- Major version upgrades planned with you, with a rehearsal
Typical use cases
- A Django, Rails, or Node application that expects PostgreSQL
- Workloads using JSONB, full-text search, or geospatial data
- Moving off a hosted database whose pricing scales faster than the data
- An analytics or reporting store separate from the transactional database
Responsibility split
Written down so there is no argument about it later.
You handle
- Schema, indexes, and query plans
- Connection pooling on the application side
- Telling us which extensions you depend on before you depend on them
How provisioning works
Operator-provisioned, usually same business day. Extension requests are confirmed before the database is handed over so nothing changes underneath you.
Order
Other tiers in Applications and databases
Entry
Application Starter
One application container and one managed database, wired together.
$19 /mo
- Application container plus a managed database schema
- Private in-cluster networking to the data tier
- Daily database backup with a fourteen-day restore window
View details
Redundant application instances, a larger database, and a change process.
$59 /mo
- Multiple replicas behind health checks with rolling deploys
- Larger managed database with point-in-time restore requests
- Staging environment matching production configuration
View details
A dedicated schema on our data tier, backed up and patched by us.
$8 /mo
- Dedicated schema and credentials, not a shared database
- Daily logical backup with a fourteen-day restore window
- Engine patching coordinated with you in advance
View details
A Redis-compatible cache with an eviction policy you chose on purpose.
$6 /mo
- Dedicated instance, not a shared keyspace
- Eviction policy and memory ceiling agreed at provisioning
- Private in-cluster access, never exposed publicly
View details