1Deployment models
You can change the deployment model later (§4). To start,
pick the one that is quickest to set up.
01 · OVHcloud
Managed Cloud
DatatenantOVHcloud instanceVPS, Public Cloud or dedicated server · EEA region
InferenceGRIDObsigen GRIDmodels in the EEA · Zero Data Retention
We deploy and maintain Obsigen on dedicated OVHcloud infrastructure. One contract: infrastructure, deployment and maintenance on our side.
infrastructure certifications
- ISO/IEC 27001
- ISO/IEC 27017
- ISO/IEC 27018
- HDS (health data) on OVHcloud Public Cloud instances
best forthe fastest start, no IT effort
Book a demo 02 · your infrastructure
Self-hosted
Datatenantyour environmentserver, VPS or private cloud
InferenceGRIDObsigen GRIDmodels in the EEA · Zero Data Retention
We install and maintain Obsigen in your environment. Hosting, access and security policies stay under your control.
infrastructure certifications
depends on your hosting provider
best fororganizations with their own IT and hosting
Book a demo 03 · on request
On-premise
Datatenantyour data centerserver room or colocation
InferenceGRIDGRID on-premise≥ 256 GB of memory for models
The full stack - data, GRID and models - in your infrastructure. Inference with no connections to external model providers.
infrastructure certifications
depends on your data center
best forregulated sectors and highly sensitive data
Let's talk Compare deployment models →
2How they differ
For engineers →
“Memory for models” is the memory the model can access: GPU VRAM or unified memory. Model quantization,
context size and the number of parallel turns change the actual threshold - which is why we set the hardware
configuration at deployment, not from a table.
4Tenant migration
Getting started does not require buying hardware - you can decide on your own infrastructure later, based on real usage.
We plan moving the tenant to another deployment model together with you.
5On-premise
We prepare each on-premise deployment individually: the hardware configuration, model selection and throughput
are set at deployment. We publish performance results after measuring them on the specific configuration.
Let's talk about an on-premise deployment →