Integrations

The systems your operation already runs on.

Open API by default. No rip and replace. Your stack stays.

Kairos sits as a peer to your existing ERP, TMS, WMS, and carrier networks — not a replacement for them. Customer-tenant-scoped APIs, real-time event delivery, named connector partners. The discipline is the interface.

How we integrate

We meet your stack where it is.

Most AI platforms sell rip-and-replace. We don't. Kairos was built to sit alongside the operational systems your team already runs — your ERP, your TMS, your carrier networks, your communications stack — and operate as a peer. Five deployment modes; the one that fits is the one we run.

The interface is the product. Every integration is tenant-scoped at the data layer, audit-logged at the action layer, and governed under the same security, privacy, and continuity terms that govern the rest of the platform. No shadow data flows, no opaque connectors, no integration-as-line-item.

Integrations are part of the platform tier you buy — bundled, not line-itemed. Custom connector work — your proprietary carrier APIs, your in-house ERP, your legacy data shapes — is scoped per engagement and priced before work starts.

When migration off a legacy system is the right move, we have documented playbooks for it. When it isn't, we operate the integration and the agents that run on top of it. Customer-requested integrations move first.

The integration surface

Named partners. Tenant-scoped boundaries.

Every integration partner is named. The canonical list with data-flow and certification details lives at /sub-processors.

ERP & TMS

SAP · Oracle · Infor CSD · NetSuite

Native integrations with the operational systems your enterprise already runs. In-tenant deployment leaves your incumbent stack in place; Kairos augments it.

Carrier networks

SMC³ CarrierConnect XL · Old Dominion Freight Line (ODFL) · direct LTL & TL carrier APIs

Rating, tendering, transit visibility. A growing roster of direct carrier APIs added as customer-routed lanes require them.

Parcel

EasyPost

Rating, label generation, and tracking across 100+ parcel carriers in a single API surface.

Voice

Bland.ai

Outbound and inbound voice AI for carrier check-calls, appointment confirmations, and exception handling. Tenant-scoped transcripts.

SMS

Twilio

Driver and dispatcher messaging. Two-way thread management. Tenant-scoped phone numbers and message content.

Email

SendGrid

Transactional and customer-facing email. AI-grounded reply drafting with citation and confidence scoring.

Maps & routing

Mapbox

Geocoding, routing, ETA calculation, lane visualization. Tenant-scoped origin/destination data.

AI inference

Anthropic Claude (primary) · AWS Bedrock (model hosting) · OpenAI (fallback)

Tenant-scoped retrieval. Providers do not train on customer API content under the terms we operate under. See /sub-processors.

Identity & access

Firebase Authentication · SAML & OIDC SSO (Enterprise)

Role-based access at the application layer; MFA on production and admin access; SSO surfaces on Enterprise and Sovereign tiers.

Data & storage

Firebase Firestore (primary) · AWS (analytical workloads)

AES-256 at rest, TLS 1.2+ in transit, multi-AZ replication. Tenant isolation enforced at the data layer, not at the policy layer.

API surface

REST. Webhooks. EventBus.

REST
Kairos exposes a documented REST API. Authenticated, tenant-scoped, rate-limited. Every endpoint operates within the same tenant-isolation boundary that protects the rest of the service.
Webhooks
Material events in your tenant — load tendered, in-transit milestone, exception raised, invoice ready — emit on the platform's event surface and can be subscribed to via webhook.
Bring your own carrier APIs
If you have direct carrier API credentials, we wire them in. Customer-routed lanes drive integration priority.
Authentication
Role-based access at the application layer. Least-privilege at the infrastructure layer. SAML and OIDC SSO available on Enterprise and Sovereign tiers.
Migration patterns

We've done this before.

Migration off a legacy operational system is a sequenced engagement, not a flag-day cutover. The platform has a documented playbook for replacing legacy TMS systems — including a current MercuryGate replacement pattern — and an API-first integration approach for the major distribution ERPs.

Enterprise customers under NDA receive the full sequencing document, the data-shape diff against their current system, and the operational risk matrix before any cutover decision is made.

What we don't do

The opposite of every SaaS integration page.

  • We don't sell connectors as line items.
  • We don't lock you in. Your data exports on demand, in standard formats.
  • We don't charge per integration.
  • We don't migrate you off your ERP unless you ask us to.
  • We don't gate the documented public API behind a sales call.

Bring your stack.

Customer-requested integrations move first. Tell us what you run; we'll show you the integration map, the security boundary, and the path.

Talk to salesTrust portal