Deploy LangChain agents inside
confidential VMs.
Drop-in ChatOpenAI swap. Every reasoning call goes to a model in an Intel TDX enclave at our inference provider. Existing LCEL chains, LangGraph state graphs, agents, retrievers, and tool calls run unchanged.
Requests pass through our relay, which sees them in clear (TLS ends at our host). To keep plaintext off our servers, run your own inference server in a Confidential VM and terminate TLS inside its trust domain. Confidential VMs
Built for legal RAG, financial analysis, healthcare summarization, and any pipeline that needs EU AI Act Article 12 logging without ever shipping privileged context to a US controller.
Why run LangChain inside Intel TDX
Standard LangChain pointed at OpenAI is great for prototyping. For production workloads in regulated industries, three risks make it unshippable.
Privileged data leaving the firm
Default LangChain pointed at OpenAI sends every retrieved chunk, every tool argument, and every generated output to a US controller. For privileged matter notes that is enough to break legal-professional privilege.
No Article 12 audit trail
OpenAI logs are not written to your audit sink. Article 12 of the EU AI Act requires automatic logs, retained for the system lifetime, that you control. With LangChain on a foreign API you do not get the inputs or outputs you need.
No hardware isolation
Standard cloud inference is "encrypted in transit, encrypted at rest" but plain RAM during compute. A privileged provider, malicious admin, or compromised hypervisor can read prompts. TDX removes that category for the model's host.
VoltageGPU is a French controller (VOLTAGE EI, SIREN 943 808 824) whose TEE models run in Intel TDX enclaves at its US inference provider, with attestation evidence of the serving instances on your nonce. Pointing your existing LangChain stack at our endpoint puts the model behind that boundary; our relay still sees requests in clear.
Install
Standard langchain, langchain-openai, and langgraph from PyPI. No fork, no patch, no proxy.
5-minute quickstart
Construct one ChatOpenAI instance pointed at https://api.voltagegpu.com/v1. Use it anywhere a ChatModel is expected, chains, agents, LangGraph nodes, retrieval QA, structured output. Streaming, tool calling, async batch all work identically.
LangChain.js / TypeScript
@langchain/openai takes the same configuration. Works in Node, Bun, Deno, and Edge runtimes.
What works out of the box
The endpoint is OpenAI-compatible, so every LangChain primitive that talks to ChatOpenAI works without modification.
LCEL chains
Prompt | Model | OutputParser pipelines unchanged.
LangGraph
StateGraph nodes bind a confidential ChatOpenAI as their LLM.
Tool calling
bind_tools, create_react_agent, OpenAI tool schema all work.
Streaming
.stream() and .astream() over Server-Sent Events.
Retrievers
PGVector, Qdrant, Chroma, Weaviate keep your embeddings on-prem.
Async batch
abatch, abatch_as_completed for high-throughput pipelines.
LangGraph state graph, RAG with planner, writer, critic
Bind one confidential ChatOpenAI to every node. The whole graph (planner, retriever, writer, critic, finalizer) reasons against models in Intel TDX. Conditional edges, checkpointing, and human-in-the-loop interrupts behave identically.
Tool calling, agent reasons in TDX, tools execute on your machine
create_react_agent and bind_tools work without changes. Tools run in your process, they can hit internal APIs without those endpoints being exposed to the confidential endpoint.
Streaming with .stream() / .astream()
Server-Sent Events streaming is identical to OpenAI. Use it for chat UIs, FastAPI StreamingResponse handlers, or Next.js Edge functions.
Vector store inside TDX, confidential RAG
For private RAG you have three production-ready paths. All three keep raw documents and embeddings out of any third-party SaaS vector database.
On-prem vector DB
Run PGVector, Qdrant, Chroma, or Weaviate inside your own VPC. Only the matched chunks transit the confidential endpoint for reasoning.
Local embeddings
No confidential embedding model is offered yet. Run the embedder on your own machine, such as BAAI/bge-m3, so raw documents never reach a SaaS embedder, and send only the retrieved passages to a -TEE model.
Hybrid retrieval
BM25 + vector hybrid retrieval is supported via standard LangChain Retrievers. The reranker can also run on the confidential endpoint.
Observability + logs, EU AI Act Article 12
Article 12 of the EU AI Act requires automatic event logs throughout the lifetime of high-risk AI systems. The log is yours: a LangChain callback handler captures chain-level events on your side, next to the attestation of the serving instances fetched from GET /v1/attestation.
See the full guide: Article 12 AI Act logging , retention windows and tamper-evident sinks.
Pricing
Pay-per-token via the same /v1 API. No per-seat licence, no platform fee, no minimum. Mix models freely across nodes and chains.
Pay per token from your balance, no subscription. Every -TEE model is on the pricing page.
Why this is confidential
Every LangChain call lands on a TDX instance
Your request reaches our API over TLS; our relay forwards it in clear to a model instance inside an Intel TDX trust domain, where the host and its hypervisor see encrypted memory.
Memory encryption by the CPU
Keys held by the CPU encrypt the trust domain's memory at runtime. A dump from the host yields ciphertext, not your contracts or patient notes.
Attestation on your own nonce
GET /v1/attestation returns the TDX quote and NVIDIA GPU evidence of the instances serving a model, bound to a nonce you choose. It covers the instances, not each response.
No training on your prompts
We never train on prompts or completions. RGPD Article 28 DPA, EU jurisdiction (VOLTAGE EI, France, SIREN 943 808 824).
Developer FAQ
Do I need to fork LangChain?
No. LangChain ChatOpenAI is the supported integration point. Pass base_url=https://api.voltagegpu.com/v1 and api_key=vgpu_... and you are done. No SDK fork, no monkey patching, no proxy required.
Does LangGraph work?
Yes. Bind a confidential ChatOpenAI to each node. StateGraph, conditional edges, checkpointing, async streaming, and human-in-the-loop interrupts all behave identically.
Can my tools call internal APIs?
Yes. Tools execute on your machine; only the LLM calls leave it, through our relay, to a model in an Intel TDX enclave.
Streaming and tool calling?
Both supported. The /v1/chat/completions endpoint mirrors OpenAI for SSE streaming and tool / function calling. bind_tools and create_react_agent work without modification.
How does this satisfy EU AI Act Article 12?
The log is yours to keep: capture chain-level events with LangChain callbacks (timestamp, model, your own hashes of input and output) and archive the attestation of the serving instances, fetched from GET /v1/attestation on your own nonce, alongside them. Our API records only the model, the token counts and the cost of each request.
Latency overhead vs OpenAI direct?
We have not published our own latency or overhead measurement. A third-party benchmark of NVIDIA Hopper confidential mode reports an overhead below 7% for most typical LLM queries (arXiv 2409.03992); our relay adds a network hop.
LangChain.js / TypeScript supported?
Yes. @langchain/openai accepts the same baseURL and apiKey configuration. Drop the URL into a ChatOpenAI constructor in Node, Bun, or Deno.
How do I get an API key?
Register at voltagegpu.com/register, top up (card, BTC, ETH, USDC), and create a key at voltagegpu.com/api-keys. The inference key starts with vgpu_ and acts as a drop-in OPENAI_API_KEY with base_url https://api.voltagegpu.com/v1. Requests pass through our relay, which sees them in clear (TLS ends at our host). To keep plaintext off our servers, run your own inference server in a Confidential VM and terminate TLS inside its trust domain.
EXPLORE FURTHER
Ship a sovereign LangChain stack this afternoon
Generate an API key, swap two lines, run your existing chains against Intel TDX.