RAG and embeddings
RAG grounds answers in documents; embeddings let the system search by meaning.
Reference / plain-English terms
A short glossary of the terms that appear in procurement, vendor decks, and implementation notes. The goal is not to make you a developer. It is to make the purchase decision clear.
Pattern demonstration / same workflow, synthetic material
Terms grouped by decision
The terms below map to practical choices: where the model runs, how it finds documents, and who owns the result.
RAG grounds answers in documents; embeddings let the system search by meaning.
Self-hosted runs on your infrastructure; managed AI runs on a vendor's service.
Fine-tuning changes model behavior on examples; prompting guides behavior at run time.
The glossary boundary
Model names, licences, and features change; current details are confirmed at implementation.
This glossary covers decision terms, not a full technical manual.
Definitions help, but the workflow, data, and review rules decide the right setup.
How to use the glossary
Use the FAQ below for the definitions that appear in most conversations.
Ask what changes: data location, cost, maintenance, or answer quality.
Use the term in the lead form so the scope is precise.
We explain the architecture and what it means for the workflow.
Why trust Pristine3D?
Pristine3D Ltd builds and operates live digital products, and we run private AI workflows internally as part of our own operations. We scope around your real workflow: the documents you own, the questions your team asks, and the access boundary you approve. Based in Lagos, Nigeria, we work remotely with clients worldwide.
Based in Lagos, Nigeria, Pristine3D currently builds and operates smartcards.ng, venu.ng, photoshoot.ng, and ugc.ng in production.
One input, one output, one test set, and one person who owns the result. We scope a real workflow instead of a transformation programme.
Cloud, model, storage, and messaging accounts stay in your name. The chosen data path, access rules, test record, documentation, and training are part of the agreed scope.
Pricing / fixed scope
The final quote follows the workflow. Infrastructure and model bills stay on your accounts.
One workflow for a small team, with training and handover.
See the one-workflow packageMultiple sources, roles, integrations, and admin handover.
See the deploymentStandard care for one delivered workflow. Optional. Larger deployments and active monitoring are separately scoped.
See supportArchitecture review from $500. Standard annual support is $3,000 / ₦1.5m per year for one delivered workflow. New workflows, integrations, active monitoring, and infrastructure are separately scoped; infrastructure, model, storage, and messaging bills stay on client accounts. Full pricing and what changes the quote
Straight answers
Retrieval-augmented generation: the system finds relevant documents first, then drafts an answer from that evidence with citations.
A mathematical representation of text that lets the system search for meaning and similarity.
A store built for similarity search over embeddings, connected to the source documents.
Running the system on your own infrastructure rather than inside a public AI service.
Additional training on selected examples to change a model's style, format, or behavior.
A large language model: the component that generates text. It is a swappable part of a private deployment.
Accounts, infrastructure, documents, indexes, and credentials are under the client's control.
A documented description of where data goes, who processes it, where it is stored, and how it is deleted.
Own your knowledge base
Documents, the retrieval index, access rules, and the workflows built around them are the asset, and they compound. We deploy so the knowledge base stays yours: on your accounts, in the environment you choose, under access rules your team defines. The model behind the answers is a connector, so the knowledge base moves with you, not with a vendor.
The document store, metadata, and retrieval setup live on accounts you own. No vendor holds the corpus.
Change the model provider, move regions, or go local without rebuilding the knowledge base or the workflow.
Every improvement to the corpus improves the answers, and the improvement stays with you, not with a vendor.
Keep exploring
Start with the term
Tell us the term and the workflow. We will explain it in the context of your setup and recommend a first step.