v0.8.0
Released October 14, 2026. Supported until April 14, 2027.
v0.8.0 ships 16 behavior changes, 9 security updates, 19 new features, 26 bug fixes, and 1 deprecation. Behavior between the management plane and the data plane changed in this release. The most severe security issue cleared is high.
A fully detailed version of these release notes (including artifact versions) is included in the Admin Console.
The full release notes are opened from the Admin Console, as described in Check the management plane version.
Upgrade and rollback
- The release carries no breaking change, and no operator action is required before upgrading.
- The upgrade rolls through without dropping traffic.
- Rollback to v0.7.1 is unconditional.
Behavior changes
Gateway
A key's rate limit now counts once across every model and route it calls. Available once the data plane is on 0.8.0 or later.
Management plane API
Listing, adding and removing a project's MCP servers now needs the project MCP permission.
Attribute-based routing has two scopes, project and API key: a key's own routing policy replaces its project's.
Consoles
An MCP profile now checks each server's OAuth sign-in against the same provider the gateway uses for that server.
The old /config, /config/<id> and /dashboard-legacy pages are gone.
On a shared install, upgrading removes cross-organization read access and provider editing from a user who was granted Super Admin and whose role has since changed without a revoke, for example through single sign-on role mapping at sign-in.
tare CLI
The command-line tools now install to ~/.tetrate/bin and keep their per-user state in ~/.tetrate, created readable only by its owner.
Environment variables the CLI reads now carry a TETRATE_ prefix.
Commands that install or upgrade a cluster now ask for confirmation first, naming the cluster.
-v now means --verbose on every command.
Installing an identity that names a different data plane than the one already installed is now refused, as is installing an expired identity.
tars serve install --proxy-url is removed.
A mistyped subcommand now fails instead of printing help and reporting success.
Commands now exit 3 when they refuse to act and 4 when they changed the cluster before failing, where both previously exited 1.
tare doctor no longer reports a healthy data plane as Degraded when the doctor itself lacks an optional permission.
Data planes deployed with the GCP Terraform module now run tare doctor every 5 minutes instead of every 15, so the management plane receives about three times as many doctor reports from each of them.
Security updates
Auth
Sign-in session cookies are now limited to your own environment's domain.
Gateway
The public MCP catalog route no longer sends the browser's cookies to the catalog server, and no longer passes the server's cookies back.
All binaries are now built with Go 1.27.2 and golang.org/x/net v0.60.0, addressing GO-2026-6617 (HTTP/2 server crash via an HPACK encoder race) and GO-2026-6613 (HTTP/1 connection desync after a 2xx CONNECT response), both reachable from the AI Gateway.
A data plane whose ID another organization also uses now needs declared hostnames for its URL to be returned by the inference API and for Prompt to reach it.
tare CLI
Every binary the install script installs is now signature-verified.
Management plane API
The inference API no longer returns another organization's data plane URL, and Prompt sends only to your own data planes.
SetWorkspaceURL and SetDataplaneURL refuse to set or clear a data plane URL with FailedPrecondition when another organization uses the same data plane ID.
Consoles
On a shared install, revoking Super Admin now also removes the platform-wide read access and provider editing that came with the role.
In the Developer Console, MCP OAuth sign-in and MCP tool calls now use only the OAuth clients of the request's project, plus those set up in the Admin Console for every project.
New features
Management plane API
Project owners can list the enabled MCP servers their project doesn't have yet, searched by name and paged, to pick which ones to add.
Project owners can add and remove their project's MCP servers, and Viewers can list them.
A project or API key rate-limit policy can now limit requests per minute, requests per hour and tokens per minute beside tokens per hour, in any mix. Available once the data plane is on 0.8.0 or later.
Admins can read whether a model in the catalog is retired, deprecated, new or in preview, with the reason and any retirement date.
Admins can see which models their organization uses retire soon, and which projects and API keys still call them.
The model catalog can be synced through the admin API: preview what a sync would change, apply it in the background pinned to the exact documents previewed, and poll the run's progress.
Consoles
The Admin Console has a Rate limits tab on a project and a Rate limits section on an API key, where an admin sets requests per minute, requests per hour, tokens per minute and tokens per hour with the Block action. Available once the data plane is on 0.8.0 or later.
Admins can add a catalog-listed replacement as the next fallback in an API key's model-specific fallback policy when the model is deprecated or has a retirement date.
The Admin Console's data plane list and each data plane's page now name the release it runs from the deployed chart, or its last install or upgrade, and mark a data plane that lacks a high or critical security fix from a newer release.
Gateway
A fallback policy now covers a retired model. Available once the data plane is on 0.8.0 or later.
A data plane can now terminate TLS itself.
tare CLI
tare doctor now checks the nodes running your data plane.
The tare doctor JSON report now includes the schedule its in-cluster CronJob runs on, under data.doctor_schedule, and the management plane stores it with each data plane's status.
The data plane ingress install command has a new flag, --lb-tls-passthrough.
tetrate agentrouter doctor checks the data plane's port 443 listeners: it reports a hostname that answers 403 because authentication is missing from it, and treats the ResourceNotFound status the TLS policies show with two or more published hostnames as healthy.
A single tetrate command replaces the separate tare, tars and admin tools.
Commands that change a cluster now name the cluster they are about to change before changing it, and record the operations they ran to a log under ~/.tetrate/logs that the error names when one fails.
tare doctor now flags a data plane Controller or the egress proxy running below its desired replica count, not only one with no replicas left.
tare doctor now reports the release your data plane is running, read from the deployed chart, instead of only the version of the tare binary that ran it. Available once the data plane is on 0.8.0 or later.
Bug fixes
Consoles
Developer Console pages such as API Keys no longer show a second scrollbar.
The Developer Console home page's change figures now compare against the previous period of the same length and say so, for example "vs previous 7 days".
On a single-organization install, a user given Provider Admin or Model Admin on the Access page, directly or through a group, gets catalog admin at once, and loses it when the role is removed.
The playground no longer fails with "Invalid API key" when you return to it about a day after your last use.
Management plane API
A policy or routing update whose data-plane publication fails is now retried a few times, with a pause between attempts, instead of being dropped after the first failure.
Moving the corporate OIDC SSO provider to a different identity provider no longer keeps the previous provider's endpoints.
Corporate OIDC sign-in with Microsoft Entra ID now succeeds when the identity provider's JWKS omits its optional algorithm field.
Microsoft Entra SSO providers registered with the tenant Authority URL as the issuer keep signing in, and users without an email attribute sign in with their upn, preferred_username or unique_name, as they did before 0.6.0.
Getting, setting or deleting a project setting now returns NOT_FOUND when the project is missing or deleted.
MCP servers whose OAuth client was created through the API now get their sign-in applied on gateways.
Changes to an MCP catalog server now reach data planes that host no project gateway, so a re-pointed server stops serving its old URL and a disabled or deleted one stops being reachable at /mcp/s/<server>.
Daily usage totals and budget spend no longer drop for days older than two days.
Deleting an MCP profile frees its name for a new or renamed profile.
Adding or removing a model from a project now updates keys that carry their own settings (BYOK, fallback, traffic split, or a rate limit), so they no longer keep routing against the old model list.
Project default settings, project membership changes, the request-log mode, and rate-limit policies moved to another target now reach your gateways within the usual update cycle.
Gateway
Rate limits now hold during bursts on a data plane running more than one replica. Available once the data plane is on 0.8.0 or later.
A changed rate limit now also applies to requests on connections that were opened before the change, within the usual delay of about 10 seconds. Available once the data plane is on 0.8.0 or later.
API admins can now view, create and edit gateway auth policies.
A change to an API key's routing now takes effect even when it needs fewer routes than before, instead of leaving the key stuck deploying.
Removing a fallback policy from a data plane now also removes the fallback routes it created.
Gateway sign-in rules are now re-applied when a gateway gets its URL, when the catch-all gateway changes, when a gateway moves to another data plane, and when a gateway is deleted.
tare CLI
The install script at tools.tetrate.ai no longer exits part-way through with only some of the tools installed.
An interrupted MCP uninstall now completes the removal when it is re-run, instead of reporting success over a half-removed installation.
Commands that ask for confirmation no longer wait indefinitely when nothing can answer, so a piped or scheduled run fails with a message rather than hanging.
A data plane with hundreds of API keys no longer reports itself unhealthy in the admin console while it is serving traffic normally.
The doctor now reports API keys whose routing was never fully created on the data plane.
Deprecations
tare CLI
The tare, tars and admin commands are replaced by tetrate.