Model Deployments
PreviewShip models the way you ship code.
Group a model's releases into a project: every deployment is immutable, production is an alias you promote or roll back instantly, and each project has its own domains, environment variables, logs and analytics. Serve it managed on shared capacity or dedicated on your own GPUs.
- Pricing
- Billed as inference or per GPU-hour
- Layer
- Inference
- Deploy from
- Catalog models, Fine-tune checkpoints, Hugging Face, Uploaded weights, Pipeline outputs, vLLM, SGLang, TGI
Why Model Deployments
Every release is a deployment you can return to.
A model project keeps every deployment it has ever made. Nothing is edited in place: a new config or checkpoint is a new deployment, and production is an alias that points at one of them.
Managed or dedicated
Shared, autoscaled capacity or GPUs reserved for you.
Instant rollback
Production is an alias: move it back in one step.
Logs and analytics
Requests, latency and errors for every deployment.
How it works
Immutable deployments with instant promote and rollback.
In the console
Everything in one place.
Model Deployments lives in the LegionEdge cloud console, next to every other service in the workspace, under one account and one identity.
Pricing
Billed as inference or per GPU-hour
Managed deployments are billed per token, like serverless inference. Dedicated deployments are billed per GPU-hour for the capacity they run on.
- The new-project wizard shows a cost estimate before you deploy.
- Scale-to-zero is optional on dedicated deployments.
Catalog models
GPU rates
Related products