Registration and oversight
The ODPC registers controllers and processors and receives breach reports and complaints under the Data Protection Act 2019. The deployment documents the data path for that frame.
Self-hosted AI / Kenya
Self-hosted AI for Kenyan companies, where ODPC registration sets the frame.
Private AI deployed for Kenyan businesses under the Data Protection Act 2019, with hosting in an African region and a disclosed data path. The Office of the Data Protection Commissioner registers controllers and processors, receives breach reports and complaints, and publishes sector guidance, so the deployment documents the path before anything is loaded.
From KES 470,000 / $3,500 / NGN 2.5m floorsaf-south-1 (Cape Town) optionClient-owned accountsFull handover
Example only / architecture varies by client
Designed for review against the Data Protection Act 2019 and the Office of the Data Protection Commissioner (ODPC)af-south-1 (Cape Town) optionClient-owned billingFull handover
Why it matters here
Kenyan review starts with registration and accountability.
The ODPC's registration, breach-report, and complaint framework makes the documented data path the practical requirement.
Published expectations
The ODPC has published sector guidance on data protection expectations. The architecture is reviewed against the relevant guidance.
Data in the region
af-south-1 (Cape Town) is the default, with on-prem for stricter requirements.
The three levels
The architecture follows the constraint.
There is no single correct answer. Quality, privacy, residency, and budget decide the path.
Your cloud, in Africa
App and document store in your account in af-south-1 (Cape Town), with the model on your key. No GPU required.
For location requirements
An approved cloud region or managed service when residency and procurement matter.
For strict control
Model, embeddings, and retrieval on your hardware when external inference is not acceptable.
What it really takes
Measured workloads, not GPU shopping lists.
Hardware is sized after the workload is real. These are starting points, not quotes.
4 to 8 vCPU, 16 to 32 GB RAM
No GPU required for the app and document store. Model usage bills stay on the client account.
From 24 GB VRAM
A starting point for a small quantized text model. Model size, concurrency, and latency decide the real requirement.
Power, cooling, updates, backups
A GPU is one part of the environment. A partner data centre can be more realistic than an office server room.
Not the first promise
We size hardware after the workload is proven. No GPU inventory before a signed scope and deposit.
Straight answers
Common questions.
Where would the data be hosted?
The default is af-south-1 (Cape Town), documented in the architecture. Fully local deployment is available.
Does the ODPC need to approve the system?
No. The ODPC does not approve products. Controllers and processors remain responsible for compliance under the Data Protection Act 2019.
Who owns the accounts?
The Kenyan client owns the cloud, model, and storage accounts. Pristine3D hands over the runbook and credentials.
Do invoices come in Kenyan shillings?
Yes, from KES 470,000 for a first workflow, with USD and naira floors unchanged.
Registration, breach reporting, and review all point to the same thing: a documented data path.
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
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
What is your constraint?
Residency, ODPC review, procurement, or a no-external-inference rule. Describe it and we will map the architecture.