I use Okta Platform for single sign-on and managing the authentication process. I have used all of the geofencing features for security purposes. In the current field of cybersecurity, I have been working for seven years specifically.

My favorite aspect of Okta Platform is that it is really user-friendly. The admin configuration UI is user-friendly when you view it.

I have worked on Okta Platform's IGA features, and they were not great or up to the mark. While they were trying to get new features, it was not working as expected at that time when it was in beta. There are some features, especially on the customization side, that cannot be customized, and there are a few things that would be nice to customize as well.

I would like Okta Platform to protect non-human identities in the environment, such as service accounts.

In terms of industry or regulatory requirements, it depends on the person implementing Okta Platform. All necessary protocols need to be followed, but I don't think Okta Platform has set any templates to ensure these protocols are being followed. It would be a nice-to-have feature where they could set some templates and provide guidance on what can be implemented.

I have been working with Okta Platform for five to six years overall.

Okta Platform is stable with very few instability issues.

Okta Platform is 100% scalable.

I have had to contact technical support for Okta Platform many times.

The speed and quality of their answers depend on the nature of the issue. Sometimes it was an easy fix, and sometimes I had to do a lot of back and forth. Speed is good initially, but depending on the problem nature, it becomes a little stagnant. However, I have no complaints as I think they have been super helpful. Even if they are not able to help, it goes to another team member, but they generally try to help.

I would give the support for Okta Platform a score of seven out of ten.

I have used alternatives to Okta Platform.

I was definitely there for the initial deployment of Okta Platform, and I would rate it as medium.

A team is required for Okta Platform. I don't believe we should be dependent on one person, and there should be people from many different teams involved. Even if there is not a lot of work, in all of my projects, Okta Platform has indicated that we need people. In one or two instances, Okta Platform professionals were not there to help, but I highly recommend someone from Okta to be there to guide us through the whole process.

Okta Platform requires maintenance on my end as a customer. It is 100% the customer's responsibility to maintain all features. Even if someone is going out of the company, there needs to be deactivation, so everything needs to be maintained by customers of Okta Platform. With respect to features and patches, sometimes they release a few patches that we will have to update ourselves, but in other cases, they try to do some silent pushes. However, it totally depends on how Okta Platform chooses to do it.

Overall, regarding the pricing of Okta Platform, I think it is a little expensive.

The biggest differences that come to mind are that, positively, Okta Platform is more user-friendly, but negatively, Okta Platform is way more expensive than a few other products in the market.

I have used Ontra, Ontra ID, PingID, SiteMinder, SailPoint, and Saviant, which are not exactly competitors to Okta Platform but somewhat similar.

How long it took to finish projects with Okta Platform from start to finish depends on multiple factors. I have done many projects with Okta Platform, starting from overnight to even a week, so it depends on the customer as well, on what is being implemented, and what the go-live date is for the particular time. The deployment depends on a client-to-client basis. My overall review rating for Okta Platform is eight out of ten.

I use Okta Platform as an administrator to set up new SAML and SSO apps. We also use the governance module as well. We also use the automation functions with workflows. We use it mainly as our main identity platform. I have been using it at all my past companies.

What I appreciate about Okta Platform is that it is most of the time a very good no-code platform. It allows us to set up new SSO integrations quite easily, even if the app doesn't really support SSO natively. It is pretty easy to configure on Okta Platform.

Okta Platform has impacted my organization positively by providing convenience, first of all. There are no more different passwords for many different apps, since SSO doesn't really require password storing. Security has also improved because we eliminate a very big weak point that passwords represent. Additionally, we maintain control to ensure we only give access to the necessary apps to the necessary people.

I would definitely see improvements in the governance module of Okta Platform. The way we do certification of accesses, certification campaigns, and access requests could be improved. A better way for users to actually request an instance in Okta Platform, for example, an app, without having to use a third-party integration for ServiceNow or Jira Service Management, would be valuable. Having something built in to Okta Platform would be beneficial.

From the features perspective, functionality-wise, I would see recent features included in Okta Platform. Our company works on a hub-and-spoke model, and Okta Platform did introduce a way to have more of a federated level. What they call claim sharing, and we really would appreciate a bit more improvement on that functionality, since that functionality helps us to have a single identity on a hub and pass that identity to the other spokes and have seamless login between all of them. Claim sharing helps with that, but the function is still not the best, especially related to authentication policies. There are still some issues, especially when we have some mismatch between the authentication policies on different spokes. I definitely would appreciate some more improvements. Additionally, I would appreciate a bit more improvements on the logging features of Okta Platform, which still are not the best.

I have been working with Okta Platform for more than five years at this point.

Regarding the Okta Platform, it has been stable. We do have different cells in different countries since we work on a hub-spoke model. On our EMEA cell, it has been quite stable. We did have some problems before on our US cells in these past few months, but nothing too serious. Most of the time, issues happen after hours on the US market. On our EMEA side, there have been no issues in these past few months.

I find Okta Platform scalable and have not hit any limitations or scalability issues with it. We do have a good contract with our vendor that allows us to set up new users at any time and they basically review the contract a year after if we need to have more users. We really don't have scalability issues.

If I would evaluate customer service and technical support of Okta Platform from one to ten, I would say a very good nine. We do have a very good relationship with our customer support representative, customer support manager in this case, or CSM. We also have a dedicated Okta Platform tech that we go to with more high-level questions. The level one support with the normal ticketing system from Okta Platform works pretty well most of the time. I never faced any issues, and if we need to escalate it for more complex issues, we can go to our dedicated tech manager support or our customer success manager and they are pretty quick to respond.

I have mainly used Okta Platform. I did use a bit of Ping Identity, but it was so long ago that I really don't remember a lot of the platform at this point.

When it comes to the deployment process of the initial setup with Okta Platform, we definitely faced some complexities, especially related to the way users authenticate. Sometimes authentication policies are a bit buggy in the sense that sometimes they really don't detect the correct browser that the user is using or there are issues related to the location of the user. The part of security authentication sometimes really doesn't work as well as it could. We did experience some problems in that sense.

The deployment of Okta Platform was implemented fully in-house.

We did look at other solutions as well, such as One Identity and Ping Identity, before choosing Okta Platform. We decided to go with Okta Platform since it was the more complete option on the market at the time, with all the necessary functions that we had, especially related to authentication policies. It also had a better catalog of pre-built apps as well, so it was a bit more simple. We also started looking a few years ago to maybe replace Okta Platform with Entra ID, because we also did have Azure products, but we decided to keep Okta Platform because Okta Platform still has much more documentation and much more time in the market. Their solution is a bit better in that sense.

My best piece of advice for others who are looking into implementing Okta Platform would be related to the knowledge base. I would make sure people read through the main knowledge base from Okta Platform, so the main steps of integrations. One of the good advantages of Okta Platform is that most applications and authentication are all the same, since it uses base protocols such as SAML or OIDC. If you are able to build one, the other ones are pretty easy to build. Go through the knowledge base that Okta Platform has, which is very rich for understanding if it is actually a good solution for your problems. If it is, Okta Platform would be a good solution to use.

The AWS services that are integrated or secured through Okta Platform mainly include AWS Cloud directly for cloud computing purposes.

Okta Platform does protect non-human identities in our environments, such as service accounts. We have the perspective that we can monitor the access, so who actually accesses the accounts and who is the manager of those accounts. We maintain password rotation and password policies for those types of accounts, which are different from a normal user account. Okta Platform helps us with that.

Related to the financial market, Okta Platform helps our company address specific regulatory requirements because we need to be SOX compliant, since we are a public traded company. Okta Platform helped us with being SOX compliant.

I have noticed measurable security and operational improvements in our cloud-based workloads since implementing Okta Platform. One of the main ones is access to AWS cloud environments. Thanks to Okta Platform, we can set up push groups to the AWS IAM module. We can actually give access to specific AWS spaces to specific teams in this case. For example, if we have a cloud team that works on a specific region, we can give access to an Okta Platform group to that specific team, and they will have access to that AWS cloud space. We have a lot of that, and it helped us a lot.

I would rate this review a nine overall.

Use cases include onboarding SAML applications, onboarding OIDC applications, onboarding third-party vendors for accessing these applications, enabling single sign-on across internal and external applications, enabling multi-factor authentication, and enabling adaptive authentication that triggers based on risk score.

Okta Platform is among the market leaders in this space. They have numerous integrations available out of the box, and some of the functionality beyond access management is also there, such as IGA capabilities and PAM capabilities. Overall, I have had a good experience.

Okta Platform has been in the industry for a while, so they have become quite mature in terms of product. The product is robust and does not have many bugs in it. They offer a range of out-of-the-box connectors, so you can quickly onboard target applications without custom integration. The ease of integration with multiple other applications is a key point I would highlight.

The main benefit is single sign-on. All access management solutions, including Okta Platform, provide single sign-on capability and multi-factor authentication capability. These are the two core functions any organization should implement. Beyond that, they also offer advanced capabilities such as passwordless authentication, so you can integrate your FIDO2 equivalent devices and enable passwordless authentication to your applications. These features are basically why they are quite famous in the market.

Okta Platform secures access to cloud infrastructure, APIs, containerized workloads, and AI and GenAI services in a similar way to how they do SAML and OIDC. Recently, they have rolled out some capabilities in the GenAI or Agentic AI area, where they can secure AI agents and manage the provisioning and deprovisioning of their identity and access parts. Regarding web APIs and everything, they have solutions to secure API accounts, ensuring access is provided only to required users based on access control.

Okta Platform does have PAM capabilities, and there they onboard non-human identities and manage and govern them. They definitely have some of the latest capabilities, such as OpenID and OIDC connections that you can utilize for your cloud workload and manage access to your cloud provider. They also have some fine-grained access available, enabling segregation of duties. These improvements bring operational efficiencies as well.

Okta Platform is quite mature, but I would like to see more integration. While they have a vast range of integrations out of the box available, if their PAM and IGA capabilities were more mature, then Okta Platform could be the single solution for everything, covering access management, privilege access management, and governance of identity. This would mean one would not need to take multiple products for specific identity needs in each area.

I have been using Okta Platform for seven to eight years now.

I find Okta Platform to be stable.

I believe Okta Platform is scalable. You can deploy it for 10,000 identities to 5 million identities. They have good elasticity and resiliency, so I find it quite scalable.

Both the tech support team and customer service team are good.

I have used OneLogin in my past with one of my employers, and we were using OneLogin for single sign-on, MFA, and passwordless journey.

The pros are that both Ping and Okta Platform have been in the market for a while, and they were among the first to provide single sign-on and MFA capabilities. They have become quite mature with multiple capabilities available, which is advantageous. They are enterprise-grade solutions and mature enough for any kind of organization to deploy. On the other hand, with OneLogin, there were some bugs I encountered, and I always needed to work with the product and R&D teams to get them fixed, so the product was not as mature or stable then. The pricing point for OneLogin is appealing, which draws customers in, but in terms of capabilities and features, both Ping and Okta Platform have a slight advantage.

Okta Platform is much easier to deploy.

I am using the SaaS deployment model.

Okta Platform has delivered ROI in two ways. First, it improves the security authentication and authorization processes across the organization, securing applications with single sign-on and MFA. Second, it helps cover compliance requirements, whether following SOCS compliance or any similar compliance. It assists in reducing user friction and the manual work of managing multiple applications independently while improving security.

I would not say Okta Platform is a cost-effective solution. It is an enterprise-grade solution, so it is comparatively on the higher side in terms of cost. It is not as cheap as you may find with other single sign-on products.

The main key feature Okta Platform is currently working on and has launched recently is Agentic AI for securing those Agentic AI identities. That is the one I would highlight as compelling at this moment, given that everyone is talking about Agentic AI.

My advice is to understand your requirements and decide your product based on that. Okta Platform could be good for enterprise customers because it serves multiple use cases and offers various capabilities, similar to Ping. If your requirement is very specific, then conduct an assessment and POC, identify your real use cases and future growth areas, and then make the investment to achieve real ROI.

Most likely, Agentic AI and healthcare are the two key industries. I would say everyone else as well, whether retail, pharmaceutical, or manufacturing. Everyone who wants to utilize single sign-on or multi-factor authentication tends to use either Okta Platform, Ping, or OneLogin, depending on the situation. I have not seen OneLogin in many customer environments. I would rate this solution an eight out of ten.

As part of Identity and Access Management solutions, or IAM, that many organizations use, Okta Platform is a mature cloud-first IAM platform that uses many single sign-on methods. This is one use case for applications, along with MFA and federation across SaaS and custom applications.

Okta Platform helps to secure access to cloud environments, APIs, containerized workloads, and AI/GenAI services in my architecture by allowing me to create the application in Okta Platform and assign it to the right users and groups, then start configuring the authentication. The first step is multi-factor authentication, which helps secure that only the approved users and groups are allowed to use that application, whether it's an AI application or an on-premise organization application. Another important measure to avoid attackers from gaining users' credentials, such as passwords, involves single sign-on. Additionally, Okta Platform has an adaptive access policy, meaning the user, or employee in this case, does not need to remember the password. Once the administrator configures SSO, the user does not need to go through password authentication; if they are authenticated using MFA, it works directly.

The use of Okta Platform to protect non-human identities in my environment, such as service accounts, machine-to-machine access, or AI agents, is limited since in the organization I work for at Deloitte, we use Microsoft for that. Okta Platform is a great IAM solution, but it is not an IGA solution, short for Identity Governance. The first thing an organization needs to look at is to understand their use case: do they need IAM or IGA or do they only need IAM? Because if it's only IAM, Okta Platform is good, but if they also need IGA to govern non-human identities and others, it is not a solution for that.

Okta Platform helps to address specific industry or regulatory requirements such as healthcare and financial services in my cloud environment. For instance, it benefits the banking industry and the e-commerce industry as well. However, it is available for many industries because it's a very mature and cloud-first IAM platform, making it perfect for companies or startups that are just starting out; they don't need to go through on-premise setups.

What I like about Okta Platform includes its large, pre-built application integration catalog, which is very useful. It also has strong support for the SAML standard and OpenID, commonly referred to as OIDC. Additionally, it offers good API and extensibility for custom use cases and works well in hybrid and multi-cloud environments.

The main benefits that Okta Platform brings to the table include strong authentication, which is the first thing, and adaptive MFA, which is very good. For example, if someone tries to log in from a country that is different from the countries they typically sign into, then Okta Platform will ask them to perform another authentication to verify that it is, in fact, the same user. Strong authentication is crucial, along with federation that I used for both cloud and on-premise systems. Federation worked very well, and it facilitates fast SaaS onboarding, with application templates in Okta Platform which make the whole configuration easier. Coming from a Microsoft background, I appreciate how Okta Platform is vendor-agnostic, meaning you do not need to depend on anything; it can work with any identity or identity governance vendor.

I noticed measurable security and operational improvements in my cloud-based workloads since implementing Okta Platform. It is very stable; we didn't have many errors when it came to users trying to log in, which is the first thing. Federation also worked, and that's one use case I can say I used it for. I had a client that was an organization with over 5,000 employees, and they wanted the authentication to go for Microsoft, but through Okta Platform. In reality, what happens is the user tries to log into an Okta Platform application and then gets redirected to Microsoft. That is federation, which refers to redirecting them to a Microsoft page. Once they complete the right authentication, they are redirected back to Okta Platform, making it a successful use case for a large organization in the insurance industry.

While there are many good things about Okta Platform, I would like to see improvements, especially in the IGA capabilities, which are limited compared to more dedicated IGA tools. I believe adding this would give them a real benefit. Additionally, it is not designed as a privileged access management solution, referred to as PAM. As I come from a Microsoft background, I see that Microsoft has both IGA and PAM capabilities, which Okta Platform lacks. Another area for improvement is pricing; it becomes complex and expensive when you add features. I would like to see licensing transparency, possibly some cost control notifications. Lastly, better policy visualization would be nice to have, showing how the policies configured can be represented more visually.

I have been working with Okta Platform for the past year.

When it comes to scalability, I find that Okta Platform's performance is very good. That's the whole point. As soon as you scale up, it often comes with additional costs, but that worked perfectly for us. We managed to implement it for a large organization with many users, so there was no problem; it was very stable.

I would evaluate customer service and technical support for Okta Platform by noting that we did need assistance once when we blocked ourselves out and had to contact Okta Platform support. It took about two days for them to respond, which I think is reasonable. However, this also depends on the support license that you have. We had the minimum one, but still, two days is acceptable as they helped us resolve the issue.

My experience with the deployment of Okta Platform is that the initial setup is straightforward for standard use cases such as fast SSO and MFA. However, complex environments such as hybrid AD, custom applications, or lifecycle automation require careful design and skilled implementation to avoid the technical debt that's often referenced.

Regarding the pricing of Okta Platform, while it is high and complex, I find it does bring a return on investment. The important thing is for companies to evaluate the total cost and not just the base licensing because once you add more features, the total cost increases. This evaluation varies based on the organization's use case; if it's below around 100,000 users, it should be fine. However, if you plan to go beyond that, evaluating the total cost becomes crucial.

I decided to switch to Okta Platform for different use cases for different organizations, particularly at Deloitte. We noticed that many of these organizations that are very Microsoft-heavy, meaning they have many products with Microsoft, find that Microsoft Entra ID, which is an IAM and IGA solution, fits them perfectly because they are already in that Microsoft ecosystem. However, for organizations that are not heavily involved with Microsoft, then Okta Platform is a great solution because they do not need to be dependent on any vendor. It's cloud-first, and so if you need specific IAM without being tied to Microsoft, I think Okta Platform is the best alternative.

Given my experience with Okta Platform and with other technologies, my advice to other organizations considering it is to clearly define if they want IAM versus IGA requirements as early as possible. Okta Platform is not a full IGA platform, and organizations need to understand that coming in. They should also evaluate the total cost and not just the base licensing. Lastly, if they are Microsoft-heavy organizations, they might consider Microsoft Entra ID, but if they are not deeply tied to Microsoft, then definitely go with Okta Platform. I would rate my overall experience with Okta Platform as an eight out of ten.

Our company is an educational training platform operating as a global online training model. We focus on IT services and training, managing global employees and user accounts while handling the onboarding and offboarding process. We specifically use Okta Platform to manage MFA, SSO, and logins for multiple applications. It is integral to our identity and access management strategy, effectively centralizing our application management. We opted for Okta Platform because we wanted a separate, unique platform solely dedicated to identity management, unlike Microsoft Azure, where additional interconnections like Entra ID and Intune might be required.

Okta Platform offers valuable features such as centralized identity and access management, which allow for a single sign-on process, simplifying user authentication across applications. Its scalable management solutions provide strong multi-factor authentication, integrating easily with various applications using protocols like SAML, OAuth, and OpenID Connect. An intuitive admin interface makes user roles and access policies easy to manage, enhancing overall operational efficiency and security.

Security improvements are notable, with centralized identity control and reduced IT workload through automation. Okta Platform supports onboarding and offboarding employees, improving user experience with fewer logins needed.

Overall security posture with adaptive multi-factor authentication centralizes access control, especially benefiting hybrid and multi-cloud environments. Smooth deployment and scalability eliminate lag, providing seamless and stable operations in managing user accounts and identities.

Okta Platform's pricing model can be expensive for smaller organizations, affecting user feature accessibility. Initial setup and configuration require careful planning and experience from administrators. Cloud-based infrastructure may lead to access issues during downtime or service disruptions. Support response time could be improved, especially for non-premium customers.

Pricing could be more competitive compared to alternatives like Ping Identity, OneLogin, and Microsoft Azure AD. More responsive customer service, enhancements in setup configuration, and support could improve the platform. Prioritizing customer issues in support tickets based on urgency level might enhance response time, helping businesses manage crises more efficiently.

We have been using Okta Platform for almost three and a half years.

Okta Platform is absolutely stable, with no experienced lag. This ensures immediate action upon changes applied within Okta Platform, stabilizing operations in managing user accounts, identities, logins, and user profiles. With functionalities running smoothly, it fulfills stability expectations effectively.

Okta Platform's scalability is robust and performs well. It responds quickly and does not delay processes, yielding timely, appropriate results. There is no lag, allowing the platform to function smoothly. It is secure, providing needed scalability without impacting performance.

While the deployment process was smooth, helped by Okta Platform's support team, more immediate assistance post-deployment is required. Currently, the support response time is too long, adversely affecting business during urgent issues or scenarios. A suggestion is improving the customer support experience by introducing a priority system for issues, allowing urgent cases to be addressed swiftly. Adding features in support ticketing to prioritize urgency could enhance effectiveness.

By offering a system to set varying priority levels on support tickets, urgent issues could receive quicker attention, benefiting business continuity and customer satisfaction.

We considered other identity platforms available in the market and ultimately chose Okta Platform for its unique, standalone identity management capabilities.

Oakta Platform's deployment and initial setup were smooth and straightforward. We were guided effectively by Okta Platform's support team on how to configure it to fit our business needs and tenant setup.

Our team implemented the platform internally without utilizing external consultants, integrators, or resellers, except for support guidance from Okta Platform's support team.

We have a basic business standard license for Okta Platform. If we go beyond that, it is a little pricey compared to other models. Alternatives like Ping Identity, OneLogin, and Microsoft Azure AD offer minimal costs.

Comparisons were made with platforms like Microsoft Azure, which require interconnections, unlike Okta Platform's independent design. Our management team ultimately preferred Okta Platform for its unique identity management focus, taking insights from Okta Platform's demo presentations.

Okta Platform's genuine uniqueness in focusing on identity is appreciable, unlike other tools requiring interconnected services. However, the pricing, initial configuration, and support response need improvements for enhanced customer satisfaction. A customer feedback mechanism to prioritize urgent issues might ensure timelier assistance during crises, maintaining business continuity and satisfaction. I would rate this overall experience as an eight out of ten.

In my current job, we do rely a lot on Okta Platform but we are not using some more advanced features from them; we have some basic subscription with Okta Platform regarding the single sign-on product they offer.

In both my previous job and in this one, we are using it as our main identity provider for our employees to log in into as many apps as possible with it, just to keep things as secure as possible and provide a good employee experience. Instead of our employees having to remember a lot of passwords and credentials, they rely on one single Okta Platform account to access as many systems as possible.

We are not relying on Okta Platform to secure access to cloud infrastructure, APIs, centralized workloads, or AI/GenAI services in our architecture at this time. I know there are ways to leverage Okta Platform for securing APIs and servers, but we mostly rely on Okta Platform for human access.

We do have some service accounts that we rely on, but I wouldn't say we are using more advanced features from Okta Platform. We do use those service accounts to integrate with other platforms, but I understand that the question was mostly about more advanced features from Okta Platform.

Both in my current job and the previous one, we were in Fintech companies in the financial space. One of the reasons to go with Okta Platform is because they are a well-reputed company, providing some attestations such as SOC 2. We try to go with a reliable, reputable company that other companies in the same space tend to choose, so it's a no-brainer to go with Okta Platform.

Okta Platform is the gold standard when it comes to identity providers and the single sign-on experience. I haven't tested similar solutions or any of the competitors, but I'm happy that both companies I worked for decided to go with Okta Platform, which is the gold standard. Most documentation out there provided by other platforms that integrate with Okta Platform usually has an Okta Platform sample; they document how to integrate with Okta Platform, and they may not do the same for integrating with other platforms. Their documentation is pretty good, and there are some communities built around Okta Platform as well. I participate on the Mac Admins Slack, which is a large IT community with a few channels dedicated to Okta Platform products or services, and there is also an Okta Admins community with Okta Platform employees engaged. I appreciate that they build a community around their product, and I can reach out to them on these other channels instead of having to open a ticket with them.

They have good documentation and there are subject matter experts engaging in these communities, including some Okta Platform employees. Their user interface is pretty good.

Okta Platform certainly speeds up the onboarding and offboarding process for employees. When we onboard them, in most cases we only need to grant them their Okta Platform credentials and they will be all set with their accesses. It's also easy to add new apps; if someone joins the company and they have all the apps they need, but then someone requests access to some other app, it's easy to grant them access to that app without jumping through hoops. Similarly, when it comes to offboarding, we know that deactivating their Okta Platform account is removing the keys to everything they have access to. In my current company, we don't have the lifecycle management product by Okta Platform, which automates the provisioning of users across platforms, but I used that at my previous job and it was a time-saving feature.

I have my own wish list of things that I would like Okta Platform to have. They released some features related to device access, such as Okta Device Access, which is an add-on that requires payment. I would expect Okta Platform to include more features over time in their less expensive subscriptions. I wish Okta Workflows could be included in a better way; we currently only have five workflows available, which doesn't provide much value. More workflows available in a paid subscription would be beneficial.

With AI permeating every service, I would like to have some kind of AI chatbot available on Okta Platform interface to ask questions about Okta Platform and how to integrate things. I relied on Google's AI chatbot to ask similar questions, but I would feel more confident asking them to an Okta Platform AI bot. I think someone mentioned there may be something coming from Okta Platform related to this.

I have been working with Okta Platform for about five or six years.

I haven't had any crashes, downtimes, or performance issues with Okta Platform; it has been very reliable for us.

I would think Okta Platform is easy to scale; we are a small company, but we're growing and adding new employees regularly. I haven't faced any significant scalability issues yet, but I believe Okta Platform can be scaled easily.

I have opened some tickets with Okta Platform customer support, but I often prefer to dive into documentation or reach out to relevant communities instead to find answers quickly. We do have access to their support, but I find it sometimes slower than engaging with knowledgeable people in those communities.

On a scale of 1 to 10, I would rate Okta Platform's technical support around an eight or nine. I've only opened a few tickets, and I have had a good experience receiving answers.

I didn't use any different product previously and didn't evaluate other solutions available in the market. We relied on Google for some single sign-on features but I haven't implemented Google's SAML solution in a broad way.

In my previous job, I was kind of in charge of deploying Okta Platform to the entire company. I took a three-day training from Okta Platform, which helped transition me from being a non-believer to a believer in Okta Platform. Deployment was quite a challenge, but taking that training made a difference. In my current job, they already had a contract in place with Okta Platform, but the deployment was easier because we were primarily using the single sign-on feature and adaptive MFA; it was a simpler deployment overall.

We went directly with Okta Platform and didn't go through partners or any marketplace for purchasing it.

I would think there are measurable improvements on our security and operational costs just by relying on Okta Platform. We're a small startup, and we aren't measuring these things closely, but I would think there are improvements due to our use of Okta Platform.

I don't have specific data points to share regarding ROI, as I am not much into hard data. Maybe I could get some numbers from colleagues or my manager eventually, but right now I don't have an answer for this.

Regarding my experience with the pricing aspect, I am not much into the pricing side of things, but I think Okta Platform is not an expensive company for the service they provide. We don't have Okta Workflows or Lifecycle Management due to cost, but the value we get from Okta Platform makes it a non-expensive expense for us.

I didn't use any different product previously and didn't evaluate other solutions available in the market.

I have my own wish list of things that I would like Okta Platform to have.

They have good documentation and there are subject matter experts engaging in these communities, including some Okta Platform employees. Their user interface is pretty good.

I haven't had any crashes, downtimes, or performance issues with Okta Platform; it has been very reliable for us.

Both in my current job and the previous one, we were in Fintech companies in the financial space. One of the reasons to go with Okta Platform is because they are a well-reputed company, providing some attestations such as SOC 2.

On a scale of 1 to 10, I would rate Okta Platform's technical support around an eight or nine. I've only opened a few tickets, and I have had a good experience receiving answers.

Regarding my experience with the pricing aspect, I am not much into the pricing side of things, but I think Okta Platform is not an expensive company for the service they provide. We don't have Okta Workflows or Lifecycle Management due to cost, but the value we get from Okta Platform makes it a non-expensive expense for us.

I would rate this review a 10 out of 10.