That's a good one. Obviously, you need a working business model, just start something. There are projects that start by just being a cool piece of software attracting a lot of GitHub stars... but I would hope that you'd have some sort of an idea of how you're going to monetize that in the end.
We, for instance, use an open core model. What we have actually in the open source side is that we have this open source automation stack that's built on Python, the bottom layer of the stack is Python. Then we have robot framework, and a lot of automation libraries on top of that, that you can use to integrate different kinds of applications. Then we have a configuration format on top of that, that defines that software, that sort of that software robot, as we call it, that piece of automation. And then we have a tool chain on top of that to put it all together and make it a sort of a nice automation project that you can manipulate and configure and run it anywhere. So that's the really the open source side.
Then on top of that, well, obviously, we do support developer tools as well, that's just another thing. But on top of that is the operational layer that you will need to, to really use that automation stack in your kind of enterprise company setting. And we realised early on when we started to apply Robo Framework into RPA that, sure, it can automate things that you can run locally. But when you want to actually sort of operate that automation in a company setting, you need scheduling you need to be able to run it remotely on local networks, and so forth. So we started applying, like CI and CD tooling, a bit basic stuff like Jenkins on trying to see that could we actually operate this with CI tools. And it turned out, that was a huge hassle. And it wasn't really meant for that. So we figured out that, hey, we should create a platform that can be used to run this automation code anywhere in the cloud, inside containers, inside virtual machines, on local ,on prem machines, and anywhere that you need to run when you're running that in a company setting. So that's the proprietary crust that we built on top of that open core of the automation stack.
That's a pretty popular model right now, works well for many companies. For infrastructure companies, you have the basic hosting model, so you have like, database software, like MongoDB, or Timescale DB, you obviously have the hosting. There you have, you know, the scary proposition that Amazon is gonna copy you, and just host your open source database for you. And that's really scary. So I see that those companies are starting to apply a new licencing model. So it's open source, but not open source for for hosting. So they kind of are blocking those cloud vendors from hosting it for them. So that's obviously if you have that kind of infrastructure platform thing, that's, that's a good way to go. But be mindful of the, you know, big three cloud players competing against you. That would not be a nice feeling, probably to have.
And then the kind of the, in my view, the legacy open source model, which is, you know, Red Hat, you know, selling support and services. And I think that this false understanding in the world that open source equals to support and services. And that's just really not the case. And they are much more exciting business models, and pricing models and opportunities to actually monetize open source software. And that's mainly because of kind of vast cloud adoption in the world.