Custom agents, built around how you work
No generic "skills" to configure. We map your real workflow, then build an agent team with your rules, your exceptions and your customers' quirks.
Service, not a seat licence
Supply Chain Agentic Service
Your supply chain team, multiplied by agents.
We build custom AI agents for
freight forwarders
— wired into the legacy systems you already run, trained on your own data, and live in weeks. Your people approve. Agents do the rest.
Custom-built, not off-the-shelf
TMS · WMS · ERP · EDI
Private open-weight LLM
Human-in-the-loop
Freight agent team · live operationsRunning
Freight forwardingBookings, quotes, docs, customs and milestone updates.
TruckingLoad tenders, dispatch, POD capture and detention.
3PLClient onboarding, order intake, billing and SLAs.
4PL & control towersMulti-carrier visibility, exceptions and orchestration.
WarehouseASNs, slotting, dock scheduling and cycle counts.
ManufacturingSupplier POs, MRP signals, inbound and quality docs.
How we're different
Platforms sell you software.
Supply Chain Agentic Service
e.g. Aera, Unloq, Snowfire
e.g. o9 Solutions, Kinaxis
e.g. Nauta
Platforms sell you software.
We give your team more hands.
Decision-intelligence and planning suites are built for global enterprises with clean data lakes and multi-quarter programs. Most forwarders, carriers and 3PLs run on email, PDFs, EDI and a TMS that's older than their newest hire. That's exactly where we start.
Speaks legacy fluently
EDI, SFTP, AS/400, ODBC, Excel drops, shared inboxes and green-screen TMS. If a human can read it, an agent can work with it — no rip-and-replace.
Start without a data lakeYour own private LLM
Open-weight models deployed in your VPC or on-prem, adapted to your codes, lanes and document history. Your data never trains someone else's model.
Open-weight · on your hardwareAgents act. Your people approve what matters.
Agents don't stop at recommendations — they post to the TMS, send the update, book the slot. Low-confidence fields, unknown layouts and money decisions stop for a human, with the evidence attached. Every action is logged and reversible.
Execution with guardrailsLive in weeks
One workflow, scoped in days, in production-like test in about a week. Expand once the numbers prove it.
5-day reference pathCloud28.ai
Us- What you buy
- A managed service that builds and runs your agents
- Best fit
- Forwarders, carriers, 3PL/4PL, warehouses, mid-market manufacturers
- Legacy data
- EDI, SFTP, AS/400, ODBC, PDFs, screen-level automation
- Where AI runs
- Your VPC or on-prem, open-weight model option
- Time to value
- Days to weeks, one workflow at a time
Decision-intelligence platforms
- What you buy
- Platform subscription + implementation
- Best fit
- Global enterprises
- Legacy data
- Connectors to major ERPs
- Where AI runs
- Vendor cloud
- Time to value
- Typically months
Planning suites
- What you buy
- Enterprise planning software
- Best fit
- Large manufacturers & retailers
- Legacy data
- Data integration program
- Where AI runs
- Vendor cloud
- Time to value
- Typically quarters
Agent SaaS
- What you buy
- Pre-built agents, configured
- Best fit
- Teams on modern email & cloud tools
- Legacy data
- Inbox, documents, common APIs
- Where AI runs
- Vendor cloud
- Time to value
- Days to weeks
In production · Freight forwarder
One orchestrator. Eight specialists.
Coordination
One orchestrator. Eight specialists.
Quote to cash, zero retyping.
This is the agent team we built for a freight forwarder, now running in production. It quotes, reads Outlook and Teams in real time, checks documents, applies each customer's SOP, works inside their legacy freight ERP, keeps one trusted shipment record, chases carriers and invoices on proof of delivery. Click an agent to see what it does and where a person stays in control.
Coordination
Orchestrator Agent
Your team asks in plain language: search, draft, book, status, complete. The Orchestrator works out the intent, brings in the right specialist agents, runs their checks in parallel and returns one clear answer, with the next action and who owns it.
Orchestrator Agent
Your team asks in plain language: search, draft, book, status, complete. The Orchestrator works out the intent, brings in the right specialist agents, runs their checks in parallel and returns one clear answer, with the next action and who owns it.
Resolve & searchMatching shipments, timeline, owner
Draft workflowApproved draft, linked everywhere
Specialists own the facts and the system changes; the Orchestrator can't bypass their permissions.
Explore the Orchestrator Agent →
Pre-booking salesQuotation Agent
The Quotation Agent turns quote requests from email and Teams into priced, customer-ready quotes. It looks up contract and carrier rates, applies each customer's pricing rules and margins, drafts the quote for approval, chases open quotes and hands accepted ones straight to booking.
Request intakeStructured quote request
Rate lookupRate options with source and validity
Quotes below your margin floor or outside pricing rules need sales approval.
Communications & operationsFreight Agent
The Freight Agent turns emails, Teams messages and attachments into evidence on the right shipment. It checks documents against the stage you're at, triages exceptions and proposes the next action — with severity, owner and due time.
Freight searchMatches with coverage
Freight statusChanges, blockers, accountable next actions
Emails and documents are treated as evidence, never as instructions to execute.
Document readinessDocument Agent
The Document Agent works out which documents a shipment needs for its mode, route, customer and stage: commercial invoice, packing list, bill of lading, air waybill, customs declaration, certificate of origin, insurance. It checks what has arrived, cross-checks the details and chases what's missing before the cut-off.
Required documentsShipment document checklist
Intake & classificationFiled, versioned documents
Low-confidence fields are flagged, never silently accepted.
Customer policySOP Agent
Each customer has its own way of shipping. The SOP Agent reads your customer SOP workbooks from Teams and SharePoint, tracks every version, picks the right variant for each shipment and checks bookings against it before anything moves.
Select SOP variantExact policy version
Draft templateMissing-field checklist
One operations manager approves SOP changes and exceptions.
Native executionLegacy ERP Agent
Most forwarders run a freight ERP that won't be replaced this year. The Legacy ERP Agent works with it directly through its own service interface (SOAP/WCF in our first deployment). It previews every change, waits for exact approval, executes, and reads the result back.
Preview draftDraft preview, nothing written
Execute on approvalNative record and verified receipt
Runs standalone: it doesn't need the TMS or any other agent to start or to work.
Explore the Legacy ERP Agent →
Digital twin & control towerTMS Agent
The TMS Agent keeps the single source of truth for every shipment: references, timeline, exceptions, actions, owners and documents. It tracks operational KPIs, flags delayed departures and arrivals with their impact on manufacturing and warehouse distribution, and gives executives shipped and arrived volumes against forecasted sales.
Search & statusTimeline, freshness, exceptions, owners
Delay & impact alertsRisk alert with impact and evidence
Raw observations are kept separate from accepted facts.
Carriers & terminalsPartner Agent
The Partner Agent manages connections to carriers, airlines, terminals and other partners. It resolves the right tracking identifier, reads the latest status from official sources, registers tracking and normalizes partner events into your timeline.
Connection healthCapability matrix
Tracking identityIdentifier with provenance
Read access is switched on first. Each action is enabled only after its contract, authorization and testing are in place.
Proof of delivery & paymentInvoicing Agent
The Invoicing Agent closes the loop after delivery. It collects proof of delivery, reconciles charges against the quote, booking and carrier invoices, drafts the customer invoice in your billing system, flags disputes and follows up until payment arrives.
POD capturePOD linked to the shipment
Charge reconciliationReconciled charges, variances flagged
Invoices go out only after POD is confirmed and charges reconcile or are approved.
9 agents
One orchestrator coordinating eight specialists, from quote to cash.
Real-time
Messaging and acknowledgement across Outlook and Teams, so every action has an owner.
5 commands
search, draft, book, status, complete. That's all your team needs to learn.
0 unapproved
Records created in the freight ERP without exact human approval.
Legacy data connectivity
If your system is old enough to vote,
If your system is old enough to vote,
our agents still speak its language.
Supply chain runs on systems nobody wants to migrate. We connect agents to what you already have — through APIs where they exist, and through files, feeds and screens where they don't.
EDI X12 204 / 214 / 210EDIFACT IFTMIN · IFTSTACargoWiseIBM AS/400 · iSeriesSAP ECC · S/4HANAOracle · Dynamics 365SFTP · FTP dropsManhattan · Blue Yonder WMSODBC · SQL ServerShared inbox · PDF
EDI X12 204 / 214 / 210EDIFACT IFTMIN · IFTSTACargoWiseIBM AS/400 · iSeriesSAP ECC · S/4HANAOracle · Dynamics 365SFTP · FTP dropsManhattan · Blue Yonder WMSODBC · SQL ServerShared inbox · PDF
Excel · CSV templatesREST · SOAP · GraphQLCarrier & port portalsGreen-screen TMSTelematics · ELDMicrosoft 365 · GmailScanned BOL · PODMES · MRP feedsCustoms filings
Excel · CSV templatesREST · SOAP · GraphQLCarrier & port portalsGreen-screen TMSTelematics · ELDMicrosoft 365 · GmailScanned BOL · PODMES · MRP feedsCustoms filings
Documents
PDFs, scans, emails and spreadsheets turned into structured, validated records.
Feeds & files
EDI, SFTP drops and flat files read and written on your existing schedules.
Databases & APIs
Read-only by default over ODBC, SQL, REST or SOAP; writes only through approved paths.
Screens
Where there's no interface, agents operate the screen a person would — logged and supervised.
System names are trademarks of their owners and are listed as examples of integration targets, not partnerships.
Private AI on open weights
Your data. Your model.
Your data. Your model.
Your building.
Shipping data is commercially sensitive. We can deploy open-weight language models inside your environment and adapt them to your documents, codes and history — so the intelligence you build stays an asset you own.
- On-prem GPU, private cloud VPC, or hybrid with routing by sensitivity.
- Fine-tuned and retrieval-grounded on your SOPs, rate sheets, lanes and past orders.
- Model routing: small local models for routine work, stronger models only where you allow.
- No vendor lock-in — swap models as better open weights ship.
LlamaQwenMistralGemmagpt-ossDeepSeek
Your environment
Agent teamOrchestrator + specialists
Your private LLMopen-weight · tuned on your data
Knowledge & memorySOPs · mappings · history
ConnectorsTMS · WMS · ERP · EDI
Guardrails & auditapprovals · logs · rollback
How an engagement runs
Start with one workflow.
Start with one workflow.
Scale what proves itself.
01Days 1–2
Map
We sit with the team, collect real samples, and pick the slice with the most retyping and the clearest rules.
02Days 2–4
Build
We build the agent team, connect your systems and set the guardrails your people want.
03Day 5+
Prove
Production-like test on your real documents. Measured against baseline effort, cycle time and rework.
04Ongoing
Operate & expand
We run, monitor and improve the agents — then add the next workflow your team chooses.
Proof
Real workflows. Measured outcomes.
Reference engagements with the details your operations and IT leads will ask about.
Logistics · operations connector
5-day path
Customer PDFs → TMS-ready rows
Order PDFs extracted, validated, enriched with port codes and delivered for TMS import, with exceptions routed to people.
Read the use case → Freight forwarding · agent team8 weeks
Automating freight operations
A nine-agent team for a freight forwarder, from quote to cash: inbox, documents, customer SOPs, legacy freight ERP, TMS, carriers and invoicing. In production in 8 weeks.
Meet the agent team → Commerce workflow3-day path
Inherited system, controlled workflow
An undocumented legacy system mapped, extended and handed over with rollback and admin manuals.
Read the use case →
Answers
Questions ops and IT leads ask first.
Is Cloud28.ai a software platform?
No. We're a service. We build custom agents around your workflows and systems, then operate and improve them with you. You own the workflows, rules, mappings and data.
How is this different from Aera, o9 or Kinaxis?
Those are enterprise platforms for decision intelligence and planning. We build execution agents for the day-to-day operational work — documents, bookings, updates, exceptions — inside the systems mid-market logistics teams already run. See comparisons →
We run an old TMS with no API. Can you still help?
Yes. Agents can work through EDI, SFTP, file imports, database reads and, where needed, supervised screen automation.
Does our data leave our environment?
It doesn't have to. We can deploy open-weight models on your infrastructure, or route only non-sensitive tasks to hosted models you approve.
What stops an agent from making a costly mistake?
Confidence thresholds, business rules and approval gates. Uncertain items stop for a person with the evidence attached, and every action is logged.
Do we get KPIs and risk alerts?
Yes. Our TMS Agent flags delayed departures and arrivals and shows the impact on manufacturing schedules and warehouse distribution. It also flags capacity gaps, inventory mismatches and missing documents. Exception checks across logistics and warehouse inventory are acknowledged by your team, so nothing closes silently. Executives see what shipped and arrived against forecasted sales.
Will this replace our team?
It's designed to let the same team handle more volume and spend time on customers and exceptions instead of retyping.
Book discovery
Bring us the workflow your team retypes the most.
In one call we'll tell you whether agents fit, what the first slice should prove, and which systems we need to touch.