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
The shared control planeLive

Trunnion Core

The orchestration and governance layer every platform runs on.

Core coordinates mission workflows, models, tools, identity, policy, human approval, and the evidence a release is designed to retain. It is not sold as a standalone product. It ships through Trunnion platforms and scoped custom builds.

Discuss this capability All innovations
System roleTrunnion Core
  1. 01Mission definition
  2. 02Identity and policy
  3. 03Agent team
  4. 04Model and tool routing
  5. 05Human authority
  6. 06Evidence 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

One policy surface

The workflow, model, and tool path can be evaluated against the same release-specific authorization boundary.

02

Human authority stays explicit

Consequential actions are designed to pause for a named operator to approve, edit, or reject.

03

A record follows the run

Execution and approval evidence is designed into the workflow, with exact coverage and replay verified per release.

Trunnion Core operating pattern

How Trunnion Core fits into a governed run.

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

  1. 01
    Mission

    Declare the job

    Define the objective, inputs, allowed systems, and decision owner.

  2. 02
    Policy

    Resolve authority

    Identity, attributes, and tool rules scope what the run may do.

  3. 03
    Compose

    Route the work

    The control plane assigns bounded tasks across agents, models, and tools.

  4. 04
    Approve

    Stop for a person

    Consequential actions wait for an authorized human decision.

  5. 05
    Evidence

    Retain the record

    The verified release determines the action, approval, and reasoning evidence available.

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

Where it connects

One innovation layer, connected to product work.

Every Trunnion platform runs on Core. Each platform keeps its own workflow, release evidence, and deployment scope.

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

What this page establishes.

Public materials describe the architecture and design intent. Implementation details, control coverage, conformance, security behavior, and availability must be verified for the exact product release and environment.

Program status
Live
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