Layer E · Model Providers
Meta Llama
Open-weight model family where economics depend largely on the hosting path rather than a single public billing surface.
Last checked . Visit Meta Llama
At a glance
- Category
- Model Providers
- Control layer
- E: Native provider controls
- Five-Layer model
- Usage Transparency
- Status
- Active
- Typical buyers
- Engineering and platform, FinOps
- Delivery
- Self-hosted
Buyer fit
Best for organisations with in-house infrastructure and ML engineering capability that want flexibility, data sovereignty, and independence from closed-model pricing. The TCO of self-hosted Llama includes significant infrastructure, security, and maintenance costs that are entirely internal. Not visible in any vendor invoice.
Market outlook
Meta's open-weight strategy is strategically distinct from closed-model providers. Designed to commoditise the model layer and prevent OpenAI, Anthropic, and Google dominance. This benefits enterprise buyers through competitive pressure on pricing across the market.
What to check
- Where applicable, cost is usually determined by the hosting provider or self-hosted infrastructure rather than a transparent universal Meta price sheet.
- Direct Llama API details are less publicly visible than closed-model APIs, and some official docs require login.
- Optimisation and allocation are mostly delegated to the infrastructure or model-hosting layer chosen by the enterprise.
Sources
The map describes vendors from public sources; it does not rate, rank or recommend them, and no listing is paid for. Confirm pricing and capabilities with the vendor. See how the map is built.
By Ed Epstein, who works at IBM. The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. About and disclosure · Methodology