ROADMAP.md

KitOps Roadmap

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

In-Progress

• Create a Homebrew cask for KitOps
• Create Python SDK for KitOps
• Improve handling of TAR files generated by Kit
• Demo: using ModelKits with MLFlow
• Convert a model from Hugging Face to ModelKit

Recently Completed

See the full changelog from 0.4 and 0.34

• Demo: using ModelKits with Jupyter Notebooks
• Add Windows & Linux for kit dev command
• Add --filter option to kit info command
• Deploy ModelKits as containers
• Added parameters field to datasets and code
• Enhanced proxy support

Roadmap Themes

UX Improvements

• Pack and convert models directly from Hugging Face

Deployment

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.

• Enhance unpack for deployment-specific directory structures

CLI Distribution

Users want to be able to get the Kit CLI from locations like Brew, Choco, and Conda.

• Install with Brew
• Use KitOps with our Python SDK
• Add support for Choco
• Add support for Conda

Attestation

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

Signing

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

Kit Dev

• Kit Dev: Generate example code as the parameters and prompts are entered
• Kit Dev: A way to see JSON communicated between the server and responses
• Kit Dev: Hide parameters that are not frequently changed