Private pilotProduct

id.Reys

A freight and bidding platform where every deal rests on verified company data and fixed, versioned terms.

A deal from a load on the board to a signed contract

Problem

On freight exchanges it is hard to know who you’re dealing with, and easy to disagree later about what was agreed. Contacts leak without a trace, and shippers retype loads from their own TMS by hand.

Who it's for: Shippers, forwarders and carriers in Russia.

What we built

  • Company profiles built only from verified data.
  • Load publishing, bids and choosing a carrier — in one place.
  • Terms are fixed: every deal keeps the version it was agreed on.
  • A carriage contract for every deal: approving a version and signing by SMS.
  • A decision log: which employee changed what, when and why.
  • Contacts are shared on request, and the history shows it.
  • An API for any TMS: publish loads straight from your own system.
  • Notifications and commands in Telegram and MAX.

Our role

The whole product: concept, architecture, engineering.

Status

Private pilot: the platform is deployed and being prepared for its first trips with carriers. We’re opening it in stages to prove each part on real deals.

Stack

  • TypeScript
  • Node.js
  • MongoDB
  • Next.js

Interfaces

The id.Reys load board: 20 offers with routes, dates, body type, the rate incl. VAT and a “Place a bid” button
The load board: route, terms and organiser right in the list
id.Reys loads on a map: loading and unloading points across Russian cities next to the load list
The same loads on a map
An id.Reys load card: Nizhny Novgorod — Kazan, ₽64,000 incl. VAT, weight and volume, loading method, exact addresses and the shipper’s instructions
A load card: everything a carrier needs before bidding
A company passport in id.Reys: the “Verified by id.Reys” mark, tax and registration numbers, legal status, confirmed trips and trust signals with source and date
A company passport: facts with sources, not a single score
A company’s terms version tree in id.Reys: four versions of the offer, their dates in force and the number of deals under each
Terms by version: every deal is tied to its own
Comparing terms versions in id.Reys: version 3 against version 4 for vehicle arrival, waiting time and payment
What changed between versions, clause by clause
Carrier bids on a load in id.Reys: four offers with each company’s check status, rate, terms and Choose / Decline buttons
Carrier bids, with every company checked
A carriage contract for a deal in id.Reys: the Nizhny Novgorod — Kazan route, the cargo, the current version with a ₽63,500 rate and payment terms, and an Approve version button
The carriage contract: approving a version and signing by SMS
The decision log in id.Reys: which employee changed rates, carrier categories and assignments, when, and why
The decision log: who, when and why

Similar problem? Let's talk

Topic: id.Reys

For example, name@company.com or @username

Let’s talk

Leave a contact — we’ll reply with a next step.