Custom software project · Active development
Proof of Restore
A Windows-first, offline-first application for testing selected backup artifacts in an isolated sandbox and producing inspectable local evidence—without executing restored binaries or scripts.
The current codebase is a credible release-candidate baseline for continued v0.3 work, but it is not ready for a final paid or public release. There is no download or availability promise on this page.
Current product evidence
Restore checks and evidence in one local workspace
The gallery shows verified captures from the current preview line. Proof of Restore currently uses a fixed light palette, so the same genuine product captures remain visible in both Viken Data themes.
Inspectable gallery
Proof of Restore preview workflow
Open five genuine screens from the current 0.2.26-preview line. The Windows application currently uses a fixed light palette, so the captures stay unchanged when the Viken Data theme switches.
Implemented scope
Restore selected evidence without turning validation into execution.
Proof of Restore keeps the workflow local: define sources and plans, restore a controlled sample, run read-only checks and retain the result for review.
Multiple source types
Register local folders, individual files, ZIP archives and network shares, with explicit include and exclude filtering.
Deterministic discovery and sampling
Enumerate candidate artifacts and select a repeatable sample rather than implying that an opaque subset was checked.
Isolated restore sandbox
Restore selected artifacts into a controlled local sandbox without launching restored executables, scripts or application workloads.
Read-only validation
Apply general and file-type-specific checks, including reusable recovery presets and explicit validator profiles.
Local proof artifacts
Generate JSON and PDF evidence with deterministic hashes, plus persisted run details, restored-artifact facts and validation results.
Operator workflow
Manage plans, profiles, manual and scheduled runs, queues, history, diagnostics, workspace portability and local support bundles.
What the evidence means
A checked sample is evidence, not a universal guarantee.
The product is designed to make the tested scope and result visible. It does not claim that a successful sampled check proves every artifact, every application or every disaster-recovery scenario.
Scope and limitations
Restore readiness has boundaries worth stating plainly.
Current validators provide structural and safely explainable checks. They do not recreate every application or certify every business meaning hidden inside a file.
Not application-native recovery
The application does not restore artifacts into live services, execute application-specific queries or prove that an external system can consume the result.
Validation is deliberately bounded
Checks do not prove PDF render fidelity, Office macros or formulas, arbitrary business schemas, XSD imports or every semantic rule a domain may require.
Local, one-machine operation
The current model is local-only and offline-first. Cloud orchestration, telemetry, distributed workers and remote execution are outside the product boundary.
Development status
A substantial preview, still short of public release.
The current baseline includes working portable and installed package tracks, restore and validation orchestration, reports, history, diagnostics, workspace portability, offline licensing foundations and local hardening controls.
Remaining release work includes clearer first-run UX, calmer profile editing, final commercial licensing decisions, support and fulfillment operations, signing and trust, installer polish, upgrade safety and final launch acceptance.
Need a tool for a different validation or evidence workflow? Our custom software development service starts with your source data, required checks and operational constraints. This preview is a work example, not a ready-made offer for every recovery scenario.
Project enquiry
Contact us about a restore or validation workflow.
Send the source types, artifact types, operational constraints and required evidence to support@vikendata.com. We can assess a focused custom workflow and explain the limits of non-executing validation.