Digital 5PL · Lead logistics partner
The logistics operating system for asset-light execution.
We plan and execute inbound and outbound shipments across ocean, air, road, rail and parcel as the extended arm of your supply chain. Underneath sits a kernel: policy you can execute, a stream every system subscribes to, and a twin you can test against.
What makes it an operating system
Most logistics software is a set of screens over a database. An operating system gives you a kernel, a bus, a scheduler and an SDK — so the network can be extended by people who do not work here.
Rule kernel
Operating policy written as versioned, executable rules. Dry run against real records first; every automatic decision is explained and reversible.
Typed event bus
Every state change is a typed domain event on one append-only stream. Features and partners subscribe instead of being wired point to point.
Digital twin
Replay a real period against a different policy and see the cost, consolidation and service difference before you commit to it.
Pool optimiser
Rolling-horizon planning across the whole unplanned pool and across customers — not one order at a time.
Connector SDK
A connector is a manifest, not a deployment. Third parties add channels without touching the platform.
Conversational ops
Ask the network a question in plain language. Answers respect exactly what the asker is allowed to see.
Network benchmarks
Opt-in, aggregated lane economics. Every participating shipper makes the next quote sharper for the rest.
Auditable by construction
Append-only audit of every rule version, simulation, replay and configuration change.
Every channel your partners already use
Onboard a shipper, consignee or carrier on whatever integration they can support — and land it all in the same canonical shipment spine.
SFTP drops
Watched folders with naming rules, PGP-ready handling and per-drop run history.
EDI translation
X12 and EDIFACT parsing to the canonical model, plus 214/IFTSTA style outbound builds.
API endpoints
Per-partner ingest URLs with schema validation, idempotency and replay.
Webhooks
Signed inbound events and outbound delivery with retry and delivery receipts.
OCR
Structured fields from scanned bills of lading, invoices and delivery notes.
Mailbox ingest
Read message bodies and attachments, then map them like any other channel.
Configurable
Field maps, code lists and validation rules per partner and message type — no redeploys.
Observable
Stage-by-stage traces: received, parsed, mapped, validated, applied — with raw payloads kept.
Auditable
Append-only audit log of every rule version, simulation, replay and configuration change.