Company
Freight deserves an
operating system.
Most freight still moves on spreadsheets, message threads and memory. Conventional TMS products fail small operators through configuration burden and fail complex ones through rigid schemas. We build the layer both can live on.
Thesis
One product. No regional editions. Ever.
A regional movement is a local movement with additional complexity — more legs, jurisdictions, documents, currencies, parties and risks. The underlying model supports that complexity from the beginning; the interface reveals it progressively.
That is why there is no “Southern Africa edition,” no “SMB edition,” no migration cliff between them — and why an operator can grow for a decade without leaving.
Decision hierarchy
- 1Safety, law, contractual commitment, tenant isolation
- 2Correctness of the freight operating record
- 3Human accountability for consequential actions
- 4Operator usefulness and time-to-value
- 5Global extensibility and interoperability
- 6Reliability and cost efficiency
- 7Interface elegance and delight
When decisions conflict, the higher rule wins. Design is a weapon — but it never overrides trust.
Southern Africa pilot
The hardest proving ground we could pick.
Informal communications, variable connectivity, cross-border documents, multi-currency operations, subcontractors and inconsistent master data. A freight system that works between Walvis Bay and Lusaka has earned its assumptions.
And by rule: nothing Southern African is hard-coded into the core. Countries, borders, documents, currencies and terminology arrive as versioned packs — the pilot validates the model, it does not define the product.
Trucking first
Domestic and cross-border in the same movement model, owned and subcontracted capacity.
Messaging-led capture
Status and evidence over WhatsApp and Telegram, structured into the record.
Low-cost devices, weak signal
Offline queues, compact payloads, a PWA that respects a 360-pixel screen.
Customer-owned storage
Originals stay in the customer's S3, Drive or SharePoint — by design.
Principles
Written down, so we can be held to them.
The system proposes; policy governs
Intelligence drafts, explains and recommends. Committing consequential actions stays attributable to authorized people.
Truth must be qualified
Observed, reported, inferred, predicted and confirmed are never collapsed into one undifferentiated fact.
Quiet is a feature
No manufactured alerts, no engagement theater, no worker surveillance dressed as analytics.
Channels are interfaces
WhatsApp and email carry work; the structured record stays in Fraytline, linked and auditable.
Small-operator test
Every feature must deliver value without enterprise machinery — or it isn't core.
Enterprise test
The same model must carry branches, entities, approval matrices and audit — without replacement.
This site and its workspace are a demonstration build with synthetic data, created from the Fraytline design blueprint.
Enter the demo