Transcript

That means that you can build one way of talking to all the models instead of having to have five different software stacks, one for each, and then try and unify the things later by yourself. Exactly. And it's, you know, it doesn't scale when you need to replace one by, you know, by the new fancy model. So, you know, I think it's essential to have kind of this abstraction layer, so we have all the models and you can swap with one line of code. You can swap model, you know, A to B, see how it performs, see how it sticks, and, uh, be able not to get locked into, uh, you know, uh, to a single SDK or API mechanisms. I think it's, it's... And that's why we, you know, made it an open architecture so it's easy to, uh, to move on. I don't believe in, in getting people locked into, uh, your product. I think if you bring value, you should be there. If you don't, you shouldn't. So having kind of an open architecture and open framework with all the models, and you can bring your own models, you can bring, you know, commercial models, and we release models same day as they're released. So it's a great way for all the teams to, uh, to move fast