# Deploy dots.ocr on dedicated GPUs

dots.ocr by dots.ocr, deployable on sference as a dedicated deployment: reserved GPU capacity, private endpoint, European GPUs, billed per GPU-hour on monthly commitments. Request it at https://sference.com/models/dots-studio/dots.ocr.

## Specs

- Hugging Face: https://huggingface.co/dots-studio/dots.ocr
- Category: OCR & documents
- Parameters: 3.0B
- Architecture: Dense
- Context: 128K tokens
- Published precision: BF16
- Checkpoint size: 6.1 GB
- Minimum footprint: 1 GPU (80 GB) or 1 GPU (141 GB) to load the weights; more for long contexts and concurrency
- License: MIT (Commercial use allowed)

## FAQ

### Can I run dots.ocr on a dedicated deployment in Europe?

Yes. sference deploys dots.ocr on GPU capacity reserved for you, behind a private endpoint, with every request processed on European GPUs and logged in your audit trail. Tell us your expected volume and latency targets with the form on this page and we come back with a sizing and a quote.

### How many GPUs does dots.ocr need?

The published checkpoint is about 6.1 GB (BF16), so loading it takes at least 1 GPU with 80 GB of memory each, or 1 GPU with 141 GB each. Long contexts and high concurrency need more for the KV cache; quantization needs less. You don't pick hardware on sference: you choose a performance tier and we size the deployment.

### Is dots.ocr licensed for commercial use?

dots.ocr is published under the MIT license. Permissive: commercial use, modification, and private deployment allowed; keep the copyright notice.

### How is a dedicated deployment priced?

Per GPU-hour on a monthly commitment, sized to your throughput and latency targets.

Facts from Hugging Face, synced 2026-10-27. All deployable models: https://sference.com/dedicated.md