Feature

Model Access Policies

Limit each organization, team, and key to an allowlist of models and providers. Fallbacks stay inside that list, and a request with no permitted route is rejected.

Allowed routes

Scope

Org, team, key

Fallbacks

Same list

Miss

Rejected

The models and providers a key can call, including routes blocked by a parent policy.

Allow

Named providers

Only these routes can receive the request.

Inherit

Parent list

A child key cannot widen an enforced list.

Reject

No route left

The request stops when nothing permitted remains.

New capabilities

What your team gains with Concentrate

01

Set the allowlist where the work lives

Choose the models and providers an organization, team, or key can call. A request for anything else does not leave Concentrate.

02

Children inherit the tighter list

When a parent enforces the restriction, a team or key under it cannot add providers the parent blocked.

03

Fallbacks stay inside the list

If the first route fails, Concentrate tries the next destination only when that destination is still allowed. A prohibited route is not used as a backup.

Who Concentrate is designed for

How model access policies decide where a request can go

You choose the allowlist. Concentrate enforces it on every request, including fallbacks. Model access controls are the same setting. A HIPAA organization adds a second limit: the route must also be BAA-covered and support zero data retention.

Allowlists

Restrict models and providers on the organization, a team, or a key. The key can only be narrower than an enforced parent.

Inherited restrictions

An enforced parent list wins. Creating a new key does not reopen providers the organization already blocked.

Fallback behavior

Fallback destinations are filtered with the same rules as the primary route. A destination outside the permitted set is skipped.

Healthcare routes

On a HIPAA organization, BAA coverage and zero data retention are required even when a model is on the allowlist. See the HIPAA LLM Gateway for the locks, HIPAA Inference for the API and inference, and the BAA-eligible filter in Model Fortress for the routes.

Feature basics

Frequently asked questions

What is a model access policy?
A model access policy is the allowlist of models and providers on an organization, team, or key. Concentrate will not send a request to a route outside that list. When a parent enforces the list, a child key cannot widen it.
What happens when no permitted route is left?
Concentrate rejects the request. Fallbacks are checked the same way, so a fallback destination outside the permitted set is not tried. On a HIPAA organization the permitted set is also limited to BAA-covered, zero-data-retention routes.