TODAY — FLAT PLAN, ROLLING WINDOW
09:0014:20 — limit reached19:20
You're mid-refactor when the window closes. Nothing is wrong with your usage — you just wait five hours, or open your wallet somewhere else.
VPL — VIRTUAL PRIVATE LLM · WAITLIST OPEN
Your own instance. No reset timer.
A private LLM instance on EU hardware, for a flat monthly fee. Nothing counts down and nothing resets — the only limit is how many requests you run at the same moment, and you set that with one slider.
The ceiling isn't the bill. It's the clock.
a flat plan you can still get locked out of isn't flat
ON SOLHEIM — CONCURRENCY ONLY
09:00no ceiling to reach19:20
The only limit is how many requests run at the same moment. Send more and they queue for milliseconds — the day never stops and the invoice never moves.
-
THE CAP
Flat-fee assistant plans still meter you through a rolling window. The work stops on someone else's schedule.
-
THE JURISDICTION
Your code and your customers' data go through a US-jurisdiction provider, and your DPA has to explain it.
-
THE FORECAST
Per-token billing makes next month a guess. Capacity you rent by the month is a line item you can plan around.
One project. One VPL.
if you have ever rented a virtual private server, you already know this product
A project gets its own virtual private LLM — one endpoint, one key. A slider sets how many instances it runs, and an instance is one request in flight. Three instances means three things at once: your agent, your editor, your test loop. The API is OpenAI-compatible, so Cline, Roo Code, VS Code BYOK and your own backend all talk to it unmodified.
| ON A VPS | ON A VPL | WHAT IT MEANS FOR YOU |
|---|---|---|
| vCPU + RAM | instance count | One slider, one dial. Inside that size, run as much as you like, all day. |
| no request quota | no usage window | Nothing counts down and nothing resets. You are never locked out mid-task. |
| OS image | open-weight model | Pick and pin the model. Swap it by changing one string, no migration. |
| one server, one host | one project, one VPL | Keys, usage and limits stay per project — nothing is shared by accident. |
| datacenter region | EU-only region | Nothing leaves EU jurisdiction — GDPR and AI Act posture by construction. |
Three steps, then it's just an endpoint.
nothing to install, nothing to rewrite
-
01
Create a project
A project is one VPL: its own endpoint, its own key, its own usage. Name it after the thing it serves.
-
02
Set the instance count
One slider decides how many requests run at once. Move it up for a week of parallel agents, back down after. That is the whole capacity model.
-
03
Point your tool at it
Base URL and key into Cline, Roo Code, VS Code BYOK, or any OpenAI SDK. Nothing else in your setup changes.
export OPENAI_BASE_URL=https://api.solheim.eu/v1 export OPENAI_API_KEY=slh_live_9f3c… # beyond your instance count, calls queue. # they do not 429 and they do not cost extra.
EU-hosted, all the way down.
sovereignty is an architecture, not a checkbox
INFRASTRUCTURE
GPUs at EU-owned providers in EU datacenters. No US hyperscaler in the serving path, so no CLOUD Act exposure to write into your DPA.
MODELS
Open weights under permissive licenses, pinned per instance and run by us. Your prompts are not training data — not ours, not anyone's.
- qwen2.5-coder-32b
more images as capacity lands
ROUTING
Requests never leave the region, and this page loads nothing from a third-party origin — no US CDN, no analytics, no fonts phoning home.
PRICING PREVIEW
One dial: how many at once.
instances × a flat monthly rate. no tokens, no tiers, no overage
indicative only — no numbers are final until we've validated real concurrency. Waitlist signups get founder pricing at launch, and discounts belong on annual prepay and instance volume, never on concurrency.
Who it's for.
same product, same dial, same price
DEVELOPERS RUNNING CODING AGENTS
You live in Cline, Roo Code or VS Code and you hit the window most weeks. Three instances is an agent, an editor and a test loop running at once — for as long as the day lasts.
FOUNDERS WHO NEED AN INFERENCE BACKEND
Your product needs a private LLM behind it, with a bill that doesn't move when traffic does. Point your backend at the same endpoint and size it the same way.
It is one product, not two. What changes between these is what you point at the endpoint — not the pricing, not the API, not the machine.