Skip to main content
IronKernel
Products Solutions For Customers About FAQ Contact
IronKernel Platform

Platform foundations for operational integrity

IronKernel provides shared contracts, reusable runtime primitives, and explicit product boundaries so teams can execute without brittle handoffs.

Proto-first operational contracts

Cross-product workflows are grounded in explicit contracts that keep operational behavior consistent between products.

  • Contracts are versioned and product-scoped.
  • Cross-product behavior is reviewed through explicit interface changes.
  • Typed service boundaries reduce integration ambiguity.
Open platform brief

Proof snippets

  • Platform documentation defines reusable contract-oriented building blocks.

    verified

    docs/products/ironkernel/product.md · Product Role in the Platform

    Contract: proto/*/*/v1

Shared runtime primitives

Routing and geofence capabilities are implemented as shared libraries consumed across operational products.

  • Routing provider abstraction supports multiple backends.
  • Geofence engine centralizes zone logic and event semantics.
  • Products consume shared primitives rather than duplicate implementations.
Open platform brief

Proof snippets

  • Routing provider module is documented and implemented as shared platform capability.

    verified

    docs/products/ironkernel/product.md · Module Catalog > Routing Provider

    Code: backend/libs/routing

  • Geofence engine module is documented and implemented for cross-product use.

    verified

    docs/products/ironkernel/product.md · Module Catalog > Geofence Engine

    Code: backend/libs/geofence

Operational ownership boundaries

Product ownership boundaries are explicit so dispatch, maintenance, yard, and personnel decisions stay consistent.

  • Crew owns personnel readiness and credential posture.
  • CMMS owns asset lifecycle and maintenance readiness context.
  • TMS and YMS consume shared state for execution decisions.
Open platform brief

Proof snippets

  • Crew ownership and decision boundaries are defined as normative behavior.

    verified

    docs/products/crew/product.md · Canonical Ownership & Decision Boundaries (Normative)

  • CMMS integration contracts define cross-product operational boundaries.

    verified

    docs/products/cmms/product.md · Cross-Product Integration Contracts

Integration model

Cross-product workflows follow explicit ownership boundaries. Products exchange typed contracts instead of hidden side effects.

Boundary principle

Product teams own their domain decisions and expose stable contract surfaces.

Flow principle

Events and RPC contracts propagate state transitions across CRM, TMS, CMMS, Crew, YMS, and Pilot.

Verification principle

Marketing claims are tied to product docs and code/contract references before publish.

AI-ready architecture

A single operational data model means AI features don't need integration — they're native. IronKernel is building intelligence across the platform.

On Our Roadmap

TMS

Dispatch Co-Pilot

Conversational AI that queries live loads, ranks drivers by performance and proximity, and briefs dispatchers on their day.

CRM

Lead Scoring

Automated scoring of inbound inquiries based on historical conversion patterns, surfacing high-priority leads to your sales team.

Crew

Document Intelligence

Instant data extraction from CDL photos, medical cards, and compliance documents. High-confidence scans auto-advance onboarding.

YMS

Dock Queue Forecasting

Time-series models predict dock wait times by hour, enabling proactive trailer routing and detention avoidance.

AxialOps

ML Fault Classification

Trained on synthetic vibration signatures from AxialSim, the classifier identifies bearing defects, imbalance, and looseness before analysts open the spectrum.

AxialOps

Remaining Useful Life

Track vibration severity over time and predict days to critical threshold, scheduling preventive replacement during planned downtime.

These capabilities are in active development. Availability varies by module.