A licence read first
The licence and use policy for the version you choose, checked before any build.
We have no published Llama build. Our AI product calls a Claude-compatible API, and each Llama version carries its own licence and use policy that you should read before you build.
The licence and use policy for the version you choose, checked before any build.
A FastAPI service in front of a model you host.
Token counts and cost reported per workspace, as in Sales OS.
A model name kept in settings so a change is configuration.
Illustration. A dashed outline marks where the technology would sit. We have no published build on it.
Source: Meta developer pages, dev.meta.ai/llama, checked 5 November 2026. The site now leads with Meta Muse models. Read each licence and use policy yourself.

An engine that crawls a site and writes a graded brief through a Claude-compatible API, with cost and tokens reported per workspace.

A chatbot project delivered at a fixed price, with GraphQL in the stack.
Python
PyTorch
Docker
Kubernetes
TensorFlow
AWSMeta lists Llama 4, the Llama 3 family with 3.1, 3.2 and 3.3, and Llama 2. Its developer site now leads with the Muse family and keeps Llama in its own section.
Each Llama version has its own licence and use policy, such as the Llama 4 License. We do not give legal advice. Read the terms for your version and ask your lawyer.
No. We say so on the first call and show the nearest work, which is Sales OS on a Claude-compatible API and a fixed-price chatbot project.
You do, from the first commit. Repositories and cloud accounts stay in your name.
Thirty minutes on your data, your hosting and your licence needs. No sales pitch.