Request a pilot

What a pilot tests

Usefulness, review burden, and operating cost — on your own material

• Usefulness: does tracing a conclusion back to its evidence, or catching what a reissued document touches, actually save the time it claims to?
• Review burden: how much work does it take a real person to approve, reject, or return what the model proposes — and is that worth it compared to re-researching from zero?
• Operating cost: what does running Piko on your own hardware actually cost in electricity, support time, and any optional external services, alongside the reference-machine numbers we can already show you.

What it asks of you

A real workload and a real reviewer

• A real research packet, a supplier or regulatory bulletin, or a decision history worth defending later — something with actual documents and actual stakes, not a demo dataset.
• One person willing to sit on the review queue: approving, rejecting, or returning claims as they come up. Piko’s safety property depends on that person actually doing the job.
• A dedicated machine on your premises. Piko runs on hardware the business owns; there is no hosted version to sign into instead.
• Patience for gaps. Piko will sometimes show you what it couldn’t verify instead of a confident guess — that’s the point of the pilot, not a defect in it.

Said plainly

What’s true about Piko right now

It’s a working appliance under active construction, proven on a reference machine — not a released product, and not yet running for any customer. There is no pricing and no availability date. A pilot is how usefulness, review burden, and operating cost get tested for real, on your material, before either of us treats it as more than that. See the full capability list and measured numbers before you reach out.

Start a conversation

Tell us about the workflow you want to test

No form, no signup — just a message describing the material and the question you want traced.