Skip to main content

Answer every buyer’s evidence question from one set of records.

Lots and their lineage, the certificates behind them, the rules checked before anything moves, and the reports you hand over: one platform, one ledger per company, in your own words and units. Your people approve every change.

Lots and lineage

Know where every kilogram came from, and where it went.

Register harvests and receipts in the units your people already use. Deliveries, splits and processing keep the link to every input, so any lot can be followed back to its farms and forward to everyone who holds part of it.

  • Type tonnes, pounds, bags or bushels: the lot is recorded in exact kilograms, and nothing is rounded without saying so.
  • Split, merge, dry, hull, roast or mill: each new lot keeps its inputs, and the form warns when the output looks too high.
  • History is never edited. Corrections and status changes are approved proposals, and the earlier version stays on record.
Learn more
Fictitious demo data

Certificates and evidence

See who stands behind every certificate.

Labs and certifiers you trust attach certificates and lab results to your lots. Each one carries its evidence level, so a buyer sees at a glance what the issuer signed and what the company only declared.

  • Four evidence levels, from declared by the company to signed by the party, quoted the same way everywhere and never upgraded.
  • Withdrawn and disputed certificates stay on record with their state, so nobody relies on one that is no longer in force.
  • Evidence checks list each requirement of EUDR, FSMA 204 or your own set as recorded, missing or expired, gaps first.
Learn more
Fictitious demo data

Lot rules

Stop the wrong delivery before it leaves.

Lot rules check every registration, delivery and processing before it happens. An owner turns them on and off in business words, and each change is a proposal with a preview of what it will do.

  • Only allowed receivers get your lots; a delivery to anyone else waits until your administrators allow them.
  • Require certificates on a lot, and set when lots expire and which seasons apply.
  • Every change to a rule is previewed before it is approved, and can be undone.
Learn more
Fictitious demo data

Automations

Let routine work prepare itself.

An automation reads as When, Only if, Then, and you build it on a canvas. It notifies, generates reports and prepares proposals; anything that would change the records still waits for a person to approve it.

  • Start from a lot event, a certificate about to expire, a new finding, a message from your ERP or a schedule.
  • A test run evaluates the conditions for real and only simulates the actions. An owner switches it on after reading what it will do.
  • Every run says why each step ran or was skipped, and owners can halt all automations at once.
Learn more
Fictitious demo data

Humboldt, the AI analyst

Find the gaps before a buyer or an auditor does.

Control packs for EUDR, FSMA 204, certification schemes and your own policy check your records every day. Humboldt, the AI analyst, explains each finding in business words, groups findings by cause and suggests what to do next.

  • The controls decide what is a finding: the same records against the same pack always give the same findings.
  • Humboldt cites the records behind every sentence it writes and suggests at most three next steps per run.
  • A person turns a suggestion into a draft. Humboldt never creates or sends anything itself.

People approve every changeHumboldt runs on Claude by Anthropic.

Learn more
Fictitious demo data

Custom agents

In design

Give one recurring job to an agent of your own.

Custom agents are in design, and nothing here is built yet. Each will take on one job, such as chasing certificates that are about to expire, from a playbook you write the way you would brief a new colleague.

  • The playbook holds the goal, the steps and your own rules, drawn as a graph you can read and change.
  • You choose when it starts and grant it a few tools. It is tested before it goes live.
  • It reads, matches, chases and drafts. People approve anything that changes the records.
Learn more
Fictitious demo data

Network and sharing

Get evidence from your suppliers without the e-mail chase.

Connect with the companies one step up and one step down your chain. Each side ticks what it shares, item by item, and asks for what is missing from the lot itself.

  • Share deliveries, certificates, lab results, the EUDR statement and plots, each one separately and by consent.
  • Evidence requests replace e-mail: tick what is missing, set a date, and both sides see when it is overdue.
  • A recall reaches every company holding lots made from the recalled lot, along the lineage.
Learn more
Fictitious demo data

Reports and the audit pack

Hand over documents anyone can check.

Dashboards and reports are built from your records, and every number opens the records behind it. Every report is signed, and anyone can check a copy without an account.

  • Ready-made reports for EUDR, FSMA 204, traceability, inventory, certificates and audits, in PDF, Excel, CSV, GeoJSON, EPCIS 2.0 and UNTP.
  • A PDF carries its signature inside the file; other formats come with a signed manifest.
  • The verification page says whether a copy is unaltered and who signed it, with no account.
Learn more
Fictitious demo data

Every feature has its own page

Nine features, one record per lot.

How it works

Every feature works on the same three steps, for every lot.

  1. Record

    Register lots in your units, with their origin, quantities and certificates. Deliveries, splits and processing keep the lineage.

  2. Approve

    Every change starts as a proposal that reads as a sentence. A member with the right to approve confirms it with a second factor.

  3. Prove

    Evidence checks, signed reports and a public record of each lot that anyone can check, without an account.

See it with your own lots.

Tell us what you trade and where it goes. We will show you the platform with your products, your units and your rules.