Private deployment and custom work
Some documents cannot leave your infrastructure. That is a project, not a toggle.
The platform is containerised, which means it can be moved. But a private delivery involves licensing, deployment documentation, handover and arrangements for models that run without an external connection. We assess each one rather than pretending it is a configuration option.
Assessed per project. There is no packaged private-deployment product.
When this conversation happens
Four situations where private deployment is the real requirement rather than a preference.
Regulated content
Documents that a compliance regime does not allow to be sent to an external service, regardless of the contractual terms.
Client contractual restriction
Your client's contract says the material stays inside a defined perimeter. The obligation flows down to whoever processes it.
Public sector and defence
Procurement that requires the processing to happen inside a controlled environment, often with no external network path.
Volume economics
At very high sustained volume, running your own instance can make sense for reasons that have nothing to do with secrecy.
What a private delivery involves
Being direct about this: it is a project with real work on both sides. Here is what that work is.
Infrastructure assessment
What hardware you have, what the processing load requires, and whether the models can run on it.
Licensing terms
A commercial agreement covering the deployment. We do not publish licensing prices — terms are set per project.
Deployment and documentation
Installation into your environment plus the documentation your team needs to operate and update it.
Offline model arrangements
If the environment has no external network path, the models have to be delivered and updated by other means. This is often the longest part of the project.
Handover and training
Your team operates it. That requires more than a README, and we plan for it.
Ongoing arrangement
Updates, model refreshes and support are agreed as part of the delivery rather than assumed.
Custom pipeline work
Separate from private deployment, and often more useful.
A lot of the value in an engagement is not deploying the software somewhere else — it is adapting the pipeline to a document type, a workflow or a terminology regime that the standard path does not fit.
Examples of the kind of thing that gets scoped: a document class with unusual structure, a review step that has to happen inside your process, an exchange with a system we do not already talk to.
This work is scoped per engagement and depends on what the document actually needs. Send one and we will tell you whether it is a configuration, a project, or not worth doing.
Private deployment questions
Can we buy a private deployment?
It can be assessed, but there is no packaged product with a price. A private delivery involves licensing, documentation, handover and arrangements for running the models without an external connection.
What hardware does it need?
That is what the assessment is for. It depends on the processing volume you need and what you already have. We will not quote a specification before looking at your environment.
Can it run with no internet access at all?
That is the situation the offline model arrangements exist for. It is usually the longest part of a private delivery, and we plan for it explicitly rather than treating it as a detail.
How long does a private deployment take?
We will not give a timeline before assessing your environment. Any number offered before that assessment would be invented.
Is our data used to train anything?
No. We do not use engagement material to build or train models. The specific commitments your compliance requires are agreed in the engagement terms.
What about custom work that is not deployment?
That is often the more useful conversation — adapting the pipeline to a document type or workflow. Scoped per engagement, and we will tell you if it is not worth doing.
Tell us what the constraint is.
Regulatory, contractual or practical — the starting point is the constraint, not the technology. Describe it and we will tell you plainly whether a private delivery is workable.
- Describe the requirement
- We assess feasibility
- You get a straight answer