id.TMS

A freight company needs a transport management system, but not every company is willing to keep its client, rate and carrier data in someone else’s cloud.

Who it's for: Carriers and forwarders.

• Orders. A route with loading and unloading points on a map, the distance, statuses and priorities.
• Trips. Several orders on one truck: the combined route, driver, vehicle, revenue and the driver’s rate.
• Records. Drivers, tractor units and trailers, counterparties, claims.
• Access. Roles with per-section permissions and two-factor sign-in.
• Data. Passports, addresses, tax IDs and VINs are stored encrypted, with the keys kept in Vault. The system runs on the company’s own servers.
• Built on what we’ve learned from the TMS we’ve been evolving for TK-IRSA since 2022.

In development. Orders, trips, route maps, records and roles already work. The screenshots use demo data.

• Next.js
• MongoDB
• Redis
• HashiCorp Vault
• MapLibre