v1.1.0 · 100K stress tested

Boring infrastructure that proves where your robots were.

When a robot causes an incident, the question is always the same: where was it, exactly, and can you prove it? GridStamp is the evidence layer. SHA-256 proof chains, HMAC-signed frames, 100% replay detection. Tested at 200 concurrent robots with zero false negatives.

100K
Ops in 43 seconds
2,323
Ops/sec throughput
100%
Replay + tamper detection
0.86ms
p99 proof latency

Who this is for

GridStamp is sold to the person who writes the check when something goes wrong — not to the roboticist who wrote the code.

Insurance

AV & robotics underwriters

Reduce loss ratio by resolving location-of-incident disputes with cryptographic evidence instead of he-said / she-said. Lower your uncertainty tax.

Pilot: $5,000/mo · 3 months
Read the insurance one-pager →
Logistics

Visibility platforms & freight

Give your shippers cryptographic proof-of-delivery they can verify offline. Upgrade ETAs from claims to receipts. Resell as a "Verified Visibility" tier.

Pilot: $2,500/mo · 3 months
Read the logistics one-pager →
Gaming

AR & location-based apps

Catch the ~9% of top players who GPS-spoof. 91% spoof detection at <0.5% false-positive rate. Stop tournament prize leakage and whale churn.

Pilot: $2,500/mo · 3 months
Read the gaming one-pager →

Proven at fleet scale

Two independent test suites. A 92-day fleet simulation with public Waymo/Tesla/Starship data. And a 100K production stress test with 200 concurrent robots.

100K stress test — concurrent robots200
100K stress test — operations99,911
100K stress test — throughput2,323 ops/sec
Replay detection4,000/4,000 (100%)
HMAC tamper detection2,000/2,000 (100%)
Proof chain verification200/200 robots (100%)
Proof chain links verified80,000
p99 proof generation latency0.86 ms
Fleet simulation — operations14,554,382
Fleet simulation — agents5,500 across 20 fleets, 8 cities
Unit + integration tests passing221+
LicenseApache 2.0

How the receipts work

Three layers, cryptographically isolated. Every operation produces a receipt your counterparty can verify offline — no dependency on GridStamp's servers.

STEP 1

Signed capture

Every camera frame is HMAC-SHA256 signed at capture time. Monotonic sequence numbers prevent replay. Any post-hoc edit invalidates the signature.

STEP 2

Merkle-rooted memory

The full operation history is committed into a Merkle tree. Tamper with any point in the history and the root changes — detection is instant.

STEP 3

Proof-of-location

SSIM + LPIPS + depth comparison against trusted landmarks. The camera has to actually see the place, not just claim a GPS coordinate.

STEP 4

SHA-256 proof chain

Every spatial proof links to the previous via hash chain. A robot's complete operational history becomes a tamper-evident linked list an underwriter can verify end-to-end.

What we're honest about

Risks we disclose to every pilot

  • Jurisdictional admissibility varies. We claim "audit-grade" and "dispute-resolution-grade," not "court-admissible in all US states." Counsel review is part of every pilot.
  • First-mover reference risk. Until a receipt is challenged in a real dispute, we can't point to precedent. Your reputation is what makes the first syndicate comfortable.
  • Receipt storage is non-trivial. ~8KB each. Rollup proofs bring long-term storage down, but it's a design conversation we have early.
  • Founder-led support. There is no support team yet. Jerry answers. This is a feature for pilots and a risk at scale.

Want to see the receipts?

30-minute call, no pitch deck. I show you a spoofed incident being caught live and a receipt verifying offline. If the math works for your book, we talk about a pilot.