Custom Models
Bring your own weights: fine-tunes and distilled open models run on the same API, infrastructure, and audit trail as the catalog.
Custom Models
Upload your own Hugging Face weights and serve them through the same OpenAI-compatible API as the catalog. Fine-tunes and distilled open-weight models run on the same infrastructure, pinned versions, and audit trail as catalog models. vLLM/SGLang models work out of the box, and we stand up custom runtimes for models that need them.
Custom model hosting is arranged per customer as part of an enterprise agreement. Talk to us with the model and your expected volume.
Requested, then provisioned
Custom models are requested from the console and provisioned by Sference. A model moves from pending to available once it is ready to serve; you call it by the same model id you registered.
Register a model
- In the console, open Custom Models and choose Add model.
- Enter the Hugging Face model id (for example
your-org/your-finetune) and its architecture (the base family it derives from, e.g. Qwen or Llama). - If the repository is private, mark it as such so we can arrange access.
- Submit. The model appears with status pending while we provision it, then flips to available.
Access to private repos
For a private Hugging Face repository, grant Sference read access (or share a scoped token) so the weights can be pulled. Public repositories need no extra step.
Call your model
Once the model is available, use it exactly like a catalog model: same endpoints, same request shape, same pinned-version guarantees. Reference it by the model id you registered:
sference responses create \
--model "your-org/your-finetune" \
--content "Summarize this contract in three bullet points." \
--waitYou can also open it in the playground from the console, or route production traffic to it through a dedicated deployment.
Billing
Hosting and per-token rates for custom models are agreed per customer as part of an enterprise agreement, not published as a rate card. Pricing depends on the model, the hardware it needs, and your volume. Every request carries the same request-level logging and audit trail as catalog traffic.