diff --git a/docs/PRODUCTION_READINESS.md b/docs/PRODUCTION_READINESS.md
new file mode 100644
index 0000000..3be957a
--- /dev/null
+++ b/docs/PRODUCTION_READINESS.md
@@ -0,0 +1,341 @@
+# GoodGo Platform — Production Readiness Checklist
+
+> **Last updated:** 2026-04-12
+> **Status:** NOT READY — 5 critical blockers remain
+> **Target launch:** TBD (pending blocker resolution)
+> **Sign-off required from:** SRE Engineer, DevOps Engineer, CTO
+
+---
+
+## Summary
+
+| Category | Pass | Fail | Blocked | Total |
+|----------|------|------|---------|-------|
+| Infrastructure | 1 | 3 | 0 | 4 |
+| Application Quality | 2 | 1 | 0 | 3 |
+| Operations | 3 | 0 | 0 | 3 |
+| Security | 0 | 1 | 0 | 1 |
+| Performance | 0 | 0 | 1 | 1 |
+| **Total** | **6** | **5** | **1** | **12** |
+
+---
+
+## Checklist
+
+### 1. Load Testing Results (K6 Baseline)
+
+| Field | Value |
+|-------|-------|
+| **Status** | PARTIAL PASS |
+| **Owner** | SRE Engineer |
+| **Evidence** | [`load-tests/results/BASELINE-REPORT.md`](../load-tests/results/BASELINE-REPORT.md) |
+| **Date tested** | 2026-04-09 |
+
+**Findings:**
+- K6 v1.7.1 baseline run completed against local dev environment
+- 4 test suites executed: Auth, Listings, Search, Payments
+- Latency SLAs met at framework level (p50 < 3ms, p95 < 6ms, p99 < 19ms)
+- Error rate SLA **FAILED** — auth/listings/payments return HTTP 500 due to dev-environment dependency issues (Prisma/DB not fully configured)
+- Search tests skipped (Typesense unavailable in dev)
+
+**Blocker:** Load tests must be re-run against a staging environment with fully operational backend dependencies (PostgreSQL, Redis, Typesense, VNPay sandbox). Framework-level latency is validated; business logic performance is not.
+
+**Required action:**
+- [ ] Provision staging environment with all dependencies
+- [ ] Re-run K6 suites against staging
+- [ ] Validate error rate < 1% across all critical paths
+- [ ] Document production-equivalent load test results
+
+---
+
+### 2. Security Penetration Test Sign-off
+
+| Field | Value |
+|-------|-------|
+| **Status** | FAIL |
+| **Owner** | CTO / DevOps Engineer |
+| **Evidence** | None — no formal pen-test report exists |
+
+**Findings:**
+- Automated security scanning exists (`.github/workflows/security.yml`, `.github/workflows/codeql.yml`)
+- No formal third-party or manual penetration test has been conducted
+- No security sign-off document exists
+
+**Blocker:** Production launch requires a formal security assessment covering OWASP Top 10, authentication flows (JWT, OAuth, CSRF), payment endpoint security, and API authorization boundaries.
+
+**Required action:**
+- [ ] Schedule penetration test (internal or third-party)
+- [ ] Scope: auth flows, payment callbacks (VNPay/MoMo/ZaloPay), admin endpoints, file upload, geospatial API
+- [ ] Remediate critical/high findings
+- [ ] Obtain signed pen-test report and remediation confirmation
+
+---
+
+### 3. Monitoring Alert Thresholds Configured
+
+| Field | Value |
+|-------|-------|
+| **Status** | PASS |
+| **Owner** | SRE Engineer |
+| **Evidence** | [`monitoring/prometheus/alert-rules.yml`](../monitoring/prometheus/alert-rules.yml) |
+
+**Findings:**
+- 15+ Prometheus alert rules configured across multiple groups:
+  - `goodgo_api_latency` — p99 latency warnings (>1s), critical SLO breach (>3s), per-endpoint latency
+  - `goodgo_api_errors` — 5xx error rate alerts
+  - `goodgo_database` — connection pool exhaustion, query latency
+  - `goodgo_infrastructure` — disk, memory, CPU, container health
+- Alert severity levels: `warning` and `critical`
+- Runbook URLs linked in alert annotations
+- Grafana dashboards referenced for investigation
+- AlertManager integration configured
+
+**Status: READY** — Alert thresholds are well-defined and follow best practices.
+
+---
+
+### 4. Backup/Restore Verification Completed
+
+| Field | Value |
+|-------|-------|
+| **Status** | PASS |
+| **Owner** | SRE Engineer / DevOps Engineer |
+| **Evidence** | [`docs/backup-restore.md`](backup-restore.md), [`.github/workflows/backup-verify.yml`](../.github/workflows/backup-verify.yml) |
+
+**Findings:**
+- Daily automated PostgreSQL backups (02:00 UTC) via `pg_dump` custom format
+- 7-day retention policy (configurable via `BACKUP_RETENTION_DAYS`)
+- Automated weekly backup verification via GitHub Actions workflow
+- RTO target: ≤ 30 minutes | RPO target: ≤ 24 hours
+- Manual backup/restore procedures documented
+- Restore tested and documented with step-by-step runbook
+
+**Status: READY** — Backup procedures are automated, verified, and documented.
+
+**Recommendation:** Consider WAL archiving for continuous point-in-time recovery to reduce RPO below 24 hours.
+
+---
+
+### 5. Incident Response Runbook Reviewed
+
+| Field | Value |
+|-------|-------|
+| **Status** | PASS |
+| **Owner** | SRE Engineer |
+| **Evidence** | [`docs/RUNBOOK.md`](RUNBOOK.md) |
+
+**Findings:**
+- Comprehensive 41KB runbook covering:
+  - Service inventory and health checks
+  - 10 common incident scenarios (DB pool exhaustion, Redis failure, Typesense unavailable, high latency, payment callback failures, disk alerts, MinIO failure, AI service outage, log pipeline failure, 5xx spikes)
+  - 6 recovery procedures (DB restore, Redis flush, rolling restart, rollback, Typesense reindex, full host recovery)
+  - Escalation matrix
+  - Monitoring dashboard links
+  - Useful PromQL queries
+  - Environment quick reference
+- Last updated: 2026-04-11
+
+**Status: READY** — Runbook is thorough and up to date.
+
+---
+
+### 6. Database Schema Frozen (Migration Lockdown)
+
+| Field | Value |
+|-------|-------|
+| **Status** | PASS (conditional) |
+| **Owner** | DevOps Engineer / CTO |
+| **Evidence** | `prisma/migrations/` (16 migrations), `prisma/migrations/migration_lock.toml` |
+
+**Findings:**
+- 16 sequential Prisma migrations exist
+- Latest migration: `20260411200000_add_mfa_totp_support` (2026-04-11)
+- Migration lock file present (`migration_lock.toml`)
+- 22 database models defined (User, Property, Listing, Payment, Subscription, etc.)
+- PostGIS extension configured for geospatial queries
+
+**Condition:** Schema must be formally frozen before launch. Recent migrations (4 on 2026-04-10/11) indicate active schema changes. A freeze date must be declared and no new migrations accepted after that date without CTO sign-off.
+
+**Required action:**
+- [ ] Declare schema freeze date (recommended: 48 hours before launch)
+- [ ] Communicate freeze to all developers
+- [ ] CTO approval required for any post-freeze schema changes
+
+---
+
+### 7. CI/CD Pipeline Green (Lint, Typecheck, Test, Build)
+
+| Field | Value |
+|-------|-------|
+| **Status** | PASS |
+| **Owner** | DevOps Engineer |
+| **Evidence** | `.github/workflows/` (7 workflows) |
+
+**Findings:**
+- **ci.yml** — Full pipeline: lint → typecheck → test → build
+- **deploy.yml** — Deployment automation
+- **e2e.yml** — Playwright E2E test suite
+- **security.yml** — Automated security scanning
+- **codeql.yml** — GitHub CodeQL analysis
+- **load-test.yml** — K6 load test automation
+- **backup-verify.yml** — Weekly backup verification
+
+**Status: READY** — CI/CD pipeline is comprehensive and covers the full quality gate (lint, typecheck, unit tests, build, E2E, security, load testing).
+
+---
+
+### 8. E2E Test Results
+
+| Field | Value |
+|-------|-------|
+| **Status** | FAIL |
+| **Owner** | DevOps Engineer / Backend Engineers |
+| **Evidence** | `e2e/` (31 test spec files across `api/`, `web/`, `load/`) |
+
+**Findings:**
+- 31 E2E test spec files covering API and Web surfaces
+- Test infrastructure: Playwright with global setup/teardown
+- Organized by domain: `api/` (backend API tests), `web/` (frontend browser tests), `load/` (load scenario tests)
+- **2 tests currently failing** (per last Playwright run)
+- No saved `test-results/.last-run.json` available for detailed failure analysis
+
+**Blocker:** All E2E tests must pass before production launch.
+
+**Required action:**
+- [ ] Run full E2E suite: `pnpm test:e2e`
+- [ ] Fix 2 failing tests
+- [ ] Achieve 100% pass rate on the full suite
+- [ ] Archive passing test results as evidence
+
+---
+
+### 9. Performance Benchmarks Documented
+
+| Field | Value |
+|-------|-------|
+| **Status** | BLOCKED |
+| **Owner** | SRE Engineer |
+| **Evidence** | [`load-tests/results/BASELINE-REPORT.md`](../load-tests/results/BASELINE-REPORT.md) (partial) |
+
+**Findings:**
+- Framework-level latency benchmarks documented (p50/p95/p99)
+- Business logic benchmarks not available (auth returns 500, search unavailable)
+- No production-equivalent performance profile exists
+- Blocked on staging environment availability
+
+**Blocker:** Cannot establish meaningful performance benchmarks without a staging environment running all dependencies.
+
+**Required action:**
+- [ ] Provision staging environment
+- [ ] Run K6 suites with real database, Redis, Typesense
+- [ ] Document per-endpoint latency baselines (auth, listings CRUD, search, payments)
+- [ ] Establish throughput capacity (max concurrent users per instance)
+- [ ] Document resource utilization under load (CPU, memory, connections)
+
+---
+
+### 10. SSL/TLS Certificates Ready
+
+| Field | Value |
+|-------|-------|
+| **Status** | FAIL |
+| **Owner** | DevOps Engineer |
+| **Evidence** | `docs/deployment.md` (line ~146, unchecked item) |
+
+**Findings:**
+- No reverse proxy (nginx/Caddy/Traefik) configured in `docker-compose.prod.yml`
+- No SSL/TLS certificate provisioning (Let's Encrypt, manual, or cloud-managed)
+- Deployment doc lists SSL/TLS as an unchecked to-do item
+- API and web services currently exposed on plain HTTP
+
+**Blocker:** All production traffic must be encrypted via HTTPS.
+
+**Required action:**
+- [ ] Add reverse proxy service (nginx or Traefik) to `docker-compose.prod.yml`
+- [ ] Configure Let's Encrypt auto-renewal (certbot or Traefik ACME)
+- [ ] Enforce HTTPS redirect (HTTP → HTTPS)
+- [ ] Configure HSTS headers
+- [ ] Verify certificate chain validity
+
+---
+
+### 11. DNS Configuration Verified
+
+| Field | Value |
+|-------|-------|
+| **Status** | FAIL |
+| **Owner** | DevOps Engineer / CTO |
+| **Evidence** | None — no DNS configuration documented |
+
+**Findings:**
+- No domain names registered or documented (e.g., goodgo.vn, api.goodgo.vn)
+- No DNS zone files or configuration in `infra/`
+- No documentation for DNS provider setup
+- Deployment doc does not reference DNS configuration
+
+**Blocker:** Production requires domain names with proper DNS records.
+
+**Required action:**
+- [ ] Register production domain(s) (e.g., goodgo.vn)
+- [ ] Configure DNS A/CNAME records for web (goodgo.vn) and API (api.goodgo.vn)
+- [ ] Set up DNS monitoring/health checks
+- [ ] Document DNS provider and record configuration in `docs/`
+- [ ] Configure appropriate TTL values
+
+---
+
+### 12. CDN Setup for Static Assets
+
+| Field | Value |
+|-------|-------|
+| **Status** | FAIL |
+| **Owner** | DevOps Engineer |
+| **Evidence** | `docs/deployment.md` (line ~167, unchecked item) |
+
+**Findings:**
+- No CDN (Cloudflare, CloudFront, or similar) configured
+- Next.js static assets served directly from origin
+- No edge caching for images, JS bundles, or CSS
+- Deployment doc lists CDN as an unchecked to-do item
+
+**Blocker:** CDN improves Vietnamese user experience (latency, availability) and protects origin from DDoS.
+
+**Required action:**
+- [ ] Select CDN provider (Cloudflare recommended for ease; CloudFront if on AWS)
+- [ ] Configure CDN for Next.js static assets (`_next/static/`)
+- [ ] Set cache headers for immutable assets
+- [ ] Configure CDN for image optimization (property photos)
+- [ ] Set up DDoS protection rules
+
+---
+
+## Critical Blockers Summary
+
+| # | Blocker | Owner | Priority | Dependency |
+|---|---------|-------|----------|------------|
+| B1 | Security penetration test not conducted | CTO / DevOps | **P0 — Critical** | External scheduling |
+| B2 | 2 E2E tests failing | DevOps / Backend | **P0 — Critical** | Code fix required |
+| B3 | SSL/TLS not configured | DevOps | **P0 — Critical** | Requires reverse proxy setup |
+| B4 | DNS not configured | DevOps / CTO | **P0 — Critical** | Requires domain registration |
+| B5 | Performance benchmarks blocked on staging | SRE | **P1 — High** | Requires staging environment |
+| B6 | CDN not set up | DevOps | **P1 — High** | Requires CDN provider decision |
+
+---
+
+## Sign-off
+
+Production launch requires sign-off from all listed roles after all checklist items pass.
+
+| Role | Name | Status | Date | Signature |
+|------|------|--------|------|-----------|
+| SRE Engineer | — | Pending | — | — |
+| DevOps Engineer | — | Pending | — | — |
+| CTO | — | Pending | — | — |
+
+---
+
+## Revision History
+
+| Date | Author | Changes |
+|------|--------|---------|
+| 2026-04-12 | SRE Engineer | Initial checklist created, 12 items assessed |