From a4f011c00acf4f9abb851cb2ad50ac12b1677bf3 Mon Sep 17 00:00:00 2001
From: Tamal Saha <tamal@appscode.com>
Date: Tue, 2 Jun 2026 21:44:55 +0600
Subject: [PATCH] Document Complete Transaction History with Point-in-Time
 Recovery

Adds a feature card and an in-depth page describing how KubeStash supports this capability.
---
 .../complete-transaction-history-pitr.md      | 21 +++++++++++++++++++
 data/products/kubestash.json                  | 13 ++++++++++++
 2 files changed, 34 insertions(+)
 create mode 100644 content/features/complete-transaction-history-pitr.md

diff --git a/content/features/complete-transaction-history-pitr.md b/content/features/complete-transaction-history-pitr.md
new file mode 100644
index 00000000..cbdd3eed
--- /dev/null
+++ b/content/features/complete-transaction-history-pitr.md
@@ -0,0 +1,21 @@
+---
+title: Complete Transaction History with Point-in-Time Recovery
+description: Complete transaction history database with point-in-time recovery (PITR) to any second.
+menu:
+  main:
+    parent: features
+    name: Complete Transaction History with Point-in-Time Recovery
+    weight: 60
+---
+
+# Complete Transaction History with Point-in-Time Recovery
+
+KubeStash maintains a complete transaction history database for supported engines (PostgreSQL, MySQL, MongoDB, and equivalents) by continuously archiving WAL, binlog, and engine-equivalent transaction logs. Combined with periodic base snapshots, this enables Point-in-Time Recovery (PITR) to any second within the retention window. The transaction log archive itself is the complete, queryable transaction history of record, which satisfies audit and regulatory requirements for transaction-level traceability without standing up a separate CDC pipeline.
+
+## Related concepts
+
+- [BackupConfiguration](/docs/latest/concepts/crds/backupconfiguration/)
+- [BackupBlueprint](/docs/latest/concepts/crds/backupblueprint/)
+- [RestoreSession](/docs/latest/concepts/crds/restoresession/)
+- [RetentionPolicy](/docs/latest/concepts/crds/retentionpolicy/)
+- [BackupVerifier](/docs/latest/concepts/crds/backupverifier/)
diff --git a/data/products/kubestash.json b/data/products/kubestash.json
index 804465f9..2d8f5686 100644
--- a/data/products/kubestash.json
+++ b/data/products/kubestash.json
@@ -168,6 +168,19 @@
       },
       "summary": "",
       "description": "Stash comes with native support for monitoring via Prometheus. You can use builtin Prometheus scrapper or CoreOS Prometheus Operator to monitor your database in Kubernetes. You can use the Grafana to view key operational metrics, including compute/memory/storage capacity utilization, I/O activity, and instance connections."
+    },
+    {
+      "title": "Complete Transaction History with Point-in-Time Recovery",
+      "image": {
+        "src": "/assets/images/addons/illustrations/declarative-api.png",
+        "alt": "http"
+      },
+      "icon": {
+        "src": "/assets/images/products/stash/features/declarative-api.svg",
+        "alt": "http"
+      },
+      "summary": "Complete transaction history database with point-in-time recovery (PITR) to any second.",
+      "description": "KubeStash maintains a complete transaction history database via continuous WAL (PostgreSQL) and binlog (MySQL) archiving. Combined with periodic base snapshots, this delivers Point-in-Time Recovery (PITR) to any second in the retention window. The transaction log archive is itself the complete transaction history of record."
     }
   ],
   "versions": [