The “How to Distribute Customer Identity to Non-Engineering Teams” webinar explores a better way to manage customer identity and access management (CIAM) by reducing the reliance on engineering teams. This webinar addresses the common challenges faced by organizations and introduces strategies to enable non-technical teams to take on CIAM responsibilities without compromising security or efficiency.
Key highlights include:
This webinar is ideal for engineering leaders, product managers, and security professionals looking to streamline CIAM processes, improve cross-team alignment, and free up engineering resources for higher-value work.
Alrighty. Hello, and welcome, folks, to how to distribute customer identity to non engineering teams. Today’s exciting webinar is brought to you by Frontegg and produced by ActualTech Media. My name is Mackenzie Putici with ActualTech Media, and I’m excited to be your moderator for this conversation today.
Today’s engineering teams shoulder the burden of feature requests and platform maintenance tasks surrounding customer identity and access management or CIAM, which often feel like low value distractions from core product development. Meanwhile, non developer stakeholders like customer success and infosec teams rely on engineering to fulfill their mission critical needs, leading to delays, status updates, and frustration on both sides.
Well, there is a better way, and that is what we are here to discuss today, A low code intuitive identity management platform that removes the dependency on engineering in a controlled way. Likely, that is why you’re here. You are looking for a better way to approach CIAM.
And luckily, we have got Frontegg CEO, Sagi Rodin, joining us to face this challenge head on. This is gonna be such a cool conversation, and I cannot wait to get started. So why don’t we zip through a little bit of housekeeping, and we will get things on our way.
Alrighty. First, I want to draw your attention to the question section of your webinar console. This is the best place to get involved, get interactive, post all your insightful questions, comments, feedback, and ideas. We do indeed want to hear from you.
So why don’t you find that questions tab now, and let’s start out by saying a quick hi, hello, hola, bonjour, aloha, or any greeting that you’d like to give to the other audience participants here today. Give a wave to the community out there. As a quick side note, that window is also the best place to reach out and let us know if you have any technical issues during today’s session. Knock on wood, of course, that doesn’t happen to you, But a quick browser refresh is usually enough to shake some fear into the tech gremlins crawling around here.
But if not, just shoot a message in that questions tab, and the ActualTech media crew and I will be here to help. And the last thing I wanna point out on your audience console is the handouts tab. Go check out some cool resources and follow ups to our conversation today because it is just packed with great info. So if you haven’t already popped over there, you’re gonna wanna get those awesome handouts as well.
Now finally, a cool bit of content. Sorry.
All that cool content is incredible.
So we’ve got a little bit more of a giveaway than just that awesome information, and that is a two hundred and fifty dollar Amazon gift card as a prize drawing at the end of our webinar. And, of course, you do need to be in attendance during the live event to qualify for the prize. All winners must also meet the ActualTech media price terms and conditions, which you can find in the handouts tab as well. So check that all out.
Additionally, there is a fifty dollar best question gift card up for grabs. So if you’re inquisitive, well, today, it may just pay to be curious, which I love. I’m gonna be posing some of the questions from you to Saghi, our speaker today. And so this is a great opportunity to be able to speak directly to the great minds, that we have here on the webinar.
So take advantage of that, and, again, keep those coming in throughout the presentation.
Alright. Well, that is everything for the housekeeping. So let’s get things started. I’m so excited to introduce you all to Sagi Rodin. He is the CEO of Frontegg, so an honor to have him on today.
First, I am gonna be posing some questions to Sagi in a fireside chat style. Then, Sagi’s gonna be going over a demo of some various profiles in Frontegg, and finally, we will dig into the questions from you, you are on the audience. So this is a reminder that there is that fifty dollar best question gift card up for grabs and that we will be answering as many questions as possible in the time that is allotted.
And with that, Sagi, I’m gonna bring you over to the stage and ask you to introduce yourself a little bit further.
Welcome. Welcome. Welcome.
Thank you so much, Mackenzie. Great to be here and great to talk to everybody.
So I guess we can, we can start. We’re Frontegg, building the next generation of, customer identity.
And, a bit maybe about our history shortly.
So, I’m Sagi and, together with Aviad, the guy that stands here next to me. We founded Frontegg in 2019, both of us coming from the security and cloud backgrounds, engineers in our hearts and souls. And we started Frontegg because we saw how customer identity was becoming increasingly complex for SaaS companies. So since then, that was, twenty nineteen. We’ve grown quite a bit and, got backed by, great investors like, Insight, Stripes, and, others. Some amazing company joined us. So we work with companies like, Siemens, Datadog, CrowdStrike, NVIDIA, a lot of just to name a few. And, you know, really proud of the people that work at the companies. So we’re spread between the Israeli office and the office in, in the Bay Area in Mountain View. And I’m taking the call from, Mountain View, today.
So that’s a that’s a bit about us.
Maybe a bit one slide that we’re very proud of.
We’re constantly being high rated by real engineers as the leading solution for customer identity.
This is, from G2. And, you know, it’s really great to see those folks really kinda clapping and, and routing for us.
And, and maybe, you know, just the last slide before we kinda, dig in and I and I and I give you the mic to ask me some questions.
This I think this mission statement really captures what we’re all about. We believe every software product could become better when identity is just not a bottleneck. So it’s not just about making identity simple for developers, which, obviously, we’re doing, but it’s about making it work kinda seamless for everyone who touches it, from the engineering teams building the product, to to security teams protecting it, to the end users who actually, experiencing it, live.
So that’s a bit about us, and, and that’s it. That’s, from me.
Alrighty. Well, let’s dive into this. I’m excited.
The first thing I wanted to mention kind of as a a level set is that it’s become the accepted norm for engineers to be fully responsible for implementing and managing customer identity. How did this become this way? How did this come to be?
Yeah. It’s it’s quite interesting how we got here. So, you know, back when SaaS was just taking off, customer identity, user management was seen as just another kind of technical feature. So you can think about it just like as a database management or API integrations, and it made sense at the time to hand it over to engineering because, well, who else is going to handle it? Right? But here’s what happened. As companies grew, things got more complex. And suddenly, you need to handle things like multi tenancy and enterprise SSO and security policies and multifactor authentication and handle user invites within the product and compliance regulations and stuff like that.
But it still stayed with engineering simply because that’s just how it always have been. Right? So, you know, what’s I think it’s fascinating is that for the longest time, there was just no other alternative. Right? So that just remained the way it was. And, we didn’t have tools like that, would let nontechnical teams safely, handle identity task without risking the security, aspect, without breaking things. So engineers became this sort of identity gatekeepers by default. And, it’s, it’s kinda like became the necessary evil, situation where everybody knows that identity is critical, but it’s often seen as a technical burden rather than a strategic asset, because that’s basically just not the core of what, you know, almost any company is doing.
And that’s really what we need to change.
I like that. So then, you know, we we’ve gotten here, but then from your perspective, you know, as as we kinda look at the challenge or the negatives of this, what are some of the biggest hidden costs, you know, time, resources, or otherwise that engineering teams face because they’re the sole owners of customer identity management? Yeah. A lot of hidden costs. So, you know, this is something I’m really passionate about because, I see it happening all the time. And, also, you know, as a developer in my previous life, I live through this pain kind of firsthand. You know, the biggest hidden cost for me is innovation.
Because every hour your engineers spending managing things like CIAM is an hour they’re not spending on building features that actually make your product unique. And, what really kills productivity are this kind of constant ad hoc interruptions that engineers get. And, you know, they’re deep encoding the new features, and suddenly they need to drop everything to help reset multifactor authentication for a customer, adjust the security policy, manage user invitation flow.
You know, these small interruptions add up very fast. And, and there’s the security pressure. Right? Like, with standards like GDPR and SOC two and HIPAA, engineers are constantly having to update, and, audit their software, manage authentication methods, and implement new security features. So it’s not just about building features anymore.
It’s about maintaining this ever growing complexity. But what often gets kinda unnoticed is the also the operational drain. And think about all the time spent managing SSO integrations, configuring this, MFA factors, you know, setting up tenant isolation, handling user provisional flows, you know, name it. And, these aren’t just one time tests. They’re going like, ongoing maintenance that actually slows, slowly eats away all of your engineering focus on the core.
You know, if if I need to think kinda where it hits me, I think it hits me at home sometimes because I remember this one time when I was a developer, like, deep into developing this exciting new AI feature, that I was very passionate about. Right? And then boom. We hit this with the, you know, this authentication bug. Not even something I built. You know? Just some legacy SSL integration acting up. And I spent, like, three days debugging it while you know, because customers can’t log in. Right? Like, it’s a mission critical bug. So everything else had to stop. And all I could think about was getting back to that AI feature, but instead, I was kinda, you know, neck deep in identity, logs, trying to find out what happened.
And, you know, every developer knows how that feeling how that feels. Right? And when you have to kind of put your real innovation on hold to deal with something that shouldn’t even be your problem in the first place. And that’s exactly why we’re trying to change this whole approach to CIAM. I love that. And I love the I love that kind of immediate response of innovation is at stake because, you know, I think a lot of companies are like, well, we wanna save time. We wanna be efficient, but those are all kind of these never ending desires. But if you ever ask a company lead, you know, do you wanna be less innovative? They’ll be like, well, no. So I I think you really hit on something powerful with that.
So speaking of this kind of, like, you know, potential loss of resources, do you think there’s a communication gap between stakeholders like information security and engineering, or is the tension around customer identity more often a structural and systematic issue in organizations? You know, those are all kinda good candidates, I I think, kinda to understand the problem more deeply.
But, you know, it’s interesting. Like, I think that while communication between teams isn’t perfect and probably as the organization grows, it becomes even, you know, less, perfect, the real channel challenge, I think, is more fundamental. It’s about structure. So most organizations haven’t figured out who should own identity management beyond the engineering team. And I see that all the time. Like, security teams want more strict MFA policies.
They want, you know, very detailed audit logs, while engineering is under pressure to ship features fast and make login experience smooth.
And it’s not that they’re not talking. They’re just, you know, operating with different priorities.
And what we often see is this bottleneck effect where nontechnical teams constantly waiting on engineering for identity related needs. So whether, you know, setting up rules, managing users, permissions, you know, roles, stuff like that. And not because engineers are slow, you know, but because the system isn’t set up for efficient collaboration. And the real issue is that most companies just slack the right tools to bridge the to bridge these gaps, between the technical and nontechnical teams. And when every security policy update or authentication flow, you know, needs engineering involvement, you’re kinda bound to have friction. It’s it’s built for friction.
So it’s not about better meetings. It’s about rethinking how we approach identity management at the process level.
Yeah. That’s really interesting. And, you know, so I think as we think about that and and that it’s it’s not though it can’t be done, it’s kind of how it’s assigned and how it’s communicated, you know, that this customer identity management, it’s not a tech issue, really. Right? But it does impact aspects of of product security, even customer support. So how would you suggest organizations maybe foster this kind of better collaboration between the technical teams and the nontechnical stakeholders?
Yeah. So let me share what I’ve seen that works really well. So first, you need the right tools. Right?
So platform that let, you know, nontechnical teams handle basic CIAM tasks themselves, you know, like configurations, like managing the invites, setting up the policy, setting up the the custom, settings for each account or even sometimes on a user level. Right? Sometimes a certain user needs different configurations. Right?
So you need to enable the back office teams, the operational teams, to do that, and that needs to be very easy and seamless for them to do that. Otherwise, you know, they will just give up. It’s also crucial to be really clear about ownership, about who owns what. So when everybody knows their role in the CIAM process, like, who can adjust security policies, who can handle the user provisioning, who manages the tenant configuration.
You kinda when that’s clear, you avoid those frustrating back and forth for unnecessary handoffs and, you know, misalignments.
And, and sometimes that’s often kinda overlooked, but you also need training. And you’ll be amazed at how much smooth things, get when, you know, when nontechnical teams understand what are the fundamentals of identity management, when it’s, you know, concerned to them. And they make better decisions. It’s everything is very clear for them. There’s bunch of, you know, amazing AI tools. For example, you know, we we, like, three months ago, finished integration of an AI tool into Frontegg where, you know, you can just post the question, how do I do that or that or that, and you get an answer. You don’t need to look, kinda find your way across this, you know, cumbersome screens and portals.
And, you know, that’s what’s really powerful is getting engineering product security, success teams together regularly. So it it doesn’t have to be long meeting. Just quick things to stay aligned on security requirements, on the authentication flows, on user management needs. And, you know, just one pro tip, involve nontechnical folks early in the process. It’s much easier to address these needs upfront than, you know, after the launch.
Very nice. Very nice. And, yeah, as you’re describing that, I can totally think of, say, like, you know, an a new recruit needing to be onboarded, and there’s HR, and they just need this done because this person is with them. But they have no real concept of what’s going on behind the scenes. And and, you know, it’s it’s it’s frustrating, but it’s almost comical where you could just see the disconnect and how it could play out and often does play out. So, I love this idea of encouraging them to get involved early.
Exactly. And you need to think about it. They passed the same DNA they had at previous companies. So they’re just they just don’t know that this might become part of their day to day job.
So you kinda have to, you know, make sure that they understand.
And, the early they understand it, the better it will be.
That’s awesome. So so then, you know, as we kind of talk about that and empowering the nontechnical stakeholders, how would you go about that? So, like, how do you pass on the torch of ownership without maybe losing control? What where is the the quantity of this is the right amount, and how do you go about that?
Yeah. So, you know, so you’re kinda asking what engineers can do to empower others and kinda, you know, release this, constant constraint. Right? So Exactly. You know, I always say it’s, yeah, so I always say it’s it’s one small change. And this change is not easy to make, but, you know, it’s one single change of approach.
And maybe, you know, speaking to the architects, to the engineers, to the VP of engineerings, the, you know, that are out there today, Maybe that’s one thing I would I would like you to remember from all of that is, you know, don’t solve for the feature. Solve for the independence. And that means, you know, don’t solve for this one Jira task that you have at hand, but, you know, for avoiding the ten that will come after.
And if you think about empowerment of others in the future, for the thing that you build or that bug that you solve, you give a ten x value to the company rather than just solving the problem at hand. And how do you do that? The key is using, you know, first of all, using low code platforms that make identity management accessible without requirement of deep technical skills. And think of it like giving people guardrails. Right? Like, they can’t break anything important, but they still can get their work done. And we’ve seen great success happening with automation.
You know, when you automate repetitive tasks like access provisioning, you create templates of things, so templates of, roles and permissions, and you can just duplicate and copy them, between different types of customers. So you’re not that way, you’re not only freeing the engineer times, but also reducing the chance of, an error happening. Right?
Another secret source maybe is really good documentation. You know, when nontechnical users have clear instructions, they become much more independent.
So they don’t need to kinda rely on engineering for every little thing. And I think that, you know, it’s about finding that sweet spot when engineering maintains control of the critical stuff while empowering other teams to handle the day to day tasks safely and efficiently.
So that’s that’s, you know, that would be my kinda two cents, for for for this. You know? Don’t solve for solving the feature. Solve for the independence of using this capability in the future.
That’s awesome. Thank you so much. I think we need to take that out and make it as a a quote that you can use for something, your your LinkedIn.
Awesome. So, with that, do you do you actually wanna show us under the hood and kinda give us a a demo of of what’s going on with these different profiles in Frontegg?
Yeah. You know, I would love to show how we kinda stand behind that in practice and, build a product that adapts to this evolution that is happening. Right? Because if you look at products, like, even five years ago, those products were aimed only at, you know, the basic kinda capabilities and the configurations behind them.
When today, you can think about customer identity as kind of the backbone of a SaaS product. Right? Everything starts from there. You know?
The users, the accounts, the the support and the the the feature management, everything. So so it becomes kind of the nervous system of, of the modern product.
So I would love to show you how the different folks in the organization use, Frontegg on the day to day.
Okay. Take it away.
Okay. So we will see, several kinda live examples.
Let’s start. So first of all, we can see here, an architect, for example, configuring, user pools. So user pools is basically connecting your existing identity provider, so you don’t always have to migrate users and stuff like that. Right? So it should be very easy to connect a new application.
Now think about it. Some organizations have one app whilst while others can have hundreds of applications, that, you know, that they need to connect. And, and the configuration of those applications should be very, very easy. So we made it at Frontegg kinda very intuitive to take the whole environment, the whole ecosystem you have in your organization, and, and basically just connect it, to Frontegg. So you can enjoy the value of everything that our platform has to offer, while not having to have this, you know, bottleneck of, you know, migrating everything to Frontec. So so this is the example that that, we’ve seen here.
You you know, and and then it becomes also about configuration of API access controls. Right? So let’s say that an architect wants to control who can actually access a certain API. Now I’m talking about APIs because APIs are still on the engineering, side of control. Right? They’re still kinda, considered as an engineering thing and not a product thing sometimes.
So no problem. If, you know, if an architect wants to take a certain API and make sure that you know, for example, here we see, we only want certain folks to access this, funds, API that, that we have in the organization. They can do it easily through our API access control.
So so this would be the second example.
The third and last kind of final example on the architect side is what about, you know, engineering teams, architects?
They’re kinda in the middle. They’re not, you know, developing code day to day, but they’re still pretty, you know, pretty technical folks.
They were engineers probably, like, ten years ago. And we made it very simple for them to achieve day to day tasks. Like, for example, here, making sure that, some users, have no access to to a certain API or to a certain feature. So they can use these short code snippets, on their own and basically just, you know, just, make sure that, they achieve their access control, capability very, very easily.
So that captures, you know, the architect persona. Right? Basically, think about it as, you know, enabling the architect with with the simple tools that they can achieve the task day to day without opening the task to, to the developer, which is very convenient for, architects. And we see in our systems that, you know, architects use that all the time.
The second, persona that I will cover is infosec or the security teams. Right? So what is important for security? Security is getting more concerned over time with what is happening within their customer facing applications.
So, you know, five years ago, we spoke to a security persona. They would only mention workforce. What is happening with the employees? What type of SaaS applications they can access?
What type of cloud assets they can access? But now they’re getting very worried about what is happening with their customer facing applications, and they need information about that. And we want to make sure that they get it in a very easy way.
So, you know, first example I will show is just reviewing security events, and managing basic policies. So you can see here that we enter the security events screen of Frontegg. You get full kind of visibility, over what is happening, within your application or within the ecosystem of applications. You can get the different security rules. We have nine proprietary engines, that that control the the different aspects of security risks for the customer facing apps. So for example, here, brute force protection was enforced.
Right? And that took us, like, just a second. So the infosec teams are really enabled, empowered by controlling the security aspects of the applications, without having to involve the developers in that, and that’s really, really convenient for them.
The second example I will show here for the security team is changing multifactor authentication session management. So, you know, I remember working in an enterprise and regularly, the these policies would change because of different requirements, by different compliance mechanisms that that we enforce. And, you know, just changing how much, what’s the length of the session. Right? And what is the concurrent amount of devices that can connect to to a certain user or forcing, you know, multifactor, different types of multifactor.
So so that’s, you know, that that’s those are, like, really important things, But think about how, you know, difficult it could get to enable those things or control granularity of which tenant can get, you know, this setting or which customer a huge new bank that we just signed needs very strict policies. And here, the InfoSec team can basically do that on their own. They don’t need to open tickets. They don’t need to involve engineering. They have the whole control at the at the back office.
So that’s really great. And, you know, I think the the third thing that I will show here is, you know, connecting to the ecosystem. Right? So we always know that Infosec, the most important thing for them is to connect everything to their existing tools.
Because, let’s face it, they have so many tools open on their dashboards. Right? And they want to kinda achieve everything from, from a single place without going to too many places. So for example, here, they can just connect their Splunk, ship all the customer identity logs to Splunk with a very simple configuration and, and do that on their own and basically, you know, continue the whole filtering, the dashboard, setting up the alerts on their favorite system, in this case, Plank, but we support, a lot of others kinda out of the box.
So this is about Seysaw, and I think the last, persona that we will cover is the product persona. Right? So we constantly talk about this tension between engineering and product. Right? So product kinda sits on this, you know, border or a crossroad between the business and the operational side of, of developing the features.
So they constantly speak to customers. They hear requests. They speak to sales and get requests to, you know, to develop things or configure other things. And and, you know, there’s constant tension here where product wants more, engineering is trying to to get them what they want, but also trying to maintain decent quality.
So we’re really trying to solve that tension between product and engineering.
I I will show a few examples that, you know, we try to make it very easy for the product people to, do their day to day job without, relying on engineering solely. So for example, here, we can see configuration of, of a login through, builder.
So you can see here kinda a WYSIWYG, you know, experience of setting up your login screen. You can see here that, you know, logins and sign up screens today are a way to control business. Right? So conversion, for example, through your sign up page, it is a thing that is being measured, not only in product led growth approach, but but also, you know, enterprises, allow sign ups today through short trials, and and it’s really important to get, you know, the best out of your sign up page.
So you can you can kinda see here how easy it is to control everything on the sign up page. Right? So you can set up the colors. You can set up the brand.
You can set up the pictures. You can do everything. You don’t need to change a single line of code.
And, you know, I I would kinda, urge everybody to sign up after this discussion to our platform, play with it. This is, this is really cool and, and sometimes, like, overwhelming. Like, oh, wow. Like, you know, so many things.
And it’s so easy to achieve it, at Frontegg. So, you know, we’re really proud of this builder that, that we, that we built along the years. So, so this is the first example. The second, it also involves product, and it talks about, you know, configuring feature flags.
Right? If you think about it, feature flags are just another way to manage the access control for see certain features. So why you have to use three different systems to configure, flags? Right?
So here, you know, we we identified a new feature within our app. We we defined it. We create a rule for who can actually, access this feature. Right?
So for example, here, only emails in the in the list in the provided list will be able to access this, this, feature.
We can play with the targeting for, for the access.
And after reviewing, basically, we can, we can just edit. And if we need to somehow enforce it or help our developers enforce it, we can just, you know, share with them this short snippet of code and tell them, okay. You know, you can you can just put that in the code.
You know, it wouldn’t take you more than a few minutes.
But most of the times, those flags are all already configured within the system, so they can just be just be configured for, for additional access, very convenient, for the day to day operation.
And the final thing, I will show you on the product side is the number one problem in SaaS, which is pricing. Right? We’re constantly trying to identify, what is the optimal pricing, setup for our product. Right?
So we’re moving features from the free plan to the paid plan, and, you know, we’re creating features that are becoming usage based and not a Boolean yes or no within a certain plan. Right? So you can use ten of those. You can use twenty of those here on the enterprise tier.
It’s unlimited or whatever. And think about the complexity of setting up those, kind of very important, aspects of business, right, that that happen almost in a monthly basis. There are changes. And on a monthly basis, when a small thing changes, you need to speak to engineering.
So here we’re showing how easy it is to set up an additional plan or to move a feature from one plan, to another.
Another example of how we can enable the day to day operation of SaaS, to, to nontechnical personas.
So that’s, you know, those are kind of the examples that I’m showing here. We have many others in our platform. I didn’t show customer success, for example, and how they’re using Frontegg, right, or or business people and how they enable SSO or or, you know, go to market features just like that. So that exists as well. And, obviously, you know, feel free to contact me afterwards, and we can arrange a demo.
Alrighty. Awesome.
Thank you for that, Sagi. You really are are a great presenter. I love seeing Frontegg in action as well. And, truly, as much as I love tech, when I see a coding screen, my brain kinda slows down, whereas this, it’s just so slick. It’s easy.
This is really great.
We’re gonna have to we’re gonna have to dive in further at some point.
For sure.
Okay. Well, we’ve got a few questions in the queue. So I know we don’t have a ton of time left, but what do you say we dive in and, address a couple of those?
What to start with?
Yes. Okay.
Since AI is a hot topic, how do you see trends like AI and automation impacting the role of identity and access management in the next few years, and what should engineering leaders start thinking about today to stay ahead of these changes?
Yeah. So I think, you know, we can tackle the this question from different angles. Right? So AI, at the end of the day, like, if you look ten years forward, probably applications will not be point and click, and you will just use prompts to operate most of the kinda functions that you have, enabled through, you know, UI basic UI as we know it in SaaS.
And and, you know, I think that we need to adapt to it. What we’re doing at Frontegg is basically taking the AI aspects and allowing to achieve certain tasks within the day to day operation, without working hard. So, for example, in our new flows feature, I won’t be showing that, today because we don’t have time. You can you know, if you need to create this cumbersome kind of flow diagrams of what a user experiences and if they are doing that, then do that, it’s it becomes, like, really hard to achieve those things with with drag and drop and configurations.
So we made it really easy. We added a prompt. And, basically, through this prompt, you can do anything through natural language. Right? So we’re trying to constantly adapt to that.
I think that another thing that, you know, another angle that we can address to that is authorization within this kinda agent, world that, that we’re all kinda hopping into.
And and, you know, authorization is not going to be, you know, this kinda structural, parameter based key value authorization, but going to be, authorization that is more natural language authorization. And we’re adapting to that as well. So I think that, you know, we have a lot of awesome innovations that are happening and will be happening soon.
For the engineering managers, I think that, you know, this also has to do with embracing these tools that will just make it easier with time through AI, to achieve these day to day operations. And when we can automate things or create things, like, on the fly and generate things things automatically, you know, that that would be amazing and will will help us achieve the day to day tasks in even easier way.
That’s great. I love it. The easy button is what I’m always looking for, so it looks like you’ve got it.
Okay. Next question I’ve got here is, what are some practical ways you’ve seen practical ways you’ve seen companies bridge the gap between engineers and nonengineers?
Yeah. So, you know, just, just as I, mentioned here, you know, define the right processes, do the right training, and use the right tools at the end of the day. Right? And, I think that, you know, sixty percent of the problem is solved when using the right tools. Right?
It can just help the day to day, you know, very easy kinda shift. And and sometimes, you know, we’re thinking about embracing new tools as something that, you know, it’s hard. We need to migrate users. We need to adapt to this new, system, adapt to this new language, adapt to this new UI.
But at the end of the day, sometimes when the tools are good, then the onboarding part is not that hard as we sometimes think. And and, you know, you can in a month and we’ve seen that happening through Frontegg, a huge organization that came and said in the first call, we have, you know, a very unique problem. No way you can solve it for us. And then, you know, three weeks later through a POC, they understand that it’s not only that they solve their problem that they thought they have, but we solve so many other pains for them, through, you know, embracing just how the way that we think about things.
So so, you know, I would I would argue so that that should be the right approach.
I love that. And I think that is a it is such a mindset thing, and you kind of alluded to this in a few ways throughout the webinar. But, you know, it’s not like fixing just for a specific problem, a specific tool. Once you take an approach that really does get so many things out of the way, all these tedious things, you’re you’re just surprised by the overall outcome sometimes. Hopefully, always.
Okay. We are gonna have to wrap up shortly here. So I wanna mention for those of you, in the handouts tab, there is a case study. So, you know, if you are looking for kind of a practical way this has been rolled out, that’s one of the handouts, and I will cover all the handouts, in a minute. But, you know, as we wrap up here, Sagi, if someone’s just excited to try this out, find a little bit more information, what would you say are kinda first steps, next steps for anyone out there in the audience?
Yeah. So, you know, we’re customer first. So first of all, I would love people to shoot me a note personally, you know, before we go to the official channels.
That would be great, you know, not only to kinda sell you the product, which I’ll I will try probably, but, but just to talk to you and hear about your, you know, your way of thinking about things and your challenges, and it’s always great to learn. So that’s on the personal note. On the more kind of official channels, you can sign up to Frontegg. It’s a you know, we have a freemium tier.
We have a free trial for the whole, platform so you can play with it. No strings attached. You can talk to our team. You know, we constantly get the best support badge, in the industry, because we’re really centric about the customer, yeah, about the customer and their challenges.
We’re proud of that. So, you know, I’m I’m I’m owning this. I’m I’m saying that while, you know, being very proud. So you can contact our team.
You can get into our Slack channel. There’s a community there. You can ask any question. We would love to help, not only about identity, but about how to kinda, you know, create this right ecosystem within your SaaS environment, within your modern product environment.
And, you know, we would love to share from what we’ve learned.
That’s great. And and I love the the focus on the human element. You know? With with automating everything in tech, it is great to to hold on to that and just know that, hey. I actually need some help, or I’m developing this. I want I wanna dive in. And and so having those resources and those kind of quick contacts, I think, are so valuable at the same time.
Alright. Before I let you go, any final, nuggets of wisdom? Anything you think people, should be thinking about as we kind of end twenty twenty four and move into twenty twenty five?
You know, we we examined a lot of the customers that we had. We had, about twenty startups that started to build with us and made a huge success through, you know, this amazing exits and stuff like that. And what we’ve learned is that when you handle your product properly and your customers love you is that’s where it’s where they, you know, will will, recommend you to their peers. And and, you know, so I would just say invest in your product, invest in the user experience, and, you know, find the right methods, how to achieve that without throwing everything on the engineer and making everything the problem of the, you know, of the engineer.
They have a lot on their minds. They’re doing amazing work. Let’s make it easier for them, but also not sacrifice the business and not sacrifice the user experience while doing that. So I think that, you know, this I hope that I help with that during the conversation today.
Awesome.
And I think you give a unique perspective.
Right? You’re a CEO, founder, but you’ve also worked in these different roles. So you you do have this kind of larger holistic view of of, yeah, how do we how should we go about this? So I think hearing from you has been super great.
I know I said we’re wrapping up, but I saw one just itty bitty question sneak in. So if you can address it before we wrap. This is from Michael. He’s asking, is an agent install needed for this, for Frontec?
No engine, no agent install is needed.
You know, we we we’re pure SaaS. If you do have, you know, a use case where you need one of your customers to to hold their users on their environment, we totally support that.
So you can install us as a, you know, as a Docker and stuff like that. But but definitely, no agent is needed to to support everything that I showed here.
Awesome. Well, great. I guess we are at time, so I’m gonna let you go. Officially, one final thank you for being here. It’s been such a such a pleasure, and, I can’t wait to have you back at some point in the future.
Thank you, Mackenzie. It was great.
My absolute pleasure. Take good care.
Alrighty, everybody. I think, that is my sincere thanks to to everyone for coming out today. Sincere thanks to Sagi for, letting us pick his brain and really giving some, fantastic information here and showing what Frontegg has been up to. I do want to remind you all to visit that handout section before we close out. Once again, couple great things in there. We’ve got a white paper, the Frontegg security approach, software design, architecture, and philosophy.
So that is the first thing in there. Second, there’s a case study for Hint Health, titled Hint Health Saves Engineering Resources and Improves User Security Leveraging Frontegg Identity Platform. If you did wanna check out a demo, there’s a link to do that. Easy peasy, and you can book in a time slot that works for you as well as a link to sign up for free.
And so all of those there are in the hand notes tab. You definitely don’t wanna sleep on those because we’re gonna wrap in just a sec. And final call out to those QR codes there as well, because I am gonna be taking this slide down and move into our last, couple things here. So scan away, and, and then we’re gonna go from there.
Now, tons of great information. I know it’s a sweet giveaway, but we have that one final giveaway here, our two hundred and fifty dollar Amazon gift card. And one final reminder that you do need to be live and present here on the webinar to win. And with that, I’m not gonna wait for you, make you wait any longer.
The winner of this gift card is Matthew Belland from Minnesota. Huge congratulations, Matthew. And as always, we’ll be in touch about claiming your prize after the webinar. And, again, for those of you who ask those awesome questions, we’ve got that fifty dollar best question gift card up for grabs, so you might also win that.
And we’ll be reaching out again after the webinar to let you know how you can claim that prize.
And on behalf of the ActualTech media team, I just wanna give my thanks to Frontegg for making this webinar possible. I wanna thank once again, Sagi, for being here and for giving us so much to think about today. And, of course, I wanna give special thank yous, high fives out to everyone out there in the audience because without you, this would not be possible.
And I know sometimes it’s difficult to stop, all these daily tasks and, you know, if we’re busy and we’re being, pulled in all these different directions, we don’t always have time to think ahead, strategize, and really solve the problem in a holistic sense from, implementation, from strategy, using the right tools. And so thank you for pulling your heads up today and and taking time to think about how you can distribute customer identity to non engineering teams and make some really powerful change in your organizations.
And with that, I cannot wait to see you all on another webinar again soon. But until then, I’m wishing you an absolutely magical rest of your days. Take care, everybody.
The Complete Guide to SaaS Multi-Tenant Architecture
