Compare the provenance
Review the model provider, licence, hosting, and where inference runs.
Model decision / Mistral
Mistral is the residency conversation before it is a model conversation.
Mistral's open-weight models are often considered by European teams who want a European-origin model on their own infrastructure. We review the current variant, licence, hardware, and data path before deployment, and keep the corpus on the client's side.
European-originOpen-weight modelResidency reviewClient-owned path
Pattern demonstration / same workflow, synthetic material
Fixed-scope setupClient-owned accountsDraft-and-review firstFull handover
When Mistral makes sense
The appeal is control and provenance.
For teams reviewing provider origin, data location, and procurement questions, an open-weight Mistral deployment can simplify the conversation without being the only option.
Match the task
Test quality, speed, and hardware against the documents and outputs the team needs.
Document the boundary
Sources, retrieval, permissions, and logs stay in the client's environment.
The Mistral boundary
Origin is not the same as compliance.
Current terms win
The current licence and allowed use are confirmed before deployment.
Location is documented
The region, provider, and processing path are written into the handover.
Test before trust
The model is evaluated on the team's real questions and sources.
A first Mistral decision
Start with the residency constraint, then the task.
Name the constraint
Decide whether origin, hosting, or both drive the model choice.
Review the model
Confirm the current variant, licence, hardware, and quality against the task.
Build the grounded setup
Connect the client-owned corpus, retrieval, citations, and permissions.
Test and hand over
Run real questions, fix gaps, and deliver the runbook and support route.
Mistral answers the origin question. The workflow still has to answer the quality question.
Why trust Pristine3D?
We build and operate production software.
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.
We already run live products
Based in Lagos, Nigeria, Pristine3D currently builds and operates smartcards.ng, venu.ng, photoshoot.ng, and ugc.ng in production.
We start with the actual workflow
One input, one output, one test set, and one person who owns the result. We scope a real workflow instead of a transformation programme.
The boundary stays visible
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
Know the starting numbers before you ask.
The final quote follows the workflow. Infrastructure and model bills stay on your accounts.
One Workflow
Starting from$3,500 / ₦2.5m
2 to 3 weeksOne workflow for a small team, with training and handover.
See the one-workflow packageFirm-wide
Starting from$7,500 / ₦8m
4 to 6 weeksMultiple sources, roles, integrations, and admin handover.
See the deploymentAnnual support
Starting from$3,000 / ₦1.5m
per yearStandard 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
Common questions.
Is Mistral fully open?
Some variants are open-weight under current terms; not every product is the same. We confirm the licence before deployment.
Can it stay inside the EU?
Yes, when the client requires it. Hosting, model access, and inference location are documented.
Can we switch models later?
Yes. The corpus, index, and workflow stay portable, so the model is not a lock-in.
Own your knowledge base
The model is not the product. The knowledge base is.
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.
Your corpus, your index
The document store, metadata, and retrieval setup live on accounts you own. No vendor holds the corpus.
Models are swappable parts
Change the model provider, move regions, or go local without rebuilding the knowledge base or the workflow.
The knowledge base is the alpha
Every improvement to the corpus improves the answers, and the improvement stays with you, not with a vendor.
Keep exploring
Related setups.
Start with the constraint
Which residency requirement is driving this?
Tell us the task, the origin or hosting constraint, and the review owner. We will confirm whether Mistral is the right model.