Lambda Inference API (winding down)

Lambda’s current product page says the Inference API is winding down and directs users to deploy on Lambda GPU instances. Its API-specific privacy statements come from 2025 staff replies and docs; this record does not imply the API remains generally available.

Score calculation

(4) ÷ 1 = 4.0

1 of six dimensions rated. Unrated dimensions and BDS status are excluded.

Full scoring method ↗

Setup details

The managed Lambda Inference API only. Excludes the separate Lambda GPU Cloud product and customer-operated model deployments.

Energy

↑

Lambda’s Inference API page says the service is winding down, while its API documentation describes endpoint use without publishing power, emissions, or water data for that route.

Reasoning & sources

The service lifecycle notice and API docs identify the relevant product boundary, but no footprint can be attributed to its workload or facility. For any remaining or replacement deployment, request the route’s region and usage-linked footprint rather than rely on Lambda’s broader compute claims.

The product page does not disclose service-level footprint or workload location.

Training rights

↑

Lambda hosted third-party models; the API-specific no-training statement concerns customer prompts and completions, not rights in model training corpora.

Reasoning & sources

Lambda hosted third-party models; the API-specific no-training statement concerns customer prompts and completions, not rights in model training corpora. Select the model first and review its license plus corpus-provenance disclosures; prompt no-training terms do not clear the model’s original dataset.

The reviewed sources do not establish corpus provenance or licensing across hosted models.

Inference API privacy statements from Lambda staff ↗

Privacy

↑

In 2025 Lambda staff said prompts and completions were encrypted, not retained after inference, and not used for training or other purposes. The current page says the API is winding down; these API-specific statements were not found in Lambda’s general privacy policy, so their current operational scope is uncertain.

Reasoning & sources

No score is assigned because the only API-specific no-retention/no-training statement located is a 2025 staff-forum disclosure, not a current product commitment. Lambda now says the API is winding down, and the reviewed terms do not establish whether that historical promise still applies to an available endpoint. Verify current service status and contractual privacy terms before sending sensitive data.

The API lifecycle and current endpoint availability are unclear, and the cited statement was made in a staff forum rather than a current product contract or privacy policy.

Openness

↑

Lambda’s API exposed hosted open-source models behind a managed endpoint. Lambda now says the API is winding down and points users to its separate GPU-instance product; users can self-host eligible weights there, but the endpoint/runtime itself is not open.

Reasoning & sources

Open upstream weights can move to customer-run GPU deployments, but the managed API itself is closed and winding down. Check whether the chosen model’s weights and license permit inspection or relocation, and whether the serving runtime moves too; API compatibility alone is not an open stack.

Open upstream weights can move to customer-run GPU deployments, but the managed API itself is closed and winding down.

The current end-of-life timetable and model-by-model availability are not stated on the product page.

Worker treatment

↑

Lambda’s careers page describes its internal compute-infrastructure workforce and hiring, but does not report worker outcomes for data labeling, contractors, or the suppliers supporting this winding-down inference API.

Reasoning & sources

Company recruiting material says who Lambda hires, not how external workers in the service chain are treated. Since the API is winding down, confirm the actual serving provider and request vendor-level labor and audit evidence for that route before relying on Lambda-level claims.

No relevant annotation pay, worker conditions, or independent labor audit was identified.

Government & military

↑

Lambda’s government CRADA datasheet describes agency and defense-partner infrastructure work, but does not tie those relationships to the winding-down Inference API.

Reasoning & sources

The company’s defense-related infrastructure relationships are relevant at the organization level, while this API’s customer and endpoint scope remains unestablished. Keep the API relationship unrated until a contract names the model-serving service and deployment; verify the replacement route if the API has been retired.

This bounded review cannot rule out undisclosed customers or use of separate Lambda infrastructure.

BDS status

↑

We did not find Lambda, Inc. among the named targets in the two official BNC campaign lists. This is a limited list check, not BDS approval.

Reasoning & sources

Lambda, Inc. is not a named target in the checked lists, but BDS uses selective campaigns, so absence cannot establish a clean record. Your selected model, cloud and billing route can introduce other companies into the purchase.

This review covers the named targets in the BNC consumer/pressure guide and No Tech campaign, not every BDS campaign, local group, investment or supplier. Lists and ownership can change. A company’s absence from these lists is not an endorsement or proof that it has no relevant relationships.

All sources