LucidLink + AWS: Enterprise collaboration without compromise

everyone. My name is Gergana Burman. I'm the director of, growth marketing here at LucidLink, and I'm joined today by my colleague, Alex Ferris, who is the director of solutions engineering. Alex has worked with some of the largest enterprises who use our platform and has a very deep expertise in media workflows. So I'm very excited for him to walk you through our newest enterprise offering featuring AWS and the benefits it can bring to your organization. Please make sure to use the q and a feature. We will make sure that at the end, we leave enough time to answer, anything after the overview. And with that, I think I can hand it off to you, Alex. Thank you very much, Gurgaana, for that introduction. And hello, everybody out there on the Internet. I'm very excited genuinely to show you something new from LucidLink today. And Alastair says hi. Hello. Feel free to say hello in the chat, everybody, if you're there. And, likewise, you'll see just to the right of that, the q and a button. That's where you wanna ask your questions. But good good to see you all on the webinar. I'm gonna get straight into it, and I'm gonna share my screen. And in the meantime, Kigana will have launched a poll, I think. Hopefully, that will have popped up for you. We can take a couple of minutes just to answer that. The webinar we're going through today is LucidLink and AWS, enterprise collaboration without compromise, which sounds very exciting. What we're gonna be talking through is a new product from LucidLink that's based on our partnership with AWS. It's something we've never been able to offer before, and it's something that nobody else has been able to offer before. So we're really excited to show you more about it. The first thing I want to highlight is another recent announcement you may have seen on social media, on our website, on various platforms, and that is the release of the new LucidLink. This was previously referred to as LucidLink three point o and is now LucidLink. This is completely changing the way LucidLink works. This is providing a new user model, which is different from LucidLink if you've used it previously. It's providing a web client along with a desktop client, and it's based on our partnership with AWS. However, this is not the focus of today's webinar. Instead, we're gonna look at what we're now calling LucidLink classic, which is the previous versions of LucidLink. And that's because in the latest version enterprise features are not yet available. And as this is about enterprise video collaboration, we're gonna focus on what we've done to LucidLink Classic and specifically LucidLink Classic Enterprise that enables this enter enterprise level collaboration. So if you're familiar with LucidLink, and I can't see the poll results here. I don't know if you've seen them yet, Gugana. We have a yeah. We have a mix of, people who have seen a demo and who haven't. Great. Okay. Well, we're gonna do a demo in a minute. So you'll you know, if you haven't seen it, you'll see something really cool. If you have seen it before, you'll see something really cool and something new, which is great. And this is our advanced file space backed by AWS, otherwise known as LucidLink Classic Enterprise. This has all of the great streaming capabilities of LucidLink, which will come into if people aren't familiar with it, shortly. But as well as that, it's got single sign on integrations. It's got GUI configuration or the ability to configure and change settings of your file space within the client applications. It's got great backup and recovery capabilities through custom snapshot features, and we support multiple storage providers in the classic version of LucidLink. The AWS, provider is something we're offering bundled and egress free, which is completely that basically means if you don't know what egress is, you don't have to pay to take data out of AWS. Now, normally, if you're using cloud storage, you'll be familiar with this concept of a variable cost in addition to what you pay to store your data, and that's the cost to access your data. And that can be variable, and it can get quite expensive. We'll go into the specifics of that cost later when we look at the actual value of this new product. We're offering this bundled AWS back LucidLink Filespace as an egress free platform, and there's a special price to the end of this year twenty twenty four as well. So there's some great features in this LucidLink Classic Enterprise, and this is the enterprise product that that our customers, should should be looking for. Now you might ask what's the the other value of LucidLink over the egress free features of AWS storage. And this is true regardless of the the data provider, by the way. LucidLink, as those of you that use it will know, you get instant access to your data through it. That basically means if you're a user on the ground like me here in in my office I've just had the polls pop up there, so let's have a look. So we've only got one person who's not seen a demo. Lots of people have used it. That's great. Okay. And more than fifty percent are using e c two in the cloud. That that's important for what we're about to show you. And you're all using s three storage again. That's that's great to know. You you might be familiar then with egress charges and the cost of bringing data down from AWS s three. Of course, you don't have that cost when you use a LucidLink AWS file space, and we'll come on to what that might mean later on. But thank you for filling out those results. In terms of then the workflow value that LucidLink Classic and LucidLink in general brings you, we were explaining you don't need to download your data from the cloud as those of you that use it will know. You stream directly into your creative applications or any application. As this is a video centric webinar, we're gonna look at Adobe Premiere as an example, but it can be can be any application on your operating system. You don't have to transfer data anymore as well. So you save time and money by no longer waiting or or having to pay for content to move. Now that might mean do an upload download workflow, paying egress fees or file acceleration services, you know, that you may use to copy data from one place to another, or it might mean saving content onto a hard drive and shipping it via FedEx or UPS or whatever. You don't have to do that anymore. And that's because when you upload data to LucidLink, it's accessible anywhere instantly, and you can stream it without downloading it. So save lots of time. That file space that you can see in the simplified diagram behind me as well is what we call a single source of truth. And what that means is once the data is there, every user, regardless of where they are and which operating system they're using, has the same file path as everybody else. So that means you don't need to point your projects at local copies. You don't need to relink anything, which simplifies a lot of the workflow. It removes some of the challenges around versioning and updating and making sure people are working on the right asset. You also get to work with people anywhere. So if you're a postproduction company or, you know, working with editors or creatives, you get access to a global network of them, and you can onboard people in minutes securely to work on your projects. And, likewise, if you're one of those creative users, you get access to a global community of collaborators as well. So you can work on projects happening in other countries instantly. Everything's fully secure as well. So, you know, the enterprise features of of LucidLink includes the zero knowledge encryption, which means that only you can read your data. Everything's fully encrypted. We can't read it. AWS can't read it, which allows you to meet very strict infosec requirements that clients might have, or just not worry about meeting your own company's policies. You can do that with ease without stress. So we're gonna get into a quick demonstration of the LucidLink Filespace, and I'm gonna use the new AWS backed Filespace for this. And this is the scenario I want you to imagine. Some of you will have, you know, carried out this type of workflow yourselves in the real world as your LucidLink users, but we we like to show it for for those that haven't. This is me. I'm a creative user over there in in London, and I wanna collaborate with somebody somewhere else. Now in this example, we've got an administrator in Miami. They could be anywhere. Right? And that could be a live studio production. It could be a movie set. It could be a camera crew. It could be an existing project on a NAS. It doesn't really matter. If I wanted to work on it without LucidLink, we would need to bridge that gap. We would need to send the data from Miami to London, and that would mean upload download, you know, and the time it takes to do that and the cost it takes to do that. It might mean fire acceleration across the Atlantic to a local machine I have here. Again, that takes time, and it results in a duplicate asset over here in London or anywhere else we wanna onboard someone, or we might ship a hard drive. All of these approaches take time, cost money, and break the collaboration potential between these two creatives. So we're not gonna do that. We're gonna show you how by installing the LucidLink client and connecting to a LucidLink classic enterprise file space with AWS, you get all that value that we talked about. You get a single source of truth. You get instant access to data. You get collaborative, space for one, two, three, hundreds, thousands of users to connect to all while maintaining that zero knowledge encryption. So I'm just gonna now stop that share and get my machine ready for this demo here. And I want you to remember that I'm that user over in London on that map. So when I share my desktop, you should see a LucyLink wallpaper on a macOS MacBook. Give us a thumbs up, Gagana, if you can now see that. Yes. We can. Good. Okay. So remember, I'm in London. I'm an editor, and I wanna collaborate with somebody somewhere else. Really simple. I've got my LucidLink client installed, and it's connecting me to my enterprise file space. Now I've already created this one. We can take a look at how you create these in the portal, but if you've ever created one before, it's, the same. You just select AWS instead of IBM or Wasabi or the other providers that we offer. Now this client is mounting that enterprise file space to my macOS system just like a local disk even though the data for it is in that AWS data center. Now this could also say North Virginia or Tokyo or, you know, wherever the AWS data center is. You can still choose where to put that, and we go into some of the locations we support later. Despite that data being in the cloud, LucidLink client is mounting it just like a local disk, and I can see it there in finder like I've plugged in a thunderbolt drive and I can see my user here demo one has been given access to a set of data. I've got one folder basically and inside that is some media files. Remember, these are in AWS. They're not on my local machine, but I can start using them in my applications. Finder is letting me preview that. I could double click it, open it in QuickTime or VLC. And importantly, I can jump to any part of that timeline without needing to download that whole file. Now if this was s three or OneDrive or Dropbox or Google Drive or WeTransfer or any of the other cloud storage platforms, we would have to right click download, right click make available offline, and we would wait while that file came down and copied onto my local machine. Takes time. It's insecure because we're making a a local copy. We don't have to do that. I want you to imagine when I hit play that data on that map coming down from that LucidLink Filespace into that machine in London. And when I press pause, the data stops coming. So instant access to any amount of data that you've put into the cloud, and any application will be able to access it. If it can read from a local disk, it can read from a LucidLink Filespace. So really, really simple way to get going. You can imagine people logging in, getting the driver pair, and off they go. Let's have a look at how multiple people can now collaborate. So if I switch my view here, I'm gonna connect to another machine. Now you can see this Windows machine, I hope, that's popped up. This is the guy in Miami or Paris or New York or whatever, wherever. It doesn't matter. The point is this is someone else. It's not me here in London. They're on a Windows machine. We also support Linux. And, actually, and once the file space we're looking at has the upgrade and talk about later, you'll be able to connect iOS and Android devices to this file space as well. This person is logged in as an admin. You can see the little crown there is showing me they're an admin user. That gives them access to a control panel where we can modify permissions and do stuff. Again, this is something that the newest version of LucidLink doesn't have, the ability to change these settings, to set up client side configuration through through the UI. We'll look at that in a minute. Just point out the other thing being an admin user gives you is full access to all of the data in the file space. This is relatively small like I said I've just created it and put a project in there but you can see my user in Miami has got access to all of that data, whereas the guy in London has only got demo one, user folder demo one. Now I could jump in there and see there's actually demo two and three users, but we only see demo one. And, actually, if I go up to this PC, you can see how LucidLink is mounting it to Windows. It looks like a one petabyte local disk, so really simple to use and infinitely scalable. What I'm gonna do is jump into that demo one folder, go into incoming media, and then I'm gonna select the same folder over here in London. So when I create folder in Miami, you'll see that new folder appear in finder on my Mac in London, and I'll rename this magic hour. When I rename a folder anywhere, it renames for everybody instantly without the need to upload and download file data. I'm gonna copy a file into this file space from Miami. So imagine that use case. You've got somebody. They're a camera crew. They wanna upload some camera card content. You've got daily rushes on a film set. You've got an existing project or an on prem system that you need to make available. We don't wanna send it to London. Remember, we're not transferring files anymore. What we're doing is uploading it to a single source of truth. So when I just click and drag that in like any other disk on that machine, we can see the data start uploading. This remaining upload is gonna go down and it's gonna you can visualize that data going up from Miami. Now it's actually happened so quickly. I'm not even able to show you one of the the coolest features here. I'm gonna actually quickly show you something else. I'm gonna deliberately slow down the upload of that file. Again, using a client side configuration that I wouldn't have access to in the the new LucidLink, and I'm gonna copy that file in again. I'm actually gonna rename the one I just uploaded, and you'll see that rename will happen for everybody everywhere instantly without the need to re you know, to send anything. Let's upload that file again. Now, again, same process. Think about this file uploading from Miami. It's going the data on that map is going up from Miami into the LucidLink AWS file space. We can track the remaining upload as the data goes up. And if this was Dropbox or OneDrive or s three native or whatever it is, you would have to wait for upload to complete. And then I'd say to Alex in London, okay. You can download that now. We'd have to download it and then wait for that download to complete. So we wasted a lot of time, and we have three copies. One in Miami, one in the cloud, and one in London. We don't have to do that. Even though it's still uploading, We can see that file has already appeared. Remember it's not in London. It's not on my machine. It's in an AWS data center. This little icon is showing me another user is still uploading these file changes to the cloud. But despite that, because of the streaming capability of LucidLink, I'm able to start playing that back on the ground here in London on my Mac in an ordinary application like QuickTime without having to wait for even the upload to finish, let alone the download. Now if I pause that playback, the data has stopped coming. We're still uploading from Miami, but we're no longer streaming to London. I can press play. Now we're streaming it out. We can pause it. We're not and if any of you were to connect to this file space and hit play, the data would be streaming to you as well. So this really Why does this creative studio You This really highlights how LucidLink is different from from other cloud storage. We're using s three directly. Seeing lots of questions, in the in the chat. We'll address those. I think, Yagani, you're answering them, and we can address them later. We've got time for that. Alright. So this is a really great example of that demo. It shows why LucidLink saves so much time and is unique in the way it presents the single source of truth without impacting the user's workflow. And you also saw how quickly it can upload things as well. I have to deliberately slow it down in order to show you that live playback because it uploaded in seconds. And that's because LucidLink is able to saturate the connection between you and that AWS data center. We can use all of the available bandwidth to make these parallel connections to make sure you get the most efficient, upload of content to the single source. And likewise, you only stream the data you need when you try and access it, from for for reading the data out. So there's a really great way to look at accessing data that's already there and accessing data that's currently being uploaded to the platform. Let's now look at one of the other features of LucidLink Classic Enterprise, which is the ability to change in the the client what the users can access. So if we remind ourselves, we've got this drive over here as an administrator on Windows. We've got a whole bunch of content and folders in here, and our user in London can only see one of those folders. Now I can go into that control panel again, and this time I'll click the users tab instead of the configuration tab. Let me drag that up there a bit. And I'm gonna give them access. Here's the user demo one. That's who we're logged in as. We can see they've got one permission currently and that is read access to users demo one. That's why they can only see this folder. Now I could give them specific access to folders as well. We've got this media folder. I'll say I want them to have read access to that. When I click that green square to say add the permissions to demo user one, we're not gonna send this data to London. Gonna keep reiterating that. We're not making the user download that data. We simply make it available from where it already is, which is the AWS data center. So I click that button. You'll see a media folder appear as if by magic on my machine here in London. Now that's, you know, relatively big, twenty five gigabytes. But, again, it could be hundreds of terabytes, and you get the same thing, instant access. And you can then, you know, jump in and start previewing and streaming and just working with those files just like I showed you before, instant access. And, likewise, granting instant access, you can take away access as well. So let's remove their permission. So you know what? We don't want them to have access to all of that media. We just want them to have one project, maybe the botanics folder within it. So let's delete the media permission. And just as quickly as it appeared, it now disappears. So you've basically got a drive on all of your collaborators desktop, and you can make folders appear and disappear regardless of how much data is in them, and people can access it without having to download it. This becomes especially useful for the video post production editorial workflows. And as that's the main theme of this webinar, I'm gonna show you now a a premier use case. We've seen streaming data into the finder preview window. We've seen streaming data into QuickTime. We've shown the ability to browse folders within finder. Let's put premier in front of a LucidLink Firebase and see what you can do. And, Alex, before you, get into it, somebody asked in the the q and a, section if LucidLink can work with DaVinci Resolve. And maybe you can answer if the workflow that we're seeing we'll be seeing now with Premiere is also applicable to other applications. Absolutely. Yeah. It's a a great question. And that's one of the brilliant things about LucidLink is you use whichever tools you wanna use. LucidLink mounts like a local disk on the operating system, and then any application you can install will see it like a local disk. So DaVinci Resolve, absolutely, you will get the same experience. You can stream data into DaVinci Resolve, and it looks like it's already been downloaded to Resolve. You could go to Final Cut. You could use After Effects. Any application that reads from a from a local disk. The other advantage to this, as you can imagine, I could we're kind of jumping ahead of it, but I could export a sequence from Premiere or Avid or MediaQuery or whatever into a EDL or an AF or or some, you know, some translation file, the paths of the assets will remain the same within that reference file. I can send upload that into my file space. A user anywhere in the world then on another application could instantly load that, and all the paths would would match up, and it would just load into application. So, yeah, absolutely. Resolve is really great, application to use on top of LucidLink. Thank you. Yeah. Please call out any other questions that come in. I haven't can't keep my eye on everything. I've only got one monitor here as well, so I'm sort of juggling things a bit. But, yeah, before now the only reason I'm here. Cool. Alright. So we were just showing then the groups that you can create in LucidLink. And what you can do with groups, basically, is predefine multiple permissions that you don't have to add individually to each user. K? So I've got this group here, Botanix edit. That group has read access to just one of the folders in that big media directory I showed you, and it has write access to a premier production project file. Now I can put you know, I could modify these permissions or add new parts if I wanted to do that, and I can choose to put users into that group. So when I select demo one and click that green square, again, we're just saying to the system, let demo one, wherever they are, access the files that are defined in this permission. When I click the green square, we're gonna see now two folders appear on my desktop here in London. There's the media directory now with just one folder in instead of all of those folders as before and the project file. And I can simply come in here. We've got the project file. Now remember what I said about everyone having the same file path because LucidLink mounts as a local disk. This is really important. When you open up an application like Premiere, you've got a file that points to other files. Right? That think of them as pointers going to different file paths. And what you would normally have to do, and I'm sure you're all amazed that a video has just magically appeared there that I didn't have access to a couple of minutes ago. I haven't had to download any of the media that's in that botanics folder. I haven't had to save it somewhere locally or on my own, you know, hardware on the ground here, and I haven't had to relink the files in the project. We can look at the path of that file where it's linked to within the Adobe project, and it's already where the application thinks it is. It's already in Volumes Enterprise, double a media botanics. Again, remember, that's how the file space mounts onto the operating system. So Premiere sees it, finder sees it, resolve sees it, whatever you want. We're also actually leveraging some native capability in Premiere here as well where we have multiple versions of the of the media. So we've got a proxy folder in there. You can see this is like four k content, the high res here. We've also generated Adobe or Adobe's generated proxies. You know, the the proxy workflow with Adobe, that works brilliantly as well within LucidLink. We're also able to actually see other features of Premiere that only normally work when you're attached to local storage or shared storage. This case is Adobe productions. We can see, you know, seven other projects there that other editors around the world might be working on. We can see demo four, another user is is working on that, that project there. Now I can just hit play, and I'm gonna now start streaming this data. And in fact, I'm gonna be really bold here and show my drop frame indicator. I'm now streaming this data from the AWS file space directly to my machine here in London. And I'm literally on, like, some Wi Fi network in my shared office here. Not great connectivity. It's fair. And I'm able to open that project despite just being granted access to it by an administrator in Miami and stream that data into Premier just like it's already been downloaded. And I can jump to any part of the timeline without needing to download, relink any of that stuff. And I can use it in any part of the application. So I could load these videos into the source monitor. I could mark my in and out point, you know, and I could start to modify my edit or whatever whatever it is I wanna do. And, again, we're delivering that data in real time directly from the cloud, fully encrypted without users having to copy. So really, really cool. Now when I wanna save this project, the project itself is tiny. Right? The big stuff is the media file, so we haven't had to wait. If I save my project and we load up my LucidLink client, you'll see a very so quick we missed it. Very small amount of data there as the the project file is uploaded. We could literally go to any computer in the world that's online, install the LucidLink client, log in as a user that's been given access to this part of the file space, double click that project file, and off we go. It links up. You start editing. Imagine how quickly you can start handing off work around the world. Imagine how quickly you can move to Premiere into Resolve for the final color or collaborate with an after effects artist to overlay, something in your your Premiere project. All of these things can connect in a single collaborative space with LucidLink sat behind it powered by AWS. So what I'm gonna do is close my project. I'm gonna close my production, and I'm gonna jump back to my administrator in Miami. And I'm gonna say, right. Take the demo user out of the botanics group. Simple as that. My folders have disappeared. I could be added to a different project now. I could be using a different application. We've got, you know, some some InDesign projects and whatever. Photoshop, you can use whatever you want. So really great way to onboard users wherever they are, give them instant access. One other thing you can do, and this is a unique thing of LucidLink Classic Enterprise, is the ability to set custom snapshot schedules. Now a snapshot is like a moment in time. It's the ability to look at your file space as it existed, any any moment in time. And and and with the LucidLink Classic Enterprise with AWS, you can define your own snapshot schedules. Here, we're taking a snapshot every fifteen minutes, and we're keeping the last hour, this quarter hourly schedule. We're taking one every week and keeping the last month, taking one every hour, keeping the last six hours. We're taking the last take one every day and keep the last week. So I can basically plug in what looks like a drive from any one of these moments in time to recover from things like accidental deletion or unintentional data modification. Bit of a mouthful, but that could be ransomware. It could be I've accidentally changed the sequence I didn't mean to. LucidLink custom snapshots give you the ability to define that, schedule. So we can see we took one, you know, about seven minutes ago or so, twenty three minutes past ten. This is in LA, actually. I think this machine that's why we're we're looking at time. So we've got that previous moment in time. Now if I mount the snapshots well, let's let's do this, actually. Let's as an administrator, say we're gonna delete some of the folders here. I'm gonna delete the magic hour folder that we uploaded as part of it. Now if your snapshots schedules have been taking snapshots with, you know, a short enough increment, you'll be able to recover that. And I'll go in there and I'll see it and think, oh, no. Someone's deleted my file. And if I'd have been in that folder, you'd have seen it instantly disappear. I can now mount my LucidLink snapshots, which is a bit like plugging in a, you know, a drive for each one of these moments in time. And we can jump back and and see our files as they were uploaded. So you can recover from accidental deletion or if another user intentionally deletes it or if ransomware has infected your files, we can do it without replicating the data set each time a snapshot is taken and that custom snapshot schedule is unique to the LucidLink Classic product that we're looking at today. Again all is this all of this is stored in the same AWS data center that that the main live data is looking at. So there you go. There's a real quick demo. Wanna finish up the presentation now for the remaining sort of ten minutes, and then we'll get into answering any more questions that have been coming into the chat. But this has shown you how easy it is to connect to a LucidLink Filespace, stream the data from that AWS data center into any application, and collaborate with one, two, hundreds, thousands of users around the world. Pretty cool system. So what I'm gonna do then, if I move me and Kigana's face out of the way that you probably can't see I'm offended. Well, it's just mine then. I've moved yours back. You're going to know. There we go. I'm gonna now show that webinar slideshow again. Let's just go through a couple more slides, and then we'll get into the questions. But that's what you saw. Two, users collaborating instantly around the world. So what is the impact of using LucidLink in classic enterprise? Your your budget impact. We talked about how you save egress costs, and this is something to think about. Right? Most of you are using s three. I think all of you are using s three. Some of you are using e c two compute. So after paying, if you go and store stuff in s three directly, after paying AWS to keep it there, it will cost you nine cents a gigabyte list price to pull the data out of AWS, out of s three, which is ninety three dollars a terabyte if you think about it like that. So twenty three to keep to keep it there, ninety three to take it out. And if you're not using LucidLink, you have to download the whole of every object because you can't you know, you have to download the whole thing. So the real world implication of that and we've you know, since we've released LucidLink Classic Enterprise, we've been speaking to our big customers, and one of them is gonna save eleven thousand dollars a month just on egress charges alone, as well as getting instant access to data and all the other features you get with with LucidLink. Basically, you can save loads of money from not having to pay egress, but it doesn't have to be a big chunk like that. We're gonna save on smaller datasets as well. In fact, it works out. You only if you egress anything over seventeen percent of your data in a project, you will you will save considerable money with loosely classic enterprise. So it's a really compelling, you know, partnership with AWS, and we're really, really excited by that and the things it's gonna lead to in the future as well. As well as the, you know, the egress side of it, you'll you'll make additional savings in in other aspects of the workflow. You'll speed up, you know, the the project timelines. One of our customers again, we've got many, many metrics. Our customers are happy to to share these with us. Over the years, they've delivered over eleven thousand hours, which equated to an almost ten times ROI on on what they spend on LucidLink. So it's you know, time is valuable, as they say, and egress is unfair. So which regions do we support today? US east, a couple of locations. US west, we've got, three in Asia Pacific and four across Europe, and we're adding more all the time. So, you know, watch this space for for more with what a weekend to the partnership now. Uganda, we're adding all the time, so it's super exciting. I will give you a quick example of how you create these in a minute. But you might ask, why wouldn't I sign up for the new LucidLink? K. The one that we've kind of announced and been talking about, and that's because it's not ready for enterprise. K? The great thing about LucidLink Classic, enterprise or otherwise, is it is gonna benefit from the same upgrade and feature path of the new LucidLink. So coming next year, beginning next year, we're gonna have the Filespace update tool, the upgrade tool. Now notice I don't say migration. What that means is you don't have to physically move data to benefit from the features that will come to the subsequent versions of three point o or LucidLink as it's now known. That includes the new global user model. It includes the web client, the new desktop client where there's a kind of a newer experience of feature parity between web and desktop as well, much simplified onboarding. There's new pricing models, for starter and business packages or enterprise. You know, you can continue what you're you're doing today. Really important, macOS installer. There's no kernel extension, it's called, which it basically means you don't have to even reboot. You don't have to change security settings. You install it and go. No reboot required, which is amazing. We've got improved link sharing, which means internal to other LucidLink users. They're now web friendly, so you can click them. You know, previously, they were Lucid what they called Lucid links, but these are HTTP links. You can click them. There's full encryption in line in the links as well, so lots of great stuff there. Two massive things. We've got Android and iOS mobile apps coming that will allow you to read your data on your mobile devices and upload from from them as well. There'll be web based access to your data. There will be browser based upload. There'll be external link sharing, which is different from improved link sharing in that you can share with people that aren't members of your file space. You know, if I wanna generate a link, just send it to one person, you know, and I want them to download that file, you can gonna be able to do that as well. From the enterprise perspective, you're gonna have SAML based SSO, MFA or multifactor authentication, again, to further enhance those security features. Following all that, we're gonna offer AWS specific capability, things like tiered storage architectures, which will give you the ability to have hot to cold data within a single file space. Again, the LucidLink Classic Enterprise in AWS will be the only classic product that will upgrade to support that tiered storage capability. We'll have SDKs. We'll have APIs, and we'll have improved, portals and management for for channel partners as well. So, basically, to benefit from the AWS egress free enterprise file spaces, you don't have to to wait for the enterprise features to come to three point o or LucidLink. Start today with LucidLink Classic, and you'll get all of the great features of the new LucidLink as well, which is brilliant. So there we go. We've had a good overview of what's different between the new LucidLink and classic enterprise and all the great features that that we've got in the the more established product there. Are there any questions, Gugana, that I should address or that you can address? Yes. So I'm going to group the questions a little bit, into more technical, and general questions. And then there are a couple of more specific workflow, questions around different applications and media management. So let's start with the more, general questions. Alastair here is, saying that their their use case is, four hundred users, all into one spales file space, with terabytes upon terabytes. And the question, here is, is this the best practice or is it better to split into different file spaces? Well, I mean, if you ask Gagana and I, Alastair, also, you need multiple file spaces each with terabytes and terabytes and terabytes of data and thousands of users, obviously. But there's no technical reason why you would have to do that, to be honest. You know, some of our largest customers have thousands of concurrent users and petabytes, multiple petabytes of data in their individual file spaces. It's really down to the workflows that you're running or cloud diversification that you might wanna be putting things in different places for that. If you wanna kinda go go through this, by all means, reach out. We can we can set up a call to dig into it. There's no reason why your Fireflies won't keep scaling. Alright? We will scale to support terabytes and terabytes and terabytes and hundreds and hundreds of users. However, there may be some cases that you would wanna do that, but I wouldn't say it's for a performance or for a capacity, kind of concern. It might be for things like, you know, policy about keeping data within a certain country for certain customers, or it might be around some of the latency that some of your users further away, perhaps in more rural, connectivity zones might get better experiences. But there's no technical reason to do that. But feel free to reach out. I've got your email. I mean, good to see you on the the webinar. We can chat about that. But, no, it will scale. Thank you. Another general question, about our technology. Is a CDN involved? The answer is no. That is correct? Yeah. We use our proprietary protocol, for data streaming and or data compression. And then, yeah, Alex, maybe you can cover more, but, there is no CDN involved for the stream. Yeah. The EN would would usually be used to store regional copies of the data to provide lower latency access to people that are far away. And you would have to deal with the issue of managing the replication or the update, the time to live, life cycles of the blocks that you're pushing out there. We don't do that. We are the client application on the ground, the AWS data center where the data is, and there's nothing in between. There's no gateways. There's no regional appliances. There's no caching on remote servers. You have intelligent caching on the client side. So previously accessed blocks will come from your local cache, your LucidLink cache, which can be anywhere from a hundred megabytes to ten terabytes. And that does things like mitigate challenges of low bandwidth or high latency. But all data is sourced from the cloud. It's the single source of truth. There's no regional kind of publishing or storing or replication of data in order to provide access to, the the clients. It's client storage and that's it. Thank you. So another question that popped up, while you were showing the, access and permissions, flow. Is there an API for user and permission controls? There there isn't an API yet. There is a CLI. So you can anything you can do in the GUI, you can do through the CLI. So you can programmatically change permissions, you know, grant them, take them away, modify them. The API, the SDK will include that capability, once these filespaces upgrade with the with the tool that we're gonna release next year. And that will include other features as well, like programmatic access to data, not just administrative calls to change or create users and so on. But as I say, you can do it through a command line interface today. Thank you. And one last technical question, then we can, move into the more workflow related ones. So, Dennis is asking, or maybe it's a it's a statement or agreement that there is no partial restore from the cloud. I think this was more related to the snapshots workflow. So I guess the question here is, is it correct that we we don't offer partial restore statement? Yeah. I mean, we we we can retrieve, a subset, you know, of a file. If you think about a a timeline file, like a video asset that is one hour long, okay, we could retrieve ten minutes of that file. You could clip ten minutes of that asset in a in a sequence timeline. So you haven't physically changed the file. You haven't cut ten seconds out. You would basically put ten seconds of that file on timeline. I could then send that project to Gagana, and she could open that sequence and hit play on that timeline open that project, hit play on that timeline, and it will play back ten seconds of that file. And it won't have to bring down the fifty nine minute fifty seconds, you know, before it or however you've chopped that up. So we can retrieve a subset of data from a file. Likewise, Gugana could then render that timeline using Adobe media encoder or whatever she's choosing to use it. An AME media encoder would go, right. I need that bit of data just like all of the file is already there. So in that sense, we can provide partial access to temporal files. Again, it could be like, you know, page fifty of an InDesign layout. Right? It doesn't have to be video. Some some assets you need all of it. Like image assets, you need the whole thing. Video assets, audio assets, paginated assets, you can pull down different parts of it. And that's part of the unique, technology behind LucidLink and our our ability to do that. So yeah. And a follow-up to that, what happens if you then need to trim it out? Yep. So if you need to extract that part of the file, you would use the the software to to do that. You know? AME or what whatever. It would just you would choose to render it. The software kind of thinks the data is already local, so it doesn't complain. Now we're we're kinda getting into some of the more technical aspects of how we do that, and we we have metadata that's very small that helps the applications understand which parts of which files it needs to pull. But, yeah, you could render out or clip out ten seconds of that one hour file, and only consume ten seconds of data on the client. And ten seconds of data would come down from the cloud, and you could upload it again or whatever. This is really useful and popular in some of our live event workflows. You imagine like a sports game. I'm gonna say football or soccer to some of you. Imagine you've got ten camera angles of a ninety minute soccer game. That's a lot of footage. Right? You got ninety minutes or more because you'll have half an hour either side and ten of them. And I make a three minute highlight package, which is one view one angle at a time. If I want Kigana to modify that edit, I don't want her to download ten ninety minute high resolution files. I wanted to load up a a three minute sequence that's made up of, you know, ten of those angles without having to do that. And then she could tweak it. She could overlay graphics, and she could render it out. And she would only need to down not that much. She would only need to stream out three minutes of footage, not, you know, ten times ninety minutes. So, yeah, really, really cool kind of clipping, render, export workflows based based on that. Thank you. And we can now dive in a little bit into, file and performance when we talk about, media workflows. So the first question, I'll bundle it with the second question. Does LucidLink, allow for raw camera, data streaming without proxies? Red, ARIRAW. Or is it best practice to generate proxies as well as source media on upload? And then there was a, another question who came in, which came in early that was what is the best practice for editors pinning data to edit in Premiere. So yeah. Right. Okay. Yeah. So there's no there's no, like, minimum bandwidth. You know? You you what you put in is what you get out. If you put in a eight k red or whatever and you try and play it out, you're gonna get it back. However, we can only deliver data as fast as the connection will allow. Right? So if you have a two hundred megabit per second Internet connection, it means two hundred megabit per second can fit through that pipe, basically, and no more because it's a physical limitation of your connection to the Internet. That means if your video has more than two hundred megabit per second bit rate, there's too much video per second to fit through your connection. So in in the example like that, the first time you hit play, you might get a sort of buffering effect as your connection physically won't allow that data down in real time. But because of that intelligent cache I talked about earlier, subsequent reads of that data will go at the speed of the local disk without requiring the bandwidth of your Internet connection. Again, this improves the user experience on low bandwidth connections. Now just think of it that way, bit rate of video, bit rate of Internet connection. I personally think it is good practice, and something really important you mentioned there, generating proxies on upload. You can generate proxies whenever you want. Okay? I I could upload a load of high res and say, Gugana, can you generate proxies? But in order to do that, she would have to pull all of that high res down to the transcoder to generate that proxies, which if she's on a slow Internet connection, probably isn't the most efficient way to do it. We're getting ahead. We could be generating proxies in the cloud on a virtual machine there, which which would be quite a cool workflow. But for that reason, yeah, you could generate proxies on upload, which means whilst you're uploading the high res, you generate proxies on the way through using the tool of your choice, whether it's media encoder or whatever. We're not gonna generate them. We can't even read your data, remember, zero knowledge encryption. So there's no way we can generate proxies for you. You would choose your proxy generation tool, and you would point the destination of the transcode to be the LucidLink fast pace instead of a local disk because it just looks like a local disk. And that's a great way to accommodate remote collaborators that might, you know, only need proxy, that might have low speed connections. You can always toggle. Here's a great idea. Right? When we talk about clipping that high res, imagine being able to edit your proxy timeline and go, right. I'm happy with the edit. Now I'm gonna generate export the high res. When you swap to high res and hit render, it's only gonna have to pull down the high res for the bits that you've put on the timeline. So you don't need to bring down all the high res in order to render the sequence. So you're saving lots of time. So proxies are cool. I like them. If you're happy to work with them, it does give you a lot of flexibility in terms of, what you share with collaborators, how much data you need to pull. So, yeah, cool workflow. That brings us into the pinning question, Gagana. Pinning, I didn't really cover that, but that basically allows you to precache your data from the cloud. When I hit play in Premiere, Premiere says, give me the data. Give me the data. Give me the data, and we deliver it in real time. Now I can preempt that and think I'm gonna be working on this project or this sequence or this whatever. I'm gonna precache, which means I'll right click the asset in the file space in finder or file explorer. There'll be an option to say pin. When you hit that, LucidLink knows they want the data, and they will precache the data into the client side cache before the application requests it. So that means when I load premiere, it doesn't matter if it's eight k or sixteen k or proxy or whatever. The data is already at my end of the connection, and the application can access it at the speed of the local disk. So you can do that. Pinning also locks it into the cache, which means it won't be evicted when your cache fills up. Like I say, it can go up to ten terabytes if you want it to, and it will intelligently manage that, removing the least recently accessed part of of cache data and replacing it with a b. So pinning locks it in, so it's never, evicted. Interesting. Another thing I didn't show in Premiere, and you can Google this, look it up, is our Adobe Premiere panel, which allows you to pin or precache assets from the file space based on what's been used in the sequence. So you let's go back to that sports analogy. Imagine I've got ten camera angles in my in my project bin, but I've only got two across my timeline. I can I wouldn't need to pin or precache all of those files? I can just just select the ones that are in the sequence. And our panel lets you do some clever stuff like that. So check that out. We also have that for after effects. That's right. Just mentioning. Alright. So last question so far. How is, asset management handled in this workflow with LucidLink? However you wanna do it. You know, like, you can choose whether to use Premiere, Resolve, Final Cut, Media Composer, Microsoft Excel. You can put spreadsheets in it. It doesn't really matter. Any application is gonna work with it. You can set your own choice of media asset management solution on top. Now that might be a client side solution. You know, there's no middleware, no server infrastructure, something like Kyno or Adobe Bridge or some application that allows you to sit on top of a local disk and add tags or whatever you wanna do. Right? Or it might be a more enterprise level microservice cloud or on prem solution. Now most of those MAMs will have a data mover service component, you know, to move data from a to b. It might be put it into a traditional s three bucket. It might be to interrogate an on prem NAS. Well, guess what? If you install the LucidLink client on that server, on that data mover host, it mounts a drive. You know? If it's Linux, it's, you know, slash whatever. If it's Windows, it's l drive. And you tell your ma'am, index the l drive or send a file to the l drive or whatever you wanna do. It's just another disk for the media asset management layer to, to index. So if you're using an Avid panel, like, Interplay or something like that. So we we we can offer some avid workflows through some of our emulation partners that will present LucidLink like a Nexus. I don't know about whether Interplay is gonna index. Actually, I'm that's something we'd have to kinda dig into if that's what you're talking about anyway there. But we do offer media composer workflows to present the LucidLink Filespace like a Nexus in which will give you bin locking and stuff, and stuff like that. But, generally, if your MAM or DAM or PAM or whatever you wanna call it can sit on top of a local disk, can index it, can use it as a destination or as a source of data for archive movement, whatever workflows, then you can do it with LucidLink as well. Going back to the pinning questions, is there a best practice to pin or not to pin? And I think here, what we were saying is if, it depends on what you're trying to do and how fast your connection is. You shouldn't always have to pin your media. So there is no best practice that will say you should always pin your media. Yeah. Go ahead. Yeah. I would say try it without pinning. It's designed to stream. And, you know, most of the time, it just works. Is that should be like a slogan, and that's what our customers tell us. They're like, wow. I mean, it just works. Now you you gotta be kind of realistic. If you say I've got some eight k red and I'm connecting on a ten megabit per second, you know, Internet connection, you're not gonna have a great user experience trying to stream back super high resolution high bit rate video because it just simply doesn't fit through the pipe. In those cases, you you you might wanna pin. And in fact, here's a good example. You could pin somewhere else, right, where there is a connection, and then you can get on a train. You can authenticate to the fast pace through a hot spot or something with a very low speed connection. And that means the metadata, which is very small, remember, is going through the the connection to the Internet, but your file data, the video playback, that's happening from your your cache, your pre pinned cache, which you've done somewhere else. So, I mean, it depends on the workflow like Gigano says. Another great question here. For working with a global team, is it best practice for teammates to upload to an s three instance nearest to them? For example, if you're in Tokyo, upload to Tokyo workspace and then collaborate in LA, a collaborator in LA can access. Any tips for managing latency with global teams? I would I would say, again, it kinda down to the workflow, down to the infrastructure, the latency to the users that will feel it the most. And in this example, it will be the editor. Alright? If I'm uploading something, the user experience of high latency isn't really gonna change my experience. I'm dragging and dropping. I'm doing something. I'm uploading. If I'm a video editor and I'm scrubbing, moving around, I will feel latency be more apparent to me in my user experience of the application. So in that example, I would say you wanna get the data close to the editor rather than the uploader. But equidistant between users, you know, is generally kind of what you wanna try. We do have many customers operating in three or four continents, you know, and we have Hong Kong, New York, London, all collaborating. And they might choose to put it in Germany in, like, the big, Frankfurt data centers that we're adding through our AWS partnership, or they might choose to to put it somewhere in the middle. You know? But in that that specific example, I would say the uploader will feel latency less than the editor. I am dropping a link again, for our demo page where you can request a demo that would be more tailored to your workflow, and the discussion will be more specific to what, your organization and your team needs specifically. If we weren't able to answer, though, any, further questions, please feel free to connect with our team. We we love talking to the customers, potential customers, or just people in the industry. We're at time. Thank you so much everyone who attended for your engagement, during the presentation and for all of your great questions. And thank you so much, Alex, for hosting this. It's my pleasure, Gugana. Nice to see you, and thank you everybody for joining. Follow-up with any questions. Thanks. Bye bye.