Archive safety and recovery, honestly

Files fail. VERAQIS tells you what is safe, what can be recovered, and what cannot.

VERAQIS is a beta toolkit for damaged archives and data files. It checks first, recovers only what the surviving bytes can prove, and leaves uncertain regions marked as unknown instead of pretending.

Signed Android Archiver APK available | Windows Recovery and ColdPass clean rebuilds pending | SHA-256 published

Current VERAQIS Recovery Protect screen with folder protection, checking, repair and signing controls
Current v0.2.1 Desktop UI. Long folder-protection jobs expose correlated progress and a cooperative cancel action at safe file boundaries.
VERAQIS is in public beta. Evaluation downloads carry checksums, but the Windows artifacts are not yet production-signed. The local release gate blocks publication on an exact-ref Linux gate and an installed Windows capability self-test. Recovery is always best-effort and never guaranteed; the product is designed to abstain when proof is missing.

What you can use today

A small product family built around one rule: the report must explain why a result should be trusted.

Real beta result

Damaged ZIP, health 15/100 → VERAQIS found ZIP_EOCD_001 → rebuilt the archive → 8412B recovered, 0B lost.

This is the product position in one case: prove the recoverable structure, write a manifest, and refuse to dress guesses up as recovered data.

before

Broken structure

The ZIP end-of-central-directory record is missing after truncation.

diagnose

Rule-keyed finding

The report names ZIP_EOCD_001 and scores health at 15/100.

repair

Central directory rebuild

VERAQIS rebuilds from surviving local headers instead of inventing missing bytes.

after

Manifested result

8412B recovered, 0B lost, with a recovery manifest.

Positioning

VERAQIS is not a miracle recovery button. It is an evidence-first safety tool for archives and damaged files: check the risk, recover the provable parts, and say clearly when the data is not recoverable.

ship rule | do not emit unproven data

Most recovery tools sell output

  • They lead with how much data was returned.
  • They may not separate proven data from guessed data.
  • They rarely show what was safely refused.

VERAQIS sells proof

  • Verified bytes, rows, parts and objects are counted separately.
  • False output is a hard gate, not a footnote.
  • Unknown regions remain unknown when evidence is missing.

Security before recovery

Inputs are treated as hostile. Source files are opened read-only, untrusted work is sandboxed, and output goes to a destination you choose.

No password or restriction bypass

Encrypted files are detected and reported. VERAQIS does not decrypt, recover passwords, remove restrictions or claim otherwise.

Useful even when it abstains

An honest report can still help: it tells you the format, the defect, what was checked, and why a recovery was refused.

Common questions

Plain answers for people deciding whether VERAQIS belongs in their recovery workflow.

What is VERAQIS?

VERAQIS is a beta file safety and recovery toolkit. It audits archives and damaged files, recovers only data that surviving bytes can prove, and reports unknown regions honestly.

What makes VERAQIS different from ordinary recovery tools?

VERAQIS is built around an evidence model. A recovery result must be backed by checksum, structural, object-graph or independent-copy proof; otherwise VERAQIS abstains instead of inventing data.

Does VERAQIS send files to a server?

No. The beta tools are offline-first, make no telemetry calls, and keep analysis and recovery on the user's machine.

Can veraqis recover encrypted files or passwords?

No. Encrypted archives and documents are detected and reported, but VERAQIS does not decrypt, recover passwords, or bypass restrictions.

What has actually been checked

The beta release page is intentionally conservative: it shows checks that passed, warns about what is missing, and does not hide beta limits.

PASS
cargo test --workspace --all-targets
PASS
Rust fmt and clippy with warnings denied
0
moderate-or-higher vulnerabilities in the Desktop UI npm audit
1
reviewed public beta artifact currently published: the signed Android APK
Release limit: the Android APK is release-key signed. Previous Windows artifacts were withdrawn; Recovery and ColdPass are being rebuilt and reviewed before republishing.

Everything is free during public beta.

VERAQIS Archiver, ColdPass and every current Recovery capability are available without an account, payment or license file while we collect feedback and measured results.