Platform / Model Management

A governed catalog for every model in your organisation.

Central model catalog, per-team enable lists, stable versioned aliases, and deprecation management — so teams access the right models through the governed gateway and you never encounter unexpected provider retirements.

Book a demo Browse model library

Model Catalog

A central registry of every model available in your ManyLayers deployment — frontier models from configured providers and open-weight models from the curated library. Each entry includes provider, version, capability tags, and current status.

  • Frontier models from all configured providers listed automatically
  • Open-weight models added from the curated library with optimised serving configs
  • Capability tags (chat, embeddings, vision, code) enable policy-based access rules

Model Catalog — key behaviours

01 Frontier models from all configured providers listed automatically
02 Open-weight models added from the curated library with optimised serving configs
03 Capability tags (chat, embeddings, vision, code) enable policy-based access rules

Per-Org Enable Lists

Not every model should be available to every team. Define an allow-list of models per organisation, department, or team. Requests for unlisted models are rejected at the gateway with a clear error before any provider is contacted.

  • Enable lists configured per org, team, or API key scope
  • Deny-by-default: only explicitly enabled models are accessible
  • Override lists for specific API keys enable power-user access without broad exposure

Per-Org Enable Lists — key behaviours

01 Enable lists configured per org, team, or API key scope
02 Deny-by-default: only explicitly enabled models are accessible
03 Override lists for specific API keys enable power-user access without broad exposure

Versioning & Aliases

Models are referenced by stable aliases in application code. Aliases point to specific provider-model-version tuples. Update the alias target to upgrade a model version without touching any application or routing config.

  • Aliases abstract provider-specific model identifiers from application code
  • Version pinning available for reproducible workloads
  • Alias history tracked — roll back to a previous target with one change

Versioning & Aliases — key behaviours

01 Aliases abstract provider-specific model identifiers from application code
02 Version pinning available for reproducible workloads
03 Alias history tracked — roll back to a previous target with one change

Deprecation Management

When a provider deprecates a model version, ManyLayers surfaces the deprecation date in the catalog and lets you map the alias to a replacement before the deadline. No surprise failures when providers retire old versions.

  • Deprecation dates synced from provider announcements where available
  • Alerts configured for models nearing end-of-life
  • One-click alias remapping to redirect traffic to the replacement model

Deprecation Management — key behaviours

01 Deprecation dates synced from provider announcements where available
02 Alerts configured for models nearing end-of-life
03 One-click alias remapping to redirect traffic to the replacement model
Feature matrix

Model types and management capabilities.

Feature Catalog Enable lists Versioning Deprecation mgmt
Frontier model listing ✓ ✓ ✓ ✓
Open-weight models ✓ ✓ ✓ ✓
Fine-tuned adapters ✓ ✓ ✓ —
Per-team access scoping — ✓ — —
Alias-based routing — — ✓ ✓

Bring every model in your organisation under governance.

Book a demo Browse model library