Your Own ChatGPT, on Your Own Servers
With private LLM deployment, your staff get a ChatGPT-style assistant, and what they type stays inside your network. We run open models such as Llama or Mistral in your office or your own cloud.
Why your data can't go to a public AI tool
With an AI provider's service, such as ChatGPT, what your team types and the documents it uses are processed by that provider. For some teams that is fine. For others, a contract, a regulator or plain caution says the data stays inside. A private LLM gives those teams AI without that trade.
-
“Our contracts say client data can't go to an outside AI provider.”
An open model (an AI model you download and run yourself) on your own servers answers, so what your team types and its documents stay inside your network.
-
“People paste work into public chatbots anyway.”
A private chat app your team signs in to gives the same kind of help, on machines you control.
-
“We don't want our AI tied to one provider.”
Open models run where you choose, and a better open model can replace the current one without a rebuild.
Private AI for chat, documents, records and workflows
Use a private LLM where the data cannot leave. These are the setups we deploy, all inside your own network.
-
A private ChatGPT for your team
A chat app your staff sign in to, answering with an open model that runs on your servers.
-
Answers from your own documents
The model searches your documents and answers from them, with nothing sent outside.
-
AI on your own records
The model reads the database tables you choose, where your records already live.
-
Private AI steps in your workflows
Automated steps pass work between your tools, and the AI step uses your own model.
-
A private AI service for your apps
A private AI service your own software can use, often with small changes if it already uses OpenAI.
Want the model trained on your own examples? See LLM fine-tuning
An open model on your machines, ready for your team
You get an open model on machines you control, with search and sign-in around it so your team can use it. The tests we used to choose it and a handover come with it.
-
An open model, running
Chosen and tested for your tasks, on your servers or in your cloud.
-
Kept inside your network
Documents, questions and answers stay on machines you control.
-
Search over your documents
Search set up for the documents and records you choose.
-
Sign-in and access by role
Each person reaches only the documents their role allows.
-
A test set of real questions
Your questions with the answers you expect, used to pick the model and rerun after any change.
-
Instructions and a handover
Usage logs, the code in your own code repository, instructions for your team and a walkthrough.
Pilot-first
What a first private LLM pilot builds
Pilot-first: we start with a small pilot on your own data, priced up front, before any full build. In the pilot you see an open model answer your team's real questions, inside your network, before you commit to a rollout.
- What the pilot builds
- An open model on one of your servers or a cloud machine you own, answering a set of your real questions.
- What you get
- How open models do on your questions, the hardware a full rollout would need, and a plan for it.
How a private LLM deployment works
A private LLM deployment runs an open AI model on servers you control, in your office or in your own cloud account. Nothing your team types goes to an outside AI provider. Separate tools, all inside your network, run the model, search your documents, hold your records in a standard database and run the automated steps between your tools. The stack below names each one.
-
Question
A person asks in the private chat app, or one of your apps calls the model.
-
Sign-in
The app checks who is asking and what they may read.
-
Open model
An open model on your own servers works out the answer.
-
Your data
It searches your documents and reads your records in your own database.
-
Answer
The answer goes back to the person, and the request is logged.
- Question “When does the supplier contract renew, and how do we give notice?”
- Sign-in The person is signed in, and their role may read contracts.
- Open model The model on your own server decides what to look up.
-
Your data
Searches your contracts for the renewal and notice clauses. -
Your data
Looks up this supplier's renewal date in your records. - Answer “It renews unless you give notice in writing. Here are the clauses.”
No step called an outside AI provider. The question and the contract stayed on your network.
The right model for each task, where your data may go
We choose the model per task and run it where your data is allowed to go. We build on the systems you already run, and stay after launch to keep the model current.
-
Any model, your choice
OpenAI, Anthropic, or open models on your own servers. We choose per task, on answer quality, cost and where your data is allowed to go.
-
Built around your systems
We connect the private model to the documents, database and workflow tools you already run, instead of replacing them.
-
Support after launch
We monitor the deployment after launch, keep it updated and test new open models as they arrive, swapping one in only when it does better on your test set.
-
Hours that overlap yours
We work on India Standard Time (IST): 4.5 to 5.5 hours ahead of London and 9.5 to 10.5 ahead of New York.
Every question, document and log stays on your machines
A private model is only private if everything around it is too. The model, the search and the logs stay on machines you control, and we decide with you who may reach what.
On every private LLM we deploy
- The model runs on servers you control, in your office or your own cloud.
- Each person signs in and reaches only what their role allows.
- A test set of real questions runs before each model change.
- Usage limits, with a log of what the model was asked.
Your real questions answered on one machine before rollout
We test open models on your real questions on one machine, pick the one that answers best, and roll out once it has proved itself. Each step is priced up front, and you can stop after the pilot.
The open models and tools we deploy with
Standard, widely used tools that run inside your own network, so another team could take the setup over. These are the self-hosted tools we work with.
-
Models
Open models such as Llama, Qwen, Gemma and Mistral, chosen per task. Ollama runs them on your machines.
-
Ollama
- Llama
- Qwen
- Gemma
- Mistral
-
-
Search and data
Qdrant finds the passages in your documents that match a question. PostgreSQL, a standard database, holds your records.
- Qdrant
-
PostgreSQL
-
Workflows
n8n is a workflow tool that passes work between your tools, with the AI step on your own model.
- n8n
-
Hosting
Your own servers, or a cloud account in your company's name.
- Your servers
- Your cloud account
-
Your systems
The documents, databases and tools the model may read, where they already live.
Provis Technologies AI Integration services are phenomenal. We have been witnessing growth after the AI automation they have put into our business.
Tell us what your team would ask and what must stay inside.
We will tell you which open models we would test, and what they would need to run.
Vivek SharmaCEO & Founder, Provis Technologies
Questions about private LLM deployment
What is a private LLM?
A large language model that runs on machines you control, in your office or your own cloud account, instead of a provider's service. What your team types, and the documents it uses, go to your own server, not to OpenAI, Anthropic or anyone else. We run open models with Ollama for this.
Is a private LLM as good as ChatGPT or Claude?
It depends on the task, and the pilot is how you find out. We test open models on your own questions, and compare them with a hosted model where your rules allow, so you see the difference in answer quality before you decide where the model runs.
Can we have a private ChatGPT for our team?
Yes. We set up a chat app your staff sign in to, answering with an open model on your servers. It can search the documents you choose, and each person reaches only what their role allows. Nothing they type goes to an outside AI provider.
Where does our data go?
Where you decide. With hosted models from OpenAI or Anthropic, data is processed by that provider. With open models on your own servers or cloud, documents and questions stay inside your network. Many teams use both, with the private model for the data that must stay in.
What hardware does a private LLM need?
It depends on the size of the model and how many people use it at once. The pilot runs your chosen model on your own questions and measures what it needs. You then size the hardware on what was measured.
On-premise or in our own cloud?
Either. On-premise means servers in your office or data centre. Your own cloud means machines in a cloud account in your company's name, inside your private network. Both keep the data off any outside AI provider. The choice is usually about your rules and your hardware.
Which open models do you deploy?
Models that Ollama runs, such as Llama, Qwen, Gemma and Mistral, chosen per task on answer quality, speed and the hardware they need. Ollama can also load a model that was trained further, such as one you have fine-tuned. We test more than one on your questions before choosing.
Private LLM or fine-tuning: which do we need?
A private LLM is about where the model runs. Fine-tuning is about training it on your examples. Most teams start with a private open model, clear instructions and search over their documents. Fine-tuning comes later, if the model still misses your format or style; our LLM fine-tuning page covers when.
Can our existing apps use the private model?
Yes. Ollama, the tool that runs the model, accepts part of the same connection format (API) that OpenAI uses. So software already written for OpenAI can often use your private model with small changes. We put sign-in and a usage log in front of it, so only your apps and people reach it.
How much does a private LLM deployment cost?
Three things drive the cost: the model size and hardware, how many people and apps use it, and how much document search and sign-in it needs. Tell us what you want it to do, and within two working days we come back with an approach, a rough timeline and a rough number.
How long does it take?
It depends on the hardware, the data and how many systems it connects to. We start with a pilot on one machine, so your team sees answers before a full rollout. We agree the timeline at the discovery call.
Who owns the deployment?
You do. The model runs on your machines, the code goes into your own code repository, and the cloud account is in your company's name. You get the documentation and a handover, so your team can run it yourselves.
What happens after launch?
We monitor the deployment, keep it updated and test new open models as they arrive, swapping one in only when it does better on your test set. You can also run it yourselves.
Do you work with UK and US clients from India?
Yes. We sign an NDA before we start, on request, and work only in the accounts you invite us into. The code goes into your own code repository, in an account in your company's name.
Work with experts
Built for teams whose data has to stay inside
We deploy open models on your own servers or cloud, with document search and sign-in, so questions and documents stay inside your network.
Prefer to talk directly?
-
Emailsales@provistechnologies.com
-
WhatsApp+91 88755 82124
-
UK phone+44 7862 126522
-
Video callBook 30 minutes with Vivek Sharma
We're on IST: 4.5 to 5.5 hours ahead of London, 9.5 to 10.5 ahead of New York.
-
1
The model
-
2
Your details
-
3
Additional info
Tell us what must stay inside
Describe what your team would ask, the documents and systems involved, and where the data is allowed to go.
Prefer to talk directly?
-
Emailsales@provistechnologies.com
-
WhatsApp+91 88755 82124
-
UK phone+44 7862 126522
-
Video callBook 30 minutes with Vivek Sharma
We're on IST: 4.5 to 5.5 hours ahead of London, 9.5 to 10.5 ahead of New York.


