Deploy poolside models on dedicated GPUs
2 poolside models ready to deploy on GPU capacity reserved for you, from 33B to 118B parameters, covering coding. Private OpenAI-compatible endpoint, European GPUs, billed per GPU-hour.
| Model | Type | Params | Context | License |
|---|---|---|---|---|
Laguna-S-2.1MoE poolside | Coding | 118B | 1M | OpenMDW 1.1 |
| poolside | Coding | 33B | 256K | OpenMDW 1.1 |
Specs from Hugging Face, synced 2026-10-27. Machine-readable version: https://sference.com/models/poolside.md
FAQ
Which poolside models can I deploy on sference?
2 today, most requested first: Laguna-S-2.1 and Laguna-XS-2.1. Any other poolside checkpoint or a fine-tune of one can be requested with the form on this page.
How many GPUs do poolside models need?
It depends on the model: the lineup runs from 33B to 118B parameters. Each model page lists the checkpoint size and the minimum footprint on 80 GB and 141 GB GPUs. You don't pick hardware on sference: you choose a performance tier and we size the deployment.
Can I use poolside models commercially?
2 of the 2 listed models are under licenses that allow commercial use (OpenMDW 1.1 across the lineup). Each model page summarizes its license and links the full text.
How is a dedicated deployment priced?
Per GPU-hour on a monthly commitment, sized to your throughput and latency targets.
Request a poolside model
Tell us which poolside model and roughly how much traffic you expect. Fine-tunes of these models work the same way.
- 01We size it
A performance tier, the capacity behind it, and a quote for your volume.
- 02We benchmark it
Bring one workload with a sample of real traffic; we come back with latency and throughput numbers.
- 03It goes live
We provision the deployment. You call it with the same API and model id as before.