Private database boundary
Each Managed App Starter pair uses a dedicated PostgreSQL 16 VM on the tenant-private network. PostgreSQL listens on loopback and the tenant-private address, not the public Internet or the platform management address.
Managed PostgreSQL
The database is managed as a private dependency of Managed App Starter.
DotMoose does not currently sell standalone Managed PostgreSQL. This guide documents the database capability that is actually launched inside the paired application product.
TLS and SCRAM authentication
The application reaches PostgreSQL over TLS and uses SCRAM password authentication. Cross-tenant database traffic is denied by the platform network boundary; Gate 10P proved both directions with negative tests.
Logical backup and restore evidence
The current protection path creates daily logical backups with a 35-day retention policy and a 24-hour target recovery-point objective. The restore verifier checks the archive and restores it into a disposable database before treating the protection path as healthy.
PostgreSQL’s own documentation distinguishes SQL dumps, filesystem backups and continuous archiving. DotMoose’s current Starter product uses the logical-dump path; it must not be described as continuous-archiving/PITR.
No standalone sale, HA or PITR claim
Standalone Managed PostgreSQL remains deliberately private/non-public. The paired Starter database is single-node/non-HA, and DotMoose does not claim point-in-time recovery or an uptime SLA unless separately implemented and agreed.
Managed PostgreSQL stays paired with the application
The database follows the Managed App service lifecycle, including provisioning, suspension, retention, recovery and final deletion. It is not sold as a separate database-only account.