lifecycle

For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

<!-- Tab options on this page. Append to the .md URL to filter: ?tabs=<id,...> select specific tabs (e.g. ?tabs=nodejs,shell) ?allTabs=true include every tab (no param) default: one tab per tabset

Available tabs: other tabs: text-embedding, contextualized-chunk-embedding, multimodal-embedding, reranker -->

Model Deprecations, Lifecycle States, and Support

Every Voyage AI model has a support status that indicates whether you can use the model for new projects and whether the model remains available through the [Embedding and Reranking API](https://www.mongodb.com/docs/voyageai/api-and-clients.md#std-label-voyage-api-and-clients. This page lists the current status of each model and records changes to those statuses over time.

For model specifications, such as context length and embedding dimensions, see [Voyage AI Embedding and Reranking Models Overview.](https://www.mongodb.com/docs/voyageai/models.md#std-label-voyage-models

Scope

This support policy applies to Voyage AI embedding and reranking models served through the Atlas Embedding and Reranking API at ai.mongodb.com, including the models that Atlas Automated Embedding and Atlas Native Reranking use.

This support policy does not apply to models served through the legacy Voyage AI platform at api.voyageai.com, self-managed deployments, or third-party marketplace offerings.

MongoDB announces all lifecycle transitions on this page.

Supported Endpoints

The Atlas Embedding and Reranking API serves models through the following endpoints:

Endpoint Description
ai.mongodb.com The global endpoint. Serves every model listed on this page.
eu.ai.mongodb.com A geography-scoped endpoint that routes requests to infrastructure in the European Union.
us.ai.mongodb.com A geography-scoped endpoint that routes requests to infrastructure in the United States.

MongoDB adds geography-scoped endpoints over time. The Supported Endpoints column of the [Current Model Status](https://www.mongodb.com/docs/voyageai/models/lifecycle.md#std-label-voyage-model-lifecycle-current tables lists All for models that every endpoint serves, ai.mongodb.com for models that only the global endpoint serves, and the specific endpoints for models that a subset of endpoints serves.

Model Statuses

Voyage AI models use the following support statuses:

Status Description
Preview The model is fully supported but isn't yet the current model in its capability family. While a model is in Preview, its response behavior might change slightly as MongoDB fine-tunes the model weights. A Preview model doesn't supersede the current Active model in its family. The Active model becomes Legacy only when its successor becomes Active.
Active The model is the current model in its capability family and is recommended for new projects. MongoDB supports Active models with serving-infrastructure security patches, incremental improvements, and bug fixes. For the endpoints that serve each Active model, see the Supported Endpoints column of the [Current Model Status](https://www.mongodb.com/docs/voyageai/models/lifecycle.md#std-label-voyage-model-lifecycle-current table.
Legacy A newer model supersedes the model. MongoDB supports Legacy models with serving-infrastructure security patches and bug fixes. Legacy models remain available to all customers in existing supported geographies, but might not be available in newly launched geographies. To replace a Legacy model for a new project, use the model listed in the Recommended Replacement column of the [Current Model Status](https://www.mongodb.com/docs/voyageai/models/lifecycle.md#std-label-voyage-model-lifecycle-current table.
Deprecated The model remains callable but might be less reliable than Active models, and is no longer recommended. MongoDB continues to serve Deprecated models, but doesn't provide security patches, bug fixes, or incremental improvements for them. Each Deprecated model has a published retirement date and a named replacement. Organizations that already use a Deprecated model retain access to it until the retirement date. New organizations can't access Deprecated models and are directed to the current Active model instead. Migrate to the replacement before the retirement date.
Retired The model is no longer served. MongoDB doesn't support Retired models. Requests that specify a Retired model return an HTTP 410 response that identifies the replacement model.

Support Duration and Notice

When MongoDB retires a model, MongoDB provides a named replacement model, a migration guide, and embedding model migration credits. Before each transition, MongoDB provides at least the following notice:

Transition Embedding models Reranker models
Legacy to Deprecated 12 months 6 months
Deprecated to Retired 6 months 3 months
Legacy to Retired, total 18 months 9 months

No Voyage AI model is currently Deprecated or Retired, and no model has a published retirement date. MongoDB does not provide support for models past their retirement date, or for models outside of the Atlas Embedding and Reranking API.

Current Model Status

Select a model family to view the status of each model in that family:

The Active Date is the date the model becomes the current model in its family. The Legacy Date is the date a newer model supersedes it. A Legacy Date in the future is a planned date and is subject to change. The Recommended Replacement is the model to use in place of a Legacy model for new projects. Supported Endpoints is the set of endpoints that serve the model, beginning 1 September 2026. To learn about each endpoint, see [Supported Endpoints.](https://www.mongodb.com/docs/voyageai/models/lifecycle.md#std-label-voyage-model-lifecycle-endpoints

Text Embedding

Model Status Active Date Legacy Date Recommended Replacement Supported Endpoints
voyage-4 Active 15 January 2026 Not applicable All
voyage-4-lite Active 15 January 2026 Not applicable All
voyage-4-large Active 15 January 2026 Not applicable All
voyage-code-4 Active 13 August 2026 Not applicable All
voyage-3-large Legacy 15 January 2026 voyage-4-large ai.mongodb.com
voyage-3.5 Legacy 15 January 2026 voyage-4 ai.mongodb.com
voyage-3.5-lite Legacy 15 January 2026 voyage-4-lite ai.mongodb.com
voyage-code-3 Legacy 13 August 2026 voyage-code-4 ai.mongodb.com
voyage-code-2 Legacy 15 January 2026 voyage-code-4 ai.mongodb.com
voyage-finance-2 Legacy 15 January 2026 voyage-4 ai.mongodb.com
voyage-law-2 Legacy 15 January 2026 voyage-4 ai.mongodb.com

Changelog

This changelog records changes to model status. For the current status of all models, see [Current Model Status.](https://www.mongodb.com/docs/voyageai/models/lifecycle.md#std-label-voyage-model-lifecycle-current

20 October 2026

  • voyage-context-3 is now available through the eu.ai.mongodb.com endpoint, in addition to ai.mongodb.com.

29 September 2026

  • rerank-3 and rerank-3-lite are now Active and are the recommended reranking models for new projects.

  • rerank-2.5 and rerank-2.5-lite are now Legacy. Each model remains available through the Embedding and Reranking API. For new projects, use the recommended replacements, rerank-3 and rerank-3-lite.

1 September 2026

  • Added the Preview status. rerank-3 and rerank-3-lite are released in Preview.

  • The following models are now Legacy, effective on the date listed. Each model remains available through the Embedding and Reranking API. For new projects, use the recommended replacement:

  • rerank-2, 11 August 2025, replaced by rerank-2.5

  • rerank-2-lite, 11 August 2025, replaced by rerank-2.5-lite

  • voyage-3.5, 15 January 2026, replaced by voyage-4

  • voyage-3.5-lite, 15 January 2026, replaced by voyage-4-lite

  • voyage-code-2, 15 January 2026, replaced by voyage-code-4

  • voyage-finance-2, 15 January 2026, replaced by voyage-4

  • voyage-law-2, 15 January 2026, replaced by voyage-4-lite

  • voyage-multimodal-3, 15 January 2026, replaced by voyage-multimodal-3.5

  • voyage-context-3, 30 June 2026, replaced by voyage-context-4

  • voyage-code-3, 13 August 2026, replaced by voyage-code-4

  • Added the Active Date and Legacy Date for each model, the scope of the support policy, expanded status definitions, and the minimum notice windows for each lifecycle transition.

  • Added the list of [Supported Endpoints](https://www.mongodb.com/docs/voyageai/models/lifecycle.md#std-label-voyage-model-lifecycle-endpoints and a Supported Endpoints column to the [Current Model Status](https://www.mongodb.com/docs/voyageai/models/lifecycle.md#std-label-voyage-model-lifecycle-current tables. voyage-4, voyage-4-lite, voyage-4-large, voyage-code-4, voyage-context-4, voyage-multimodal-3.5, rerank-3, and rerank-3-lite are available through all endpoints. All other models are available only through ai.mongodb.com.

30 July 2026

  • Baseline: all Voyage AI models are Active. Initial publication of model status tracking.