Ultrium Let’s talk
Menu

Technology / Custom models & vehicle evidence

Our models.
A real-world purpose.

Two custom fine-tuned models, built by Ultrium: Orá-1 for vehicle intelligence through Velocity, and Chronos-1.5 for the Chronos-1 in-car companion—not yet deployed.

Translucent panels hold distinct point patterns, with an aqua thread connecting them in a conceptual study of traceable information.
A connection you can trace.

Ultrium / Custom fine-tuned models

TWO MODELS. DISTINCT ROLES.

Vehicle understanding.
Journey assistance.

Two models. Two distinct roles.

Vehicle intelligenceDocumented through Velocity

Orá-1

Our custom fine-tuned model turns Velocity’s vehicle evidence into answers with sources, freshness, and uncertainty attached.

Orá-1 is the intelligence model, not the Velocity API itself or the Orá driver app. Access and evidence requirements are described on Velocity.

Model approach

  • Evidence-cited answers
  • Context with limits
Explore Orá-1 on Velocity (opens in a new tab)
In-car assistanceBuilt · Not deployed

Chronos-1.5

Our custom fine-tuned model for Chronos-1, the in-car companion combining vehicle evidence, conversation, and travel context.

Chronos-1.5 has not been deployed. These are planned applications, not live integrations or autonomous driving. No launch date is announced.

Planned applications

  • Location-aware agentic payments
  • Parking recommendations
  • Optimized routing
Talk about Chronos-1.5

Inside the companion / Development preview

Chronos-1
Context for the road ahead.

In development · Not publicly available

Chronos-1 is the companion: a native app in a vehicle’s infotainment system. Chronos-1.5 is our custom model for it.

Step inside Chronos

Vehicle awareness

Connects to supported Bluetooth diagnostic adapters, records telemetry, and compares readings over time.

Grounded AI assistance

Answers vehicle questions using recorded evidence, distinguishes live data from synthetic replay, and flags missing or stale information.

Voice conversations

Includes a cloud voice integration. Audible end-to-end conversation still needs verification.

Travel planning

Supports optional calendars, saved places, nearby events, directions, weather, and departure reminders.

Vehicle memory

Keeps local driving sessions and synchronizes them to a backend for historical analysis.

Safety and consent.

Complex interactions and camera capture are parked-only. External actions require explicit approval. Chronos is an advisory companion—not autonomous driving or a definitive mechanical diagnostic system.

Development preview, not public availability. Payments, parking, and optimized routing are planned. Audible end-to-end voice still needs verification.

From evidence to answers

Developer documentation (opens in a new tab)
Source inputsObservationsAssessmentsCited answers

Trace the source.

Every observation retains its origin and timing.

Keep uncertainty.

Missing data stays unknown. A code is not a diagnosis.

Cite the evidence.

Answers point to the record—not just conversation history.

Access stays scoped.

Explicit vehicle grants and separate application data stores. The Orá driver app is distinct from Orá-1 Velocity.

Product boundaries

Accountability before automation.

NIST informs our approach to AI risk—not a certification or completed assessment.

Our research references

The interactive universe is a visual metaphor—not live vehicle data or a physics simulation. Explore the field.

The next step

Working through
an integration?

Bring your sources, access requirements, and operating constraints. Let’s discuss what the evidence needs to support.

Start a technical conversation