This doesn’t stop any company spinning it up for their internal use. It only bites if you try to resell it.
Right, but given how hard it is to host it in the first place, few companies will do that.
A rack capable of serving this costs around $1M or so, well within the reach of even many mid-sized enterprises.
Right, but then you also have to hire people that can maintain & configure that rack, think about how many requests you'll be able to serve with that one rack in the first place (maybe you'll need two? or three?), etc.
There are very few companies in the world where this would be a straightforward decision.
It's not impossible that the separate agreement in question imposes light limitations.
I think one of the initial reasons why otherwise open source models started with the limitations on model-as-a-service use cases was because of quantised or entirely different models being served as the model in question on open router, and they needed a legal method to limit that. It might just be that, thought it might also be the direct opposite, hard to know.
> It's not impossible that the separate agreement in question imposes light limitations.
It's not impossible a priori but a posteriori it's just not the case.
Source: We've been wanting to host Kimi K3.x at work (and serve it to our clients) and got in touch with Moonshot.
> If the Licensee or any of its affiliates operates a Model as a Service business, and the aggregate revenue of the Licensee and its affiliates exceeds 20 million US dollars (or the equivalent in other currencies) in total over any consecutive 12 months, the Licensee must enter into a separate agreement with Moonshot AI before using the Software or its derivative works for any commercial purpose.
[0]: https://huggingface.co/moonshotai/Kimi-K3.1-Pro/blob/main/LI...