Adam Stacoviak

You know, have you all explored or have you even thought about yet if you went that route, how you can license it and still sell licenses of it?

where you can provide essentially a source available version to the open source world that, hey, if you're in a home lab environment like you do now, totally free, this license applies to you.

But if you're in production or you're in an enterprise or you're in this kind of business class, the source is available.

Contributions are not necessarily what you're trying to achieve, but you do want to have your code out there so people can see it.

But then you're also saying, here's a license to you, or here's a license per node.

You want to have an Aperture instance in your stack.

You wouldn't have multiple.

I don't see why you'd need multiple.

Maybe just one is fine.

But you got maybe a per-user license or a per-node license.

You're telling me, I don't know how it actually permeates into the network, but have you explored that world yet?

You've got a home lab, David, of course.

I mean, that's where we bake all of our ideas first.

We do them in the home lab, we figure out how it works, we nerd out, we learn, we explore, and then we take it to wherever we're going.

That's kind of cool stuff.

So it makes sense in this case then to cloud first, not because you're not for

self-hosting because you need to maintain velocity.

And the only way you can really maintain reliable velocity in this case is to have your own instances.

But in the future, if someone says, hey, you know what?

I love this.