Dedicated deployments
Reserved capacity and your own model ID, with no queueing behind other customers.
Dedicated capacity for high-volume realtime workloads, with no queueing behind other customers.
We host your weights, fine-tune on your requests and optimize decoding and kernels for them.
Reserved capacity and your own model ID, with no queueing behind other customers.
Upload weights or point us at a repo, and your model runs on the same engine and API as ours.
Fine-tune open models on your production conversations.
Draft models trained on your requests.
When a stock engine is the limit, we optimize the attention step, the KV-cache router or the serving backend for your model.
US, Europe, India or Asia Pacific, with zero data retention on the models we host.
Dedicated deployments run on the fleet we operate for every Inworld model, so a fix we make reaches your traffic in days.
Tens of trillions of tokens a month
Voice across four regions. LLM inference in the US.
Illustrative activityEach figure is the best measured case on the model it names.
Inference built for people runs on Inworld. Who are you building for?
A dedicated deployment on Inworld AI is inference capacity reserved for your traffic on the fleet we operate, with your own model ID. Your requests never queue behind other customers, and your model stays loaded between requests. The same fleet serves tens of trillions of tokens a month, and the team that runs it tunes your deployment.
Yes, you can bring your own open or fine-tuned model to Inworld AI for dedicated inference, by uploading weights or pointing us at a repo. We select the inference stack and tune quantization, caching, batching and parallelism for your workload, then deploy it. If you want to run your own serving stack, we also offer Kubernetes access to dedicated nodes.
You call a model on an Inworld AI dedicated deployment the same way you call every Inworld model, with Chat Completions requests to https://api.inworld.ai/v1/chat/completions, your Inworld API key and your model ID. The OpenAI SDK works with its base URL set to https://api.inworld.ai/v1, so moving traffic from a shared model to your deployment means changing one model ID.
Yes, Inworld AI's voice models, including Realtime TTS-2 text to speech, run on dedicated capacity too, with guaranteed capacity and no shared tenancy. A dedicated voice deployment suits apps with steady high volume that want capacity reserved for their own traffic. Realtime TTS-2 Flash returns first audio in as little as 50 ms.
Yes, fine-tuning on your production conversations is available on an Inworld AI dedicated deployment, with your approval. We fine-tune open models on your traffic, and we can train draft models on your requests for realtime decoding, which drafts several tokens ahead and has the full model verify them in one pass.
An Inworld AI dedicated deployment can run in the US, Europe, India or Asia Pacific, the four regions of the fleet we operate. Zero data retention is available on Enterprise plans and as an add-on on the Growth plan for the models we host, so prompts and completions are processed in memory and redacted from our logs as soon as processing completes. Usage metadata is kept for billing.
Dedicated inference capacity on Inworld AI is priced on demand or provisioned, with volume pricing and no egress fees. Each quote is set for your workload and traffic, and capacity is reserved for you, so your requests never queue behind other customers. For comparison, shared serving of open models starts from $0.07 per million input tokens, for Gemma 4 26B.
Yes, Inworld AI dedicated deployments run production LLM traffic with SOC 2 Type II controls, isolated tenancy and monitoring around the clock with automatic recovery. On the same fleet, 99.999% of requests succeeded on Gemma 4 31B over 30 days, more than half a billion requests with about 1 in 160,000 failing, counting server errors, timeouts and capacity rejections.