Model and vendor registry
Where the intelligence comes from, and what happens when it goes away
12 models from 7 suppliers, each with its provenance, its data boundary, the towers that call it and the agents that depend on it. The registry exists to answer one question a buyer will ask: if this supplier withdraws the model, changes the price or is bought by a competitor, what breaks and how long does it take to move.
Health
Concentration, currency, substitutability, exposure
Each reading names the weakest record underneath it rather than averaging it away.
Supplier concentration
80%
Abraxas Foundry 61% · Corvid Labs 19% of estate calls. A single commercial decision moves most of the estate.
Substitution proven
8 of 9
Of the 9 models that name a substitute, 1 has the swap written but never run. A further 3 name no substitute at all.
Deprecation exposure
168
Agents on a model whose end of life is announced. Nearest hard date Dec 31, 2026.
Run on our own hardware
3 of 12
Weights held in our own tenancy cannot be withdrawn by a supplier. Everything else can.
Operations
Suppliers, then models
A supplier row is a commercial exposure. A model row is an operational one. They fail differently and they are listed separately.
Suppliers
7 suppliers · concentration is share of estate inference calls, not share of spend
Contract Enterprise agreement, committed annual volume · term ends Mar 31, 2027
Reprice notice 90 days · exit notice 90 days either side
Unit price is fixed for the committed volume band until the term ends. Anything above the band is billed at list, and list has moved twice in the last eighteen months. There is no protection at all on a successor model: when a model is retired, the replacement is priced fresh.
Six of every ten inference dollars go to one supplier. The reasoning and extraction work could be moved on a few weeks of evaluation. The embedding work could not — the entire retrieval corpus is embedded in this vendor’s vector space and a change of provider means re-embedding all of it.
Models: Abraxas Reason 4 · Abraxas Reason 3 · Abraxas Swift 2 · Abraxas Embed 3 · Abraxas Vision 2 · Abraxas Reason 2
Contract Enterprise agreement, pay as you go above a small floor · term ends Dec 31, 2026
Reprice notice 30 days · exit notice 30 days either side
Thirty days of notice on any list change and no committed band. Cheap to leave, cheap to be repriced against.
Held deliberately as the second source. Every workflow that calls Corvid has an Abraxas route configured behind it, and the reverse is true for four of the five reasoning workflows.
Models: Corvid Counsel 2 · Corvid Embed 1 · Corvid Counsel 1
Contract Permissive licence, no vendor contract
Reprice notice Not applicable · exit notice None
There is no price to protect. The cost is the compute we rent to serve the weights, which is a Nimbus line item, not a Helix one.
The weights are held on our own storage. If Helix stopped publishing tomorrow the models already in production would keep running unchanged. This is the only part of the model estate with no deprecation exposure.
Models: Helix 70B Instruct · Helix 8B Instruct · Helix Guard 3
Contract Committed spend agreement with reserved capacity · term ends Jun 30, 2027
Reprice notice 60 days on uncommitted capacity · exit notice 120 days
Reserved capacity is fixed for the term. Burst capacity is at spot and has ranged 1.4x to 3.1x reserved in the last six months.
The serving stack is containerised and has been rebuilt from scratch on a second provider in a lab, but never under load and never with production data.
No model in the registry maps to this supplier.
Contract Annual subscription by index size · term ends Jan 31, 2027
Reprice notice 60 days · exit notice 60 days
Fixed for the term at the contracted index size. Growth past the size band reprices the whole subscription, not the increment.
Index contents are exportable as JSONL with vectors intact. The vectors are only meaningful to the model that produced them, so this dependency is really the Abraxas embedding dependency wearing a different name.
No model in the registry maps to this supplier.
Contract Annual subscription by ingested event volume · term ends Nov 30, 2026
Reprice notice 30 days · exit notice 30 days
None beyond the current term. Event volume has grown 3.2x since the contract was signed and the renewal will be quoted against the new volume.
Traces are the evidence trail behind every automated decision. They are exported nightly to our own object storage in OpenTelemetry format, so the record survives the vendor. The query experience does not.
No model in the registry maps to this supplier.
Contract Enterprise agreement bundled with the wider IT estate · term ends Mar 31, 2028
Reprice notice 90 days · exit notice 180 days
Per-identity price fixed to the end of the term.
Standard OIDC. Group and entitlement mappings are held in our own configuration, not in the provider, so a change of provider is a project rather than a rebuild.
No model in the registry maps to this supplier.
Model cards
12 models · 9 active · 1 deprecation announced · 2 retired
Provenance and boundary
Hosted Provider cloud, EU and US regions pinned per tenant · Committed volume band
Regional pinning enforced at the gateway. A US-pinned tenant cannot route to an EU endpoint even under failover.
Contractually excluded from provider training. Zero-retention endpoint; prompts and completions are not stored by the provider beyond the request.
Who depends on it
412 agents
Towers h2r · s2p · o2c · r2r · p2p · legal · ai-ops
EVS-REASON-CORE
Substitution path
Corvid Counsel 2 — tested
Corvid Counsel 2 has been run against the same golden sets. It scores 3.1 points lower on the extraction suites and 1.4 points higher on long-document review. A switch would be a visible quality change, not a silent one.
The single largest dependency in the estate. Also the easiest of the large ones to substitute, because nothing is persisted in its representation.
Provenance and boundary
Hosted Provider cloud, EU and US regions pinned per tenant · Committed volume band
Same gateway pinning as Reason 4.
Contractually excluded from provider training. Zero-retention endpoint; prompts and completions are not stored by the provider beyond the request.
Who depends on it
168 agents
Towers m2d · a2l · c2l · data-analytics
EVS-REASON-CORE
Substitution path
Abraxas Reason 4 — tested
Reason 4 passes every suite Reason 3 passes and costs 1.9x per call at current pricing. The migration is a cost decision, not a capability one, and the cost has not been approved.
Hard end of life is 135 days away and 168 agents still call it. Nobody has been named to own the cutover and no budget line exists for the price difference.
Provenance and boundary
Hosted Provider cloud, EU and US regions pinned per tenant · Committed volume band
Regional pinning enforced at the gateway.
Contractually excluded from provider training. Zero-retention endpoint; prompts and completions are not stored by the provider beyond the request.
Who depends on it
286 agents
Towers h2r · s2p · o2c · r2r · it · m2d · ai-ops · c2l
EVS-ROUTING
Substitution path
Helix 8B Instruct — tested
Helix 8B Instruct, self-hosted, reaches within 1.2 points on the routing suites. It has been run in shadow against live traffic for three weeks and is the cheapest genuine escape hatch in the registry.
High call volume, low unit cost, proven substitute. Not a concern.
Provenance and boundary
Hosted Provider cloud, EU and US regions pinned per tenant · Committed volume band
Regional pinning enforced. Vectors are written to Vectorline in the matching region.
Contractually excluded from provider training. Zero-retention endpoint; prompts and completions are not stored by the provider beyond the request.
Who depends on it
341 agents
Towers h2r · s2p · o2c · r2r · p2p · it · legal · a2l · c2l · m2d · ai-ops · data-analytics
Substitution path
Corvid Embed 1 — never exercised
Corvid Embed 1 is a plausible replacement on published benchmarks and has never been run against our corpus. Switching means re-embedding every document in the retrieval store, revalidating every retrieval-dependent workflow and accepting a period where the two vector spaces cannot be compared. That work has never been scoped and never been costed.
This is the real lock-in. It is not the biggest line of spend and it is the hardest thing in the estate to leave, because the dependency is written into the data rather than into the call.
Provenance and boundary
Hosted Provider cloud, EU and US regions pinned per tenant · Committed volume band
Regional pinning enforced. Source documents are streamed, never stored provider-side.
Contractually excluded from provider training. Zero-retention endpoint; prompts and completions are not stored by the provider beyond the request.
Who depends on it
97 agents
Towers s2p · o2c · p2p · a2l
EVS-EXTRACT-DOC
Substitution path
No substitute identified
No substitute has been identified. The two candidates evaluated in March both fell below the extraction floor on handwritten and stamped documents, which is a material share of the invoice and customs traffic.
Single-sourced with no tested alternative. Lower spend than Reason 4, higher exposure.
Provenance and boundary
Hosted Withdrawn · Committed volume band
Not applicable — no traffic.
Contractually excluded from provider training. Zero-retention endpoint; prompts and completions are not stored by the provider beyond the request.
Who depends on it
0 agents
No tower maps to this model.
EVS-REASON-CORE
Substitution path
Abraxas Reason 3 — tested
Migrated to Reason 3 in November 2025. Completed ahead of the hard date with no evaluation regression.
Closed out. Kept in the registry because the deprecation calendar is only credible if the completed migrations stay visible.
Provenance and boundary
Hosted Provider cloud, EU region only · Pay as you go
EU only. US-originated matters are routed to Abraxas Reason 4 rather than crossing the boundary.
Contractually excluded from provider training. Zero-retention endpoint; prompts and completions are not stored by the provider beyond the request.
Who depends on it
143 agents
Towers legal · r2r · c2l · data-analytics
EVS-LONGDOC
Substitution path
Abraxas Reason 4 — tested
Reason 4 carries the same workloads at a 3.1 point advantage on extraction and a 1.4 point deficit on long-document review.
Deliberate second source. Thirty days of reprice notice is short, but the workload is portable inside that window.
Provenance and boundary
Hosted Provider cloud, EU region only · Pay as you go
EU only.
Contractually excluded from provider training. Zero-retention endpoint; prompts and completions are not stored by the provider beyond the request.
Who depends on it
4 agents
Towers legal
Substitution path
No substitute identified
Held as the named substitute for Abraxas Embed 3 and running on one small legal corpus only. Four agents is not a proof.
Named as the escape route from the estate’s hardest dependency while carrying 0.4 percent of embedding traffic. The substitution path is documented, not demonstrated.
Provenance and boundary
Hosted Withdrawn · Pay as you go
Not applicable — no traffic.
Contractually excluded from provider training. Zero-retention endpoint; prompts and completions are not stored by the provider beyond the request.
Who depends on it
0 agents
No tower maps to this model.
EVS-LONGDOC
Substitution path
Corvid Counsel 2 — tested
Migrated to Counsel 2 in February 2026, eleven days before the hard date. Tighter than it should have been.
Closed out. The eleven-day margin is the reason the deprecation calendar now sits on this page.
Provenance and boundary
Hosted Own tenancy on Nimbus accelerators, EU and US · Open weights, self-hosted
Nothing leaves our tenancy. This is the only route approved for special-category personal data.
Weights are held locally. No prompt or completion is transmitted to any third party.
Who depends on it
211 agents
Towers h2r · it · legal · ai-ops
EVS-REASON-CORE
Substitution path
Abraxas Reason 4 — tested
Reason 4 outperforms it on every suite. It is used where the data boundary matters more than the score.
No deprecation exposure at all — the weights are ours. The exposure is the accelerator contract underneath it.
Provenance and boundary
Hosted Own tenancy on Nimbus accelerators, EU and US · Open weights, self-hosted
Nothing leaves our tenancy.
Weights are held locally.
Who depends on it
89 agents
Towers it · ai-ops · m2d
EVS-ROUTING
Substitution path
Abraxas Swift 2 — tested
Interchangeable with Abraxas Swift 2 on the routing suites, in both directions.
None material.
Provenance and boundary
Hosted Own tenancy on Nimbus accelerators, EU and US · Open weights, self-hosted
Nothing leaves our tenancy. Every inbound prompt in the estate passes through it before reaching any provider.
Weights are held locally.
Who depends on it
1,361 agents
Towers h2r · s2p · o2c · r2r · p2p · it · legal · a2l · c2l · m2d · ai-ops · data-analytics
EVS-ADVERSARIAL
Substitution path
No substitute identified
No substitute configured. Every agent in the estate calls it and there is no second implementation of the guard path, so a failure here fails the whole estate closed rather than open.
Called by all 1,361 agents. Cheapest line in the registry and the single point through which every prompt passes. Failing closed is the right behaviour and it is still a single point.
Actions
What is unsafe right now
Every row here is a dependency the estate cannot currently move off inside the notice period on the contract above it.
Models in live use with no second implementation
3Abraxas Vision 2 · 97 agents · Corvid Embed 1 · 4 agents · Helix Guard 3 · 1,361 agents
Substitution paths written down but never exercised
1Abraxas Embed 3 → Corvid Embed 1
Agents sitting on a model with an announced end of life
168Abraxas Reason 3 · hard end of life Dec 31, 2026 · 135 days away
Live observability
The deprecation calendar
Dated withdrawals only. A model with no published end of life is not on this calendar, which is itself a risk: the supplier can add a date at any time.
Dated withdrawals
3 models with a published hard end of life · 9 carry no date at all
| Model | Announced | Hard end of life | Days left | Agents exposed | Move to |
|---|---|---|---|---|---|
| Abraxas Reason 2 | Jun 30, 2025 | Dec 31, 2025 | passed | 0 | Abraxas Reason 3 |
| Corvid Counsel 1 | Jan 15, 2026 | Mar 31, 2026 | passed | 0 | Corvid Counsel 2 |
| Abraxas Reason 3 | Apr 30, 2026 | Dec 31, 2026 | 135 | 168 | Abraxas Reason 4 |
Is policy and strategy coming to fruition
Does the multi-supplier position hold in the traffic
The stated position is that no single supplier should be able to stop the estate. The traffic is the only evidence that counts.
Position
No single supplier carries more than half of estate inference calls.
Not holding — Abraxas Foundry carries 61%.
Position
Every model in live use has a substitute that has been run at least once.
Not holding — 8 of the 10 models in live use have a substitution that has actually been run. 1,803 agents sit behind one that is untested or absent.
Position
Enterprise content is never used to train a supplier model.
Holding on every contract in the registry.
What this page is, and what it is not
A security certification and a penetration test are organizational attestations. The product can house them, track their currency and surface their scope; it cannot manufacture them. Present the trust center as the place they live, never as evidence that they exist.
The same applies to a model card. The provenance, the data boundary and the training terms below each model are transcribed from a supplier contract; nothing here re-derives them, and no independent party has verified that a supplier honors them. Call volumes and weekly cost are computed from the modeled estate rather than metered from a billing feed. Read this registry as the inventory of what the estate depends on, not as assurance that those dependencies behave as written.