Name: Demo & Dash | See Nasuni in action
Uploaded: 2026-02-25T18:01:06.184Z
Duration: 41 min 8 s
Description: Demo & Dash | See Nasuni in action

Transcript for "Demo & Dash | See Nasuni in action": Alright. Hey, everyone. Thank you for joining. We'll give it a few minutes, to let some folks join. Just a couple reminders. I'll say it a couple times, but we have a raffle for a $100 DoorDash gift card, especially for people that engage in the chat and and ask some good questions. We already got some people saying hello, Texas, p Pennsylvania, Virginia, Denver, Napa. I'm outside of New York. Got 30 inches of snow this week, and it's it's very cold. So I'm happy some people are out of that. Oh, yeah. Boston. I'm sure Michigan is cold. But, yeah, we'll give it one more minute, and we'll kick this off. We had a lot packed into a short webinar today, but just give it one more moment for folks to join. We got a pretty good number already. So alright. Let's kick it off. My name is Ben Clark. I'm a product marketer here at Nasuni, and I'm joined by Ryan Miller, one of our senior solution architects who's gonna, do the demo part of the demo in Dash. So we're we're baking on a lot here. We're gonna kick it off with a couple poll questions. I'm gonna go into a couple of slides to set the stage, and then we're gonna jump right into a demo where you can see Nasuni in action. As I mentioned earlier, there is a raffle for a DoorDash gift card for those who engage, ask good questions. On the top right, you can you can, enter some messages in the chat, and I believe there's also a q and a tab as well. But if you if you put them in the chat, we'll move them over to q and a. We're gonna we may answer some questions as we go, but we'll have some time at the end to catch up on any questions and and go from there. So without further ado, let me pull up the first poll question. We'll kick it off with that. So just opened it. You should get a little note to go to the polls poll tab. And so what are the largest challenges you face when managing your file data infrastructure today? So these are some of the challenges that we see in the market, and talking to customers and some of the challenges that we hope to solve with Nasuni. I'm gonna answer it myself. Starting to see some votes coming in. Yeah. It's right up on the top right next to q and a. You can access this first poll. Alright. So far, managing a fragmented data environment is winning. We also have meeting performance expectations for your users and applications. Security concerns has just tied for first. Security is always a huge concern, especially with file data, file sync and collaboration between departments. We then have data classification and compliance. No one's concerned about that right now. The ability to recover from a disaster or cyber attack. Let's see. I could scroll down here. The ability or controlling cost of hardware refreshes and expanding storage needs. So we got some people voting here, and it looks like fragmented environment and security concerns are the winner here. So I'm gonna close this up, and we'll go to our our second poll here. And this is kind of top of mind and what we're seeing in the market that with, these large AI companies buying up all the hardware, we're seeing a lot of concerns about costs and lead times, when it comes to buying hardware for, you know, our customers' infrastructure strategy or, organizations within the market. So there's a second poll that just went up. I'll share here as they come in. Alright. So it looks like it is a a concern here, moderate delays or cost adjustments. We got, someone saying it significantly impacted budgets and project timelines, but overall, this this is somewhat of a concern. So that's that that's aligns with what we're seeing as well, and we can address this in a moment here. Alright. Moderate delays wins. So thank you for participating in that. And now let me jump into our couple of slides here. I think we're we got them up. So today, we're talking about Nasuni, the enterprise file data platform. And you might recognize some of these concerns here, but as we know, 80% of enterprise data is unstructured, and most of that lives in files. And so this could be your everyday files, office files, PDFs, but it also has engineering design files, architecture, financial documents, contracts, media assets. And these files are changing every day. Your work your workers are working on these files. There's new versions of these files coming out on daily basis. So file data at any organization is important and operationally critical. And so, you know, some of the concerns we're seeing that align with that poll, this data this unstructured data and files is growing, faster and faster. And it's it's generally siloed, you know, maybe between locations around the globe. But this data is usually siloed, and it's it's harder to gain insights from that data, and collaborate on that data when it does fall into silos. Costs are spiraling. We just talked about that. You know, if you need if you're running into frequent hardware refreshes or, have to buy more hardware as you continue to scale, these costs can be an issue. Files are challenging to secure. Ransomware, threats are becoming more and more advanced. You you have to be ready for when it happens to you and have a plan in place and, a a strategy to get back from these attacks, or it could be a costly incident. Hard for people to access files. So, you know, when you have a scattered workforce, hybrid remote workers, it could be hard for them to access these files quickly, and collaborate on them between locations, especially when we are talking about these engineering files, project files, some of these more advanced file types. And then, of course, it's difficult for AI to access this data. This goes back to when your data is is siloed and it's not all in one place and it's not, you know, in a in a format that this these AI tools can understand, it's gonna be difficult for you to leverage AI for your data. And so enterprise infrastructure today has not really involved to manage this reality, and so this is where comes in. And so Nasuni is the what we're calling it these days, the enterprise file data foundation for teams and the AI that supports these teams. So unlike tools that may just focus on storage or backup or collaboration or analytics, Nasuni unifies these operations at the core file lay layer, and unify not only your file storage, but backup disaster recovery, global collaboration, and intelligence. So this is not a point solution. All of these components are baked into one cloud native platform to give you a complete foundation for your file data. And this is all built on object storage, with multi cloud freedom. And so starting with just the file data platform itself, because it is built on object storage, which if you're familiar with object storage, more cost effective, more durable, and more scalable. It allows some Sunni customers to to really scale without limits. And so this this means no limits for the amount of users, the amount of files, the size of your files, or the number of immutable snapshots of your data, which are created with Nasuni whenever files are created or changed. And so this is also what allows our customers to eliminate their existing backup infrastructure. We'll talk more about ransomware and recovery and, how these snapshots or immutable versions work. But, generally, with Nasuni, customers are not backing up their file data, you know, with typical backup infrastructure with Nasuni and can can in many times, eliminate that infrastructure. And, of course, they can do this with multi cloud freedom as I mentioned. So whether it's the hyperscalers you know, you know, like AWS, Azure, Google Cloud, but also in addition to that, other public and private cloud providers. So adjacent to that, we have our ransomware protection solution. And so our ransomware solution detects, stops, and recovers from ransomware attacks in a matter of minutes, and this workflow is all within the the Nasuni management console. Ryan will show this workflow in the demo, so we'll see this in action pretty soon. And then when we're looking over at global collaboration, we have multisite collaboration and the Sunni web access within that global access and collaboration category. And so this is enabling our customers globally distributed workforces as well as remote and hybrid workers to collaborate well on the latest versions of their files, with the speed of an on prem file system. So with these aspects, we are protecting and giving fast access to the file to to these files to the people that need them wherever they are. And so now that your global file data is consolidated in in one single pane of glass, is now an excellent foundation to start getting the most out of your data. So moving up to the top left, to data data intelligence. So we have FileIQ and OpsIQ. And so with FileIQ, we provide dashboards for visibility into your file metadata. And so you can gather insights into how files are used, where they're growing, who's accessing them, to to help you with chargeback reporting and and different use cases. Ryan gonna go give you a sneak peek into both FileIQ and Ops IQ. And so Ops IQ is more for your Nasuni environment itself. And so at Ops IQ, you can monitor application performance, look at capacity consumption, and track the speed of your your data propagation from the different locations up to the cloud and to the other locations. And then finally, what we're all we've all been waiting for, activating this data with AI. So we have Nasuni data service or NDS, which is a read only API that provides direct access to your Nasuni data, allowing you to gain insights from your files within various external AI tools. And then coming later this year, we have what we're calling at the moment AI hub, which provides hosted indexing and a hosted MCP server, which will allow our users to interact with their their files, their unstructured Nasuni data, and gain insights about their files and their Nasuni environment itself using the LLM of their choice. So a lot of great use cases coming with AI Hub. And so that provides data for AI. So to summarize, Nasuni doesn't just store files. We deliver them at the speed for people or deliver them at speed for the people that need them with structure and context for leveraging that data with AI. And here are some of the metrics that we typically see from some of our customers. So a lot of savings when it comes to infrastructure. So if we're thinking of, you know, example, Windows file servers or, something like that distributed around the globe, we're consolidating that into one platform, but this also lumps in, eliminating backup infrastructure as well. So a lot of customers are seeing a lot of savings when it comes to their infrastructure up to 98% faster recovery. We'll we'll see this in action, but the the Nasuni platform has a patented process, and it can recover, over a million files in less than a minute up to 15 times faster file access. I think this example itself is is from, engineering, files from PLM software. So when we're when companies are struggling with these complex files, they're seeing a lot faster access between locations, and activated AI powered by safe and relevant file context by having it all within this foundation. So I said two slides. That was that was a long slide. Then quickly looking at how this these capabilities compound into more value. So we're lowering your IT cost. We just talked about that. You're optimizing your infrastructure and reducing complexity across the globe for your file data infrastructure. You're also lowering risk. You're protecting your data. You're reducing downtime and business disruptions. If anyone, you know, pays attention to ransomware, it's not even the cost of the ransom attack. But if you go down for multiple days, it's gonna cost a lot. And then from there, you're getting faster file access for your global teams, frictionless access, faster collaboration, more output, and now your data is ready for AI. So you're you're putting together some intelligent workflows. You're using AI. You're you're continuing this compounded value. And so these lower IT costs can help fund innovation. They can help help you leverage more I or AI tools, and they can help you scale. And this reduced risk increases productivity. So you're not dealing with downtime. You're not dealing with lost productivity, or, you know, projects that are delayed. And then from there, you get better data for AI that makes AI smarter, and smarter AI helps boost productivity. And then because productivity is boost, you get more data and you continue to scale that gets created and protected while your costs are continually managed. So we got a little loop here. And the the basic message here is that when your enterprise file data is fast, it's governed, it's semantically secured and context aware, your productivity compounds, and you you realize these costs, this protection, and this boost in productivity. And so with that being said, let me move on to our first part of our demo at Ryan. So the the demo is gonna be separated into a couple sections. The first part is gonna be what the admin sees from the new Nasuni management console, and then we have a second shorter demo about what your users will see. So I'll kick it over to Ryan. So I wanted to start off, by showing folks, basically, a view of the administrative, functions for Nasuni. I'm start off with what we call the NMC, the Nasuni Management Console. The NMC is a single pane of glass for all the management functions, within the environment, regardless of whether you have one edge appliance or 500 edge appliances or 50 edge appliances. There are some other dashboards as well that we'll talk about with FileIQ and OpsIQ, but from a management perspective, everything comes down to the, Nasuni Management Console, or NMC. The main screen of the NMC is what we see here, and I'm just going to point out a couple of things. On the left hand side, we have system health. So we can tell that there are some updates available for the NMC, for the edge appliances. We see that all of our edge appliances or filers are online. Any antivirus violations are going to show up here. If we have any sync setting errors, they're going show up there. We also have just a summary of what we have for shares within the environment, SMB slash CIFS shares, NFS shares, error exports, and FTP directories. And the biggest thing really is basically how much data do you have in your environment. What is your cloud usage, and how much data is is in the is in the environment, environment, plus your license capacity. So a very high level view, 10,000 foot view of the environment. If there is an update that you need to download, it's a matter of just clicking here, and then you can select which appliances you want to update. Type in a confirmation code here, update filer, and it will download the package and then install it if you want to right away. It will install it. So you don't have to manually download a ISO file or anything like that and then manually upload it. It's all streamlined within the platform, within the NMC. The next thing I want to show you is the, volumes. And here, under the volume section, we have a list of all of our volumes in our environment. We also see which Edge appliances those volumes are attached So in this example here, we have a volume called Nasuni Azure demo volume. It's connected to edge appliances NEA zero one and NEA zero two. These edge appliances could be located right next to each other, or they could be thousands of miles apart. You could have one that is in Boston, one is in LA, pointing to the same volume that resides in Cloud Object Storage. So right here, in this demo environment, it's very simple. We just have one volume connected to Edge appliances. But if you had a bunch of volumes, you would see them listed here along with those Edge appliances that they are connected to. Another thing you see here is the latest snapshot, and right now one is one is kicking off. These snapshots happen on average for production, environments about every five to fifteen minutes. You can set your schedule on a volume by volume basis. So in this case, I have this one set pretty aggressively at one minute because it is a small demo environment. Again, most production environments are gonna have that frequency set to every five or fifteen minutes or so. But the nice thing is is that you can have a volume that maybe you don't wanna have it that aggressive. Maybe you only want it once a day, once every six hours. You can do that. So depending on the workflow, depending on the workload, you can put it on different volumes that have different snapshot frequencies. The other thing that I want to point out here is the snapshot retention. By default, we retain all snapshots. And there is no limit to the number of snapshots. A lot of platforms have a limit, whether it's 200 snapshots or a thousand snapshots per volume, something like that. We don't have any limits, at least what we've run into. And we've had customers that have been on us ten years taking a snapshot every fifteen minutes. In aggregate, across their volumes, they have millions of snapshots, haven't run into any limits there. So that's the nice thing about our, snapshot technology, the way that we do things. There are no limits, and you can retain them forever. Of course, if you have legal or compliance reasons that you need to, get rid of them after a certain period of time, you can do that. You can specify how long you wanna keep a snapshot, years, months, days, stuff like that. So another thing that I want to show you, within the management console is a ransomware demo. So I'm going to set this up, and we're going to go into the cyber resilience tab, and I'm going to enable mitigation detection. And as I'm doing this, I'm gonna explain how our detection works. So what we do is we detect when ransomware happens, and that can either be done by anomalous or destructive behavior, or it can be done by known extensions, like Deadbolt, WannaCry, something like that. The known extensions, obviously, are going to trip easier because those are known extensions. The destructive behavior, that's going to take a little longer because we're basically looking to verify that it's something smells like ransomware, something just seems a little off. We're seeing a lot of renames. We're seeing a lot of deletes, stuff like that. And when we do, we trigger it. It gets triggered as ransomware using those different confidence levels that you may have seen me just go through, very low to very high. And that's essentially how twitchy is the system gonna be. If it's very low, it's gonna be a little bit more sensitive. If it's very high, it's not gonna be quite as sensitive. You may have legitimate workloads or scripted functions that do a bunch of renames or deletes, and we don't want to have those be false positives. So we allow you that flexibility. Once, ransomware is detected, it's going to be mitigated. It's going to be the offending IP address or username. We have two different types of mitigations. The IP address or username is going to be blocked from that NAS share, and that's going to limit the damage. Instead of having 100,000 files, maybe it's only going to be a couple 100 files. And then the last thing we do once the damage has been done and it's been mitigated is, we allow what we call a targeted restore. We know what files have changed in the system because of our auditing, so we can actually help with doing the restore and lower that mean time to recovery. I want to point out that you can always do a restore using the file browser. You can always go back to a previous version before the ransomware struck. You can always go back to a previous version of the file system and restore individual files and folders. However, in this situation, the onus is on you to pick the files and folders to determine which have been corrupted and do that manual restore yourself, but it's always available. You can always do a ransomware restore regardless of whether you have the ransomware add on or not. What the ransomware add on does is does this detection and the mitigation and the targeted restore that we're going to see here in a moment. So now that I have this enabled, I'm going to go over to another machine. And actually, before I do that, I'm just going to show you some of the data that we're going to encrypt. So we have this ransomware data, some test data, natural images, airplane. I'm gonna go in here, and we see that we can view an airplane there. So I'm gonna go over to another machine, and I'm gonna run a ransomware script that is going to encrypt this data in real time. So we go over to this victim machine, and I'm gonna run this. And just to show you, we have the same dataset. This is the same volume just being accessed by another machine. We see the same data. I'm gonna run this ransomware script. Gonna choose encrypt. I'm gonna choose a random extension type, and I'm gonna choose our dataset that we're gonna encrypt. So at this point, it's going to go through the file system and start encrypting stuff. So this is I'll minimize this. So we have this. This is kind of your heart drop moment where you see that data is being encrypted. And in fact, if we go over to our first machine that we were looking at and we look at that same data set, we see it being encrypted here. Now, typically what happens, this gets around, to around 200, 300 files or so, and then it stops. So we're just gonna give it a few moments here to go through its list of files. And, again, what this is doing is the system is looking at this, and it's recording that files are being encrypted, that something is happening. And it's it's looking to see whether it's a delete file or a rename or something like that. And it's if it basically, this this seems kind of weird. This seems kind of fishy. So it's going to trigger, again, around two two hundred twenty five, 250 files is usually where it stops the ransomware in its tracks. And, actually, one of the things I'll just show you real quick while it's finishing this up is OpsIQ. This is an appliance dashboard that shows the health of the edge appliances. So this is not around management in terms of creating volumes and assigning volumes. This basically tells you what's going on with the, edge appliance, CPU usage, available memory. And what I think is the most useful thing, cache misses. Basically, what we're looking to see is about 98, 99% cache hit rate. If we see our cache misses get up around five or 10%, that may be an indication that the cache is undersized and it needs to be adjusted. And then customers, you can you can call support, and, work with support on expanding that. So you get some nice information just about how the system is running from a from an appliance perspective. Okay. Going back to this, we get to 205, and then it stopped. Now if we go back to our victim machine, it stopped over here as well. So now if we go back to our cyber resilience page, we see up top in the NMC that we do have a notification a ransomware attack has been detected. And under incident management, we see that we do have an incident here, and there's a timestamp. In blocked sources, this will eventually be, populated. Oh, and it just populated right there. Sometimes there can be a couple minute delay. Incident management, let's look at this real quick. So we have a generate report, and we're going to look at this, and this gives us all kinds of information about the ransom ware attack, where it came from, the IP address, how many files were impacted, what the time snap the the the time stamps of the snapshots were before the ransomware attack, and so forth. We have all kinds of great information. Now this is saving you hours and potentially days' worth of investigative, efforts, just right here. It's it's available in moments. So then what we can do is now that we've determined that something has happened, and we know that the system has blocked it, we can do a targeted restore. And I'm going to restore everything back to the original, folder. Click on restore folders. Perform restore. Now this is gonna take a few moments, and this is a unique thing that we have with with ransomware and our ransomware recovery. We are sitting in the data path, so we are able to restore data from a backup that is online. We are not scanning a backup and doing kind of a post process. Oh, you got hit by ransomware and then having to pull from a backup that's in another location that's over a WAN, something like that. We are sitting in the data stream. We have, we basically have pointers to the versions of the files before the ransomware, so we are able to restore, the files much faster than any other product in the market. This is a patented process. And our goal is not to prevent ransomware from happening. We're gonna leave that to the edge detection. We're gonna leave that to the network and the packet sniffers and all that other stuff. Our goal is to help reduce the mean time to recovery after a ransomware attack has occurred. So the speed of the restore is going to take a little bit of time just because the nature of the performance metrics of this system. We do have a ransomware demo where we have beefed up a machine where we can restore a million files over a petabyte of data in under a minute. So, really, it just comes down to how much CPU, how much memory are you giving this this machine. So here, it's just gonna take a few moments to restore all of our data. But if we go look at the files that we that we are that were encrypted, we can see these starting to revert to their original form. And, actually, what I wanna do before it totally catches up to me here, we try and open up one of these encrypted files, and we can. And if once it gets to two zero five, I'll open up this one again, and we'll be able to see that we can view the unencrypted file. Back to two zero five. Now we open this, and there's the file unencrypted. So we've done the ransomware restore. This took only a few moments. Much easier. We've done a lot of the work for you. Now, the machine that actually did the ransomware, that was executed from, is still blocked. So I'm going to go over to blocked sources, and I'm going to remove this block. Now this is simulating you've identified the laptop or whatever the workstation that someone has run their ransomware, script from. You've done whatever cleaning that you need to do that. You've done the restore. Everything is good to good to go. So you can unblock that client, and that person can resume their work. And just doing a little bit of cleanup here. And now if we go back to our victim machine, that's an error message from when it originally failed. This machine now has access to our data again. There we go. The last thing I wanna show you real quick is, we looked at, OpsIQ. I just kind of want to show you, FileIQ. It's great when you have all the file data or you have all the data consolidated in one place, but you kind of really need to do something with it. Once it's there, now you can start reporting on it. And that's what FileIQ is all about. It's all about giving you dashboards. You know, we have volume stats here. We have some other ones that I'll show you in a moment, that give you an idea of what normally goes on with the system, how much data is on the file system, how many directories, the file counts, activity levels, stuff like that. And it can help show what's going on if there's a peak. If something's going on that's a little bit like what happened here, we have demo volume two, all of a sudden the volume size dropped. Did someone delete a whole lot of stuff? Was it intentional? Over time, can see, is this a periodic thing that happens once a month? Maybe there's a process that's doing that. This is stuff that is very hard to do when you have all of your data siloed in different platforms, but once it's all consolidated and you have something like FileIQ, it's very easy to see some of these trends and find out what's going on. Another dashboard is the inspector dashboard. This is an audit trail, essentially. And this will give you everything that has happened on the system. So users who are changing, renaming files, changing security metadata, all kinds of stuff, you can get an idea of what users are doing. So it's much easier to see, like, oh, did so and so change permissions? What are they reading? What are they what are they writing? Who's putting these files in? Did files get moved from one path to another? You know, people move files around all the time, and you have no tracking of that. It ends up getting duplication of files. This can help you identify where that's happening. So that's it from the management perspective, and I'll be back here in a few minutes to talk about things from the user perspective. Thank you. Alright. Thank you, Ryan. So just one quick slide before we get to the perspective of the user. We talked a little bit at the beginning about how your users can accelerate global collaboration and have great performance and file access speed no matter where they are on the globe. So number one, Ryan touched on this a bit, but the most used data and files are cached at the location from object storage for 99% average hit rate. And this is with smaller appliances up to 98% smaller capacity versus your traditional file server, or NAS infrastructure. And and then from there, we have, what we call global file acceleration that enables intelligent propagation, to prioritize which which data is propagated up to the cloud and, you know, realized in the other locations faster to ensure these changes are reflected globally with speed. Finally, we mentioned with Nasuni web access, when you have a workforce that's hybrid or remote, we provide a, a a web tool with VPN less remote access to your file data, for this hybrid workforce as well as global file locking technology to make sure workers are working on the latest version even for complex project file types. And so our our file locking works for, you know, some of those engineering file types that we we talked about earlier. Let me see here. We have we only have only about ten minutes, so let me jump into the next demo and let Ryan show you what this looks like for from your user's perspective. And we're back to look at how things look from the user perspective. So, from the admin bit before, you already kinda saw a little bit of this. Basically, what we do is we present map drives to the users just like their normal Windows file server or an Isilon or a NetApp filer. So you just have a a typical mapped drive. Now in this case, we do have in this, we have this this machine where I have it mapped to the j drive using Edge Appliance o one, and we have the k drive mapped to edge appliance o two. These two are looking at the same, exact volume, and in fact, if we descend into them, we can see that it's the same data set. But they are accessing the data through two different edge appliances, which could be located very far apart, or they could be next to each other. So that's the main thing is that it's a Windows mapped drive. It's it's that's how it looks and and and feels to the user. It's no different than what they're used to. We also support Windows previous versions. So we can go into restore previous versions, and we can see a bunch of versions from today. We can go back to previous points in time. This demo environment doesn't go back too awful far, but you could imagine that if you had an environment around for a year that you would have stuff from last week, last month, three months ago, stuff like that. One thing that I do want to point out when you do have multiple edge appliances and they are pointing to the same volume is that you can have potential conflicts, users accessing the same data from two different edge appliances. So I'll show you what that looks like or an example of what that can look like here. So I'll go into the j drive here, and we have this file that I have, test dot o d t. I'm open this up, and notice that I opened this up from the j drive n e a o one. So I have this file here, and I'm just going to type in some more stuff, and I'm going to save that. Now, if we try and open this up from the k drive, which is another edge appliance, we will get a message that says that the file is already in use. Open read only, open a copy, or cancel. It says unknown user just because certain data has not propagated yet. That does take a few moments to to propagate where it shows the individual user. But the point is we get this locked notification so that I am not stepping on someone else's toes. So if we go back to this one here, and we close out of this. Now when we do have so that was our global file lock that's showing that when you try and open up a file from one location that's open in another location, it will give you that notification. Now we do have, some things that need to happen on the back end after we have written some data to a file, when it needs to be propagated up to the cloud, the other edge appliance has to be notified of that. So it does take a little bit of time. So we're just giving this a good twenty to thirty seconds for that information to propagate over to the other side. So we'll open it up on the k drive here, and let's see what we got. And here we go. We have that data has been propagated. Now, obviously, while I was talking there, we did have to wait a good ten seconds. It's not instant. But think about what you would normally have to do in this sort of a case. You don't have to have users calling each other up, messaging each other on Slack or some other message platform saying, hey. I'm done with this file. It's all done behind the scenes for you. You do have to wait a few moments for things to propagate, but it's a much more seamless and much simpler to the user from the user perspective process than what you had before. So that's pretty much it from the user perspective. It's a MapDrive. We support the Windows previous versions. You saw the global file lock, how it prevents a user from opening up a file that's already opened by another user. And when that first user has closed it out after a few moments, it, those changes get propagated over to another edge appliance that could be remote, and then that user, opening it from that remote edge appliance sees that that changed data. So thank you. Alright. So that concludes the demo. We'll get to q and a right now. The last thing is if you're interested in learning more about Nasuni, we just covered a ton of different capabilities all at once, all squeezed into, a small demo. Take a shot of the QR code, and we can schedule a personalized demo for you and your environment. And so with that, let's see what kind of questions have come into the chat. From Tim, I see it shows as a map network drive. Is there a software that you push out to computers via a RMM that then maps to the data? And Ryan answered this one in the chat. We do not push any software to the client machines. What you saw was a standard map drive in Windows via SIFs and SMB. What SIEM integrations do you currently have? I can take that one. So right now for our you know, especially for our ransomware protection solution, we have SIEM integrations with Microsoft Sentinel and CrowdStrike. We have Splunk coming soon, I believe, this quarter, and there's a few other major SIEM tools that we're looking at. And and we really prioritize this because some of our larger customers that have, you know, global security teams and use these same tools every day for for monitoring alerts, require this and want this in addition to our ransomware solution, to you know, because they're gonna be looking at these management tools. So our ransomware solution that's looking for ransomware attacks and anomalous behavior at the edge will send these detections and alerts up to these same tools that can be then, given to this your security teams for, secondary actions from there. Let's see. What kind of alerts and notifications are sent to IT teams in the case of a ransomware attack, and how are they configured? Ryan, if you're there backstage, you wanna take this one? Yep. Just coming on. Which one would the alerts and notifications are sent to IT teams. We send out SNMP, SMTP, those kind of alerts, Syslog, and yeah. Those are the three main ones. Syslog, SNMP, and SMTP for email, for bubbling up to your Syslog aggregator, stuff like that. In addition, the the SIEM integrations that Ben mentioned, like Splunk and Sentinel, we also have audit logs that get dropped into the volumes onto onto shares. So that is even if we don't directly integrate with a product that you have, as long as it can read something and read those log files, they're, like, CSV files, as long as it can read that and and basically pull that data in and and and propagate it up to whatever visible whatever visibility platform you have there. Yeah. Absolutely. Let's see what else. Yes. I think you mentioned this, but a little bit more about the retention period for these immutable datasets. Yeah. So by default, we keep everything. The idea, when Nestor New was first founded was that people don't like to delete data. They're kind of hesitant to. It's people like to talk about wanting to delete data, but nobody ever wants to pull the trigger on actually doing So, we our default is that everything is immutable and it's and it's and it's kept forever. That being said, as I mentioned in the demo, there are certain use cases, legal, whatever, you know, that you might have to get rid of stuff a little bit earlier. So you can set that at a volume level, you know, have five year retention, seven year retention, something like that. And then after that period of time has has passed, that that data will be will be deleted on the back end. Alright. Well, thank you, Ryan. I think if we have no more questions from the audience, I think that's all that's in the q and a section. But thank you everyone again for joining, and thank you, Ryan, for for taking us through the Nasuni management console. You're welcome. Thank you, everybody, for attending.