Optimized LLM inference for production applications.
Serving a language model to real users is a different job than running one on a laptop. Production inference means concurrent requests, streaming tokens, predictable capacity and a clear view of what every request cost you. HostYourAI runs open models such as Llama, Qwen, Mistral and DeepSeek with vLLM on European GPUs, exposed through an OpenAI-compatible API, so your application code barely changes.
Where that inference happens matters. Every prompt your users send is data, and often personal data. Keeping inference in European datacenters, backed by a Data Processing Agreement and a public subprocessor list, turns a compliance headache into a checkbox you can actually tick.
Support tickets, medical notes, contract clauses: whatever your users type ends up in a prompt. Under the GDPR you are accountable for where that text is processed. Inference that never leaves multiple European regions keeps your data flow map short and your DPA meaningful. HostYourAI does not train on customer data, and traffic is encrypted with TLS in transit and AES-256 at rest.
Round trips to another continent add delay to every token of a streamed response. For chat interfaces, where perceived speed is the time to the first token, serving from European GPUs to European users simply feels faster. Popular models on the shared Router are kept warm through a warm pool, so requests do not wait for a cold model to load.
Inference bills are notoriously opaque. HostYourAI uses one prepaid credit balance, topped up with iDEAL, card or SEPA, and every request is metered so you can see usage per key. Because the API is OpenAI-compatible, moving in or out is a base URL change, not a rewrite. Details are on the pricing page.
Three things separate a demo from a service. First, streaming: the API supports server-sent events on /v1/chat/completions, so tokens reach your UI as they are generated. Second, capacity: the shared EU Inference Router pools demand across a warm fleet, while dedicated GPU instances give you a vLLM server of your own, with an encrypted API key and a VRAM floor that prevents deploying a model onto a GPU that is too small. Third, observability: per-request usage records and a 99.9% uptime SLA, so you know both what happened and what to expect.
| Production requirement | How it is met |
|---|---|
| Token streaming | SSE on /v1/chat/completions, OpenAI-compatible |
| Fast first token | Warm pool keeps popular Router models loaded |
| Guaranteed capacity | Dedicated vLLM instances billed per hour |
| Usage visibility | Per-request metering from one credit balance |
| Availability | 99.9% uptime SLA |
| Right-sized hardware | VRAM floor enforced at deployment |
from openai import OpenAI client = OpenAI( base_url="https://hostyourai.com/api/v1", api_key="hyai-...") client.chat.completions.create( model="llama-3.3-70b", messages=[{"role":"user","content":"Hallo!"}])
Create an API key, pick a model from the model catalog, and point your existing OpenAI client at the new base URL. This JavaScript example streams a response from Llama 3.3 70B:
import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://hostyourai.com/api/v1",
apiKey: "hyai-...",
});
const stream = await client.chat.completions.create({
model: "llama-3.3-70b",
messages: [{ role: "user", content: "Summarize this ticket for the support team." }],
stream: true,
});
for await (const chunk of stream) {
process.stdout.write(chunk.choices[0]?.delta?.content ?? "");
}The catalog lists over 100 open models, including Llama, Qwen, Mistral, DeepSeek and Gemma. The Model Garden shows the state of each one: warm, warming up, serveable, or on request.
Usually only the base URL and API key. The API is OpenAI-compatible, and there is also an Anthropic-compatible /v1/messages shim for code written against that SDK. See the guide to migrate your OpenAI client to the EU Router.
The Router bills per token and suits variable workloads. A dedicated instance bills per hour, gives you isolated capacity, and idles down when unused. Both draw from the same prepaid credit balance.
Popular Router models are kept warm, so there is no load time. Less common models may show as warming up in the Model Garden while vLLM loads the weights.
Yes, /v1/chat/completions supports SSE streaming exactly as the OpenAI API does. Set stream to true and consume the chunks.
Inference runs in European datacenters across multiple European regions. HostYourAI provides a DPA, publishes its subprocessor list, and never trains on customer data.
From model hosting to a customer-facing API, it is built for developers and businesses who want their AI running on infrastructure they actually control, inside the EU.
Your data and your models stay on European GPUs. GDPR-friendly by design.
Llama, Qwen, DeepSeek, Mistral, FLUX and plenty more. Pick one and it is warm in minutes, with no DevOps on your end.
Point your existing client at the Router and keep your tools. No rewrite, no lock-in.
No infra to manage. Pick a model, get an OpenAI-compatible URL, ship.
Choose from the Model Garden or paste any HuggingFace ID. Set the VRAM and pick an EU GPU.
We deploy vLLM, run readiness probes, and hand you a warm OpenAI- and Anthropic-compatible URL plus an API key.
Point your client at the Router. It auto-routes to a warm instance, idles GPUs when nobody is online, and logs every request.
HostYourAI keeps your models, prompts and data on European GPUs. It is built for teams that care about compliance, reliability and real control.
GPUs and data residency inside Europe. Your prompts never leave the EU.
Run open-weight models with no black boxes or hidden telemetry.
GPUs idle when nobody is online, so you only pay for what you run.
Your infra, your keys, your models. Leave whenever you want.
The Router speaks the OpenAI and Anthropic APIs, so it drops straight into the clients and SDKs your team already runs. Just change the base URL.
Try HostYourAI for freeYes. HostYourAI runs open models on GPUs in European datacenters via vLLM. Your prompts and outputs never leave the EU and there is no US cloud provider in the chain.
Yes. All processing happens inside the EU, a Data Processing Agreement (DPA) is available and the subprocessor list is public. Open weights also mean no training on your data.
Yes. Point your existing OpenAI or Anthropic client at our Router (https://hostyourai.com/api/v1), change only the base URL and API key. No rewrite, no lock-in.
Pay-as-you-go on one prepaid credit balance: the shared router per token or a dedicated GPU per hour. Free to start, no minimum, no fixed monthly fee.
Text and image models on dedicated EU GPUs. Every model tested on our own hardware.
Explore more about EU-hosted AI on HostYourAI.
Chat with dedicated instances and Router models in the Playground. Test prompts, compare models and then see per-request usage and latency.
Read more →Point your Anthropic client at our Router through a /v1/messages shim and run open models on European GPUs. Drop-in, EU-hosted, no rewrite.
Read more →Fine-tune LLMs for your specific use case. LoRA, QLoRA, full fine-tuning on dedicated GPUs.
Read more →Deploy any open model on a dedicated European GPU with vLLM. Your own endpoint, encrypted upstream keys, idle when nobody is online.
Read more →Host RAG pipelines for AI with your own knowledge base. Vector databases, embeddings, and LLMs in one platform.
Read more →Host AI chatbots on European infrastructure. Customer service, internal assistants, and more with GDPR compliance.
Read more →