WonderPhi Vault for organizations — perpetual single-organization commercial license

Everything below is identical to the retail product. What's different: your license covers the entire buying organization (unlimited machines, VMs, containers, cloud instances) with no seat count, no annual renewal, no telemetry, no activation. Redistribution / SaaS / hosted-service exposure require a separate OEM arrangement.

Easy Setup — No Package Manager, No Account, No Cloud

Single Python file. Python 3.8+ standard library only — nothing to pip install. Run with:

python wpv-recipe.py

Sample plan files ship with the download and run out of the box. Pair with WonderPhi Compute to execute the generated plans in parallel.

WonderPhi Vault — 30 batch recipes for encryption & security operations

Thirty recipes for the daily cryptography-and-audit chores: GPG encrypt/decrypt at scale, AES-256 file wrapping, code signing, TLS certificate lifecycle, tamper-evident hash sidecars, PII scanning, secret-scrub audits. Point at a folder or a key ring, get a plan.

What it is, in plain English

Each recipe knows how to do one crypto or audit task — encrypt this folder, decrypt that one, verify these signatures, scan for PII, hash every file for tamper detection. You give it a target (folder, file list, key ring). It emits a plan-line per input. Compute runs them in parallel. Nothing leaves your machine.

How you use it — three steps

1. Run the recipe file. python wpv-recipe.py in the folder that contains your input files, or wherever you want the plan written.
2. Point at the target. The recipe asks (or reads from a text file) what the input is — a folder, a list of hostnames, a CSV, whatever the recipe expects. It writes a plan file: one shell command per line.
3. Hand the plan to Compute. Drop the generated plan.wpc.txt into the WonderPhi Compute inbox, and every command runs in parallel across your cores. Read the honest log when it's done.

Worked examples — three of the 30 recipes in this library

gpg-encrypt-folder — encrypt every file in a folder for a recipient

One plan-line per file. All 500 files encrypt at once. Output goes to a separate folder you specify.

python wpv-recipe.py gpg-encrypt --input ./exports --output ./encrypted --recipient alice@example.com

# emitted plan:
# gpg --output ./encrypted/report001.pdf.gpg --encrypt --recipient alice@example.com ./exports/report001.pdf
# gpg --output ./encrypted/report002.pdf.gpg --encrypt --recipient alice@example.com ./exports/report002.pdf

sha256-sidecar — drop a tamper-evident hash next to every file

Emits one .sha256 sidecar per file. Verify later with sha256sum -c.

python wpv-recipe.py sha256-sidecar --input ./release-artifacts

scan-pii — audit a folder for social security numbers and credit cards

Pure Python, regex-based. One plan-line per file. Aggregated report at the end.

python wpv-recipe.py scan-pii --input ./exports --output pii-audit.tsv

Under the hood — the honest technical picture

Every crypto recipe delegates to the real thing: gpg, openssl, signtool, certutil. The recipe never rolls its own cryptography — it drives tools that have decades of scrutiny behind them. Audit recipes (PII scan, secret-scrub) are pure Python and their entire source is readable in a single sitting.

• Never rolls its own crypto. Delegates to well-known tools. Auditable.
• No key material handling. Recipes don't ship keys, don't manage keys, don't touch keys — they just invoke gpg or openssl which use your existing keyring.
• Reversible by default. Encrypt recipes never delete the source; you always keep the plaintext until you're satisfied.
• PII / secret-scrub is pattern-based. Fast, deterministic, no ML, no cloud calls. Regex definitions are inspectable and tunable.
• Offline-first. Every recipe works on an air-gapped machine.

How it compares to the manual way

What you need

• Windows / macOS / Linux workstation.
• The crypto tools each recipe wraps: gpg (GnuPG), openssl, and (on Windows) signtool. All standard-issue.
• Python 3.8+ to generate the plan. Standard library only.
• WonderPhi Compute to run the plan in parallel.

What's in the download

• wpv-recipe.py — the recipe generator (Python 3.8+, standard library only)
• README.md — per-recipe reference for humans
• INDEX.md — alphabetical list of every recipe with a one-line description
• samples/ — ready-to-run demo input files for every recipe
• LICENSE.txt — perpetual single-user license, personalized with your name and order number at delivery

Common questions

License & support — Industrial variant

Perpetual, non-exclusive, non-transferable Industrial license. Covers all machines, VMs, containers, and cloud instances operated by a single organization (the legal entity named on the purchase receipt plus wholly-owned subsidiaries). No seat count, no machine limit, no renewals, no activation, no telemetry.

Employees, contractors, and consultants under the organization's direction may operate the software solely for the licensed organization's benefit. Rights end when their engagement ends.

Not permitted without a separate arrangement: redistributing the software; hosting it publicly; embedding it in a product/SaaS/PaaS you sell to third parties; sublicensing.

Support: email chris@cri-one.com.

Every download's LICENSE.txt is personalized at checkout with your organization name, order number, and issue date. USA sales.