Skip to content

Why this shape

What this looks like when the system has to survive production

Some data cannot go to a third-party processor at all. Not under zero-retention terms, not encrypted in transit, not with a DPA. For those environments the only architecture that passes review is one where the model, the vector store, the orchestration and the logs all live inside the perimeter, and the network proves it.

We have delivered exactly that for a regulated EU enterprise: open-weight models on vLLM inside their VPC, a self-hosted vector store, Langfuse held internally, and egress rules that block external model APIs. The residency figure they cleared us to publish is 100%. The same pattern runs on premises on your own GPU nodes.

What you get

Delivered as a working production system, in your cloud account

Model serving on vLLM

Qwen 3.8, Gemma 3, Llama 4 or DeepSeek V4.1 served with quantisation and batching tuned to your hardware and latency budget.

Self-hosted retrieval

Qdrant or pgvector inside the perimeter, with permission-aware retrieval and an audit entry per query.

Network isolation

Egress to external model APIs blocked at the network layer, with the rule set documented for your security review.

Internal observability

Tracing, quality and cost dashboards hosted inside the environment, never on a vendor SaaS.

Fine-tuning in place

Domain adapters trained on your GPUs so the training data never leaves either.

Review-ready documentation

Architecture, data flow and access model written for the person reviewing you before contract.

Architecture

The private deployment we ship

Users reach the model through a gateway inside the perimeter. The open-weight model and the vector store run on your hardware. Observability is held internally and nothing routes outside.

When this is the wrong tool

If your policy allows hosted models under zero-retention terms, they are usually cheaper and more capable for the same task. We confirm the actual contractual requirement on the scoping call before recommending a private build.

Internal usersSSOAPI gatewayegress blockedOpen-weight LLMvLLM on client GPUsVector storeself-hostedObservabilityheld internally

Proof

Delivered systems closest to this work

Every figure comes from a system running in production for a real client.

Regulated EnterpriseEU

A private LLM deployment where no request ever leaves the customer environment

1. Problem. A regulated enterprise wanted a modern language model over its internal documents, under a contractual ban on sending that content to any third-party processor. Even zero-retention API terms did not clear the bar: nothing could leave the environment at all.

2. Solution. A fully private deployment inside the customer VPC: open-weight models on client-owned GPU nodes, self-hosted vector store, orchestration and observability, with egress to external model APIs blocked at the network layer. The audit answer to "where did this data go" is the same as "where does it live".

Open weightsvLLMSelf-hosted VPCQdrant

The client's name, sector and jurisdiction are under NDA. The residency figure is the measurement they cleared us to publish.

3. Impact

100%
Data residency inside the client VPC
0
Requests leaving the environment
Open
Weights, on client-owned hardware
Full
Audit trail held internally
HealthcareUSA

HIPAA-compliant clinical decision support for a hospital network

1. Problem. A US hospital network had patient records, lab results and ICD mappings sitting in silos, none of it reachable at the point of care. Clinicians needed decision support without adding friction to already demanding workflows.

2. Solution. A HIPAA-compliant clinical platform on GCP Vertex AI using a hybrid Agentic RAG pipeline. Patient records, lab data and medical literature unified into one queryable layer. Role-based access across every clinical and admin role, a full audit trail on every response, and a zero-downtime SLA.

Agentic RAGGCP Vertex AIHIPAAFHIR

3. Impact

91%
Factual accuracy in clinical responses
27%
Reduction in patient onboarding time
48%
Less manual clinical documentation
HIPAA
Compliance built into the architecture

Questions

private LLM deployment: what buyers ask first

A 27B to 32B class model serves well on 1 to 2 current data-centre GPUs with quantisation; larger models scale from there. We size it from your concurrency and latency targets on the scoping call.