What DeepSeek runs
The models themselves and the infrastructure that serves them. We do not run a data center, we do not own GPUs, and we do not keep a private copy of the model weights.
Delivery
How the service reaches you
The model runs on infrastructure we do not own. The contract, the endpoint and the person who answers the phone are ours. This page is about where that line sits.
Where the line sits
A request you send through the endpoint we issue is processed by DeepSeek's model service. Everything around that request is ours. Both halves are below, so your procurement team can see exactly which is which.
What we run
The layer around the model, not under it — the commercial relationship that keeps access in good standing, and the paperwork your finance team needs.
We are stating that plainly because the alternative — a page of stock photography and the phrase "our infrastructure" — would be a claim we could not support if your security team asked us to evidence it.
What we actually operate
This is real work, and it is the reason this site exists at all.
The account with the model provider
We hold the commercial account, and we maintain the relationship that keeps it in good standing. That relationship is the thing that keeps your access working.
The endpoint and the keys
We issue the endpoint you call and the API keys you use, and we can revoke them. Keys are ours to manage, which means they are ours to shut off if they leak.
The contract and the invoice
The contract, the invoice and the closing documents your finance team needs — issued by a company they can check, not by an individual.
A named contact
A named contact, and a defined route to escalate when something breaks. One person on your account who owns the answer, rather than a ticket queue.
What that means for you in practice
One counterparty
You deal with us, not with the model provider. You do not open an account with them, you do not put a card on file with them, and you do not have to explain to your finance team why a line item sits on somebody's personal account.
The trade-off, stated up front
We cannot show you a data center, because there is not one. If your procurement process requires a site visit or a tour of a facility, we will not be able to satisfy it — and we would rather say so now than after you have spent a month on evaluation.
If something breaks
Some failures are not ours to fix
The model runs elsewhere, so a fault inside that layer is not something we can repair. We are not going to pretend otherwise on a status page.
What is ours
The obligation to tell you what is happening, to say so when we do not yet know, and to keep one person on your account who owns the answer. That goes into the agreement, not just onto a web page.
What we will not do
We will not claim somebody else's infrastructure
We will not describe somebody else's infrastructure as ours, and we will not put a facility photograph on this page to imply otherwise.
And we will say so in writing
If a supplier evaluation form asks whether we own the compute, the honest answer is no, and you are welcome to quote this page when you write it down.
DELIVERY · HOW THE SERVICE REACHES YOU
STEP 1
DeepSeek runs the model
their infrastructure, their updates
STEP 2
We hold the account
commercial relationship and support
STEP 3
You get one contract
one endpoint, one invoice, one contact
- No data center of our own
- One counterparty instead of two
- A named contact on your account
Tell us what you're running.
Send us your monthly volume and what you use today. We usually reply within one business day with a price and a named contact.