Every module, one platform

Drayage Cloud is composed from modules. Each one owns its records and talks to the others through the platform, so operations, accounting and delivery stay in step.

Drayage operations

Ports, terminals, lanes, quotes and bookings in one place.

User app

The records dispatch and the rate desk work from every day. Places are keyed on UN/LOCODE, terminals carry the details the gate cares about, and every quote and booking prices against a lane.

  • Ports and inland cities keyed on UN/LOCODE, enriched from the published list
  • Terminals with FIRMS code, gate hours, appointment system and chassis pool
  • Shipping lines by SCAC, linked to the terminals they call at
  • Lanes shared by every tariff that prices them; CY or SD is derived, never typed
  • Quotes and price sheets with container lines and charges
  • Bookings converted from accepted quotes, carrying their charges with them

Accounting

The books, built in rather than bolted on.

User app

Ledger, invoices, bills, parties, pricing and settlement. Customers, steamship lines and terminal operators are Accounting organizations, so the record dispatch picks is the record that gets billed.

  • General ledger and a financial dashboard
  • Invoices and vendor bills
  • Organizations and contacts shared with operations
  • Charge codes the drayage charges post against
  • Payment settlement

Assistant

Ask about your operation in plain language.

Both apps

Chat agents that read the same modules you do. Each app's agents see that app's toolsets, and a tool that moves money asks before it acts.

  • Agents with read access to drayage and accounting records
  • Destructive actions require confirmation
  • One conversation store per install

Communications

Invoices go out without anyone pressing send twice.

Both apps

Messages are queued from the desktop and delivered by a background service. A channel that is paused leaves a message queued, never failed, so nothing is lost while a mailbox is being fixed.

  • Invoice delivery from Accounting
  • A queue every message passes through
  • A service that drains the queue over email

Monitor

Faults and logs, collected and alerted on.

Admin app

Every app writes its faults through OpenTelemetry. Administrators see them, filter them and get alerted when something needs a person.

  • Fault and log collection from every app
  • Alert rules with delivery through Communications

Data Factory

Move data in and out on a schedule.

Admin app

Pipelines, triggers, datasets and linked services, with monitoring over every run. Reference data loads through it and reloads without touching what a customer typed.

  • Scheduled, tumbling-window and change-feed triggers
  • Datasets and linked services
  • Run monitoring and alerts

Administration

Environments, teams and access, managed in one place.

Admin app

Create environments such as development, staging and production, each with its own database and credentials. Invite teams, issue keys and review activity.

  • Environments with isolated databases and credentials
  • Teams, users and API keys
  • Security settings and an activity log
  • Sign-in with Microsoft Entra ID

See it on your own lanes

A demo walks through a quote, a booking and an invoice using ports and terminals you work with.

An unhandled error has occurred. Reload ×