Auvik vs Domotz (EP 817)

[Uncle Marv]
Hello friends, Uncle Marv here with a special edition of the IT Business Podcast. We are here on a Wednesday afternoon to do something, ah, it's going to be a little bit new for people and hope that it works out and it turns out to be a good thing. And today we are doing the first of a three-part series that I am calling Auvik versus Domotz.

And I'll explain that in just a little bit, but for people that may have been directed here and you don't know what this is, the IT Business Podcast is a show for solution providers. So IT professionals, managed service providers, where we talk about everything in the channel. We talk about how to run your business.

We talk about how to deal with vendors. We talk with vendors as they try to share us the tools and things that can help us maintain our customers and do all the things that we need to do to make some money. So that's the show in a nutshell.

Today's show is specifically Auvik versus Domotz and it's basically the idea that there has always been a thing where we need to do network monitoring. We have so many managed devices on our networks and, you know, we need to be able to map the network. We need to have alerts when new things pop on the networks and the two biggest names that I know of, and there may be others that people will say, well, why aren't they in there?

Well, these are the two that I know and are probably the most trusted among the channel in the sense and, you know, Auvik is known for its lightning fast deployment and getting set up pretty quickly, user friendly interface, network mapping, and Domotz in the same manner is also known for its fast setup, its intuitive interface, flexibility, and integrations that go beyond network devices. So the idea is which is better for you as a provider to use with your clients. Now normally when I talk either about vendors or have vendors on the show, we try to ask all the pertinent questions.

We let the vendors do their dog and pony show and then of course there's always what happens behind the scenes where, you know, MSPs will talk about the things that they don't do and ask the hard questions. Doing a show like this where I asked two vendors, I want you guys to come on a show together and let's do a battle royale and no, vendors don't want to do that. They don't want, you know, to hear another vendor talk bad about them on the show.

They don't want to, you know, have me as the host talk bad about them. So this took some time to put together and I actually have asked other vendors to do this where we just, hey, I want vendors to come on the show and let's just do a side by side comparison. Let's do a pitch.

It's not going to be a battle royale. It's not going to be, you know, mano y mano. And Auvik and Domotz were the first two to do this and it took, still took a little time because we had to lay down some ground rules and of course one of the things that you'll notice today, I have two MSPs coming on, one for each product, one for Auvik, one for Domotz and none of these are people you've seen on the show before if you're a regular listener or watcher.

They're not my friends. So these are not people that I could have pulled over to the side and said, hey, we're going to have this show up. Will you talk about this?

They're not going to be nice to me. They're not going to do all that stuff. These are two vendors I met probably about a month ago and it was just a real quick, nice to meet you.

Here's what we've got, you know, planned for the show. Would you be willing to do this? They said yes.

So that was the first thing is I wanted to get MSPs on the show that had not been on before who I did not know. So that was one thing that was able to happen. Thank you to the vendors for doing that.

The format today is going to be just simply a question and answer where I get to do demos that may come later in the second and third show, which will be the vendor response shows. So somebody from Auvik and somebody Domotz will come on afterwards and just do a little recap. They may say what they liked, what they heard, and we may do some demos then.

But today it's just going to be me getting an idea of what made you decide on the product that you chose. What do you like? And yeah, I'm going to ask at least one question about, you know, what do you wish it would do that it doesn't do now?

Each MSP is going to get the same questions and hopefully I'm going to phrase them the same way so that there's no bias. There's not going to be a favoritism that you see me show one or the other in the way that I ask the questions or the way that, you know, I interpret their answers. I'm going to try not to respond.

It's going to be basically blah, blah, bland as can be so that I can let you, the listener, you the viewer, make your own decision about what each says. So it's not the public showdown that I think a lot of you were looking at, but I think it is something where it will, you know, be a little bit of a head-to-head in terms of how each responds to the questions and, you know, of course afterwards we'll give you links to go and do a sign-up for each so that you can do that or you can wait until the vendor response shows, which should be in about one to two weeks, where we have them come on and they may do a little bit of a demo while they're here and all of that. So I did want to give you an idea of this is how it's set up. This is what it is.

It is not the typical dog and pony show and it is not the battle royale that you may think it is. I've tried to say that from the very beginning. Anybody that I've talked to, it was hard to get two vendors on the same show to do this head-to-head battle and so I want to thank Auvik and Domotz for doing that.

Of course, you know, basically if you do not know the products, Auvik and Domotz are cloud-based platforms that, you know, are set to monitor devices. They're both designed for MSPs, IT professionals. They do multi-tenant management.

They provide real-time monitoring device discovery. There is a lot of stuff I can say that are similar and not similar, but I'm going to not do that and allow the MSPs that I have to do that for us. And we're going to do a little bit of a coin flip as to how we start.

So I created a wheel of names and we are going to spin and that will determine which MSP speaks first and which MSP speaks second. So you see the wheel of names. If you are watching the live show, if you are listening to this by audio after the fact, you will hear the spin and you will hear the name chosen.

So here we go. That is the spin.

Domotz.

[Uncle Marv]
And Domotz is going to be going first. So get that off the screen there and get set up for our speaker here. And here we go.

All right. Here we are with Robinson Roca. He is from Helient Technologies and has been in our industry for quite a while.

He's been with Helient since 2019. But Robinson, let me first say welcome to the show. Thank you for doing this.

Thank you for having me. I appreciate it. All right.

And just for a little bit of perspective, why don't you tell us about Helient Technologies?

[Robinson Roca]
Yeah, sure. We are an MSP VAR, which is a value-added reseller, have been around for almost 13 years, going on 13 years, with a practice that provides MSP services, management and support, as well as value-added reselling, such as Cisco's deployments, networking infrastructure, and a major Azure reseller and implementer for many, many clients in various verticals.

[Uncle Marv]
Okay. So is that kind of what sets your MSP apart a little bit, that you focus heavily into the cloud architecture?

[Robinson Roca]
That's right. So it's a mixture of being able to take a customer who's on-prem to cloud or taking a customer who's on-prem to a hybrid deployment and being able to provide that service as a full complement of technologies without having to go to various different vendors to do one thing. Everything from cabling to full-blown Azure deployments.

[Uncle Marv]
Very nice. Very nice. And for a little bit of demographics about the company, I know you said you've been around since 2013, but size of the company, typical client size, number of endpoints, that sort of stuff?

[Robinson Roca]
Yeah, we're growing. We're growing. I think at the moment, we're now at 90, no, I think we're now at 110 employees.

So we're growing. And our verticals are typically within... We started in legal, and a few years ago have expanded into healthcare, amusement parks, and several other verticals that you wouldn't expect.

But we've kind of expanded to areas that are favorable to business growth, customers that are really looking to move into cloud-based deployments. And we're finding that to be a very lucrative and essential part of our business.

[Uncle Marv]
Okay. All right. Let's go ahead and get into the questions here.

And I'm going to read these the same for both of you. And let's start with, what specific challenges in the business led you guys to Auvik? Oh, yeah.

[Robinson Roca]
This is great. It's a good question. One of the holes that Auvik fills is the ability to provide an easy way of showing a customer what they have and what's wrong.

Today, it's very difficult to find a tool that allows a customer direct access into the infrastructure, into the health of their infrastructure, without having to have full-blown training. Okay. I can show a customer an Auvik interface, and they can very easily find information they want just by clicking around and finding what they need.

But the beauty behind it is the power that it offers that customer. When properly deployed, we can give them information that they normally would not have at their fingertips, how much traffic is going to a certain destination, and what that traffic is. That's all integral to what we're offering, simplicity, but power.

[Uncle Marv]
All right. Out of all of that, what feature do you find most valuable and why?

[Robinson Roca]
Hmm. I would have to say it'd be the NetFlow capabilities within Auvik. NetFlow is key because when a customer says, my bandwidth is being eaten up, and I don't know why, you want to be able to tell them why, right?

So instead of having to dive into a piece of equipment and begin a large analysis of where the traffic came from and where it went, I can very easily open up Auvik, go right into the NetFlow section that provides that data. Where did the traffic go? Where did the traffic come from?

How long was that traffic flow initiated for, and how much bandwidth overall did it take up? In my opinion, that's a powerful area. Besides Syslog, besides the fact that I can create alerts that are customized to my particular need, I think that is extremely powerful.

Okay.

[Uncle Marv]
Were there any particular integrations that helped influence your decision?

[Robinson Roca]
Oh, yeah. So when I brought Auvik into my practice at Helient, I needed to make sure that I had a tool that allowed me to integrate with what we were already doing. And you'll find that MSPs leverage tools that are sometimes disparate.

And if we have an opportunity to tie them together in a certain way, we try to jump on that. So in this case, Auvik integrates with Autotask, which is a PSA, it's our ticketing system. So every time an alert goes off, we have it set so that certain thresholds, when they meet that threshold, a ticket's created.

That ticket from our PSA is assigned to an engineer, and immediately you have an engineer diving into the particular problem that needs to get resolved. But the best part about it is the system will automatically close the ticket if it closes within a certain timeframe, or if the error clears within a certain timeframe. So now I can reduce the level of stress upon my team, because if a ticket opens and three minutes later, the alert clears, the ticket's closed.

So that really does come in handy.

[Uncle Marv]
Nice. Let's move to, hopefully this is an easy one. How easy was the initial setup process?

[Robinson Roca]
You know, I've been using Auvik for quite some time, probably one year after they actually came out. But over the years, I've watched it change. It went from a pretty easy deployment, double-click and executable, and done, or run a command line.

Now there's an actual interface, and whenever I light up a new customer into Auvik, it's a friendly interface that I can have any of my junior engineers execute and get done to get that customer onboarded. It's significantly easy, it's ridiculously simple, and I look forward to training my younger engineers and jumping in and getting it started.

[Uncle Marv]
All right. How has the platform improved your ability to manage multi-site networks or distributed infrastructure?

[Robinson Roca]
This is key. This is really, really important. I'll tell you; I have customers that have multiple locations, multiple offices.

And I may have a customer that has two offices, a headquarters and a branch. I have customers that are 19 offices and a headquarters and 18 branches. And the key piece of this is I can create a top level for that customer and then add every one of their branches underneath that top level.

But what I love most is their new capability of being able to run a collector on a Raspberry Pi. And that enables me to deploy collectors in more places, gathering more local information than having to run it on a virtual machine that may only be at headquarters. Now I can have data collection in branches in multiple places, powered and managed in ways that you may not have normally been able to do if it was a traditional VM or physical server.

[Uncle Marv]
Okay. Let's see. Has Auvik helped you reduce downtime or troubleshoot issues more effectively?

[Robinson Roca]
Yeah. We used to use a different tool for monitoring prior to Auvik, and it was prone to a lot of false alerts, a lot of false errors requiring the team to go running and taking care of certain things. Auvik is intelligent.

If you've got three IP addresses on a switch and one of those IP addresses goes down, well, the whole device is not down, just that IP address. Auvik's intelligent enough to tell the device is up, but that IP address is down and appropriately give me the right alert. That's key because previously without Auvik, it was deemed whatever interface was being pinged or monitored was down, then the whole device was down.

Intelligence is key, and Auvik has it.

[Uncle Marv]
Well, you may have already answered this, but I'm going to ask the question anyway. Can you share an example of a time when real-time alerts from Auvik helped prevent or resolve a critical issue?

[Robinson Roca]
Yeah. We've had an instance where a customer had saturation in their network. They used their internet connectivity for basic internet connectivity but also were doing data replication to the cloud.

They were unable to tell what was eating up all their bandwidth. Jumped into Auvik, pulled out Auvik Flow, looked at the data that was being sent to source and destination, and immediately jumped into, it looks like it's your replication from one of your Haiku servers that's replicating up into Azure and eating up all your bandwidth. I think we need to scale down that replication, and that should resolve the problem.

And that was an immediate answer. Didn't have to spend time digging in. It was all in Auvik.

It took me all of three to four minutes to get to the right window and maybe five minutes to really diagnose the problem.

[Uncle Marv]
Okay. Do your clients actually know that you use Auvik?

[Robinson Roca]
Yes, yes. We actually provide Auvik access directly to our clients. The great thing about Auvik is being able to provide a customer who doesn't know how to use it direct access and really not have to provide any training.

Auvik has its own online available education sites that I can just give a customer if they have questions. So it's a really easy thing to deploy and offer to customers. Okay.

[Uncle Marv]
Now, how do they perceive the value or the benefits of Auvik?

[Robinson Roca]
You know, I have customers that have traditional, for example, Cisco Catalyst infrastructure, where you have to have CLI access to really do anything. And they're not engineers. They don't have the ability to jump into a CLI and know what to do.

Giving them an Auvik interface lets them see what they care about. What does my bandwidth look like? Is the port on that server down or is it up?

Can I see if an alert was triggered this morning when I woke up and then went away? Everything they need is at their fingertips. So it has been extremely powerful and empowering to our customers to have a GUI that they can see and make sense out of the black magic that happens in their data room.

[Uncle Marv]
All right. And of course, I do have to ask one question that might seem like a little ding. If you could add or improve one feature in Auvik, what would it be and why?

[Robinson Roca]
I think it's on the roadmap. There is a syslog capability within Auvik, where Auvik can collect logging from firewalls or switches and give your insight into what's happening. So if the device reboots and you lose the onboard logs, you have logs built into the collector.

What I would love to see in the future is direct alerting based on ingested logs. So if a log says memory is high, which I think there's already a system in place for memory, but something that triggers an alert based on the words within the syslog to be able to create an alert based on that particular syslog entry.

[Uncle Marv]
All right. Well, thank you very much. I tried to ask these questions as generic as possible and not jump in with follow-ups.

But here's one question I'll ask. If there was another MSP that was considering a network monitoring solution, how would you describe your experience with Auvik to them?

[Robinson Roca]
Their support's amazing. The sales team and the sales enablement is very, very helpful. Onboarding and getting Auvik in place is ridiculously easy.

It's almost a no-brainer to bring Auvik online. It becomes beneficial over time to add more and more clients into the Auvik deployment because your overall costs start to come down as your endpoint counts start to go up. Not to mention the billable devices versus non-billable devices is amazing.

What you get and not have to pay for, such as monitoring IP phones or printers, is indispensable. I have customers where they want to know that their printer is offline, online, or it doesn't have paper or is out of ink and not have to pay for it. That's a positive on my side.

[Uncle Marv]
Okay. So, Robinson, thank you. We are going to have your contact information in the show notes for the podcast in the description for the video.

But where can listeners find out more information about Helient or about you?

[Robinson Roca]
Sure. You can go to www.heliant.com to get information on our company and our site and what we offer. You can always reach me at LinkedIn.

I'm Robinson. Roca at LinkedIn, so I'm easy to find. I post all the time, so feel free to look for me. All right.

[Uncle Marv]
Robinson, thank you very much for doing this, and we'll chat again soon.

[Robinson Roca]
Thank you. Have a great one.

[Uncle Marv]
All right. So, a couple of housekeeping things. Somebody sent me a message on my phone there.

No, my light isn't on. Sorry about that, but we're rolling with it. And two, yeah, I screwed up.

Domos was supposed to go first, and I had the wrong signage. And I apologize, and I thank Robinson for rolling with it, and I trust that our next MSP will do the same. That's what happens when you do things live, folks.

And I'm not even going to blame the introduction card on anybody. It's my show, my name. So, too bad.

So, yeah, so that was Auvik and Robinson Roca. And now we are going to get set up for Domos. And obviously his card is not going to be correct.

But let's continue on here with part two of Auvik versus Domos. And joining us to talk about Domos, I have Darcy Wilson, the Vice President of Operations and Director of Service Delivery at 365 Technologies. Darcy, first of all, welcome to the show, and thank you for doing this.

[Darcy Wilson]
Thank you so much. It's my pleasure.

[Uncle Marv]
All right. So, tell us first about you, your history, background, and about 365 Technologies.

[Darcy Wilson]
Yeah, as you mentioned, I'm the Vice President of Operations here at 365. I've been in the IT management and leadership business for about 25 years now. And I really value my ability to deliver service to clients and show them the value that we can give them by taking away the trouble that they would normally have to worry about themselves.

I find that really fulfilling.

[Uncle Marv]
All right. And I guess one of the questions that I like to ask is, what do you think kind of sets 365 Technologies apart from other service providers?

[Darcy Wilson]
Yeah, well, I think the big thing is our personal focus and the fact that we're also a small business in Winnipeg. So, we provide fully managed services, help desk support, security monitoring, and cyber security. But we take that personal approach.

We understand the struggles that small businesses have. We share some of those struggles, and that allows us to really take that strong personal approach to solving their problems.

[Uncle Marv]
All right. You mentioned that you're also a small business. So, what about the demographics of both your business as well as the bulk of your customers?

[Darcy Wilson]
Yeah. So, we serve a variety of industries. We're focused mostly here in Winnipeg, Manitoba, but also throughout Western Canada.

We've got clients in industries from finance, construction, retail, and healthcare. There's a variety. But I think the common thing is that they want to have worry-free IT.

That's the term we use. And they expect us to take care of all their IT problems and shift that responsibility away from them having to worry about it.

[Uncle Marv]
Okay. All right. So, let's get into the questions here.

First, what specific challenges in the business led you to Domos?

[Darcy Wilson]
Yeah. So, the biggest factor was that we really had a requirement to find a feature-rich networking solution, monitoring solution that was intuitive and allowed us to gain actionable insights that any technician in our company would be able to understand. And we really needed something that would also allow us to dynamically update our documentation.

So, those were the two biggest factors.

[Uncle Marv]
Which feature do you find most valuable in Domos and why?

[Darcy Wilson]
Yeah. That's an easy one. It's reverse proxy without question.

Reverse proxy give us the ability to securely connect to our client networks, their network devices without opening ports or adding any security risk to the environment.

[Uncle Marv]
Okay. Were there any particular integrations that influenced your decision?

[Darcy Wilson]
Yeah. So, as I mentioned earlier, one of the big factors for us was dynamically updating our documentation around our client environment. So, that integration into IT Glue, which is our document platform of choice, that was a big one for us.

[Uncle Marv]
All right. How easy was the initial setup?

[Darcy Wilson]
It was super simple. And that's what we were looking for, is a solution that didn't take a lot of investment and time. And it continues to be that way.

We can deploy and set up a new client location and a probe and start having actionable intelligence within a matter of an hour or two. And we really, really appreciate that.

[Uncle Marv]
Okay. You may have hinted at this, but how has the platform improved your ability to manage multi-site networks or distributed infrastructure?

[Darcy Wilson]
Yeah. So, that was a big factor for us. And we do have some multi-site clients.

So, the biggest thing for us is it allows us to have that central dashboard, that single pane of glass that MSPs look for, where we can see all of our clients and all of our locations in one place. It allows us to monitor their topology and look at performance of their network in real time across all sites. So, it's also allowed us, as I said earlier, to update documentation quickly and easily.

So, as network devices change throughout whatever location that we're referring to, that information is automatically documented and our technicians know about it in real time. So, it's a big thing for us.

[Uncle Marv]
Great. Has Domotz helped you reduce downtime or troubleshoot issues more effectively?

[Darcy Wilson]
Absolutely. The combination of dashboards and alerts make it really easy for us to proactively identify problems. Our techs can look at the history of a device or a specific interface on the device, and they'll oftentimes be able to quickly identify the source of a problem without an on-site visit, and that's another key for us as an MSP.

It's really critical.

[Uncle Marv]
Okay. So, I'm asking a little different twist on this. Can you share an example of a time when real-time alerts from Domotz’s help prevent or resolve a critical issue?

[Darcy Wilson]
Yeah. So, I think the best way for me to answer that is, again, refer to the fact that Domotz was the first time we were really able to effectively identify problems proactively and not have to rely on a symptom or a client calling about a problem. So, we've seen a lot, and some of our biggest clients, we own their entire IT department from start to finish.

There are no IT resources, and so they rely on us monitoring the health of their network in real time, and any outages cause them significant financial impact. So, being able to identify a problem and solve it before they even know about it is a game-changer for us.

[Uncle Marv]
Okay. Nothing that really sticks out as, like, the crude-to-draw of…

[Darcy Wilson]
Well, any time potentially we can help our clients save money by reducing downtime is an opportunity to celebrate, and I don't know of any particular one that stands out, but we do see it, and we see the positive effects of having the tool in place.

[Uncle Marv]
Okay. Do your clients know about Domotz?

[Darcy Wilson]
In general, they don't. They just see it as part of our toolkit providing our service and being able to know about the health of their environment. Having said that, we do have some co-managed environments where there are on-site resources or the client has IT resources of their own, and in those cases, they have access to Domotz, and they're able to monitor the devices themselves, and we can collaborate on the health of their network.

[Uncle Marv]
All right, and so for the people that you do have it in place, do they see or how do they see the perceived benefits?

[Darcy Wilson]
Yeah, well, again, they just expect that by hiring us to be worry-free IT, that the tool is just part of our entire package of service delivery that helps keep the network healthy and maintain their business. So I don't think that they necessarily see a single benefit specifically from Domotz, but they do expect that it's part of the best possible service that we can provide and the best collection of tools that we can use to provide that service.

[Uncle Marv]
All right, let's see how honest you are with this one. If you could add or improve one feature in Domotz, what would it be and why?

[Darcy Wilson]
Yeah, and that's a tough one. I think it goes back to that multi-site environment that we talked about. So it allows us to see today individual locations.

What would be great for me is being able to see all of those locations rolled up in a single pane of glass per client so that we can see all of the alerts, the health of all of the sites within a client in one single pane of glass. So I think if there was one area, that would probably be it.

[Uncle Marv]
All right, all right, Darcy, thank you very much. Here's a closing question or two. If another MSP were considering a network monitoring solution, how would you describe your experience with Domotz to them?

[Darcy Wilson]
It's been positive right from day one. I do have to say that's something that sets Domotz apart in this industry is that I do see them as a true partner. They're willing to listen to my concerns.

And I believe that this is not unique to us. I believe other Domotz users have the same experience. The team is willing to listen to our comments, our feedback, and take direct action, at least in my case.

And I really value that. I wish more partners and vendors in the channel sort of felt the same way. And it would be really beneficial to us if all of our partners felt the same way.

[Uncle Marv]
All right, so I'm sure some people are going to see this and want to reach out. So where can our audience find more information about 365 Technologies or connect with you?

[Darcy Wilson]
Sure, so the best way is our website, which is 365tech.ca or search us on LinkedIn at 365 Technologies.

[Uncle Marv]
All right, Darcy Wilson, 365 Technologies, thank you for doing this, sir. And we look forward to talking to you again down the road.

[Darcy Wilson]
Thanks so much. It was my pleasure.

[Uncle Marv]
All right; there we go. That is the conclusion of part one of our three-part series, Auvik versus Domotz. And again, thank you, folks, for putting up with the mistakes that we did with the name cards and doing them out of order.

But as most of you know, I don't edit, so it is what it is. I'll send my apologies to both Auvik and Domotz specifically, because I'm sure that they would have wanted better from me. But so for the most part, yeah, you can saw we kind of threw some softballs there and wanted to get the similar features between the two.

I do want to obviously let you know that, you know, at any time you can go to each and do a demo. I put links in the chat boxes. If you're watching on the YouTube, it's there.

I don't know if it's in LinkedIn, but we'll get it over there. And it will definitely be in the show notes of the podcast when you go and download it and listen there. So for Auvik, you'll go to itbusinesspodcast.com slash Auvik. And for Domotz, itbusinesspodcast.com slash Domotz, as you see on the screen there or in the show notes. And that's just going to lead you to a place to sign up for some free trials. And yeah, I'll go ahead and do my disclaimer here, because some of you are going to say, Mark, you use one of these, don't you?

Yes, I do. And by sending you to the link, don't think that that means anything. I don't get any kickbacks or affiliate money by sending you to the one that I use.

So don't worry about that at all. This was simply to do a comparison by other MSPs that were fair and unbiased in a sense that it's not me telling you, it's somebody else. But just to run down real quick, the similar features that we talked about here, we talked about the centralized dashboard, you know, any glass, both offer the centralized dashboard.

You can monitor multiple clients and sites from a single interface. Both offer real-time monitoring of network devices and infrastructure, along with the ability to set up alerts for proactive issues. Both seem pretty easy to set up and use and deploy.

And each talked about the integrations that they have, all the integrating with the PSA, Autotask, Domo, integrating with IT Glue, documentation, I noted, and reduction of downtime and proactive troubleshooting. And that's really what it is too. So again, that's it for part one of this series.

Part two will be coming, like I said, in a week or two. And that will be a response both from somebody at Auvik and somebody at Domo's. And, you know, they'll have a little bit more liberty to talk about what we did today.

And of course, I do expect to hear from some of you out there. You can send me an email, use the website, itbusinesspodcast.com, and send me an email there. Or if you have my direct information on the socials, especially on LinkedIn or my email, send it to me and let me know.

Was this a good thing or not? And would you like to see more? But that's going to do it, folks.

Thank you very much. I do want to say thank you again to Darcy and Robinson. I also need to say thank you to, let's see, so Molly Rast at ICR Technologies.

They were, she was very helpful in getting the Auvik team to jump on this. Let's see, Violet Chapel with Domo's was very instrumental. And then Darcy had a marketing person, Patty.

And I never asked her how to say her last name. So if I butcher it, I'm sorry. But Patty Aziraj helped out a lot with there.

So I want to thank you, send a thank you message to those as well. And I look forward to seeing you when we do part two and part three of Auvik versus Domo's. That's going to do it, folks.

Thank you for joining. And we'll see you next time. And until then, holla.