Logistikore

A multi-tenant TMS for freight companies that both run their own trucks and broker loads to outside carriers. Dispatch, fleet, carrier brokerage, accounting and billing sit in one platform, and each tenant's subscription decides which modules unlock.

Most freight software assumes a company is either an asset-based carrier or a broker. Firms that do both end up running two systems and reconciling between them by hand, so a load brokered out and a load run on own equipment never appear in the same profit picture.

• Run an owned fleet and a carrier brokerage from one order pipeline
• Generate driver pay from dispatch data instead of spreadsheets
• Isolate every company's data while one team supports all of them
• Price orders in three currencies without corrupting the reporting totals

A Next.js front end over a Node service on PostgreSQL, split into a Regular module for owned equipment and an Outsourcing module for brokerage, sharing one order pipeline so margin is computed the same way on both. Stripe carries plan subscriptions, cycle discounts and usage limits. Python services handle the AI assistance and the scheduled FX-rate jobs. Pusher and Socket.io drive live counters, and every action lands in an audit trail.

• Brokered loads and owned-equipment loads report profit through the same pipeline
• Driver pay comes out of dispatch data rather than a spreadsheet
• New companies onboard onto isolated subdomains without a deployment

Multi-tenancy is mostly a permissions problem wearing a database costume. The isolation was the easy half; deciding what a dispatcher can see about a customer they were not assigned took longer than the schema.