Model wishlist
Request a model
kLLM seals a model only when its architecture has a validated implementation; unsupported architectures are not sealed on the fly. Models that are not yet supported are collected on a public wishlist on GitHub, and the team adds them over time.
The wishlist
How requests are handled
Each architecture needs its own sealing implementation, checked by a float64 exactness test, before any model built on it can be sealed. The wishlist decides which architectures come next.
- 01
Search first
Search the open model requests on GitHub. Add a reaction to an existing request instead of opening a duplicate.
- 02
Open a request
The Model request issue form asks for the model identifier, the upstream link, the modality, the architecture, the preferred engine and the reason for priority.
- 03
Prioritization
The team prioritizes requests by demand and by the work each architecture requires. A request is not a commitment to support a model or to a date.
From the command line
kllm request prints the address of a new request with the model identifier filled in. Open the address in a browser, complete the form and submit it; the command itself sends nothing. When kllm search finds no library model, it prints the matching kllm request command.
0.2 lineThese commands are on the main branch and are not yet part of a tagged release.
# Print a prefilled model request address
$ kllm request mistralai/Mistral-7B-Instruct-v0.3
# Search the library first
$ kllm search mistral
Supported today
Architectures with validated sealing
Before requesting a model, check whether its architecture is already supported. Plain serving, without a key, covers every model the chosen engine supports.
Contribute
Add an architecture
To add support for an architecture, follow the guide for adding a model family. Every new family requires a float64 exactness test. Reference the corresponding request issue in the pull request.
Enterprise
Day-zero model support
Customers of kLLM Enterprise can obtain support for newly released models from the day of their release, under a customer key.