As a public community project the KitOps roadmap is always open to feedback. If you think a feature lower in the list is more important, or feel that we've missed an important feature please:
- Open an issue in the repo
- Tell us in the KitOps Discord channel
- Send us a message on X / Twitter
🛳️ = Shipped
🚗 = In-progress
📅 = Planned
💡 = Idea (please provide feedback)
- Change
kit devimplementation to use Llamafile 📅 - Export Llamafile from ModelKit 📅
- Generate example code as the parameters and prompts are entered 💡
- A way to see JSON communicated between the server and responses 💡
- Hide the parameters that are not frequently changed 💡
- Add
kit devcommand to Kit CLI on Windows 💡 - Add
kit devcommand to Kit CLI on Linux 💡
- Creating a ModelKit from a Jupyter Notebook 📅
Users want to be able to deploy their models through existing CI/CD/CT pipelines. Since KitOps doesn't know the details of a user's deployment pipeline or process we will unpack a ModelKit into an appropriate directory structure for one of several deployment targets.
Users want to be able to get the Kit CLI from locations like Brew, Choco, and Conda.
- Add support for Brew 🚗
- Create a Kit Python library 💡
- Add support for Choco 💡
- Add support for Conda 💡
This feature will come in two parts: build attestation and self-attestation. Build attestations will be done by KitOps itself, adding a SLSA attestation about how the ModelKit was built. ModelKit creators can add an optional attestation for specific assets in the ModelKit, or the whole ModelKit. Users can include any 3rd party attestation Verification Summary Attestation (VSA). Additional attestations could be added as predicates. Attestation would be included as a separate layer in the ModelKit.
- Add provenance for KitOps ModelKit builds 💡
- Add CLI warnings if attestation was expected and not found 💡
Users can optionally sign their ModelKit using something like Cosign in order to add an extra layer of security to their packaging.
- Add docs on signing and verifying to docs 🛳️