- Organisation
- Nubank
- Predecessor
- Self-managed PostgreSQL 14.17 with 7.5 TB, more than 31 billion rows and a three-instance topology
- Destination
- Amazon Aurora PostgreSQL-Compatible Edition 14.17
- Workload
- NuPay checkout, payments, refunds, settlement, back-office APIs, background jobs and event consumers
- Stage
- Completed NuPay database migration
- Retirement status
- The named self-managed NuPay PostgreSQL topology was migrated; wider Nubank database retirement is not claimed.
- Confidence
- High
- Next trigger
- A later Aurora expansion or retirement statement for additional Nubank workloads.
Programme context
Nubank completed the production migration of NuPay's mission-critical PostgreSQL estate to Amazon Aurora PostgreSQL.
Why this matters: The record identifies a named organisation, an explicit predecessor and destination platform, and a bounded workload and lifecycle stage.
Migration timeline
| Date or stage | Milestone | What changed | Evidence status |
|---|---|---|---|
| Preparation | Migration milestone | Nubank designed a constrained migration sequence for the three-instance topology. | Source-stated implementation |
| Three-hour window | Migration milestone | Three database migrations completed within a three-hour total window. | Source-stated cutover window |
| 21 Jul 2026 | Migration milestone | AWS and Nubank published the technical account. | Dated primary evidence |
Workload migration matrix
| Workload | Predecessor | Destination | Status by 23 Jul 2026 |
|---|---|---|---|
| NuPay checkout, payments, refunds, settlement, back-office APIs, background jobs and event consumers | Self-managed PostgreSQL 14.17 with 7.5 TB, more than 31 billion rows and a three-instance topology | Amazon Aurora PostgreSQL-Compatible Edition 14.17 | Completed NuPay database migration |
Implementation and architecture
- AWS Database Migration Service supported the move.
- The largest constraint period lasted one hour and seven minutes.
- Zero-data-loss and minimal-downtime statements remain attributed source claims.
Known unknowns and contradictions
- The exact calendar date of the production cutover.
- Any residual self-managed PostgreSQL dependencies outside NuPay.
- The wider Nubank database migration roadmap.
No missing fact is inferred to broaden the source-supported migration claim.
PlatformTrace analysis
The source supports completion for the named NuPay payment workload, not every Nubank database or banking application.
Performance, cost, uptime and operational outcomes remain attributed source claims unless independently stated otherwise.
Evidence ledger
- AWS Database Blog, 21 July 2026
Technical account co-authored by Nubank engineers identifying the 7.5 TB estate, 31 billion rows, Aurora target and completed production migration.
Corrections and updates
23 July 2026 — Initial Verified dossier published from the complete five-lane overnight intake and corrected central adjudication. Later milestones will be appended rather than silently replacing this state.