M
MVP DB
Platform Facts

Architecture &
Guarantees

No marketing fluff. Just the raw details of how MVP-DB isolates your workloads, handles backups, and keeps your projects alive.

01. Hosting & Infrastructure

Region: All databases are provisioned in eu-central-1 (Frankfurt, Germany) to provide optimal latency across Europe and acceptable latency globally.

Engine: We deploy pure PostgreSQL 17 with native extensions enabled (including pgvector and PostGIS). No custom forks.

Provider: While you do not need an AWS account or DevOps expertise, our control plane and compute nodes run on Amazon Web Services (AWS) using EC2, EBS throughput-optimized storage, and Lambda for connection-less orchestration.

02. Tenant Isolation Model

To offer flat-rate pricing without cold starts or compute units, we utilize a Schema-Level Virtual Database model.

This means your database lives on a shared cluster, highly isolated via Postgres schema scoping and strict IAM role bindings. We operate a massive internal PgBouncer pooler and allocate explicit concurrent connection caps depending on your plan.

Noisy Neighbor Guardrails

Our centralized Warden polling service constantly assesses compute resources and storage bytes. If you exceed your storage quota, writes will be strictly paused to prevent cluster abuse while reads will remain operational.

03. Backups & Restore

Automated Dumps: We execute full automated logical backups via pg_dump daily at 03:00 UTC. Retention windows vary by plan: 7 days on Starter and Builder, 30 days on Pro.

Self-Serve Restore Workflow

  1. 01. Open Backups — In the database detail view, open the Backups tab to see retained daily backups for that database.
  2. 02. Download or Restore — You can download a backup directly or trigger Restore from a specific retained backup.
  3. 03. Restore queues asynchronously — The restore request is queued and processed by the control plane. No support ticket required for the standard restore path.
  4. 04. Connections replaced cleanly — Active connections are terminated, current data is replaced with the selected backup, and the database comes back on the same connection endpoint.

There is no formal restore SLA. Restores are best-effort and typically complete within a few minutes. Customers are responsible for maintaining independent backups of critical data.

Create Database - $3/mo