More users per GPU. On any GPU.

ARK runs open frontier models on any NVIDIA GPU from Turing to Blackwell, GeForce cards and mixed generations included, and keeps scaling as users pile on. Use it on ARK Cloud, or run ARK Core on your own GPUs.

Or try it on ARK Cloud: sign in with Google, get free starter credits.

Tokens per second, all users togethervLLM 0.27.1ARK
2.5×
vLLM's throughput at 64 users, on the same two RTX 5090, first token 7.0× sooner. vLLM is faster for one user.
The benchmark
Attention size
1M tokensshared by all requests in flight on Qwen3.6-35B-A3B on ARK Cloud
API dialects
OpenAI + Anthropicone key, same models, change the base URL
Modalities
Text, vision, audiochat, reasoning, tools, embeddings, speech to text
Where it runs
EU or on-premARK Cloud in the EU, ARK Core on your GPUs
Drop-in compatible

Keep your code. Change two lines.

ARK speaks the APIs your stack already uses. Point the OpenAI or Anthropic SDK at ARK, pick an ARK model, and the rest of your application stays as it is.

  • OpenAI: chat completions, embeddings, audio transcriptions, model listing
  • Anthropic: messages and token counting
  • Streaming with usage, tool calling, reasoning, image input
  • Stateful sessions: send only the new turn, ARK keeps the conversation
app.py2 lines changed
 client = OpenAI(
-    base_url="https://api.openai.com/v1",
+    base_url="https://api.ark-labs.cloud/api/v1",
     api_key=os.environ["ARK_API_KEY"],
 )
 
 response = client.chat.completions.create(
-    model="gpt-4o-mini",
+    model="arklabsai/Qwen3.5-122B-A10B",
     messages=messages,
     tools=tools,
 )
Three ways to run ARK

Start in our cloud. Move it in-house when you are ready.

The API, the models and the behaviour are the same wherever ARK runs, so a prototype built on ARK Cloud becomes a self-hosted service without a rewrite.

Self-hosted · your GPUs

ARK Core

The ARK platform on your own infrastructure, on-premises or in the GPU cloud you choose. A model can span several GPUs and machines.

  • The same API and models as ARK Cloud
  • Runs on NVIDIA GPUs, from RTX cards to the data centre
  • Your network, your logs, your keys
Self-hosted · custom

ARK Tailored

A deployment designed with our engineers: models, hardware sizing, integration and support.

  • Capacity planned for your traffic
  • Custom models and integrations
  • Direct line to the team that builds ARK
Patchwork clusters

Every GPU you have, working as one.

Bring machines with whatever NVIDIA GPUs they carry. ARK joins them over ordinary Ethernet into one deployment and splits each model across them, so cards of different generations and sizes serve the same model together.

  • One model, three machines, two GPU generations: Qwen3.5-122B-A10B runs in production on four RTX 5090 in two machines and an RTX 4060 Ti in a third.
  • Mix generations and sizes, from an RTX 3060 to data-centre GPUs.
  • Grow by adding a machine: its servers join the running deployment and their models appear in the API, with no restart.
One model split across three machines with different NVIDIA GPUs, joined over Ethernet: four RTX 5090 in two machines and an RTX 4060 Ti in a third. Qwen3.5-122B-A10B, one model Machine 1 RTX 5090 RTX 5090 Machine 2 RTX 5090 RTX 5090 Machine 3 RTX 4060 Ti standard Ethernet
Measured, not promised

Throughput that grows with your traffic.

Measured on ARK Cloud through the public API with real summarisation traffic. Qwen3.5-122B-A10B on four RTX 5090 GPUs kept the median time to first token under 0.6 seconds up to 24 concurrent requests, and processed 5,726 tokens per second at 60.

Qwen3.5-122B-A10B
5,726 tok/sinput + output at 60 concurrent requests
Qwen3.6-35B-A3B
7,448 tok/sat 48 concurrent, on four RTX 4070 Ti SUPER
First token
0.27 smedian for Qwen3.6-35B-A3B, one request at a time
Reliability
730 / 730Qwen3.5-122B-A10B requests completed across the run

Throughput on ARK Cloud

Total tokens per second (input + output) as concurrent requests grow. Summarisation traffic, about ten input tokens per output token, October 2026.

Total throughput on ARK Cloud as concurrent requests grow 0 2,500 5,000 7,500 10,000 1 8 16 24 32 48 60 Concurrent requests Tokens per second (input + output) 7,439 Qwen3.6-35B 5,726 Qwen3.5-122B
Qwen3.5-122B-A10B · 4× RTX 5090Qwen3.6-35B-A3B · 4× RTX 4070 Ti SUPER
Sovereign by design

Your prompts stay inside the perimeter you choose.

ARK Cloud runs in the European Union on hardware we operate ourselves. When your rules say data must stay on your premises, ARK Core and ARK Tailored put the same platform inside your own network.

  • No training on your data. ARK serves models; it does not train them.
  • Logs without content. Request logs keep metadata: prompt fields are redacted and generated text is not logged.
  • Known models, published licences. Every model is an open-weight model you can inspect, with its licence on our model page.
  • Your own perimeter when you need it. Run the whole platform on your infrastructure with ARK Core or ARK Tailored.
Works with your tools

Agents, SDKs and apps connect in minutes.

All integrations

Your first request is two minutes away.

Sign in with Google, copy your key, and call any ARK model with the SDK you already use.