Skip to content

Integration

Databricks logo

Databricks

Evaluate, guard, and observe models served from the Databricks lakehouse: Mosaic AI Model Serving endpoints under the Hyperpriors control plane.

Request access to connect

Connections are provisioned in private beta — not authorised from this page.

01 — Permissions

When connected, Hyperpriors is limited to the following — declared up front, revocable at any time. Scope is granted during provisioning, not by a button on this page.

  • 01

    Route agent requests to Mosaic AI Model Serving endpoints through the Hyperpriors harness

  • 02

    Run evaluation suites against models served from your Databricks workspace

  • 03

    Enforce guardrail policies on the inputs and outputs of Databricks-served models at runtime

  • 04

    Record traces, token usage, cost, and latency for every serving endpoint call

  • 05

    Track behavioural drift as model versions are promoted through MLflow

02 — Details

Built by
Databricks
Category
Data and AI platform

03 — Notes

About Databricks

Databricks is a data intelligence platform built on the lakehouse architecture, combining data engineering, analytics, and machine learning in one environment. For AI workloads, Mosaic AI Model Serving exposes custom models, fine-tuned models, and foundation models as managed endpoints, while MLflow handles experiment tracking, model versioning, and the registry through which models are promoted towards production. Many organisations treat Databricks as the system of record for both their data and the models trained on it.

What the integration does

Hyperpriors treats a Mosaic AI serving endpoint like any other model target. The harness routes agent requests to your endpoints with retries, timeouts, and fallback routes configured centrally rather than per service.

Evaluation suites run against the models behind those endpoints, so a new version registered in MLflow is measured against the same fixed suites as its predecessor before it takes traffic. Because serving infrastructure changes as well as model weights — runtime upgrades, endpoint configuration, dependency updates — Hyperpriors watches for behavioural drift across serving-stack upgrades, not only across model versions. Guardrails inspect inputs and outputs at runtime, and observability records every call with trace context, token usage, cost, and latency.

Promotion through the registry becomes a reviewed, measured change: the evaluation evidence sits alongside the model version it describes.

Get started

Connect your Databricks workspace and serving endpoints from the Hyperpriors dashboard, or contact us to talk through your deployment.