Consultation, documented
Tools that monitor staff trigger information and consultation of employee representatives under the Labour Code. The deployment documents what the system does so that consultation can proceed.
Self-hosted AI / France
Private AI deployed for French businesses with the document store on your accounts and hosting in an EU region such as Paris. The RGPD and CNIL context is designed for review, and every model provider or channel is named before the system is used.
Example only / architecture varies by client
Why it matters here
The CSE consultation is part of the deployment reality, not an obstacle to it.
Tools that monitor staff trigger information and consultation of employee representatives under the Labour Code. The deployment documents what the system does so that consultation can proceed.
Purpose limitation, minimisation, and a named processor list are part of the architecture, so a CNIL-aligned review has something real to inspect.
The model, the channel, and the region are disclosed in writing before the first document is loaded.
The three levels
There is no single correct answer. Quality, privacy, residency, and budget decide the path.
App and document store in your account in eu-west-3 (Paris), with the model on your key. No GPU required.
An approved cloud region or managed service when residency and procurement matter.
Model, embeddings, and retrieval on your hardware when external inference is not acceptable.
What it really takes
Hardware is sized after the workload is real. These are starting points, not quotes.
No GPU required for the app and document store. Model usage bills stay on the client account.
A starting point for a small quantized text model. Model size, concurrency, and latency decide the real requirement.
A GPU is one part of the environment. A partner data centre can be more realistic than an office server room.
We size hardware after the workload is proven. No GPU inventory before a signed scope and deposit.
Straight answers
An EU region such as eu-west-3 (Paris), or your own infrastructure when the requirement is stricter.
Where monitoring tools are introduced, the Labour Code requires informing and consulting employee representatives. We hand over the documented data path that makes that step straightforward.
The design follows RGPD principles, including a disclosed processor list and documented data flows, so the review by whoever owns compliance can be thorough.
Yes. The starting-point ballpark is €3,300 for a first workflow, with the same USD and naira floors as the global pricing.
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
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 constraint
Residency, procurement, CSE consultation, or a no-external-inference rule. Describe it in English or French and we will map the architecture.