Tier 0 model control plane

Model Hub

One control plane for every model your projects run

Model Hub is a self-hosted, single-owner control plane for providers, model catalogs and project assignments. Projects pull a token-scoped projection, then call providers directly; inference traffic never passes through the hub.

In buildControl plane and admin UI· 2026-10-28
TypeScriptHonoAstroSQLite

See where Model Hub sits in the Tier 0 family.

Problem

Model configuration is duplicated

Every project tends to keep its own provider credentials, model list and pricing. The same model is configured many times, aliases drift between projects, and there is no single place to see which project may use which model or what it costs.

Approach

Control plane, not a gateway

Model Hub keeps the authority for credentials, catalog entries, aliases, roles and budget data. Each project pulls its own projection with a token and connects to the provider directly. The hub never proxies inference, streaming or centralized billing.

What it does

01

Provider vault

Presets for Ark Plan, Ark Platform, Agnes, Anthropic, OpenAI and OpenSpeech; credentials are sealed with AES-256-GCM, masked and rotatable.

02

Five-modality catalog

Text, image, video, audio and embedding models share one catalog with pricing, endpoints and dialect adapters.

03

Assignments and guardrails

Many-to-many model/project assignments with primary/fallback roles, per-project aliases and daily budgets.

04

Distribution and cache

Token-scoped projections use revisions, ETag and 304; a 0600 local cache keeps projects running if the hub is down.

What is real today

Taken from the current catalog description and the public landing copy.

Shape
control plane, not gateway
Catalog
5 modalities
Assignments
many-to-many
Distribution
ETag / 304 + 0600 cache
Secrets
AES-256-GCM envelope

Boundary

It is not an inference gateway, a streaming proxy, a centralized billing system or a vault for end-user BYOK keys. Inference and budget enforcement stay inside each project; the hub supplies the configuration and collects usage.

Planned integration

→ This product

uses · Proposed

Agent Ops

Cost and budget control

Evidence (1)
  • agent-ops/docs/prd/Agent-Ops-多Agent角色与团队-PRD-2026-11-19.md

    PRD M3 future scope: Agent Ops cost and budget control through Model Hub usage data.

See where Model Hub sits in the Tier 0 family.

Open the product map