Name: Rocket Customer Webinar: Rocket® Terminal Emulator Web + Rocket® Terminal Emulator Mobile Lifecycle
Uploaded: 2026-02-18T17:31:47.055Z
Duration: 52 min 40 s
Description: Rocket Customer Webinar: Rocket® Terminal Emulator Web + Rocket® Terminal Emulator Mobile Lifecycle

Transcript for "Rocket Customer Webinar: Rocket® Terminal Emulator Web + Rocket® Terminal Emulator Mobile Lifecycle": Hello, everyone. Thank you all for joining us today. I am Evan Tackett in solution marketing here at Rocket. I I get to look after RTE and secure host access and and all of our emulators here. I am joined by the principal product managers, Barbara Ballard and Chris Lal. I am really looking forward to the session. There's a lot of exciting stuff happening in the emulation space here at Rocket, and all all of this really impacts you. So I'm excited about the journey that we're on, so I'm really looking forward to going through it with you. Just a little bit of housekeeping, we really want this to be an informative and engaging session. So if you have questions, feel free to pass along in the q and a panel, add comments and chat. I will keep an eye on those and make sure that we raise them so that Chris and Barbara can get some answers. And you should notice too later in the session, there is a email address, rocketconnectivity@rocketsoftware.com. That email address goes right to Chris and Barbara. So if there are questions that you think about later, don't wanna ask on the session, you're you're more than welcome to reach out that way too. So with that, I think I will go ahead and hand things off to Chris to get us started. Sounds good Evan. Thank you very much and thanks for joining today. Let's talk about what we're gonna talk about. So we're gonna start with the historical background, kinda how we got to where we are today at Rocket Software. There's been a lot of changes over the years in this industry, and we're gonna look at exactly how we got here, what the path forward looks like. So today, really, we're gonna be talking about our new solution secure host access. Customers wanna know about product life cycle. So for planning, so we're gonna talk about, you know, what it looks like product life cycle looks like for some of the heritage products And then going forward with secure host access, you know, how are you are we gonna support you? What's our commitment to you? Let's go and do that for a bit, talk about that for a bit. And then, yeah, we'll take questions during and after the presentation. First, a disclaimer. This is this is a part of the exciting part. So some things are forward looking here. Right? So we're gonna be talking about a lot of things and some of the things we're gonna talk about today are, you know, in the future happening in the future. We're doing our best to make sure that we're giving you accurate information, but things could change. When we finish this recording, you can come back and look at all the deep exciting details here in the disclaimer but just wanna let you know that you know we're gonna try to give you as much good and accurate information as possible and that's the disclaimer for today. Thank you. Alright. So historical background. This is always an interesting journey to look at. So Barber Knights, you know, started with a company called AttachMate way back when And you can see our journey here, how we got to Rocket Software, kind of a busy sort of constant change situation. This is kinda history that's happened over the last twenty to thirty years. You probably see, you know, your legacy organization that is the company that made your terminal emulator. Right? So we talk about Siegel Software, Zephyr, Open Connect, kind of some of the heritage rocket, historical rocket companies that did terminal emulation in the in this market. You could probably draw us, you know, similar sort of historical chart for the company you work for. There's always merger acquisition activity, a lot of change. Yeah. So this is a very, you know, interesting. We'll probably be referring back to this journey chart a few times during our presentation today. But hopefully, can find, you know, where you started with which product from the heritage company in this chart and then and kinda map it to how you got here with Rocket. Alright. So that's the corporate journey. I'm gonna turn it over to Barbara now to talk about our mission and and some of our values. Thanks, Chris. Yeah. And thanks for spending some time with us this morning. So we're here really to talk about RTE Web, your use of RTE Web, and kind of where Rocket Software is going. As Chris indicated, he and I came over from a very long stint at previous companies, so we've been in the emulation market for a long, long time. What I will tell you is I was not so sure about Rocket when I joined them from AMC, but I am just really happy to be here as an employee, and I can now understand why customers are pretty happy about being with a emulation company like Rocket. They do the right thing. They trust their customers, and their customers trust them. There's some really big empathy involved. Right? I'm a pretty big customer advocate. That's just one of the things that's always been really important to me as a product manager. I believe the closer I am to my customers, the better my products will be, and that's where Rocket lives. So I just wanted to and just so you know too, a little bit of a level set here, we're doing these webinars for anyone using an emulation product that is now owned by Rocket. So while we're crafting this message to you, an RTE web customer, we're actually doing the same content for several customers across the globe using different emulators, some that came from all of those different companies that Chris had listed. So this is pretty widespread. I think we have 16 emulators right now that we're supporting in Rocket. So RTE is one of those. It's a great emulator. But I just want you to know that you're not alone in what you're hearing. Lots of customers are hearing this. And out of our values and our mission, we want to partner with each one of you so we understand how you're receiving this message today. We're going to tell you a little bit about a journey that we're going on that I think you'll find a lot of value in, but we also understand that change is difficult. That said, our values are all about connecting with you, doing the right thing, listening to you, and partnering with you. That was heartfelt. I hope that you'll listen to the rest of the webinar and understand where we're going, ask a lot of questions if you're listening to this on a recording because I know that happens too. We're going to give you an email address on this webinar a couple of different times. I know Evan has mentioned that. That's straight to Chris and I so please use it. There's nothing you can't ask us. We're transparent and we want this to be a journey that you'll enjoy going forward. I think I'm going start that journey right now, friends. So let's talk a little bit about this state of security. This is really why we're making the move that we're making. Not to say that our TE Web is not a very valued, very secure product because it is, right? It's got some of the coolest security features in it. It is a top level emulator. But at the same time, we need to do more and I'm going to dig into what more means in a little bit. But really it is about the security landscape as we see it. I've spent about the last ten, fifteen years delving into how to take an emulator and blend it into the ecosystem of security in large organizations. That's what I specialize in. At the heart of Secure Host Access is that middle stat on your screen. This is a year over year comparison. 71% increase in the cyber incidents that have used stolen or compromised credentials. That is alarming. When I started looking at security, it was back in 2013. It was after the OPM breach, Office of Personnel Management. A couple of things happened there. One, I had a large federal government customer come to me and say, wow. Okay. Now the federal space is telling us we can't use usernames and passwords. And that's pretty easy out there in the enterprise, but it's not so easy in the mainframe or other host based systems. What are we gonna do? That's kind of where Secure Host Access got its start. But it was also a personal thing for me because I'm a vet and my information was leaked and I didn't appreciate that. So I took a little bit of a turn there in my career and I kind of devoted myself on figuring out how do we do better in the industry and how do we make sure that these bad actors out there can't use compromised credentials to get access to information we don't want them to get access to. Whether it's your information or mine, it is hosted somewhere and we've got to do better. So that's how this journey started and that is a statistic that is fairly overwhelming considering how much we've known about security in the last ten or fifteen years. I say that because if there were easy answers, we'd all be doing it. There are no easy answers. So we're going to dig in a little bit about layers of defense in-depth, right? No silver bullets. That's how the military handles things. They give you layers so that if the bad actor gets through a layer, you're always putting more layers in front of them between the bad actor and the crown jewels which is information on your mainframe or other host based systems. So, Chris, let's talk a little bit about the product, itself, Absolutely. and then I'll and then I'll kinda go into how the solution fits into customer organizations. Thanks, Barbara. Yeah. So, secure host access is a solution we're talking about. It's a security first terminal emulation solution, and it really, has three tiers. And the three tiers are, the the first tier being pro. And pro is really the desktop terminal emulator. So most folks are familiar with that. Know most folks on this call are using web based terminal emulation, but you remember way back when when, the desktop terminal emulator had all the features, all the capabilities, the native Windows desktop client. And it had, you know, basic security features, TLS, SSH, some cases, data redaction, which is kind of a cool feature of, you know, hiding sensitive data on host screens. So that's kind of a cool feature that was in some of our desktop terminal emulators. Then the enterprise level is where you're able to centrally manage your desktop emulators. So you can once you have central management of your desktop emulators, you can enable other functionality like integration with your identity and access management solution to enable things like multi factor authentication, automated and single sign on to the host, and and then do, you know, like I said, centralized management of your thick clients. And then there's anywhere anywhere tier. Probably the, you know, addition or the tier that the audience that's listening today is most interested in here because it includes the desktop emulator but also the web based emulator, the thin client. And with that, you can actually essentially manage your entire host access estate of thick clients and thin clients, those web based clients, if if you have a need for that. Or you can just manage your, you know, thin web based clients or HTML five clients as well. So very flexible solution and it enables you to, you know, implement those increasingly important security capabilities like multifactor authentication and also productivity enhancing features like automated sign on, single sign on to host systems. So that's kind of an overview, a quick overview what the secure host access solution looks like. And Barbara's gonna go into much more detail here and and let's do that now. Some of this is going to be familiar to you. I want to drill into what RTE Web is and kind of the differences between RTE Web and what Secure Host Access is that you understand kind of where we're going, some benefits that you would receive, if you will, and really kind of almost what stays the same. I don't want you to think that this is total change. While there is change here, this was a great emulator, still is, and has a lot in it. There's just going to be more for you if you will in Secure Host Access. So like RTE Web, Secure Host Access integrates your IAM. With a thin client, with a web based application even outside of emulation, more often than not those web based applications are integrated into your IAM. That's pretty normal regardless of what the web base is. RTE is no different in that. And Secure Host Access also does that. What is a little bit different is we have more availability. Securist Access is very it is all about specifications. So we don't go out there and partner with all of the different IAM vendors. What we do is we do specifications that will allow you to integrate with your IAM. So from a IAM perspective, we integrate with OIDC, which is one of the net new, if you will, integration types, one of the new specifications, allows you to integrate into many different IAMs. The one that comes to mind is intra ID, which is one of the new ones that I'm hearing about all the time. But with that integration, we also bring to the table the thick client, So that is pretty important. So when you were using RTEweb, you may have been using it as a part of RTE anywhere, which is thick and thin, but they did not bring the emulator, the thick client emulator, into that IAM picture. With Secure Host Access, all of the emulation can be checked by your IAM. I'm gonna show you a little diagram here in just a bit, and that'll that'll help draw a better picture for you. So the goal with Secure Host Access is again to add layers of defense in-depth. One of those that we can add here is that IAM integration. On the right hand side of this slide we're really talking about this onslaught of mandates that are coming out, whether they are new ones like NYCRR. It is fairly new although I think it's already been out there for over a year. Seems like it's new. Lots of states are going the same direction. I think there's at least five of them out there, if not more. These are all being introduced to require multi factor authentication. We all know what it is. We all think it's great. Many of us are using it today in the enterprise. But if you have it in the enterprise and you can leverage multi factor to either grant or deny access to the mainframe, that's adding a layer of defense. So that's why we're talking about these regulatory mandates now. So I mentioned there's new ones coming but there's also the ones that we know and love. Maybe love's a little bit of a stretch there but PCI DSS for example. We've all known about PCI DSS for years. Just in April 1, it became mandated that you use multifactor. No longer a best practice, absolutely a requirement. We hear HIPAA is gonna roll that way by the end of the year. So lots going on there. Federal mandates have changed over the years. They went from no more usernames and passwords to gotta use multifactor. So everybody's rolling that way. More mandates are coming out. The existing mandates we have are being updated. Here's the other thing I want to drop for you, is really part of why we're having this conversation, part of what we're doing in security. Security is already a little bit more frightful than it was six months ago. We have new threats upon us. The fake worker is something that none of us had imagined that companies, well known companies, very secure companies, are unfortunately hiring a bad actor rather than the employee they thought they were hiring. And this is because of some new technology that people from countries want to get to information and so they are portraying themselves as a person you want to hire. This can be done via several ways. They can actually be a fake worker, but they can also just buy somebody's identity. So lots of ways to do that. More, I think, of a threat is AI. We all know AI. Rocket's taking a pretty big stance in the AI market with our development products going forward. Everybody wants in on AI. It's going to change our lives, right? That's what we're hearing. It'll make you better at your job, right? Yep, it will. And when you think about a threat actor, it's going to make them better at their job too. And I personally think that there's gonna be more threat actors than ever before because they don't have to know how to code. We've always said the mainframe is secure because even if you got into it, you wouldn't know what to do. That is gonna change with AI. So so now these layers of defense and depth are more important than ever. So sorry to go a little drama on you there, but I do want you thinking about these things because that is why we're delivering Securos Access to Market. Okay. So let's take a little look at my architecture diagram and I'm gonna try to tell a story here for you as my RTE customer. I will mention in case you're using Anywhere so that you know how that interacts. So very similar product than what you have with RTE. So there's an emulator on the left hand side with RTEweb. It is a web based emulator that you open in a browser with RTE Anywhere. That is your desktop emulator that you could download actually from that server. But the difference here is in the server and what it does and the benefits that you will gain from it. I have a benefits slide later. So the important thing is if you use a desktop emulator, you will be challenged by that IAM the same way your web based emulators are challenged. And you may not be challenged but it doesn't mean you're not authenticated, right? Because of the specifications, could be doing single sign on. And most companies again today do multi factor in their organization. It's just harder to do on the mainframe. We're talking about integrating that thick client if it's part of your portfolio. The most secret sauce here that will give you a reason to look at this product sooner than later is on the right hand side. So first thing I want you to know is we integrate with the IAM so I know who you are. You're a Bob at Rocket Software, right, because that's who you log into in your organization. I take a mapping at the server and I can map Bob at Rocket Software to BobFL in Rack f. So I can map those two. And based on a secure communication, a secure relationship between the Secure Host Access Server and a component on the mainframe. And I'm gonna just stick here with z because it's just easier to talk about one. But, for example, ZMFA sold by IBM. If I have a relationship with that, then I can do a single sign on for you. So because ZMFA trusts that I've already authenticated you in the enterprise, it knows who you are, and through that trusted relationship, it will pass back a one time token. And so Bob will be automatically signed into the mainframe application. That is so much benefit. Let me let me tell you. It ups the security game. Right? If you're using a password today, you gotta rethink that. Right? But it's hard. Right? What do I use instead? If you're using ZMFA today, your end users are likely going through a web page and being asked to copy a token over to the RACF or ACF2 or Top Secret login screen. Anytime you introduce a human, you're introducing risk. Got here because of customers. That's how we build our products. Customers were coming to Rocket and saying, I need Better. I don't wanna copy and paste a token. I need this to be automated. And that's what you get with Secure Host Access. So from benefit perspective, that is one of the biggest things you will get out of this. By the way, we can do this on any host type. So if you're connecting to an I series, for example, we actually have an MFA for I series right here at Rocket. If you're going to VT, we have solutions there. And we're working on more solutions because we also know that there is not one answer to everybody's organization. Right now, we're working on a certificate based authentication to the mainframe that would be automated as well. But the goal here, if I leave you with anything, is to put more layers of defense in-depth so your IAM and this single sign on so that an end user launching an emulator, rather it's thick or thin, is challenged by your IAM in your enterprise, is looked up in your user directory. We also support claims based authorization to make sure that they actually should connect to this mainframe application, and then we automatically sign you in. That is a pretty streamlined process, better for the user, but it's also way more secure because this is using one time tokens in two different places that is almost impenetrable by a hacker. I say almost because things change every day, but today, that is just is much more value than than you can get, today out of almost any emulator on the market. So I'm gonna leave you with that. Let's see. Oh, sorry. I did say I would cover benefits here. So so let's I I'm just really trying to raise this up so that I can get you some energy here going on Securos Access so that you you don't think it's just another emulator because it is frankly not another emulator. It is a security solution. And you'll see on my next slide, I actually really want you to start taking a look at it so that we can partner. But here's some benefits. Single sign on to host based applications. That's what I just said. RTE Web, the web client itself does sync does, interfaces into your IAM on the front end. The thick client does not, so you would get that in this solution. But what I'm talking about is that single sign on in the back end. That entire stream is single signed on over two separate tokens. That's what I'm that's the real benefit here. The other benefit is the closer you set that server to your host, all of the thirty two seventy traffic or fifty two fifty or VT, the host protocol you're using, stays between the server and the host. That's really important. Of that happens on the client. And the processing does not happen on the client. All happens on the server. Secure Access supports OIDC, and that's really important if you're looking at some of the new authentication types out there like enter ID. That's an OIDC. RTE supports SAML, so you may be using something SAML based today. SAML and OIDC can be swapped, but they are definitely different. And then another thing that we do in Secure Host Access is we can do your authorization via a claim. A claim is a field, if you will, when you're using OIDC and SAML that we can hook up that name. So we can say, Oh, that's Bob in the enterprise. Is he authorized to get to the host? So we do claims based authorization. From an administrative standpoint, are paint a picture in your head, we're containerized. RT web is also containerized. But expanding that a little bit, we are orchestrated. So in our deployment models, you have orchestrated containers, and that right there gives you a bunch of stuff. I'll get to that in just a second, but think about that. We have three deployment models. We have a virtual software appliance, and that is just the easy button. Right? So it is a software appliance that you put in your virtual machine architecture, whatever it is today, we support 99% of them. You deploy it. You have a Web UI. It has an OS inside of it, but we take care of all that for you. We do the updates. A lot of customers like that, but when you get bigger, you worry more about having other things on that server, if you will, on that pod, on that virtual appliance, and we don't like you to add things there because it's ours and we're kind of dependent on what's in there. We'll make you take it off if we have to troubleshoot. So for large organizations, more of them are picking up the Linux install. Don't be scared. Linux I know it scares a lot of people. Wow. I'm a Windows shop. Actually, I have my favorite customer, she has totally moved over, and she is very happy. And that's because from a Linux perspective, really, it's just the install. We can help you there, but it does give you the ability to manage your own OS and add other things to that server if you need it. Remember, I told you, think containers orchestrated. Here's the other thing we're doing is we're this is pretty new and we're adding more to it is we can deploy to an environment where you use your own orchestration tool. So so we call it bring your own Kubernetes, but we're working on supporting OpenShift. There's a lot of things and moving pieces there because that's there's a lot to do and a lot of prerequisites. So we are partnering with customers to make sure that we can grow that going forward. Now the reason why I ask you to paint that picture in your head is because of this statement, supporting high availability with less administration. RTE Web has great high availability. They have pretty good administration. Here's what I want you to know. Because we are pods that are managed by an orchestration tool, you can have less servers or less pods. When you scale, you can scale up instead of out. And the administration, it is almost like magic because that is what orchestration does. When one server goes down and you have already said, I gotta have four of those guys, it will ramp up another one. So so the fact that this is orchestrated inside or you orchestrate it yourself through the deploy with your own orchestration tool, That's what gives us this high availability with less administration. We can do high availability across everything because high availability means something different to every organization. You could talk about data centers. You could talk about pods. You could talk about geographical locations. You could talk about zones. We will partner with you to understand what high availability means to you, and then we'll choose the right deployment model. It really is, and know RT's web is great at this, but it really is pretty amazing to understand how this happens. I'm having a couple conversations right now that that customers are just really, wow. I can really do this with less servers. So I want you to take a look. And then finally, and I think this is pretty big for a lot of customers, is we completely manage both the thick and the thin emulator from that single console. Today with RTWeb, you might make a change from SSL to TLS, for example, and it picks up the next time the guy logs in. But we can do that for thick as well. We can make surgical changes to your thick client sessions. At least personally, I find most customers have to have a mix of thick and thin because of all the business logic that's wrapped around that thick client. So that's why we have RTE anywhere. We have a lot more management capabilities for Thicken there than you've ever seen before. Those are kind of the benefits. Now let's look at my advice to you. We're going to talk about maturity here in a minute, but you've probably already received the email. So what I'd like you to do is I'd like you to look at Secure Access when you get time. We'll talk about maturity in a minute, but Secure Host Access is out there and ready for you to entertain today. I would say, based on what I've been talking about for the last half hour, if some of that really interests you, then let's get together and let's get you an evaluation copy and let's have you look at it so you can test. The other thing I will tell you is let's partner. Right? That's in the email address that Evan was talking about, and that gets to Chris and I. And Chris and I can get to anywhere on the back end. So if you don't know who your rep is, you don't know how to get an evaluation, send us an email. If you are nervous about this move to Securos Access, send us an email. If you are angry because you feel like Rocket Software is making you move, which is not true, and we'll talk about that in a minute, send me an email. Doors are open. Communications are open. We want to hear from you. So I it's still on me. And part of this is on me because I own, RTE Web. So, so now let's talk a little bit about the maturity announcement that you received. So I know this can be unsettling to you. So I wanna I'm a straightforward, very transparent product manager and customers are really important to me. What we're doing here at Rocket is we want to concentrate all of our development on one product. As I told you in the beginning, we're doing this for anybody, any of customers using all of the emulators that they've been using for up to the last forty years. Right? So some of these customers I talked to thirty years ago when I was a frontline support representative and could barely spell emulation. They're still on the same emulator. We're telling this to everybody. We want to focus on one emulator because we could do more for you by doing that and we are trying to attack, if that's the right word, this security ecosystem that we are now all dealing with and making sure your emulator is secure in that environment. So we sent you an email on or about January 17, and we told you that RTEweb is going into maturity in 2027, so just short of a year from now. What does that mean? Because that announcement could just be startling in its own self. All it really means is that the innovation, new enhancements, new requests, they're all going to go into Secure Host Access. What it also means is we will continue to support you. You will get annual releases. This is no commitment, but the plan is about an annual release that is much like a service pack that has bugs and, of course, security patches. The other thing that's really important is if there were something to happen let's think about a Log4j, for example, because that freaked everybody out if that happens and we're impacted in RTEweb, we will be on that and we will get you answers and we will deliver a solution. We are not stepping away from this product. It not only does not mean end of life, it also does not mean end of development because we will continue to fix and give you security fixes. But what it does mean is the new innovation, the new CERs, the new authentication types, maybe the next version of TLS. Just imagine, if you will, the things that we need to do from security purposes. That's going to go into Secure Host Access, which is why we're giving you a year's notice and we're asking you to take a look at Secure Host Access. And we wanna partner with you. Okay. I think I'm finally gonna give it back to Chris. Yes. Thanks, Barbara. That was that was quite a marathon you just ran. I'll get some coffee. So you touched on product life cycle a little bit. Yeah. Can't grab some coffee. You touched on product life cycle a little bit here. So let's let's talk about the actual published product life cycle and the policies that are related to product life cycle. So when we got to Rocket, we didn't really have a life cycle policy for the terminal emulators. And some of the different Rocket products have different life cycles. Some are published. Some are not. So we spent quite a bit of time, probably six months, you know, thinking about our secure host access strategy, the legacy terminal emulators, and kind of what the best approach would be going forward. You talked about maturity quite a bit, Barbara, which is great, very helpful. But we finally, you know, put together our product life cycle policies. Those are now published and available on the ROCCAT website. And I know Evan does a great job of getting us the link to that like you did in the last one. So we'll share that in the q and a chat section for you to be able to access the product lifecycle page on rocket.com. They're new and improved. I think you'll find that they're very easy to understand. You know, we didn't like I said before, we didn't really have a consistent set of policies for all the emulators. We have that now. We continue to communicate changes and updates regarding product life cycle policies and the products in general, secure host access, RTE web, some of the other products via the very different channels. So we've got email. Obviously, we've been sending out emails regarding the product life cycle, the maturity phase that's upcoming for RTE web. We have the forum now. So there's a brand new forum on the ROCCAT software website for discussing product issues. You can post any questions there and and we'll get back to you on those. There's the documentation portal which is, you know, all the online documentation. You can access that instead of having to, you know, look at it in the product or find it in the product. You can just look it up online which is very handy. And then we also have the Rocket customer community where all the, you know, downloads of the software media are published including secure host access. And so a lot of, you know, things related to the product, the product life cycle are available now. The graphic at the bottom bottom of this page gives a general idea of the, you know, life cycle policies that we're now implementing. So we call the first release of a product general excuse me, a general availability And that's really years one to three, you know, of a product versions, life cycle. And then we go into limited support for a couple of years and then restricted support for a couple of additional years. And all those have definitions, what they mean, and so forth on the product life cycle page on the Rocket Software website. And we'll share that link with you, again, as we said. And let's go now and talk a little bit about kind of our commitment to you. And Barbara's been sprinkling in some comments about our commitment and our support to our customers during this kind of change from all of our terminal legacy terminal emulators to Secure Host Access. As as we discussed, you know, RocketTE web will continue to be supported. I don't know if anybody is familiar or uses the mobile product, but that's also part of this commitment. You can move at your own pace to secure host access. So if you wanna stay on RTE web for a couple more years, that's fine. We'll, like we said, you know, provide updates, fixes, and so forth. Probably not any major innovations, but but we'll still support it. And and that's, you know, what what our customers are really interested in is being able to get, you know, vulner vulnerability fixes and so forth. We wanna support you through, you know, your modernization journey and ours. And that really means we need to, you know, collaborate, work hand in hand, make sure that you're successful in this, you know, kinda long term move to the secure host access product. And, Barbara, I'll let you, cover the other bullets because you haven't spoken enough today. Yeah, now that I have more coffee, can go again. Sorry. Yeah, so this really is about Rocket's commitment to you. We really believe in what we're doing. We believe in the journey of Secure Host Access. With that said, we also know change is hard. So we do want to partner with you. I think this product life cycle is really important because while we've talked about it in the past at ROCCAT, we've never had this actually out there on our website to where you can see. The other thing I want to make sure that when you saw that graphic from Chris, that's really for Secure Host Access because when RocketTE enters maturity, it won't have the GA and such, but it will have a product life cycle. And so we wanna make sure that you know what that is. So we're working right now to make sure that that's very clear on our webpage. And again, of course, you know if you have questions or you don't understand something, shoot us an email at that email address on your screen. So the other thing I will say is you never go on a journey like this and get it all right. It just doesn't happen. Even though Rocket's a great company and I believe fully in what we're doing, there's always something that you can do better. And I believe that wholeheartedly. So there is some work to do. Right? There are features that are in RTE Web that may not exist in the same way in Secure Host Access. This is where we need to hear from you. We need to know what you're using, and we need to partner with you so that you're never in a position where you're not on an innovative roadmap. I actually bring on that conversation. I am working with a couple of very large RTE web customers right now to understand how they use it, to understand what features and functionality are really important to them, to ensure that we make sure that Secure Host Access is the product that they can move to with as seamless of a change as possible. We're working on tools right now that can take all of your information out of RTE Web and then upload it into Secure Host Access. So we're doing a lot behind the scenes, but I'm sure there's still work to do. So please don't hesitate to reach out to us, tell us what you like, and the door is open for you to tell us what you don't like as well because we're here to listen. I think, Evan, we're gonna open it up for questions. That's right. Yeah. Oh, Chris, go ahead. Sound. like you were gonna say something. Yeah. So yeah. There's always, you know, some good questions. Thanks for posting the links by the way in chat, Evan. So those are good to have. A couple of questions that often come up, Barbara. So you've got a web based solution. You're talking about secure host access web. And people have been used in the past in the web based solutions, Java, the Java technology and so forth. Can you make some comments and answered questions related to whether Secure Host Access you know requires Java or uses Java in any way? Yeah, it's interesting. I was just on a call before this call with a customer who uses a Java based emulator. No. So RTE had an an HTML interface and so does Secure Host Access. So no Java on the client side at all. There's this is a Java application, so there's server side Java, and we keep up to that on a regular basis to ensure that we're meeting all the security mandates and to make sure that we correct any third party because, obviously, we don't produce Java. And to make sure that we're up to date, make sure all of our third party components. So there is no Java on the client. That's really important here. So great question. Glad for you to ask that so we can clear that up in case anybody doesn't know. Thank you. And then with regards to the secure host access road map. So I think a lot of the questions that we get typically are, you know, what is on the road map? And, you know, we have to adhere to new security regulations and so forth and we want to make sure we can do that with this go forward product. If a customer wants to see what's on the road map what can we tell them? Yeah. That well, that's a great question, Chris. Because normally, they go through their account representative, which again, if you don't know who that is, email that address. And then you and I get on the phone and we show them what we're doing. Right? So the closer we are to the delivery of what is proposed on the roadmap, the more concrete that path is, right, because development has already started. And then farther out, we usually have about a two year roadmap. Farther out is a little bit grayer, but bigger topics that we're hearing from customers. Generally speaking, you will see in this product three themes. It will be making any kind of security changes that are required to keep up with these mandates. We we absolutely keep tap on the mandates. We absolutely make sure that we know what's coming up. So if, for example well, and it's not mandate, but let's say they come up with a new specification on a on a way to do authentication, we would be working on that. So, any kind of security changes will be there. Also, to be fair, is any kind of security updates. We are constantly in every release honing in on third party components and what has to be updated there. That's one theme. Theme number two is what are our customers asking for? What's the next new thing you need in order to help you move around your business? Important. We listen there. We obviously want that applicable to other customers, and the more customers that bubble up, the more likely it is to end up on our roadmap. And then thirdly, I think the other theme that you're gonna see is helping customers get from Product X, the emulator that they're using, to Secure Host Access. So I mentioned some gaps that RTE has that Secure Host Access may not have today. What we need to know from our customers is that feature something that you're using. This product is really about customers. Customers and security and making terminal emulation the right fit to move to. When you when you look at the competitive landscape, we're really trying to fit into the security ecosystem and making sure that this is not just an emulator but a security solution. Are kind of the three themes of what's going to land on the roadmap. The other thing I'll mention then just about roadmap is quarterly releases. So that's another thing that I think is a benefit here. We had a pretty good cadence with RTE Web, but with Secure Host Access, we have a quarterly release plan. Our roadmap is basically twice a year where we talk about what's going to be in there, but we're a very agile team and we release quarterly and we release even in phases. So for example, you may have asked for a feature. We may give you the beginning of that feature in one release and do more for it in the next three releases. Sorry, one more thing. This is what happens when you just ask me a question and my brain The other thing you're going to see a lot, and this has to do with security so still within my themes, but you're going to see a lot about auditing, monitoring, and understanding. Giving customers the ability to understand what their users are doing. And that's important because remember, this whole thing is that user may not be who you think they are. That's what happens when you get compromised credentials. You are logging in as Chris Lull at Rocket Software but you're not really Chris Lull. Yeah. When I talked to a CISO the other day, he kind of had a phrase that I kind of caught up with and I really liked it. It's when an authorized person is doing unauthorized things. That's what happens when they're compromised credentials. That is not who. So you need to know it's about risk based management. When Chris Law logs in from a foreign country during hours that are not his working hours, that's just a really basic that's not Chris Law and we. need to know what he's doing and we've to have the ability to alert all the right people. So That's another thing that this product is really going to start concentrating in the next two years is how can we wrap up that centralized logging capability, monitoring capability, and alert capability. Yeah. And when I when I hear you talk about road map, it's all security. Security first. is. It is. Yeah. And and, you know, there's reasons for that. Right? Chris, you and I have been doing this for a long time. Right? Yeah. How. much more do you need in an emulator? So, you know, spell. checkers are nice, but that's not we're we customers are not looking for innovation in the terminal emulation space. They're looking for emulation in or sorry. They're looking for innovation in security, in high availability, in how can I deploy this and make sure that users can connect to my host? Absolutely. Absolutely. Okay. One other question here is so you have sometimes you have thick and thin users. Right? In most cases, you're gonna have some thick users because like you said, there's some business logic you've got that, you know, wrapped up in the thick client because it does Halabi or VBA, Visual Basic for Applications, or some other automation that was built twenty years ago and still runs against the thick client terminal emulator. Okay. So you've got a large organization using RT web and maybe they have, you know, reflection or rumble or some thick client blue you know blue zone RTE desktop. Okay. So now you're managing thin the web. Couple of questions. Can you manage the thick client? And then, you know, from this secure host access solution, and then and then can you do it from a single console for both thick and thin? Yep, That's a great question and this is one of the benefits coming from RTE web. Our goal is you can manage it just like the thin and we've come a long way. So again, and I might have talked about this before, think about when we move to the next version of TLS. Really when we move from SSL to TLS, right? Everybody was impacted. All their hosts were going to TLS, so you had to change your emulator. In the emulator, and really it's regardless if it is ours or a competitor's, that TLS version is held inside the session document. So that means you have to touch every session document. I got customers that have 30 different sessions sitting on their desktop and they got 10,000 users or more. That's a lot of session documents. We heard that and we resolved that or added a feature to take that action. We can make surgical changes and we can do it from one administrative console so that that change is picked up the next time the user logs in. And, by the way, not only can we do that, we can lock down that emulator so that that user can't change it back. Right? Because that's kind of important too. There was a guy Ed, that you and I used to work with a long time ago and when I really started turning my head into security, he had a saying and he said, Barbara, security is not really secure unless you manage it. So you've got to make sure that you make all these changes to make your emulator more secure, but you also got to make it to where an end user or someone who's posing as an end user can't make it less secure. So you gotta manage it. Yep. So we can actually lock down that thick client from this centralized console. And let's say, for example, you make a mistake, we can also undo that and it's all about when the user logs in, the next time they'll pick up the changes. So it it's it is really phenomenal about the changes you can make to the thick client from this product. Awesome. Thank you. Any other questions in the q and a or chat? No. I I I think we've hit on everything. So That is good. you both so much for for going through all of this. I I really think this was a great session. Like we said, if there are questions that didn't come up that you come up with later, please reach out. That email address is is here on screen now, rocketconnectivity@rocketsoftware.com. Chris and Barbara get that, and they will get you an answer. But thank you for being here today. Appreciate your attendance, and thanks again. Thank a. great day. talk soon. Thanks for spending some time with us. Thank you. Thanks all. Bye. Bye bye.