Skip to content

Privacy controls

Choose optional technologies

Necessary technology is always active because it provides security and remembers this choice.

NecessaryConsent record, security, and core site operation.
Always on
Request a demo
PlatformsGovernment & DefenseDAFPulseOperations & ERPCortrovaHaultroManaged ServicesARIAMoreZennvueRealtrAIVortiekCustom SoftwareAll platforms
InnovationsProgramsTrunnion CoreTrunnion VoiceTrunnion LLMTrunnion MeetAll innovations
IndustriesBrowse by industryDefense & National SecurityGovernment ProcurementManufacturing & ERPWaste & Fleet OperationsEvents & MarketplacesMore industriesReal EstateManaged ServicesMarketing & SEOTravel & HospitalityAll industries
How it worksSecurityInsightsAboutRequest a demoView the platforms
Model programIn development

Trunnion LLM

Model routing and evaluation, under Trunnion's control.

Trunnion is model-agnostic today. The Trunnion LLM program explores how model routing, evaluation, provenance, and release review can be controlled inside the same governed architecture. It does not identify a proprietary public model offer.

Discuss this capability All innovations
System roleTrunnion LLM
  1. 01Task context
  2. 02Model policy
  3. 03Candidate route
  4. 04Evaluation boundary
  5. 05Human decision
  6. 06Provenance record

Conceptual system view. This is not a live product screen.

Why this layer exists

A technical program with a defined place in the system.

01

Route by mission need

The architecture can select hosted or self-hosted models without rewriting the whole workflow.

02

Evaluate before release

Licensing, provenance, security, and task-specific evaluation belong in the release decision.

03

Separate program from offer

Research activity is not represented as a model endpoint, product entitlement, or performance claim.

Trunnion LLM operating pattern

How Trunnion LLM fits into a governed run.

This sequence explains the intended relationship between the capability, the control plane, human authority, and release evidence.

  1. 01
    Task

    Receive bounded context

    The mission and data boundary define the model task.

  2. 02
    Policy

    Resolve eligible routes

    Provider, hosting, licensing, and data rules constrain selection.

  3. 03
    Route

    Select a candidate model

    A release-specific router assigns work to an approved option.

  4. 04
    Review

    Evaluate the output

    Task checks and human review govern consequential use.

  5. 05
    Record

    Retain provenance

    The available release record identifies the approved routing and review context.

Illustrative workflow. Exact controls, integrations, and evidence are verified for the deployed release.

Where it connects

One innovation layer, connected to product work.

This program is being developed in relation to Core and the platform family. A link below does not establish that the capability is available in that product.

Defense & National SecurityDAFPlatform liveGovernment ProcurementPulsePlatform liveManufacturing & ERPCortrovaPlatform liveWaste & Fleet OperationsHaultroPlatform liveEvents & MarketplacesZennvuePlatform liveReal EstateRealtrAIPlatform live
Current public boundary

What this page establishes.

No proprietary Trunnion model is marketed as available. Training data, benchmarks, model weights, performance, licensing, and launch timing are not stated without release evidence.

Program status
In development
Customer entitlement
Confirmed in the written agreement
Control behavior
Verified for the exact release and environment
Certification
No certification is established by this page

Get started

Ready to build on Trunnion AI?

See the governed control plane run against your workflow, in your environment. From cloud to air-gap.

Request a demoAll innovations