Mike Krejci

You know, that is a possible way.

I don't think it makes sense for this client and I don't think it's a good decision.

And, and we, we all kind of came to agreement that, Oh yeah, that probably isn't the right way to go maybe in a few years, but not, not today, not in this system.

Um, we have, uh, we have a larger enterprise client that has requested, um, that their standard room be written in, uh,

In a traditional language, rather than AV in in or through an AV you know WYSIWYG software.

It was partially requested by their security and it team, so they could be able to.

modify the code.

They could monitor the code, look for security vulnerabilities.

They could modify it.

They could treat it like traditional software running on appliances.

That is a specific request of a customer.

And we kind of laid out some of the gotchas in that conversation to ensure we can do this.

However, your normal field team you're used to

is not going to be able to make an instant change like you're accustomed to.

We've got a corp that will support this, that will write it and modify it, and we'll make sure it's solid when we get it.

But if you want to do something a little bit quirky and a little bit odd, we're not going to change this and do this as quick as we would with

you know, the traditional AV methods.

Are you okay with that?

And they said, yep, we are okay with that because of the other things we get out of it.

And, you know, that's been a successful endeavor for us.