ForgeRecoveryForgeRecovery backs up all Forge data continuously — machine configs, CAD models, schematics, PM records, compliance documents. Every backup package is Ed25519-signed and SHA-256 verified. Point-in-time restore to any second in the last 30 days. Air-gapped backup targets for ITAR environments. RTO under 4 hours for a full suite restore.
Why ForgeRecovery is different
"Recovery time objective under 4 hours — for a full restore of all Forge data, not just a single database."
ForgeRecovery coordinates restore across all Forge products simultaneously. Machine configs, CAD models, schematics, PM records, compliance documents — all restored in parallel from a single point-in-time snapshot. The 4-hour RTO covers a complete facility data loss scenario, not a single-table restore. Measured from restore-initiated to Forge products operational.
"Cryptographic integrity verification means you know a backup is valid before you need it — not after."
Every backup package is SHA-256 hashed per file and Ed25519-signed at the package level. ForgeRecovery verifies the signature on every scheduled verification run and on every restore attempt. A tampered or corrupted backup is detected before restore begins. Verification results are logged to ForgeCompliance as audit evidence.
"Air-gapped backup targets keep your data off the network — for ITAR and defense environments where cloud backup is not an option."
ForgeRecovery writes to any S3-compatible endpoint, NAS share, or tape library. Air-gapped targets — no network connection to the backup destination — are supported for ITAR-controlled facilities. Backup packages are encrypted at AES-256-GCM before leaving the host. The decryption key never touches the backup target.
ForgeRecovery runs without operator attention. The first time you need it, it works — because integrity has been verified every day since the backup was taken.
ForgeRecovery captures incremental snapshots from all Forge products every 15 minutes. Machine configs, CAD model revisions, schematics, PM records, compliance documents, and event logs.
Every backup package is SHA-256 hashed and Ed25519-signed. ForgeRecovery runs a verification pass daily: checks signature validity, confirms hash integrity for every file. Verification results logged to ForgeCompliance.
Retention policy: 15-minute snapshots for 48 hours, hourly for 30 days, daily for 12 months. Configurable. Expired snapshots are purged after cryptographic deletion — overwritten, not just unlinked.
Select a point in time. ForgeRecovery locates the nearest snapshot, verifies integrity, and begins parallel restore across all Forge products. Progress shown per product. Estimated completion time displayed from the first restore request.
Post-restore, ForgeRecovery runs a consistency check: event log continuity, machine config checksums, CAD model revision integrity. Pass/fail logged. If any check fails, the restore is flagged and the prior restore point is offered.
Every Forge product's data — machine configs, CAD models, schematics, PM records, compliance docs, decision log, event log. Continuous snapshots with 15-minute interval.
Ed25519-signed packages. SHA-256 hashes per file. Verified daily and on every restore. A corrupted or tampered backup is detected before restore begins.
15-minute for 48 hours. Hourly for 30 days. Daily for 12 months. Monthly for 7 years. Configurable. Expired snapshots are cryptographically deleted.
S3-compatible (MinIO), NAS (SMB/NFS), or LTO tape. Encrypted packages — the backup target sees opaque blobs. Decryption key never leaves the source host.
Select any timestamp in the retention window. ForgeRecovery verifies integrity, restores all products in parallel, and runs a post-restore consistency check. RTO under 4 hours.
< 4 hrs
Recovery time objective
Full Forge product suite restore
< 60 sec
Recovery point objective
Continuous incremental snapshots
Ed25519
Backup signature
Verified before every restore
Air-gapped
Backup targets
NAS, S3-compatible, or tape
ForgeRecovery backs up all Forge data continuously, signs every package, and verifies integrity daily. When you need to restore, the verification has already been done. RTO under 4 hours — for the full suite, not just one database.