EU data residency · OpenAI-compatible

EU AI Inference API

An OpenAI-compatible endpoint, hosted in Sweden

A managed inference endpoint running open-weight models — Llama, Qwen, Mistral, Gemma, DeepSeek — on our own GPUs in Sweden. Point your existing OpenAI client at our base URL, keep your code, and your prompts stay in the EU under EU law. It's your endpoint running open models, not a relay to a US provider — so there's no third-party account to suspend and no per-token surprise bill.

See how it works Request access →

Teams building on AI want two things that rarely come together: the drop-in ergonomics of the OpenAI API, and control over where their data goes. This endpoint gives you both. We run open-weight models behind an OpenAI-compatible API on bare-metal GPUs in our Swedish data centre, so switching an existing integration is usually a one-line change — and every prompt, document and completion is processed inside the EU, never sent to a US AI provider.

Why a Swedish inference endpoint

Drop-in compatible

Keep your OpenAI client. Swap the base URL and API key — your calls, streaming and tool-use work unchanged.

EU data residency

Inference runs on our GPUs in Sweden, under EU law and GDPR. Prompts are not sent to, or stored by, a US provider.

Your endpoint, no bans

A managed service we run for you on open models — there's no third-party consumer account to get flagged or suspended.

Flat, predictable pricing

Dedicated capacity at a monthly price. No per-token metering, no bill shock when a job runs hot.

One line to switch

Already calling OpenAI? Point the same client at your Swedish endpoint.

# Same OpenAI SDK — only the base_url and key change
from openai import OpenAI

client = OpenAI(
    base_url="https://ai.internetport.com/v1",  # your EU endpoint
    api_key="ipt-••••••••••••••••",
)

resp = client.chat.completions.create(
    model="llama-3.3-70b",
    messages=[{"role": "user", "content": "Hej!"}],
)
print(resp.choices[0].message.content)

Works with the official OpenAI libraries, LangChain, LlamaIndex and anything that speaks the OpenAI API.

What powers it

Bare-metal GPUs

Served from our own GPU servers in Sweden with vLLM — real accelerators, not a reseller layer.

Open-weight models

Llama, Qwen, Mistral, Gemma and DeepSeek in several sizes. Ask for a specific model and we'll load it.

Chat, embeddings, tools

Chat completions, streaming, function/tool calling and embeddings — the endpoints your stack expects.

Shared or dedicated

Start on shared capacity, move to a dedicated GPU when you need guaranteed throughput and isolation.

Indicative tiers

Priced on capacity, not tokens. Tell us your model and throughput and we'll size it.

Starter
Good forPrototyping, low volume
ModelsUp to ~8B, shared
CapacityShared GPU
DataEU (Sweden)
Most popular
Team
Good forProduction apps, steady traffic
ModelsUp to ~70B
CapacityReserved GPU share
DataEU (Sweden)
Dedicated GPU
Good forHigh throughput, isolation, SLAs
ModelsYour choice, reserved VRAM
CapacityWhole GPU server
DataEU (Sweden)

Prices indicative — tell us your use case for a firm quote.

Frequently asked questions

No. We run open-weight models on our own GPUs in Sweden. The API is OpenAI-compatible — meaning it speaks the same request/response format, so your existing client works — but requests are served by our models and never relayed to OpenAI, Anthropic or any third-party AI service. There is no upstream account involved and nothing to circumvent.

Open-weight models such as Llama, Qwen, Mistral, Gemma and DeepSeek, in a range of sizes, plus embedding models. If you need a specific open model or version, tell us and we'll load it on your capacity.

Prompts and completions are processed on our servers in Sweden and are not sent outside the EU. We don't use your traffic to train models. A data processing agreement is available, and dedicated-capacity customers can request no-retention handling of request content.

With our self-hosted AI hosting you run Ollama and Open WebUI on your own server and manage the models yourself. This API is the managed version — we run the GPUs, the serving stack and the model updates, and you just call the endpoint. Same EU data residency; less to operate.

For European users, yes — our network peers widely and round-trip times across the continent are low. For token-streaming workloads the model's generation speed usually matters more than network latency. Tell us where your users are and we'll be straight about what to expect.

Your AI API, in the EU

An OpenAI-compatible endpoint on open models, served from Sweden. Keep your code, keep your data in the EU.

Request access Prefer to self-host?