The way to deal with authenticity is to hold proof.
We are not an encryption company. We produce proof at scale, for every action, on every file, without needing to see the content.
Everything below is public. You can verify it yourself, on your data, your files, from your terminal, without contacting us, without an NDA, without signup.
Visit /audit/export generates a real ZIP with summary.html, events.json, receipt-chain.csv, and manifest.txt, signed with a real chain_hmac. Demo mode is open to all.
ASpecs · readable, public, no NDA
Four documents. Every algorithm, every choice, every trust boundary.
What a security engineer needs before trusting any vendor. What stays closed has its own document explaining why, item by item.
No SDK to install. Just stdlib + an HTTP call to the public endpoint. Three languages, identical logic.
// 15 lines, Node.js verify a NoData receipt
import { readFileSync } from 'fs';
import fetch from 'node-fetch';
const receipt = JSON.parse(readFileSync('sample-receipt.json','utf8'));
const file_bytes = readFileSync('secret-roadmap.pdf');
const sha256 = require('crypto').createHash('sha256')
.update(file_bytes).digest('hex');
const r = await fetch('https://nodatacapsule.com/api/verify', {
method: 'POST',
headers: { 'content-type': 'application/json' },
body: JSON.stringify({ content_hash: 'sha256:'+sha256, sidecar: receipt })
});
const v = await r.json();
console.log(v.valid ? '✓ authentic, signed by ' + v.signer
: '✗ tampered or unknown');
EPerformance · the metrics you measure
Encrypt latency (p50 / p95 / p99)
Measured on AWS m6i.large (Intel Xeon, AES-NI), Node.js 20, payload type: with full AAD, receipt signed concurrently. 10,000 runs per size.
Payload size
p50
p95
p99
Throughput
1 KB
0.42 ms
0.71 ms
1.18 ms
2,380 ops/s
10 KB
0.58 ms
0.94 ms
1.46 ms
1,720 ops/s
100 KB
1.24 ms
1.92 ms
2.81 ms
806 ops/s
1 MB
8.10 ms
11.4 ms
14.7 ms
123 ops/s
Receipt verify
11.2 ms p95
requires /api/verify roundtrip
Memory footprint
+ 2.4 MB
above Node baseline
Folder sign (1k files)
1.84 s
Merkle tree, depth 10
FFree gifts · take with you
Nine tools. Download, integrate, no return trip required.
All run without an account on our side and without an NDA. These are what you drop into your CI, your Terraform, your Postman workspace, your bench script, today, before you've even decided whether we're a fit.
No eval API key, no private tenant of ours, no samples from real customers. All of those require POC scope + NDA. See open-vs-closed.md for the full breakdown of where the line is and why.
·What lives past the kit
The operational regime, under NDA, after POC scope.
The algorithms are open because an auditor needs to see them. The KEK derivation chain, multi-tenant isolation, and anti-replay state machine stay closed because publishing them weakens every existing customer, it does not strengthen you. We open them under NDA, after a POC scope is agreed.