Product Overview

Create Recoverable Copies of Critical Data

PeppyKeep is a backup and recovery tool for critical data and business systems. With timeline-based versions, multiple replicas, and recovery drills, it helps organizations, teams, and individuals build backups they can actually recover—not just unverified file copies.

PeppyKeep is suitable as a standalone backup tool, or as a backup, synchronization, and recovery verification tool outside the business system, reducing the impact of accidental deletion, equipment failure, configuration damage, service abnormalities, and operational errors.

What Problems It Solves

Copying files or writing them to a backup disk does not guarantee recoverability. Common risks include:

• Incomplete backup scope, missing configuration file, business file or database;
• The backup file exists, but there is no clear point in time and version relationship;
• There is only one copy that cannot be retrieved after a device or storage failure;
• Missing encryption key, database connection or recovery dependency;
• The backup task shows success, but the real recovery process has never been verified.

PeppyKeep brings backup scope, configuration, versions, replicas, and recovery validation into one traceable workflow, so you can answer the key questions: what was backed up, when, where it is stored, and whether it can be recovered.

The Full Backup-to-Recovery Lifecycle

1. Select the critical data, application directories, configuration files, or databases you need to protect.
2. Use a configuration template to define the backup scope, exclude rules, destinations, schedule, and retention policy.
3. Run a dry run first to verify paths, permissions, connections, keys, and the planned output.
4. Create versioned backups on a timeline and save them locally or to multiple independent replicas.
5. Regularly check backup results and download or decrypt actual restore points.
6. Run recovery drills in an isolated environment to verify that files, databases, application configuration, and critical dependencies are usable.
7. Use drill results to refine the backup scope, number of retained versions, cleanup rules, and recovery runbook.

Core Capabilities

• File and directory backup: Create recoverable copies of critical data, application directories, configuration files, and business files.
• Database backup: Back up MySQL and other databases; combine with application files for a complete restore point.
• Universal application-aware backup: For business systems with well-defined data layout and recovery dependencies—for example MySQL-backed apps. Keeps databases, application files, configuration, and dependencies on one timeline.
• Dedicated application-aware backup: For app-specific data models and sync semantics—work assets, AI Agent DB/config, design files, customer data, and more—with additional app types planned.
• Timeline and versioning: Each backup keeps a clear timestamp, config revision, and restore point so you can pick the right version to restore.
• Multiple replicas and retention: Local copies, object storage, cloud drives, and multi-site replica strategies using your existing infrastructure.
• Encryption and key management: Customer-managed keys for encrypted backups; public keys encrypt backups, private keys and passphrases stay under your control.
• Large files and directories: Split archives, checksums, and task state for datasets too large for a single bundle.
• Recovery validation and drills: Verify download, decrypt, unpack, DB import, file integrity, and app dependencies—not just job success.
• Shift-left risk checks: dry-run, structural validation, coverage reports, and audit logs to surface gaps before they bite.

Use Cases

• Protection of the core business data, profiles and work results of the enterprise or team;
• File or directory backups, and restores after accidental deletion of files, directories, or historical configurations;
• The database and application files need to be backed up by the business system in the same timeline;
• Universal application-aware backup—for example MySQL-backed business systems;
• Dedicated application-aware backup—for work assets, AI Agent DB/config, design files, and customer data;
• An environment that requires multiple backup copies to be retained across devices, nodes, or locations;
• Teams that need to regularly validate real recovery links, meet internal audit or disaster preparedness requirements;
• Large files, large directories, encrypted backups and volume transfer scenarios;
• Teams who want a standalone tool to perform backup, synchronization, and recovery drills.

Capability tiers

See the PeppyKeep website for current subscription details and feature availability.

Platforms and deployment

The PeppyKeep CLI runs on Windows, macOS, and Linux. The desktop UI is in development for Windows and macOS (no Linux desktop app); Linux is CLI-only but can be managed from Windows or macOS desktop clients. See Desktop UI.

Product scope

PeppyKeep does not currently offer managed storage. Users are responsible for their own selection and management of local disks, network disks, S3-compatible object storage, or other destinations, and for their capacity, permissions, availability, retention policies, and security configurations.

PeppyKeep is responsible for the execution of backup tasks, transfer orchestration, version management, and recovery verification, and does not replace storage services, the business system’s own high-availability mechanisms, application health checks, or full disaster recovery switching processes. Encrypted private keys and passwords are kept by the user and may not be recoverable if lost.

Start with One Critical Data Set

Select a device or critical data first, use the configuration template to complete a backup, recovery, and verification, and then gradually expand to more systems and backup copies. It is recommended to perform a dry-run and recovery drill on the tester to confirm the configuration, permissions, key, and recovery path before applying it to the production environment or critical data.

Install and get started · Backup and restore scenarios · Visit PeppyKeep