A working system — built per business, owned by you
Documents in.
Clean, checked rows
in your books.
Assay reads your paperwork on local graphics hardware, grades every field, and holds the doubtful ones for a person. A client deployment is built around your documents and systems — yours to keep.
Forward your supplier emails. Matched, checked, booked. You only see the ones that need a human.
No subscription, no card, ever. A funded $10 test budget on our infrastructure; use sample or non-sensitive documents here.
measured, not claimed — every figure links to how it is computed
watch the real machine work
From a supplier email to a booked row, in twelve steps.
This plays by itself — every step below is a stage this machine really runs, and the reading timings and counts come from a recorded run. Pause it, or walk it a step at a time. The document reading the hero replays is that same run, end to end.
Your supplier emails arrive
Forward them to your own address here and the attachments queue themselves. A sender you have never approved waits for you — nothing is read on a stranger’s say-so.
one recorded batch — measured 2026-07-05
We fed it 1,001 documents before breakfast.
One batch, two ordinary graphics cards, one hour sixteen minutes, zero failures — watch the pile drain into passed and held. Every number here is measured, not claimed.
Measured end to end and recorded. A month of a real importer's invoices — 200 documents — is a 15-minute job at this batch's measured pace. how these numbers are computed →
why you can trust what comes out
Every field carries a grade you can gate on.
This is a real document from the recorded batch, with the machine's verbatim output. Touch a field — it points to the exact spot it read.
the register — the permanent record
The record nothing can quietly edit.
Who read what, what a person changed, when it left — provable to an auditor, owned by you.
- #21476 a field checked or corrected
- #21477 approved
built into your workflow — not another tab
It plugs into what you already run.
Assay is not a website you subscribe to. A client deployment is built around your documents, rules, and software — then handed over with private or client-controlled storage and hardware chosen for your business.
- reads twice, grades every field
- checks your rules — fail-closed
- holds doubt for your person, one keystroke each
- writes everything to the permanent record
Private or client-controlled storage in your deployment.
Your corrections make it smarter — they are yours.
The record is yours — provable, portable, permanent.
the menu a build starts from
Every capability is a block — picked, tuned, and wired for your build.
The BUILT ones run today — you watched several above. The ON-REQUEST ones are added when yours is built. Assemble what your business needs; skip what it doesn't.
31 blocks in 8 groups · 24 run today · 7 built on request
Reading documents
5 built · 1 on request
Checking every field
6 built · 1 on request
A person in the loop
1 built · 1 on request
The permanent record
1 built · 2 on request
Getting documents in
3 built · 1 on request
Getting data out
2 built · 0 on request
Yours to own
4 built · 1 on request
Trying it
2 built · 0 on request
whose hardware, whose models — your call
Choose the hardware and storage boundary.
Budget — local
Open models on local graphics hardware. Measured: 98.7% at 2.2 thousandths of a cent per document. This showcase uses Assay-owned public staging; use sample or non-sensitive documents.
Quality — hybrid
The few uncertain fields escalate to a stronger model — Claude Opus, running on our own model subscription, no per-call charge. The easy majority stays local and near-free.
Private premium
A larger private model on your own server, paired with private or client-controlled storage.
Switching is configuration, not a rebuild — no rented tool offers that.
owned build vs rented tool
Stop renting document software. Own the machine instead.
An Assay build is a one-time project priced to your volume — the recurring cost is electricity. The rented tools bill forever.
Assumes 7 minutes per document done honestly (find, read, type, double-check). Machine rate: 872 documents/hour, measured 2026-07-05 on two consumer graphics cards. Electricity for your whole year at that volume: ≈ $0.16.
List prices captured 2026-07-05 from inside the products.
the next step
Try it on your own documents.
Ask for an invite and Danylo sends back a funded test budget. Then we build the version that fits your business.
Get it built for your business.
This system already runs. Everything on this page is a real, measured machine — not a picture of one.
We build and hand over a version for your business — your documents, your rules, your systems. Yours to keep, running on your hardware.
You try it first on a funded $10 test budget on our infrastructure — on our prepared sample documents, or on your own paperwork. No card, ever. Invite codes come from Danylo.
or reach Danylo directly
Tell us what you need read.
One message — Danylo reads these himself and sends back an invite with the funded test budget on it.
Already invited? Enter your code →