Know the resource envelope first
Doctor validates compatibility and estimates conventional RAM, bounded RAM, and scratch before expensive work begins.
Local proving · bounded resources · ordinary verifier
Keep proof jobs moving when RAM runs out.
The open TinyZKP engine preflights RAM and local NVMe scratch and chooses the supported execution path. TinyZKP Guard, the withdrawn local supervisor for signals, checkpoint lifecycle, diagnostics, activation, and CI policy, is no longer offered for purchase; TinyZKP is moving to a metered proving utility priced per unit of trace.
Proving stays on your compute: no hosted proving, and no witness, trace, or proof is ever sent to TinyZKP. The free hosted estimator is the one exception — it receives only a declared configuration shape (field, width, rows, AIR features), never a witness, and is rate-limited per caller.
One narrow job
A memory safety net for proof infrastructure.
TinyZKP is for teams that already have a supported Plonky3 workload and a concrete OOM, machine-cost, or restart problem. It is not a new proof system, hosted prover, or generic ZK platform.
Use RAM or SSD deliberately
Auto mode keeps the conventional fast path when it fits safely, then selects bounded execution when the estimate crosses the configured ceiling.
Resume an interrupted run
Exact-release-bound, checksummed job state makes interruption recoverable without silently consuming stale or corrupt checkpoints.
01 · CheckValidate profile and paths
02 · PlanEstimate RAM and scratch
03 · RunProve on customer compute
04 · VerifyUse the ordinary verifier
Technical differentiation
The proof remains ordinary. The execution becomes operationally survivable.
What TinyZKP changes
- Resident-memory planning and enforcement
- Checksummed external-memory scratch
- Deterministic checkpoints and resume
- Machine-readable reports for CI and schedulers
What TinyZKP does not change
- The supported AIR semantics
- The released proof format
- The ordinary Plonky3 verification path
- Ownership or location of customer data
Claim discipline: TinyZKP does not claim exclusivity, zero-knowledge privacy, arbitrary Plonky3 compatibility, or production performance beyond published candidate evidence.
One free engine
Free engine. Guard subscription withdrawn.
The MIT Community engine is the free evaluation and production path. The TinyZKP Guard subscription for the local supervisor and activation of qualified releases is withdrawn and no longer offered for purchase; TinyZKP is moving to a metered proving utility priced per unit of trace.