Co-determination is real
When a system tracks employee work, the works council (Betriebsrat) has co-determination rights. A documented data path answers those questions before they are asked.
Self-hosted AI / Germany
Self-hosted AI for German companies, with a data path you can defend.
Private AI deployed for German businesses in an EU region such as Frankfurt, or on your own hardware. The document store stays on your accounts, the model and its provider are disclosed, and the setup is designed for review against the GDPR (DSGVO) and the BDSG.
From €3,300 / $3,500 / ₦2.5m floorseu-central-1 (Frankfurt) optionClient-owned accountsFull handover
Example only / architecture varies by client
Designed for review against the GDPR (DSGVO) and the Federal Data Protection Act (BDSG)eu-central-1 (Frankfurt) optionClient-owned billingFull handover
Why it matters here
The German context is not a checklist. It is the requirement.
Buyers in Germany review data paths, not slide decks. The deployment is designed around that.
Designed for DSGVO review
Data paths, purposes, and access rules are mapped and documented so the system can be reviewed against the GDPR and the BDSG by whoever owns compliance.
Reviewed like infrastructure
German buyers treat AI as infrastructure. Disclosed providers, named regions, and client-owned billing are the normal bar, not the premium option.
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 Frankfurt
App and document store in your account in eu-central-1 (Frankfurt), 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.
Which region would the documents stay in?
The default option is eu-central-1 (Frankfurt). If your contract needs a different region, or no external processing at all, the architecture is documented before anything is built.
Does German law require something special for employee systems?
Where the system processes employee data, works council co-determination can apply alongside the GDPR. The deployment includes a documented data path that makes that review possible.
Can everything stay inside the EU?
Yes. EU-region hosting or fully local deployment, with the model provider and its location named in the architecture.
Do invoices come in euros?
Yes, EUR billing is available. The USD and naira floors remain the same starting points.
German buyers are not buying faster AI. They are buying a data path they can defend.
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, procurement, a works council review, or a no-external-inference rule. Describe it and we will map the architecture.