Name: Instabase Insights April 2025 : Exploring the Latest Features & Trends
Uploaded: 2025-04-24T16:01:04.331Z
Duration: 40 min 44 s
Description: Instabase Insights April 2025 : Exploring the Latest Features & Trends

Transcript for "Instabase Insights April 2025 : Exploring the Latest Features & Trends": Hello. Hello, everyone, and welcome to another installment of the Instabase AI Hub advancements webinar series. My name is Rachel Datlowe. I'm the senior customer enablement program manager here at Instabase, and I'm so glad you'll be joining us for today's session. Just a few housekeeping items before we get started. One, today's session will be recorded and shared with attendees, so you'll be able to share it with colleagues and rewatch as needed. Two, if this is your first time experiencing Instabase AI Hub, give us a shout in the q and a. We'd love to welcome you with some additional AI Hub fundamentals resources. Three, if you're an experienced user of AI Hub, I've got a collection of product experts on standby waiting to answer all of your questions. Please hit us up using that q and a function. Four, we're also going to have some time throughout today's session for live q and a. So if we don't answer your question in the chat, stay tuned. We may be answering it live. Five, we've got some fantastic resources to share with you, so keep an eye out for those throughout today's session. And lastly, you might have noticed we've thrown up a poll on the side of the screen asking how familiar you are with AI Hub. Please go ahead and share your feedback with us. We'd love to hear what your experience has been like. Thanks, everyone. Take it away. I'm now going to introduce our leaders of today's session, Brian Choe, our technical trainer, and Danny Lan, front end engineer. Thanks, Rachel. Awesome. Well, it's good to see everyone even though I can't really see you, but you can see me. So maybe it's good to be seen. Thanks anyways for joining everyone. I'm I'm here today with with Danny. He's a front end engineer. He has a lot of unique experiencing experiences working very closely with their product, being the hands, and the keyboard behind a lot of what you enjoy today in the platform. Before that, quick intro, as Rachel mentioned, I'm a technical trainer here at Instabase, so it's my job to enable you. And, again, Danny will be joining us, in that journey today. So I'll hand off to Danny for an introduction. I'm a software engineer at Instabase. I work on BayHub Build, which we'll be talking about a good bit today, and, excited to be here. And back to you, Brian. Awesome. Great. Well, let's dive in to today's topics. So what are we gonna cover today? What we'll be doing? Let's take a look at the list here. So as most of you know, today's session is focused on highlighting new features, new developments, advancements, in our product. And so we'll be focusing on a few of those, changes, bullets in yellow. And then as you also may know, we have a hot topic where we cover something that is hot and trending or we think will be very helpful to our customers. And, actually, Danny, will be leading that portion talking about the App Hub and the marketplace, which is a really awesome way to quick start your solutions. So we'll take a look at those two today. And we'll pretty much start with a new feature spotlight. So, again, covering the the newest latest changes, and then we'll dive into the hot topic as the last part of our segment. As a reminder, throughout the session, if you have questions, definitely share them. We're eager to answer them. But, yeah, let's go ahead and get started. But before that, what is AI Hub? A reminder is always helpful. And in case you're new, that's why this is here. So let's go over quickly what AI Hub is, and we'll start with a bullet summary. So the number one takeaway that you should have, when it comes to understanding what is AI Hub, it is an AI platform. Obviously, that's not enough to to use it, so let's go a little bit deeper. AI Hub is an AI platform, and it empowers users and businesses such as yourselves to automate, analyze, and search your unstructured data at scale. Ultimately, we allow users to build powerful solutions using mostly simple natural language and an an intuitive interface. The reason why I say mostly is because you can still do all of that, but we also have API functionality as well, so it's very customizable. And now we're just gonna visually cover exactly what we just talked about. AI Hub is a platform, and we really help, users by empowering them to tackle these three primary workflows, automate, analyze, and search. And then within that, we have functionality in our platform, you know, surrounded, surrounding these workflows. Great. If you have any questions, again, feel free to pop them in. But now we can get back to today's topics. So, again, new feature spotlight and hot topic. Up first, let's cover new feature spotlights. So in release twenty five twelve, we had this new feature come out. And this is something that folks are probably quite familiar with, being able to delete their runs, right, as they're using AI Hub. And now you might wanna delete runs for a, you know, a variety of reasons. Maybe you wanna declutter your environments, which we'll take a look at in a second, or we want to exercise, you know, best security practices, just by deleting runs and any sensitive information that might be associated. So, you know, instead of doing all of this manually, we now have the ability to use deployments, which we'll have a quick reminder of. But these essentially automate, all of the processes, that we that we want to use in our automation solutions. I know a little bit meta there, but we can configure them to automatically delete runs, instead of, again, having to do that manually. So let's take a look in the platform to see what that looks like. So here, I'm on the AI Hub home page. So if you have an account or maybe if you don't have an account, either way, this is what it would look like for you. And so I'm signed in right now to an enterprise account. If you're a commercial or enterprise, this will pretty much look the same. And what I wanna do now is go into my deployments and show you the configuration page so we can start to take a look at how we can configure deleting runs. Before I do that, let me actually just go ahead and show you the deployment runs. So I'll go into workspaces, and then I'll go ahead and click on the deploy tab. I'm in the development workspace. This is just something that I've named. And then I'm gonna click on that deploy tab. Now I can see all of my deployments. And within this one, if I open that, I can see a bunch of runs. Now if I open up this run right here, for example, we can see that we have some mock files. But imagine that these files, you know, maybe they're sensitive, right, and we want to delete them, or maybe they're old, right, and we don't need these results anymore. Maybe we've had quite a number of iterations on our underlying app, and it's just time to get rid of some runs. So what can I do to delete that? So I'm gonna go ahead and click back here. So one way to delete this run is I can go ahead and click on this check mark. Maybe I wanna delete another one, and then I can click on this actions button and do that. Right? That works. But, you know, again, let's automate this process. Right? So if we go into the deployment configuration, if I scroll down, we have this new setting here. If I click on the edit button, I can now toggle on enable automatic run cleanup. And now I can specify the number of days after which we want to delete runs automatically. So here I can just leave it at ninety, and then I can click on the delete source files toggle here as well. And so what's really helpful about this one is that if, for example, you have a file sent to your destination, right, after you've processed them, we can off optionally also delete those too. So these will be in whatever default drive that you have configured, but this is optional. So then I just need to click on save. And now ninety days after any run, they'll automatically be deleted. You can always just, you know, come back in here and edit this as well. And just general rule of thumb, you should probably keep, the number of days to be longer than however, long your SLAs are, when it comes to human review. If you have questions about this, we can dive a little bit deeper, but just a rule of thumb for those that are familiar. Great. So let's go ahead and actually turn this off because I use this for demos, and we'll get back to our slides. Again, if you have questions, pop them in the chat. Danny, is there anything that you'd like to add here or you think is helpful? No. I think what you said is great. Awesome. Great. Let's go through to our next feature spotlight. So this is another one that came out in release twenty five dot twelve. This one is big. This one will affect nearly everything that you you touch, in AI Hub, and these have to do with ergonomic changes to the UI and the UX, so user interface, user experience. And it just makes everything, like all of the different flows that are associated with developing an end to end solution pipeline, more intuitive, more connected, and ultimately more productive. So I'm gonna start with a visual overview, kind of using these slides here. But you can see a screenshot on the right, of a page where we're looking at an app. And so we can see at the very top there, we have the workspace and hub visible now. So at any point in the platform, you should be able to quickly go back to the home page or workspaces or the hub. Very, very, helpful there. And then we have the rest of the changes. So we have the app interface itself. Whenever you're looking at an app, for those that are familiar with older versions, looking at an app page, you'll you'll notice right away that this is quite different and and hopefully easier to use here. And then over in the right corner in red, this is what I like to call the journey mile marker. That's not an official statement. That's just what I call it. But it's really easy to understand where you're at in the development process. And you may have seen that before, but let's take a look, in the platform, and I'll just give you a run through. And then I guess here's a sneak peek in the other for the next topic, but let's go back to AI hub here. And so the first component is this top level navigation bar always present now. So wherever I am, I can always go and access these critical spaces. Given a little teaser of our hot topic here by visiting the hub. Okay. And then let's take a look at an app. So if I actually open this project, I know that this project I've created, it's meant to process driver's licenses. I've also created an app. And so, normally, what I'd have to do is I'd have to go back into the hub and look for the app. But now even though I'm in this project, I can just go to this, navigation kind of mile marker journey mile marker, and I can just click on the app pill, and that'll take me to the associated app. So very helpful. And then if I wanna go back, just click on the project pill. And let's say I make a change. So I'm just gonna go ahead and add a quick field here. Go ahead. I'll just leave it as a text extraction for now. But notice that I've made a change to the the project, and so, you know, the app, will probably need an update. Right? So if I go ahead and click on the app, here we can now see I have a a prompt here, like an add version button, saying, hey. You've made some changes. Why don't you go ahead and make a new version for your app? So it's very, very intuitive, very helpful to let me know what I need to do next. There's also a few other things. We have a number of check boxes here. And so these are kind of like a checklist of things that you may want to do for your project or your, your app. And you don't have to do them all, but, you know, these are just recommend steps. Basically, just trying to make it easier for, end users to understand what it is they need to do or what they can do. And so we have the same thing with, the apps as well. I've already done everything in this example, but this is really helpful. And then finally, if we want to take this app and automate the app even more by automating the upstream and downstream components, so the ingestion of files and the output of results and a lot of other aspects such as human review, the deleting runs, so on and so forth. And we can actually go ahead and click on the deployment pill, and this will quickly take us to any deployments that are associated. If you don't have one, you can create one here. And, again, we have a number of recommended checklist items to go through. So this is really helpful. This will make it a lot easier to understand where you're at in the process, just by using these. But if we dig in a little bit deeper, right, if we go back to the app page, you can see it just takes us to the overview of this sub menu here, which is already pretty helpful. And this makes it even easier even more. Right? So if we go in, like, we know we can create a project, create an app, and then deploy. But there are other things too that we can understand quickly here. So here we have an overview of the app version, and then we can see our app runs, including app runs through deployments. You can also see, runtime versions and app versions. And then importantly, right, we can also see accuracy tests. So everything is now just kind of connected, roped together, and kind of put in this sequential journey flow, and it should just make things a lot easier. Danny, any any color there that I've missed? One thing I wanna highlight that I like is that the the settings pages are are put in, like, a consistent location. So if you click on the top left there for the project or for the app, you can go to the settings. So both of them have, like, the same sort of drop down there that you can click in, and it's on the same spot. Yeah. That's that's a great callout. Yeah. And and and I like the word consistent there that you've used. That's really a primary driver behind a lot of these improvements is we wanted a more consistent experience, and less having to find where things are based on what flow you're in. For sure. Great. So, yeah, we're really excited for everyone to try this out. I know that folks have been trying this out. It's it's been out for a couple of releases now. But, yeah, if you have any questions, post them here or follow-up with the team. Alright. Back to the slides. Go through, yeah, another feature here. So this one, we've kind of hinted at. We've already kind of touched on here. And we've actually covered this in a previous session. So this specific development, really just talks about having automatic upgrades. And we just wanted to give you a reminder here that, runtime versions will be automatically upgraded. So we'll we'll start with the actual what is the change here, and then we'll go through a little bit of a reminder of what that is in case folks haven't seen it. So at a high level, though, the AI runtime, has to do with the components, the intelligence features that are driving your automation solutions. And so these, we can configure our solutions to automatically upgrade to these latest components, right, that we'll call an AI runtime version. And so we have the following expiration schedules, for AI runtime versions, meaning that after these periods of time, they will be automatically updated to use the latest model. So for our commercial customers, you will have four weeks. So when you are deploying a an app and you have certain runtime version, right, so it's using the latest and greatest at that time, intelligence features. Let's say a development comes out where, you know, we've improved one of these components and, hence, we have a new runtime version, then well, there will be four weeks, to test and evaluate the new runtime version before it's automatically upgraded, to use the new runtime version. I know that was a lot of words. But yeah. So if there's questions, definitely feel free to to ask. And then for enterprise, right, all of those same words, except instead of four weeks, there will be six months to test and evaluate your apps using the current run time before they go to the latest and greatest. So this actually started, April 14, and any AI runtime versions, between one point o point o to one point o point seven, you know, now have this countdown. So keep that in mind. Go and test your apps, and, you know, make sure that, you know, you're capturing feedback, letting us know, and that they they're working for you. Okay. So as promised, a quick overview of AI runtime, what that is. Right? So the problem that we're trying to solve is that intelligence features and functionality such as LLMs are constantly evolving. And we want you, our customers, right, and users, we want you to have the latest and greatest, but we don't want them to potentially break or, you know, decrease the efficiency and performance of your apps. And so what is our solution to this? Is we want allow we want to allow you to test these new changes. So whether they're underlying models or maybe system prompts or prompt wrappers or any improvements to the execution pipelines that underlie our intelligence automation solutions. We want you to be able to test that in a safe and controlled manner, and so that's what this is all about. Danny, anything to add there before we move on? We will nothing to add. I think that was good. Great. Thank you. And let's go ahead and move on to the next one. So this one is our last, update here before we go into the hot topic. This one is pretty specific, to certain users. So if you have configured, an s three bucket, so an AWS s three bucket as an upstream integration or downstream integration, if you have this configured as a data source for your solutions, then you will be familiar with the terms that I'm using here. But we have IAM roles. Right? And so you can add roles, and you can actually reuse them. But for security and compliance and just giving users a little bit more granular control, we're we're limiting IAM role reuse to the workspace level. So what does this mean? If you've set up and you can see a GIF here, a little bit small, although. But if you've set up a data source, right, an s three data bucket, and you have an IAM role associated with that, if you set that up at a workspace level, then you can only reuse that role, the IAM role, at that same workspace level. Now the exception is if you add an IAM role and you're connecting a drive to the organization level, right, meaning it encompasses all workspaces, then that IAM role is available to reuse for all workspaces for entire org. So just keep that in mind. If you need to set up an IAM role, you know, for the workspace level, then, you know, naturally, it should be restricted to workspace level sharing. So just keep that in mind. If you have questions, feel free to throw them in in the chat. But let's go ahead and switch gears here. So that was that was really the the highlighted features spotlighted features for the latest releases. Yeah. Now it's time for our hot topic. But before we do that, some q and a. What do we got? Great. I'm back. It's time for a quick little q and a break. A few questions for the two of you. The first one is from Greta a. If the source files are not deleted, can they still be accessed? And if they can, are there any errors while viewing given the runs, logs, and results are deleted? Yeah. That's a good question. So let's see. So if the source files are not deleted so we're talking about configuring run deletion policies in our deployments. So as you may recall, in the bottom right or bottom left, there was that, like, toggle checkbox for deleting source files whenever you delete a run. So if we are leaving that off, right, so we're not deleting source files, can we still access the files? And then are there any errors while we're viewing runs, logs, and results? So the source files will still be accessible if we don't delete the source files, but they're going to be stored in the customer's default drive. Right? So we can still access them, but we're not going to see anything through the AI Hub interface. And so, also, there'd be nowhere to see any errors. So, hopefully, that answers the question. It's a good one. I think it does, but I'll stay tuned and let you know if, we get any follow-up feedback on that one. Our next question is from Datlowe. If a run is still in review, will this also be deleted? Yes. So, yeah, that's a really, really good question because, you know, we want to be able to review our files and, you know, it's an important consideration. Yes. So regardless of the status, whether it's in review, it's completed, it's in progress. Right? If we are deleting a run, manually, right, because it's the only way to abort a current run, then it'll be, you know, it'll be deleted. And then regardless of status, if it's completed or in review, then, yeah, those will still be deleted as well. So that's that's where it comes back to that recommendation where we want to set our expiration or automatic run deletion time period, the number of days, to exceed whatever the SLA is. So if you have an SLA for, you know, hey. Reviews need to be done in thirty days. Right? Which might be quite long, but let's say, just for example, thirty days, you don't want runs to be deleted, right, in in fifteen days. Like, that doesn't that doesn't align. So you really ideally want to see, yeah, the number of days to exceed the SLA. Good question. Yeah. And then this last one is kind of open ended, so I'm curious to see where you guys go with it. It's from Margie, and it just says, anything I should be extra careful about with the run stuff. I'm guessing that this is because we've we've been talking about it a lot today, and I think we may have answered some of this with the other two questions. But if you have anything else to add. Yeah. Anything we should be extra careful with the run stuff. I guess yeah. That is that's quite an open ended question. You know, security and and yeah. Security is is, you know, based on whatever your company rules are. Right? So at a high level, if you have sensitive documents or you work in a very protected, industry, let's say, finance or health care, and you really need to control, you know, the privacy of your documents, then, yeah, just understand that you can delete files. Right? Like, obviously, we need to access them as an organization. Right? So you may need to access them when you're performing reviews, things like that. But, you know, they're not retained forever. Right? And, you know, like, it's in your hands. Control is in your hands. Right? Your files are secure, and you can delete those. So, Danny, is there anything to add to that, kinda open ended question there? That's a good one, though. Yeah. Not much to add on my end. I think that's that's everything. Alright. Well, before I turn it back over to the two of you, I'm going to briefly engage in a bit of shameless self promotion. So I wanna take a moment and direct you all to our AI hub videos. You may have already watched our fundamental series. These new videos are designed to walk you step by step through everything you'll need to know to set up and run successful deployments. I've, I've linked it for you there in the chat section, so please click to visit, watch, bookmark, and share. With that, I'll be popping back behind the scenes again. I'll see the two of you later. Thanks, Rachel. Awesome. So without further ado, I'm gonna pass it over to Danny to cover a hot topic, which is, again, the App Hub and the marketplace. Do a quick little introduction of the topic, before handing off to Mike. So the App Hub and the marketplace, Danny is gonna walk us through what those are, but at a high level, we're going to discover collectively what's possible in AI Hub, right, using and customizing various available prebuilt automation apps, which is where, they live, right, or in the hub in the marketplace. So take it away, Danny. And I'll actually stop sharing so you can so you can share screen because I know you got a live demo for us. Yeah. I'm gonna jump into the AI hub, then we can see what the hub in marketplace looks like. So let me go ahead, and we can find the right tab. Nice. So here we have AI Hub, and you can see at the top, we have the workspace and hub bar. So we can jump into the hub, and we can see all the sort of apps that are available to you. So you can see apps that you have created, apps from the organ your organization as well as apps from the marketplace. So marketplace apps are apps created by Instabase to address what we've seen as common use cases, common, document types that users want to extract. So you can imagine as, let's say, recruiting, you might want to have a resume parser. So you can see that try to classify documents as resumes if possible and then extract these information informational fields from these documents, and you also see some sample files to see what types of documents could be handled by the this resume parser. We also have a number of tax forms that are, you know, commonly seen and some more general use cases not for specific documents. You can have doc summarization to get information from long documents and doc translation. So if you have documents in different language or if you wanna change it from English to another language, you can select the input language and output language and translate your documents. So these are all sort of, examples of things you can do with our Instabase marketplace apps. And I'll dive into a specific use case if we want to do, say, pay stubs. We have a US pay stubs app. But I'll pause for a second if you have anything to add, Brian, or we can continue. Yeah. No. This is this is great. I think, you know, I've I've actually admittedly only recently learned about the doc translation marketplace app. And so the fact that, you know, not everything in here is, you know, just like another automation project. Right? Which are you know, I don't wanna discredit them. They're powerful. Right? But we have something like this where we have a tailored UI to to handle this case. Like, this is very cool, and and we've worked with some pretty impressive, like, in terms of length and complexity and, you know, in in a different language even, document, and and it's worked really, really well. So, yeah, explore explore this marketplace. There's, also chats too, chat bots. So this is really, really cool. Mhmm. Awesome. So, yeah, let's jump into a more specific example. So not only can you just try out the app, there's also the ability to customize the app, which we'll talk about in a second. So we can test it out first. We can use the sample files that are already populated here to create a sample run, And then this would look exactly the same as, a normal run where you upload your own files and test that that out. If if we jump into one of these, we'll go into the human review interface and see the information that gets extracted from this document. So this document doesn't have employer address, so maybe that's not there. But, you know, as, you know, maybe working in payroll, you'd want to extract information from these payslips and then compare that to internal information to make sure it lines up. So we may want to customize this a little bit to add information that we need or move fields that we don't need anymore. So go back. And from this page, we have customized app. If we open the app, we can also customize here. So as you can see, we'll get a copy of settings, sample files, process fields, validations. So we can create a new project called Danny Lan's US pay stubs that extends this existing app and make our own changes to it. So we'll get a copy of everything here. So we'll have the class called US pay stub. We'll have all this information, all these fields that will be used to extract information, and we'll also get a copy of the sample files here. So one thing to note is that, if you were to customize your own app and share that with your organization, those sample files would be filled with everyone in that organization. So just wanting to be careful out there. And in addition to classes and field, which is the schema, You also get the validation, so it rules to determine whether this information should be accepted or if you wanna human review it to take a look at it. But now this is done, so we can jump into the project and see what it looks like. So first, it will classify and determine if these are value as pay stubs. And I think we're looking at this one, and it'll go ahead and extract information. And maybe you want to add a new field here to get the pay period. So So we can use a derived field type, which gets information from other other fields. So we can say return the number of days between begin and end. Let's say we wanna confirm this and run that field. And let's say we have some fields that we don't need direct deposit tagline. We can get rid of that And just really customize this app for your specific use case and your specific documents. So customizing apps just gives you a good starting point instead of starting from scratch, and it gives you a good, a point to continue with, okay, your use case or your workflow. So let that run for a second, and I'll pause again if you have any comments, Brian. Yeah. Yeah. No. This is really cool. Like, we you know, just as a reminder. Right? Like, we've we've taken an app that we've seen in the marketplace. Like, hey. I like that. Right? I want I wanna use that. And so we could. But, you know, here as Danny is showing, right, we can create a custom field. We can customize it. And so we just make a copy of it, give it our own name. Right? And now we're able to configure our own customized tailored solution, but we're skipping a lot of the work because it's already been done. Right? Mhmm. And then what's really cool is that this app, for those that might be unfamiliar with AI Hub. Right? Like, we're configuring this project to handle, you know, a variety of pay stubs. So even though what we're seeing now are these three examples, these are just examples that we're using to make sure that our app, our solution, can generalize these extractions across a variety of pay stubs. And so once we turn this into an app, then it can process tons of pay slips. So, you know, a a real real accelerator, right, for for solution development. Exactly. Great point, Brian. And you also get a copy of any settings. So if you wanna see this particular app, we'll be able to recognize tables, so we can also recognize check boxes. This information is copied from the app that you customized. So here's the app. Pay period. We got the number of days. That looks good. And we can create our own app, based on this app, and we can even make this customizable. So this would allow anyone in the organization that you're in to further customize the app if you want to do that. And we can have these files again as sample files so we can test that out and go ahead and create that app. So this is sort of the reverse process where before we were customizing app, now you make an app that can be customized, and other people can use that. But after we create this app, it'll just be a normal app in the app hub that works exactly like any other app, and you can use that in your in your use case and do whatever you like with it. So now that that's done, we can go ahead and test it out. We can add some files that I have and just run that normally. And I won't, wait for this to to finish that. It'll take a few minutes. I have another copy that we can look here and see the app run. And here I've tossed in some example pay stubs that, you know, look like US pay stubs, and you can see the information was extracted. And, we got pay period, which is the new field we added. So, basically, very easy to start with an app that you see in the marketplace, make some changes to it, and then quickly repackage your own solution and really accelerate that process. So, yeah, I think that brings us to the end of the demo, and I'll I'll bring it back to to Brian. Awesome. Thanks, Danny. Actually, I've got a question. Mhmm. So can we look at that first example there? The first, sorry. If you go up to one file up in the yeah. Right there. Yeah. We can see that this is, what we're calling a distressed file. And so we can even handle this pretty elegantly. Just for folks that haven't seen it, you know, surely, we handle unstructured documents, so definitely try this out. We're Sesame Street Plumbing, have you been there? No. Not personally. It's, I hear good things. Yeah. That's a good point. We have digitization process, which you can see, pull this information even if it's, you know, not perfectly clear text and, uses that for for the extraction process. Great. No. Yeah. This is this is really powerful, very helpful. You know, I'd imagine that some customers, they'll go through the marketplace and and a lot a large majority will will see what they want. But I imagine there might be some folks that are looking for something. They find a few things and, like, oh, I really want this, like, other thing as well. Mhmm. So I just wanna give a reminder here for the group that, you know, we are open to all feedback. We're actually actively, collecting signal, you know, from our customers. We wanna hear what it is that you want, what you're working with, and then our teams, responsible for the marketplace. You know, they're they're they're eager to to get to work on that. So definitely let us know. But, we'll invite Rachel back on the stage, and we'll we'll do some q a q and a. Alright. Hello. It's me again. Before we get into the questions, you might have noticed on the far right of your screen, a quick poll just popped up. We would really love to hear what you thought of today's webinar. It only takes a couple of clicks. There's just one question. It is completely anonymous, and it really helps us help you. So please let us know, with a couple of clicks if today's session has been helpful. And now onto the questions. First, from Mary m. If you copy an app using an older runtime version, what happens? Is it updated? Yeah. So I I think I can tackle this one. Danny, feel free to jump in if you've got additional insights since you're, large parts of the magic behind that that entire functionality. But anytime you look at the marketplace apps, they should be using the latest runtime version. So we have teams dedicated to making sure that these are always working right properly and efficiently and compatible with the latest AI runtime versions. So if you take, an app, right, and you copy it, it'll automatically be using the latest runtime. So unless the very next day, there's, like, an update to the AI runtime or in the next hour or so, you should always be up to date. So you shouldn't really have to worry about that. If that does happen, you can either, a, you know, make the changes yourself to make sure it's compatible, or probably the easier way is just create a copy of it again. But, you know, it it's really kind of up to you. Alright. Next question. This one is from Denise w. Are there any additional fees associated with using the prebuilt apps? No. I don't think there are any, you know, specific fees like, oh, you if you've customized an app, that's gonna cost you. So, you know, we it's it's gonna be like you're creating a a project. So it should be normal pricing all around. Okay. Running the app is the same as running one app that you've created, and then customizing that would just turn into, like, a normal app. Okay. I suspect this question was coming from a position of, like, you know, normally, if you're on your phone, you're buying things in, like, the App Store, and so I think they just wanted to make sure. Oh, I see. Yeah. Great question. Okay. Excellent. Q and a is pretty light today, guys, which I'm pretty sure just means a job well done to the two of you. And that almost brings us to the end of our time today, but a couple of quick housekeeping items. I've just thrown a link in the chat. That's going to let you register for our next two sessions, May 21 and June 18. We're also going to be sending a follow-up email that's going to have a link to this recording of today's session. And again, it will also include that link to register for the next two sessions, May 21 and June 18. So keep an eye out for that. Thank you so much for joining us today. We appreciate your feedback. We appreciate your questions. And it's not too late for you to go in and fill in that poll, letting us know how satisfied you were with today's webinar. Help us help you. Thanks again, everyone. Thanks, all.