Skip to main content
StateSet Freight is the transportation management system for shippers, brokers, and carriers. One load record connects planning, customer quotes, carrier procurement, tenders, dispatch, tracking, delivery evidence, invoice audit, and settlement preparation. Sync owns commercial orders, Warehouse owns physical stock and warehouse execution, and Freight owns transportation planning and execution. A planned Freight load is separate from a warehouse carrier handoff, carrier acceptance, delivery, or a bank payment.

Run Freight locally

Open the synthetic workspace, inspect loads, and verify API access.

REST and MCP

Connect with role-scoped credentials and retain exact original writes.

​
Transportation work

Supported modes are FTL and LTL; equipment values are Dry van, Reefer, and Flatbed. Money is integer USD cents. Routes support up to twenty stops; the current EDI 204 gateway supports two-stop tenders, so multi-stop routes require native coordination.

​
Interfaces and identity

Freight uses a Rust API and a Next.js/React web application. Local development runs the API on port 8090 and web app on 3010. A terminal console offers operations work with original-request recovery; its financial views remain read-only. The repository’s MCP adapter runs over stdio and calls the protected API. Service credentials bind tenant, subject, and role on the server. Staff roles separate operations, finance, integrations, administration, and read access. Optional Clerk SSO uses explicit organization mappings and live session/membership checks. Carrier and customer portal identities additionally bind a server-owned counterparty; staff credentials are not partner credentials.

​
Financial and physical evidence

Recording a plan or issuing a document does not establish physical execution. Delivery, route chronology, POD review, rate matching, and unresolved incidents gate financial work. Primary carrier invoices require named entry review and an independent approval outside explicit synthetic demo mode. Settlement preparation and bank reconciliation retain financial records; they do not themselves send money through a bank. Customer refunds and carrier refunds reconcile actual external funds and preserve their original evidence.

​
Deployment scope

Real workspaces require PostgreSQL, secure web sessions, individual access configuration, and backup/restore of business data together with keys and configuration. Local demo mode can run in memory and resets on API restart without a database. Live identity-provider and carrier commissioning, off-host recovery, production capacity, and independent operator outcomes remain deployment work. This guide was checked against stateset-freight on October 20, 2026, including its README.md, docs/api.md, docs/access.md, docs/finance.md, and integration guides. Use the cross-system guide to connect it to Warehouse and Sync.
Last modified on October 20, 2026