Keelway
For 3PLs and brokerages running 10,000+ loads / month

The enterprise AI layer for freight brokerages that cannot rip and replace.

You have McLeod or Aljex live across 200 brokers, a custom data warehouse, an EDI pipeline that took two years to build, and a security team that needs SAML, SCIM, audit logs, and a signed MSA before you can buy a box of pens. Keelway Enterprise was built to fit into that environment — not fight it. AI carrier-email triage, FMCSA-backed trust scoring, rate extraction, and ranked top-five replies on every posted load, with the security and contracting posture an enterprise procurement team expects.

Talk to salesSecurity & compliance
99.9%
Monthly uptime SLA
Backed by service credits
<45d
Mid-market go-live target
Discovery → cutover
10k+
Loads/mo Enterprise floor
Tier qualifies for dedicated tenant
The platform, on tape

Keelway Enterprise — in 52 seconds.

An Apple-style spotlight of the platform your dispatchers and controllers will actually run on. Eight scenes, auto-playing.

Talk to salesExplore the platform

Built for procurement, not just operations

Enterprise software in freight has historically been measured by features. Enterprise buyers measure software by three things: can we deploy it without disrupting the floor, can our security team approve it without a three-month review, and can our CFO sign a contract that protects the business. Keelway Enterprise is calibrated for those three questions before it is calibrated for anything else.

Identity

SSO, SCIM, RBAC out of the box

SAML 2.0 and OIDC single sign-on. SCIM 2.0 provisioning so deactivating a coordinator in Okta deactivates them in Keelway within minutes. Granular role-based access — broker, team lead, ops manager, read-only auditor — each with configurable scope on loads, carriers, and rates.
Audit

Every action logged, streamed to your SIEM

Every login, every accepted carrier, every overridden trust score, every TMS write-back is captured to an immutable audit log. Stream to Splunk, Datadog, or Sumo Logic over webhooks or S3 export. Retention configurable to your compliance policy.
Infrastructure

Dedicated tenant, regional residency

Enterprise customers get an isolated tenant in AWS us-east-1 by default, with us-west-2 and ca-central-1 available on contract. No shared retrieval indexes, no shared model fine-tuning surfaces, no cross-customer data leakage paths.
Contracts

MSA, DPA, BAA-ready

Executable Master Services Agreement and Data Processing Agreement templates. Mutual NDA before any data-sharing conversation. BAA negotiated on request for healthcare-adjacent freight. Standard payment terms net-45, with PO-driven invoicing.
Reliability

99.9% SLA with service credits

Monthly uptime measured against the carrier-email ingestion path and the operator dashboard. Below 99.9% earns 10% credit; below 99.0% earns 25%; below 95.0% earns 50%. Status page public, incidents post-mortemed within 5 business days.
Support

Named CSM, 24/7 incident channel

Each enterprise contract includes a named Customer Success Manager, a named Solutions Engineer, and a 24/7 Slack Connect / Teams shared channel for P0 / P1 incidents. Quarterly business reviews against the metrics your team owns — coverage rate, time-to-cover, fraud-stopped, broker productivity.

The deployment pattern most enterprise brokerages run

Enterprise brokerages do not replace systems on a quarterly cadence. They wrap them. The reference Keelway deployment for a 200-broker 3PL on McLeod LoadMaster looks like this:

  1. Phase 1 — Overlay (weeks 1–6). Keelway runs as a read-only AI layer over the existing carrier-email channel. Brokers keep their McLeod workflow untouched. Keelway surfaces ranked top-5 carrier replies inside Gmail and writes accepted bookings back into McLeod via the LoadMaster API. Zero floor disruption.
  2. Phase 2 — Selective replacement (months 2–6). The modules where Keelway is materially better than the incumbent (carrier vetting, fraud detection, rate benchmarking, check-call automation) take over inside the existing TMS shell. McLeod remains system of record for accounting and shipper contracts.
  3. Phase 3 — Optional consolidation (year 2+). Once Keelway has been load-bearing for 9–12 months and the TMS replacement cost case is clear, brokerages with budget cycles open tend to migrate fully. Keelway TMS becomes system of record. Brokerages with sunk McLeod or Aljex investment stay on the overlay model indefinitely — both paths are first-class.

Where Keelway Enterprise fits in the broker-AI landscape

The enterprise broker-AI market in 2026 is fragmented across four shapes:

  • Voice-first (Parade CoDriver, Happy Robot): outbound capacity calls. Strong on the phone leg, silent on the inbound email-reply triage that drives 60–70% of broker time.
  • Identity-first (Highway, RMIS, Carrier411): point-in-time carrier vetting at onboarding. Excellent at that one job. Do not score per-reply, do not parse rate, do not rank inquiries.
  • Rate-first (Greenscreens / Triumph Intelligence, DAT iQ): rate benchmarking against lane history. Critical input to broker margin decisions. Do not see the inbox, do not score trust on the senders quoting those rates.
  • Inbox-first (Drumkit, Keelway): read every reply, extract structured data, surface decisions. Keelway is the only inbox-first product with per-reply FMCSA trust scoring, load-aware ranking, and TMS write-back across McLeod, Aljex, Tai, Turvo, and Revenova on day one.

For brokerages who already buy from the first three categories, Keelway is the missing fourth leg, not a replacement. For brokerages starting fresh, Keelway TMS bundles all four.

The pricing posture for enterprise

Standard Keelway is published and transparent: $799/mo flat — one plan covering both the AI carrier layer and the TMS, unlimited users, month-to-month, $0 setup. Enterprise pricing is custom — we model load volume, seat count, integration scope, and dedicated-tenant infrastructure cost into a single all-in monthly fee. There are no hidden user-license stacks, no per-feature SKUs, and no implementation fees that exceed three months of platform fee. We publish the rate card we anchor enterprise quotes against in the first discovery call.

Frequently asked questions

What makes Keelway Enterprise different from your standard plan?+
Three things. First, deployment: enterprise customers get a named implementation engineer, white-glove TMS data migration, and a 30–60–90 day go-live plan with weekly checkpoints. Second, security: SAML/OIDC SSO, SCIM provisioning, role-based access control, IP allowlisting, audit logs streamed to your SIEM, and an executable MSA + DPA. Third, scale: dedicated tenant infrastructure, regional data isolation (US-East default; US-West and CA-Central available), a 99.9% uptime SLA with credits, and a 24/7 incident response channel.
Do you support SSO and SCIM?+
Yes. SAML 2.0 and OIDC for SSO, SCIM 2.0 for user provisioning and deprovisioning. We have validated configurations for Okta, Microsoft Entra ID (Azure AD), Google Workspace, and JumpCloud. Custom IdPs supported on request.
What is the data residency story?+
All customer data is stored in AWS us-east-1 by default. For enterprise contracts we will provision a dedicated tenant in us-west-2 or ca-central-1 on request. EU residency is on the 2026 roadmap and gated to confirmed pipeline. Subprocessor list is published on /security and updated quarterly with 30 days' notice before any change.
What does the implementation actually look like for a 50-person brokerage?+
Week 1: kickoff, SSO + IdP integration, sandbox tenant provisioned. Week 2: historical carrier-data migration from your incumbent TMS, FMCSA backfill on every active carrier, label taxonomy review. Week 3: first 5–10 brokers go live in shadow mode (Keelway reads but does not act); coordinator-level training. Week 4: cutover for a single team, with daily syncs. Weeks 5–8: phased rollout across the rest of the floor with the dedicated CSM driving adoption metrics. Most mid-market 3PLs are fully live within 45 days from contract signature.
Will Keelway sign an MSA, DPA, and BAA?+
Yes to MSA and DPA — both have executable templates ready. BAA only if you operate freight under healthcare-data-adjacent scopes (hospital supply chain, e.g.) — we will negotiate scope on request. Mutual NDA is signed before any commercial conversation that requires data sharing.
Does Keelway replace McLeod, Aljex, or Tai, or sit on top?+
Either. For brokerages with a sticky enterprise TMS investment (McLeod LoadMaster, Aljex/Descartes, Mercury Gate/Infios), Keelway runs as an AI overlay — inbox triage, trust scoring, and write-back into your system of record. For brokerages ready to consolidate, Keelway TMS replaces the underlying system entirely at a fraction of legacy-TMS total cost of ownership. We will model both paths for you in the discovery call.
What is the SLA and what are the credits?+
99.9% monthly uptime, measured against the carrier-email ingestion path and the dashboard. Below 99.9% earns 10% service credit, below 99.0% earns 25%, below 95.0% earns 50%. Planned maintenance is excluded and announced 7+ days in advance via a public status page.
How do you handle our carrier and shipper data?+
All data encrypted in transit (TLS 1.2+) and at rest (AES-256). Carrier emails are never used to train shared models — every enterprise tenant runs against an isolated retrieval index. We do not sell, license, or syndicate carrier-quote data to third parties. Subprocessor list, sub-tenant data flow diagram, and our security whitepaper are available under NDA on /security.
Procurement, security, and ops all in the room?

Bring them. We'll have answers.

Talk to sales

Related

Security & compliance →

SSO, SCIM, encryption, subprocessors, incident response, and our current SOC 2 posture.

Who Keelway is built for →

Customer segments, deployment patterns, and the brokerage shapes Keelway is calibrated against.

Reference deployments →

Illustrative deployment profiles by brokerage shape — SMB, mid-market 3PL, enterprise multi-brand.

Keelway on McLeod LoadMaster →

How the AI overlay pattern works on top of an existing McLeod deployment with zero floor disruption.