Develop the model layer
Advance an in-house model program alongside the company's agentic software portfolio.

Trunnion LLM is the company's in-house model layer, currently in development. It is a model-building program - not a new label for third-party model routing.
See the work in context
An illustrative workspace for model & application teams. Explore the work and the decision behind it.
An intended product task needs explicit evaluation criteria and a documented release boundary.
Review behavior and limitations before making a release decision.
Review the material behind the proposed action.
Confirm scope, permissions and consequences.
Approve, revise or decline through the defined workflow.
An enterprise model needs to be evaluated in the context of the work it will support. Capability, limitations, provenance and operating conditions all matter. The LLM program creates a dedicated place for that development within Trunnion.
Built by Trunnion AI, a wholly owned Duskbridge company. This page presents the direction of a product in development; it does not promise release timing or available features.

Advance an in-house model program alongside the company's agentic software portfolio.
Define the evidence needed to assess usefulness and limitations for intended product work.
Establish the release boundary before describing model capabilities as available to customers.
An illustrative sequence, not a product screenshot or a guarantee of released behavior.
Identify the intended work and evaluation context.
Build and assess the model layer.
Review behavior, limitations and the proposed operating conditions.
Publish supported capabilities only when established for a release.
Start with the workflow you need to improve. Then confirm what the proposed release can actually do.
This page does not announce a public model endpoint, weights or model license. The program is building.
No. Core is the orchestration runtime and developer platform. Trunnion LLM is the in-house model layer.
No performance or benchmark claim is established here. Such claims need release-specific evidence.
Portfolio relationships do not establish an included integration or entitlement.
Start with a non-sensitive overview. Product fit, release scope and next steps belong in a direct conversation.