SolutionsSelf-hosted teams

Own the runtime. Own the cost curve.

Platform teams building an internal AI service want predictable cost and full control. ARK Core serves open-weight models on your NVIDIA GPUs under a per-GPU licence. More requests use more of your capacity, never a bigger per-token invoice.

Same API and models on ARK Cloud and on your own GPUs. Prototype today, move in-house without a rewrite.

2.5×

The tokens per second of vLLM at 64 users, on the same two RTX 5090, with the first token 7.0× sooner. vLLM is faster for a single user.

Read more
64 streams

Per model, for every model in the ARK 2.0 release benchmark. ARK 1.0 was tested at 12.

Read more
9.3×

The total throughput of ARK 1.0 at full load (median of 15 models).

Read more
2×

The context in the same GPU memory, with the 8-bit attention cache.

Read more
The challenge

Why internal AI platforms get expensive.

Per-token prices keep falling, but bills don't. Gartner predicts the inference cost of each agentic workflow will rise more than fivefold through 2028.

Gartner, 17 August 2026. Agentic models need 5–30× more tokens per task than a standard chatbot (Gartner, March 2026).

Cheaper tokens, bigger bills

Every new internal use case adds to a per-token invoice, and agents multiply the tokens behind each task. Uber reportedly used up its entire 2026 AI coding-tools budget in about four months.

Fortune, 26 May 2026, citing reports.

The price list changes under you

Usage-based billing, discounts that end at a contracted cap, prices that jump past a prompt length. Your budget follows someone else's rate card.

Your engine slows as teams arrive

A serving engine tuned for one user at a time levels off as concurrent users grow. Each new team makes everyone slower.

Big models, real hardware

The models you want need more memory than one GPU holds.

On the same GPUs

Built for many users sharing the GPUs.

We ran ARK 2.1 and vLLM 0.27.1 on the same two RTX 5090 on the same day, with the same model at the same 4-bit precision, the same prompts, the same third-party benchmark script and both engines at default settings. vLLM is faster for a single user. With 4,000-token prompts ARK serves more from 8 users upward.

UsersARK 2.1, total tok/svLLM, total tok/sARK first tokenvLLM first token
1881600.33 s1.58 s
167645111.95 s12.88 s
641,6556526.82 s47.92 s

Qwen3.6-35B-A3B, 4,000-token prompts, two repeats; zero failed requests on either engine. Full method and caveats.

Where ARK helps

An engine built for shared, internal traffic.

One deployment serves many teams and many models, with throughput that grows as more people use it.

Flat cost per GPU

A per-GPU licence with no per-token fee. Your cost is set by the GPUs you run, not by a provider's next price change.

Throughput that grows with users

ARK 2.0 batches every request in flight, so total output rises as teams pile on instead of being shared out between them.

Long prompts, read fast

ARK 2.1 reads prompts across all the GPUs of a split model at once. A 64,000-token prompt gets its first token in 4.7 seconds instead of 8.4, and bursts of long prompts are read 1.6 to 1.8× faster.

Agents that don't re-read everything

Repeated prompts come back from cache automatically, 9× sooner for a repeated 64,000-token document. Stateful sessions keep a conversation on the server, so each turn sends only the new message.

Big models, elastic fleet

Split a model over GPUs of different generations and sizes across machines on standard Ethernet; Qwen3.5-122B-A10B runs in production on four RTX 5090 plus an RTX 4060 Ti. Servers join or leave without a restart, and with a second copy of each stretch a failed server's requests are replayed on another path.

How ARK routes requests and fails over

Operable from day one

You get Prometheus metrics, structured logs with a correlation id per request, prompt fields redacted by default, and a test suite that writes JUnit results on your deployment. Per-request token usage, with cached and reasoning tokens included, lets FinOps see cost per team and per task.

“By 2028, 60% of Global 500 companies will embed AI FinOps control at inference.” — Gartner Top Strategic Predictions, 15 September 2026

Requirements

What you need to run it.

Any NVIDIA GPU from Turing to Blackwell, whether GeForce, workstation or data centre (from the RTX 3060 to the H100, H200 and L40S), on Linux x86-64 with standard Ethernet between machines. Different generations and sizes can serve the same model. Arm-based systems such as GB200 are not supported. Full requirements are on the ARK Core and Hardware pages.

NVIDIA Turing → BlackwellAny mixLinux x86-64Standard EthernetKeycloak or HTTP hooksPrometheus

Support by fleet size: see the levels on the pricing page.

Benchmark it on your own traffic.

Published benchmarks are a starting point. Your prompts, models and concurrency decide the real numbers. Send us your GPU inventory and the models your teams need, and we reply with a deployment plan and the throughput to expect. Or try the API on ARK Cloud first, with free starter credits.