As AI-native platforms reshape the healthtech landscape, customer identity must evolve to support stricter compliance, multi-org structures, and rapid scale. In this live webinar, Frontegg CEO Sagi Rodin sits down with Insight Health CTO Saran Siva to unpack the real-world challenges of identity in regulated, AI-powered healthcare environments.
From launching secure patient-facing agents to enabling role-based access across complex org charts, Saran shares how Insight Health operationalized identity without slowing down innovation. Together, they explore why identity decisions can’t wait for later and why building in-house is no longer a viable option for healthtech startups.
Learn more about Frontegg supports healthcare SaaS.
Hi, everyone. Welcoming those who have already joined us.
We’re going to wait a little bit longer just so that everybody can join. But in the meantime, feel free to write in the chat on the right hand side of your screen. Let us know where you’re joining from, and we’ll get started in just about a minute.
All right, we’ve got some people in. We’ll get started. So thanks everybody for joining us. My name is Leor Melamedov, and I’ll be your moderator today.
So just for a quick overview of what you can expect, we’re gonna start off with a fireside chat between Frontegg’s CEO and cofounder, Sagi Rodin, and he’ll be speaking with Saran Siva, the cofounder and CTO of Insight Health. Insight Health is a provider of AI clinical agents that complements clinicians for healthcare use cases.
So, Saran has been a Frontegg user for a while now, and he’s gonna be talking a little bit with Siggi about what that experience of implementing SCIM looks like, specifically for health tech companies and how he’s making use of our capabilities as well as some of the larger struggles of getting customer identity in place for your very highly regulated industry where it’s very important to make sure everything is HIPAA compliant and you have support for multi subsidiary, multifaceted organizational structures. So we’re gonna be exploring all of those different nuances.
So the first thirty minutes, we’re gonna be having a bit of a chat, and then we’re gonna go into a very brief product walkthrough where Sagi is going to showcase a couple of the Frontegg features that are best suited for b to b health care use cases.
After that, there’ll be around ten minutes for a live audience Q and A. You guys can actually at any time during the webinar, feel free to just put into the chat on the right hand side of your screen, type in whatever questions come to mind while they’re fresh, or you can wait until we bring in the Q and A section. And then we will have a chance. You can ask your questions to Sagi or Saran, and whatever is on your mind, they will answer to the best of their ability.
Then we’ll wrap up.
So we can kick it off right now. I think there’s still some folks joining, but we can get started with our fireside chat. So, Sagi, Saran, welcome to the webinar.
I’ll let you two introduce yourselves and get started.
Thank you, Leor. Saran, go ahead.
Hey, everyone. Maybe I’ll start with my introduction. Yeah, my name is Saran. I’m co founder and CTO at Insight Health. And as many of you know, we have multiple hats in the startup world, so I lead the product engineering and product marketing functions at InsightHealth.
And we are building autonomous clinical agents that handles direct to patient conversations so that any clinics of all sizes, big and small, can scale their practice and improve patient care and reduce clinician burnout. You are in the US and know about the US healthcare, there is more than three million worker shortage in the US healthcare and while the nations are spending more than fifty percent of their time in administrative tasks. And that’s why we are solving for and we have more than ten thousand provider users that are using our system.
And with AI, our goal is to have every clinician have their own AI clinician staff that can act as a co pilot.
And you’re doing it all with a with a rather small team. Right? This is a new area of AI we got to chat a bit earlier.
So very exciting. I’m Sagi. I’m the CEO and co founder of Frontegg.
We started 2019 to basically help companies innovate much faster by taking off the kind of load of building their own user management customer identity solutions.
So we handle everything from the onboarding part of a new user to getting them back into the product, logging in to managing their roles and permission, to providing a full interface and a back end system to controlling the authorization, the security policies, the audit logs, everything that has to do with making the product enterprise ready. And and obviously, the AI also affected the us and the value that we provide. So today, a lot of companies build their agents on top of our platform and also doing the user onboarding of their copilot and and other AI products through Frontegg connecting with integrations to other products and SaaS solutions through Frontegg, kinda closing the whole loop.
And we have a lot of additional exciting things coming up. And I think that health tech, health care is definitely one of the more interesting things that are happening in the the industry, but also for Frontegg. So I would love to dig a little bit further into that, Saron, and kinda understand from you why identity, user management, enterprise readiness, all of those are important in the world of health tech.
And what are the challenges? What keeps those companies kinda up at night and the challenges that they’re having with revolution of AI and whatnot. So very exciting for me, and really kinda thank you for taking the time.
I know that you’re very busy. So maybe we’ll start by asking, you mentioned that you have a small team, so tell us a bit about how this operation looks like in a health tech company, your role kind of as the CTO who’s overseeing all of the technology at the company, right? Like all of the innovation that is happening.
Where do you spend most of your time?
And maybe there’s a kinda interesting thing to to say about the the technology of InsightHealth and how it differentiates in the market.
Sure.
You know, we are one of the first, very first direct to patient facing product within the health tech, within the AI health tech. When we started, we started incorporating August 2023, just actually our celebrating two-year anniversary this month. And when we started, ChatGPT was like seven months into that. And you know, that’s when we started at just when the things are getting started, right. And the result of most of the products or most of the company startups were doing clinician facing or inward or back office type of AI, and that’s very popular.
But we started with the most of the hardest part. We started with clinician facing, sorry, patient facing as first.
And within a few months after we copied and we launched our product, we had our very first autonomous patient conversation like November of twenty twenty four.
It’s just when, you know, ChatGPT was even before it hit like a one year anniversary, we had the first autonomous clinical conversation at a patient with an oncology patient at their home setting, and they were in our, we call our, the agent as Lumi, a patient facing the Lumi was collecting a detailed health and clinical history from the patient and it provided to the clinician and the oncologist even before the patient showed up.
Then the feedback that we got was really great. I mean, because usually the visits are less than an hour and you don’t have a lot of time for the patient to go and explain all the history and then have the clinician has to do the assessment and then they have to go and also explain to the patient on how their processes, right? So and we collect all this information so that the clinician can spend quality time with the patient.
The physician can spend quality time with the patient, right? So our main differentiation between our other health tech is we are very clinically focused. Two of our co founders are practicing MDs, neurosurgeon and a cardiologist. So they’re very clinically focused, patient facing, then we spread across all the clinical workflows. We don’t also box into one area. We spread across different clinical workflows, right? Yeah, and then as said, when I’m looking at those different areas, want a platform that scale with us and scale to different customer archetype per se.
Got it, got it.
And so tell us, know, kind of what drove you at first to evaluate Frontegg?
Was there any trigger out there? What were the main kind of parameters you were looking at? Did you think about maybe building a user management solution on your own?
Walk us a bit through that decision.
So now when we incorporated or when we were about to launch our product from a POC stage to a real live customer and a patient.
Was one of the duration in front of me is to choose an authentication platform, because during the POC was a makeshift login page that was just I was just focusing on the core functionality, core workflow and login. It’s just in hard coded username and password right? Then when we were wanted to go to production, it’s when they realize, now, okay, this is gonna get real. Let’s let’s spend some quality time on this to choose a platform that’s gonna be the front door of our product. Right? And you know, I’ve been working in the tech industry for a couple of decades now, worked at small and large enterprises.
And one common problem throughout everywhere is the customer identity platform, right? I mean, almost in every companies that I work with, they are mostly homegrown either are within legacy product. And they are always there’s the identity management team is always fighting with security vulnerabilities are there is solving scaling limitations and and the first thing when a product launch, the auth layer is kind of the bottleneck at the front door of the product for the growth aspects.
I think that’s one of the things that I wanted to make ensure when I’m choosing the auth platform is a platform that scales with the product and a platform that’s not a bottleneck for our core business problem that we are trying to solve.
And, you know, and then I spent just two weeks just intensely choosing our, our platform, almost like evaluated every platform in the planet.
I would say and trialed it.
And the few things that I was looking for is something that I can try it out on my own before we go and make a purchase decision. Right? I think that’s where Frontegg checked all the boxes. Were able to do an free trial and we even run it in production for a few weeks before we made the decision to go and purchase and make Frontegg as our customer identity platform.
Yeah, I think that in the new age, it was called kind of a PLG trend a few years back.
But I think that almost with any product today, like even physical products, it just doesn’t make sense to kinda have a Greek wedding with a product without the ability to, you know, to try it out and see that it fits.
Especially when you’re talking about a critical infrastructure product that will be the face of your company. Right?
So I think that for us, it’s very important to, a, make sure that doesn’t matter how long the the prospect, the user spend on the platform, they will get the moment very fast so they understand what is different about us than the other solutions out there.
Whether it’s, you know, it will feed them or not, maybe we’re not the most, you know, the most relevant solution for them. And that’s that’s fine as well, but we want the user to really understand before they’re going into purchase process. So happy to hear that you kind of have this experience as well.
And so tell us, after choosing Frontegg, how did your team approach the integration? Maybe, you know, what were your expectations rather than, you know, no bugs, and did it all happen very fast?
How long did it get you to did it take you to get into production eventually?
And so a bit about that process after making the decision.
Yeah, I think so. Yeah, it’s it’s quite intertwined with very insightful to what was it at the stage again. This was we’re not an established company or startup, so there was some growing aspect that was tied to that implementation. For example, like when we were choosing Frontegg, I was the only engineer in the startup. I was the only one coding all the time. And when I started implementing, I really needed some help. That’s when we raised our pre seed and I was about to hire our first engineer.
Luckily I was able to convince one of the top engineer from my previous work at Twilio to come and join me. His name is Abhinav. When Abhinav joined, this was his first project.
We are going live in few weeks.
It’s a real patient interaction and it’s a small, again, small pilot going live with a small pilot with the real customer. It’s not in POC anymore. And we need to get it done within two weeks, right? And then he came on board and he looked at Frontegg documents and you know pretty much we were ready to go live within a week actually, and and even less than a week.
And, you know, with the main flow, everything with an authentication, with a single sign on, with the social sign ins with Google and Apple, Apple sign in and Microsoft. We we completed all of that. We had a login page up and running, and we set up the basic authorization and authentication, and we were live within a week from the day we signed the contract.
That’s great to hear.
In those integration phases, would you say that you expect kind of fully self explanatory product, you don’t want to contact anybody, or you’re also expecting to have a partner that you can approach, because you do realize that it might get complicated. You might have customers, especially from what I at least from other customers in the health tech industry, we know that the health care companies, health systems that eventually use your product, right, might have legacy systems, right, legacy identity providers. So it might get complicated.
What were your expectations from the product that you choose?
Yeah, I think, again, so everyone’s journey is different. Mean, journey was we are in a greenfield starting from scratch.
And we did not have our expectation as like we have zero users when we integrated, right? So not have an existing platform to migrate into.
But you know one of the things I was looking at even before is to have availability and community that can they can reach out to when we are facing issues and and everything even before we signed the contract and everything. I was part of the slack channel and was just keep keeping an eye on the slack channel on what are the type of issues that that newly integration.
What are the type of issues that they are facing and how Frontegg is solving them. I was keeping an eye on it and I was very, very impressed with the piece that you’ll have to jump in and folks from Frontegg will jump in and the Slack channel able to solve those issues. I think the support immediate support, the documentation and the robustness of the product and, you know, is it HIPAA ready? Is it enterprise ready?
And how quickly we will it will be able to help us to move into that enterprise customer segments, right? I think those are some other things that I was looking at And we did not have to reach out to the Slack support for, I don’t think even maybe once during the integration process we may have to reach out. But I think most of the documents and everything was pretty self explanatory. But even after integration, you know, we we did several other things even when we had to reach out and it gets very responsive. So so I think we’re we’re happy with with how things are going.
Yeah. That’s that’s great to hear. I think that, you know, this partnership that you’re looking for when choosing those kind of, you know, products, it’s super important. We choose SaaS products ourselves, obviously.
We’re looking more than just having an amazing product. Right? Because you wanna know that when things, you know, might get more complicated, and they probably will, especially with those complex systems. Right?
They’re customer facing. They’re critical infrastructure systems. They will get complicated, and you wanna know that you will have a partner there that will not just tell you to open a ticket and wait.
So so, yeah. So that’s that’s super important.
You know, we spoke a bit about kinda this early decision, but at the end of the day, there’s day zero features, and then there’s day one, day two capabilities that you wanna add along the way.
We try to simplify and make it like, you know, a toggle on capability for almost anything that you might need as you grow. And definitely, authorization is a big part of it. Right? Deciding who can do what within your app after they are logged in. And in healthcare it can get pretty complex.
So I would love to hear a bit about that, about the multi tenancy aspect, right, and data segregation, stuff like that across tenants.
Tell us a bit about that.
Yeah, so I think with the HIPAA compliance in healthcare, the authorization layer is a table stake even when we are selling it to one small clinic, Even if it’s a small practice with just like three or four users. So even there, having an authorization as a feature is pretty critical because you have, let’s say if there is a clinic which three or four staff, we have a front of staff, there is a medical assistant, and then there is a physician and probably a back office staff, right? And all of them needs to have their separate access mechanism because not everyone would be having access to patients clinical data, right?
So the front desk staff may just need access to the patient scheduling and the physician has access to everything, all the patient records and the medical assistant may access to only certain health records of the patient, right? So it’s kind of mandatory to have this authorization layer even you know it’s not you go to enterprise. That’s when you have to have that complex authorizations, but it’s a table stake even when we go to our first customer. I think that’s where we started with an auth layer from day one.
And so this authorizations actually that the complexity manipulates and into multifold when we as that the customer size of the customer increases when you go to multi specialty or even logical systems, the types and number of roles just multiplies a lot. I mean, have IT teams coming into the play and you have quality teams and almost every team has their own authorization that needs to be set up. A
nd even within specialty, there’s complexities like mental health records where none of the other employees within the same health system can access to that except the physician who’s seeing the patient, right? So there is quite intertwined and quite complex art mechanisms that we need to put in place from day one.
And I think that’s where, you know, we’ve been using RBAC and RBACs from day one.
Also entitlements is also we use entitlements a lot.
Think just within a few months after we really sort of Frontegg like we started using a lot of features from entitlements in making sure that the plans and features are set up properly in addition to the RBAC.
Yeah. So I’ll show that once we finish to to the audience. But definitely, see that the kinda tenant specific approach and the kinda holistic approach that we have for entitlements for having a single API to basically control all of the decisions of what a user can or cannot see according to all of those parameters is one of the features that are most popular with the health tech industry. So, yeah, so it’s great to hear that you also see the value in it.
What about, you know, tell us a bit maybe about how important it is to give the different customers their own tailored experience of of logging into the product, of setting up, you know, their own UI and branding, but also their own policies and having the ability to kinda control everything on a on a single tenant basis. And when we adjust for the audience that will be you know, that are watching that, a tenant for us is an end customer, for example, a health system that uses or a practitioner that uses InsightHealth?
Yeah.
You know, one thing where, you know, we our go to market motion is multifold. We started with an direct sales and then we extended. We’ve launched another ascribe product where we adopted the product led growth where there’s a lot of self sign ups involved.
And then our third go to market motion is strategic partnerships that we in the last one year we are expanding a lot with with with the partnerships angle, right? So I think in healthcare distribution is everything. I mean, having the technology, even you have the greatest and the latest technology doesn’t matter unless you have the distribution.
And that’s where the strategic partnerships, the angle is helping us a lot, we are partnering with EHR, the electronic health record vendors, and providing them an AI layer that runs on top of their software, right? And what gives us is an unlock.
For example, we announced a few months back a partnership with a leading pediatric CHR called Office Practicum, and they are very leading among the pediatricians. They’re one of the leading EHR vendor, and they have more than six thousand pediatricians. Their customers are users of that EHR, And it gives us the unlock to expand to that six thousand plus pediatricians by making an exclusive vendor relationship with office practicum.
But their needs when we resell our products, AI products to them, their requirements change because we got to white label, we had to adopt certain things into how their platform and we are able to launch it from their platform and to provide seamless login experience.
We got to adapt to the changes on how our partner wants us to present our product to their customers, right? I think that’s where the customizable aspect comes into the play. Now we were able to white label and put our partner’s logo in our products and, you know, and we’re able to create an unique customized landing page, like login landing page for each of our strategic partners as well.
And it’s not just that there’s, you know, our partnership goes in as the our customers, our strategic partners self manage their own customers. I mean they provide the support, they provide the go to market. So that means they are able to self manage a lot of user provisioning aspects and user support like the login support. So we leverage the sub organization feature a lot where the our partner, they have their organization on each of their customers, their sub organization, and they have the super admin access to all their sub organization.
And they were able to self manage a lot of user provisioning by themselves. Know that’s one of the things how you mentioned like a small team, how are you able to scale and this how we’re able to scale by now we are just ten employees in the company and we have almost like three strategic partners that we are not in the direct line of support to them because they are able to self manage that organization.
That’s incredible.
You know, we spoke a bit earlier on how fast you can move with this team that is laser focused and having the right partners with you. And, yeah, it’s it’s it’s so important when you you know, you choose a partner. They’re choosing you at the end of the day. So they expect you to provide them with the ability to to support the customers in making this one plus one equals three.
So I think that it’s super important. We do see that partner support hierarchies that are used through Frontegg is definitely something that we build for these kind of use cases when a partner of yours wants to be able to be delegated to manage their own stop customers. So, you know, very important capability.
You know, so we were talking about, you know, hierarchies and authorization and and multitenancy and the ability to set up things on a tenant basis, on a customer basis. Basis.
And we spoke about the authentication, obviously, and getting fast to on air and to production.
If you were kinda advising another CTO in the health tech industry that’s facing kind of similar CIAM challenges, what would you kind of tell them to prioritize maybe one or two things that are most important?
Yeah, I think the first thing I would say is do not build a identity platform by yourself. That’s the biggest mistake because there is so much healthcare challenges to solve and identity is not one of them.
So I mean, identity is just one, but almost anything that’s not related to the direct functionality that the customer touches.
I would say, not put your team engineering resources in to solve those problems, right? Anything that’s platform related. So yeah, do not build your own identity authorization platform.
Do not build anything related to single sign on our back and and any such things like let get a platform that’s proven and let that handle those heavy lifting things. Right? I think that’s that’s probably the number one. I mean, you would think, it’s just a username and password.
Let me and I mean, that’s that’s the rabbit hole that you will go down to and then think about password resets MFA and then the RBAC comes into the picture and then you know when you go into even mid mid size practices, will ask for single sign on and audit logging and that just things goes complex and it just becomes a beast on its own.
And then the second thing is, you know, thinking in healthcare, the enterprise requirements comes in much earlier than I initially thought.
And I initially I thought, maybe we’ll just authentication authorization will be good for a few years, and maybe we’ll go into top ten health systems. That’s when we’ll need all the enterprise features. But they turned out to be wrong. Mean, within like the first few months, know, we had so many deals that they will not the it team would not sign the contract without having their own access to audit logs and a robust MFA.
And the admin can self manage a lot of the basic user management by themselves. Mean, there was like the zero common from them.
So it just the enterprise requirements in healthcare just comes much sooner than I initially thought, I think. And then the last, I would say the third thing is, I think as if you are in an early stage, health tech, or even any kind of early stage startup that you are thinking about, treat your identity platform, see what it’s doing beyond the basics.
It needs to be also a growth enabler platform, because in the early stages, the growth is critical. Mean, as much as how much you wanted to build a secure platform, you got to even grow fast. And I think that’s when it was a, you know, good Frontegg is not just a basic art player for us. It’s also we are using all the lot of entitlement features and the future flagging and our pricing and packaging. Use the front entitlement plans a lot in how we price our and package our products. As I say, we have multiple go to market motions and each of its own has its own packaged way and we use the Frontegg plans to package them.
I think that the third thing I would say is choose a platform which enables your growth and not just provide. I mean, course, they be providing really robust solid out layer is critical, but go beyond that and which provides and growth enabler, right?
I mean, so I think the best code is not that the code is you don’t write, and especially it’s very true in identity.
Choose something that you can rely on another platform both from a basic security as well as growth enablement.
Awesome. Awesome.
I’m sure it will help, other folks as well. So, Saron, thank you so much, for, you know, for speaking with me. And, thank you for, you know, for being our customers and allowing us to be your partner in your amazing journey. So and and yeah. And and, you know, that’s a great segue. You spoke about entitlements and authorization. So I would love to take a few minutes and maybe show some of our audience what you were kinda talking about.
And yeah.
So I think that, you know, we will start by presenting. So this is the Frontegg platform.
And, obviously, there’s a bunch of things here like managing your accounts. This is a demo environment, obviously, Seeing the users, you can use user pools and other stuff. And obviously, there’s a full authentication section. But what I would love to focus is kind of on the roles, the permissions, the fine grade authorization features, plans. We try, as I mentioned, to look at it in a holistic kind of view of a single point where you decide whether a user can see something, can access an API, can execute some code on the back end or whatever it is.
So, you don’t have to split kind of the responsibilities between managing your plans, what they paid for, what is their role, what flags have been turned on, and etcetera.
So, let’s imagine Mediconnect, the health tech platform that is used by hospitals and clinics basically to manage patient data.
And in this screen, I will start with the entitlements, with the roles section. So in the roles section, we can see that we already have a few roles like, you know, the general admin, read only admin. We have clinician, so we can create new roles here. Let’s see maybe researcher, and we’ll give it a key. We can decide what level the role is and whether to assign the role to some specific account. So as we said, multi tenancy, so we can already assign it to some account. We can assign it as a default role that is given to a new user once invited.
And after we’ve done it, we can start assigning permissions to this role. So maybe let’s go and, you know, we already have some permissions that are given by Frontegg, we have some Medical Connect custom permissions, we can create a new permission like, let’s say, access clinical trial data.
Okay. So We can choose a category for that, right? So we created a new permission, and obviously we can assign this permission to this clinician role or the researcher role that we just created, and that’s it. So basically it’s now assigned, so if you have this role you will have this permission then you can go and create some features in your app so for example if you have AI diagnostic report feature, so you can assign permission to this feature as well.
So let’s choose read AI report and generate AI report. So now for this feature, we would also have these permissions assigned. And the nice thing about that is that you can now go and assign this feature to some subscription tier. Right?
So you wanna only allow this feature if paid for the growth tier, for example. So we can assign this AI diagnostic report to only members that are users or customers that pay for the growth tier.
So we did that.
And automatically, whoever paid for the growth tier will have this feature. And by having this feature, they would have the permission within the app. So you don’t need to kinda you know, if if the sales team or the go to market team or whoever chose to change the the growth tier, the developers don’t have to do anything, basically, and everything is controlled through that. Same goes for feature flags.
So, you can create a new flag for diagnostic reports. So flag report, for example.
And now you can choose targeting rules.
So no need to pay for five different solutions just so you can manage this feature flag so you can decide that any tenant ID that, you know, was assigned for from Europe, for example, and contains Europe will have this feature because you’re rolling it out first to the European customers, for example. So, a great kinda capability to have. Again, everything is controlled from the same API that decides whether you can see or not, whether you can use this AI diagnostic report or not. And we can go into more maybe advanced things like entity based access control, so what we call Rebac, fine grade authorization.
So you can create keys for, for example, for owners to own certain diagnostics or patient files and then you can decide which of the users can access which specific patient data file or which specific report that it generated or whatever. So here we’re talking about dynamic access to entities. So that’s supported as well. There’s cool stuff about accessing APIs and etcetera.
So a single point for all of your authorization decision, we hear that a lot from HealthTech that it becomes complicated. You have different types of users, as Ron mentioned, different types of customers, and you want kinda a single layer that controls everything through that.
So, yeah, this is kinda in a nutshell about Frontegg entitlements.
Alright, thank you for that, Sagi and Saran. So, following that chat, I would love to hear if anybody has any questions. If you do, now is the time to put them in the chat.
So we’ll wait on some of those. Okay, here we have one. So question for Did you run into any pleasant surprises after rolling out Frontegg? So anything that you didn’t expect to get out of the platform, but actually ended up turning out to be a big win?
Yeah. I think I touched on it a little bit about entitlements. I was I mean, when we were about when I was evaluating Frontegg was not a criteria that I had.
And, you know, until, you know, we were engineers, so one of my engineers was evaluating a feature plug in system.
And and we’re evaluating multiple other things like external feature plugging and other products. And that’s when, like, the engineers said, hey. Looks like Frontegg has a inbuilt system, like, Do you wanted to try it out? And it’s like, that’s an odd platform, what it’s gonna do for for that.
And that’s how it started. I mean and, you know, when we started looking into it and we realized that the potential of the entitlements on on you know, we started with some basic features enabling feature flags, and and we started getting into a little bit complex in in how we even package our products. Right? And we and then we started that’s what I’m saying.
Maybe we started using we use the plants a lot and the features a lot and every features that we release, it’s through the feature plotting system that we have. So almost everything that we do is is based on different Tech and Tech months, and it was definitely an and pleasant surprise that I was not anticipating when I was choosing something.
Thank you for that. Do you have any other questions? Yeah, all right, thank you. So here’s a question for Sigee. So to the extent that you can answer that, if you can give us a preview into anything that’s on Frontegg’s roadmap that health tech companies should be paying attention to. So I guess this is referring to, like, any features or things that Frontegg might be rolling out that would be of particular interest. So somebody asked about that.
Yeah. I think that a lot of health tech companies have, we spoke about it a bit, they have different types of customers, but they also have different applications eventually for this type of customer. So at some point, one application will not do it in many cases, not in all cases obviously, and they will develop some apps for specific customers. I think that multi app capabilities are something that we’re taking to the extent of you know basically allowing all of the levels of combinations that you can imagine of single login to multiple apps, specific login to specific apps, single or multiple user pools that are shared or not shared between some of the applications.
So I think that all of these customizations are pretty important for a lot of health tech companies. But I would also say that I think that what we find is that in health tech there’s also different kind of jargon or you know, in terms of how they would approach user management. How they would approach the different type of application.
How for example for them hierarchies, as Saron mentioned, could mean you know health partners or something else. I think that we try to make it easy as possible for health tech companies to use our product.
So, you know, so kinda having something that is more tailor made for health tech, and we’re gathering a lot of information about it, and already have some interesting roadmap coming up. And obviously things around AI that are starting to get very strong into health tech and as well as other industries. And obviously a lot of the roadmap for Frontegg is around innovation and helping innovators in the world of AI and the agentic era. So, you know, definitely will be interesting. So keep an eye on what we’re doing there.
Yep. Alright. Thank you so much, Segi. Thank you to both of you.
So for anybody else who wants to learn more about what we can do for health tech companies, you know, I think we have a clear value proposition specifically because we’re able to simplify some of the more complex aspects of customer identity, as well as, you know, allow you to do the HIPAA protect customer information within more complex organizational structures with multiple stakeholders.
So please visit our website. We do have some content there, especially for health check companies, as well as, you know, we’re going to send a Sendoso gift card, so watch out for in your inbox, you’re going to get an email from our partner and a gift card for joining us today.
And here is just two sign ups. So if you wanna sign up, try out Frontegg, some of the things that Siggi showed us today. You can sign up for free. You can try it out yourself.
For start ups, you actually get a full year for free, fully functional.
And we also, that one pager is going to give you some more information about additional capabilities that we offer that are very much relevant for health tech as well. We’re also going to be sending a recording of this webinar, so keep an eye out for that. It’s going to be available on demand.
So I want to thank you again for joining us today, and thank you again, Saran and Siggi, for the interesting conversation. And hope everybody has a great rest of your day. Thank you.
Thanks for having me. Thank you.
Thank you so much.
The Complete Guide to SaaS Multi-Tenant Architecture
