Ory is deployed in our environment as self-hosted for the time being, but we fully expect to migrate to Ory Network in the future. We use Keto, Kratos, and Oathkeeper (authorization, authentication, and gateway respectively).

Ory's services are extremely easy to stand-up, maintain, and integrate with existing applications. Being that the flows are stateful and exist within the API, integrating with any UI framework is a breeze. Review collected by and hosted on G2.com.

The documentation for the open-source offering is not so great. Many of the configuration fields are not well described or documented. Unfortunately, there are also some common scenarios that are also lacking a clear configuration and documentation (setting up additional fields, gating signups behind invitations etc (Kratos), using external authorization servers with Oathkeeper, etc. Review collected by and hosted on G2.com.

We use Ory for user authentication on our internal platform, and the integration was very seamless. There are many constructs available for identity and permissions management, which I really liked, and they made our lives easier overall. The plans and pricing also feel decent and reasonable. Service availability has been solid as well on Ory cloud / network Review collected by and hosted on G2.com.

Overall, my experience has been positive. The main area I’d like them to improve is Oathkeeper, because it isn’t very clear or straightforward to use when trying to set up capabilities like infra-level authentication and other use cases where Oathkeeper is recommended. In my view, the configuration and overall approach still need some refinement to make it easier to understand and implement. Review collected by and hosted on G2.com.

I use Ory Keto and like the depth and accuracy of the features, especially the composability of each of the products. For Keto specifically, it's the TypeScript namespacing. Writing my domain model relationships in TypeScript keeps everything accurate. Review collected by and hosted on G2.com.

I would like better distributed consistency token support, and more detailed support for 2 phase commits. I use Ory in conjunction with a dedicated Postgres DB and there's no built-in support for ensuring consistency between them. The initial setup could also be improved; a 7/10 rating with a need for dedicated Helm templates and easier config injection. Review collected by and hosted on G2.com.

The API first approach for almost all of their products. That offers adaptability in almost any system and great amount of customization that you do not easily find in other products Review collected by and hosted on G2.com.

The documentation is confusing and not that greatly organized. The release cadence of the open source product is not on par to the paid plan; finally - Hydra lacks token exchange support Review collected by and hosted on G2.com.

The entire platform is designed according to cloud-native principles. Performance is outstanding, and we can be confident that Ory will scale seamlessly as our user base grows. Consistent compliance with standards such as OAuth 2.0 and OpenID Connect Certified™ also gives us investment security. That's why I chose this platform for my start-up. Review collected by and hosted on G2.com.

Overall, our experience with Ory Network has been extremely positive. If we had to name one area for future improvement, it would be the management of identity schemes.

Currently, identity schemas are immutable once created and cannot be deleted. We understand that this approach ensures data consistency across different versions. However, in everyday development, especially in the initial setup and testing phase, this means that accidentally created or outdated schemas cannot be removed from the list.

This is not a functional problem that affects security or performance, but rather a minor operational inconvenience. A "soft delete" or archiving function for schemas that are no longer in use would be a welcome addition here to improve the clarity of the configuration. Review collected by and hosted on G2.com.

We have successfully migrated most of our applications' authentication from another SaaS provider to Ory Network (with the migration still ongoing). We are using Ory Hydra and Ory Kratos for our machine-to-machine services and web frontend applications. One of the biggest selling points for us was the ability to use a slightly modified Ory Network production configuration to run our own Ory stack on Docker. This feature enables our developers to run the entire stack locally and facilitates CI/CD pipelines for testing configurations. Additionally, their Slack community is quite active, with Ory employees providing assistance on multiple occasions. Impressively, our proof of concept for migrating to Ory Hydra/Kratos was completed in less than a day. Review collected by and hosted on G2.com.

We provision the entire platform through a CI/CD pipeline, but the Ory Workspace/Project API key system currently lacks proper access control. This is surprising, given that Ory is an auth platform that provides solutions like Ory Keto. Our pipeline relies on a collection of fairly large Bash scripts to address some idempotency issues with their CLI. The difference between the Ory CLI and the Kratos/Hydra CLI also caused some issues when developing locally. We are aware that Ory is working on a Terraform provider, and we are hopeful that it will resolve these challenges. Additionally, we have encountered instances where the documentation was either missing or too vague, requiring us to seek clarification from their Slack channel. Review collected by and hosted on G2.com.

I love having an open source oidc library at my disposal with the comfort of being able to fallback on a hosted/commercial option. I've used Ory for a production deployment and the backbone of a identity broker system, and having the extensible core of Ory Hydra has made this easy and allowed me to put the "hard parts" of OAuth and Oidc to the experts while building out for my custom use case. I have really only touched on Hydra, so cannot speak to the other parts of the ecosystem, but hydra is well designed and documented and a great choice for self-hosters. Review collected by and hosted on G2.com.

I've found the token cleanup process, particularly for postgres backends a bit lacking. For long running deployments, I found the janitor functionality actually made performance worse. Some more support for self hosters would be great, but understood that you are a bit on your own in that circumstance. It was some trial and error and production pain here, which I am sure the managed versions eliminate. Review collected by and hosted on G2.com.

I have no hesitation in recommending Ory to my customers. I have used a variety of different identity providers (including Firebase, AzureAD, Auth0 and Keycloak) over the years for different projects, and whilst they can be used to get the job done, I've run into various limitations and annoyances with all of them. Firebase in particular has been rather painful, and so when I started my most recent project I was keen to give the Ory suite a go for my customer. It already had a good reputation in the open-source community, and the team have contributed back to the Go ecosystem in the form of their fosite library.

Since adopting Ory (and specifically, Kratos for identity and Hydra for OIDC), I've been very happy with the results. Much of the difficult plumbing of login and self-service account management flows is abstracted away from you - which means fewer security pitfalls to worry about trying to avoid, because security best practice has been baked in to the design. Despite that, I've been able to customise the user interface with ease and implement my customer's branding and design requirements. Review collected by and hosted on G2.com.

Like any product, I've run into areas of documentation that could have been slightly clearer. There is an Ory Slack workspace for asking questions, and I've felt like any feedback on documentation I've provided has been heard.

Sometimes pull requests can take a while to be reviewed, but this is only likely to affect prospective customers who want to contribute back fixes to the project. Balancing running a company with managing a number of open-source projects, and reviewing contributions is always tricky. Review collected by and hosted on G2.com.

open-source approach, support for OAuth/OIDC, and the option to self-host. Review collected by and hosted on G2.com.

Documentation for the beginners can be better Review collected by and hosted on G2.com.

The Ory team has been a supportive and thoughtful partner for us, including one-on-one technical support and adding requested features/changes. We chose Ory and Ory Network because they could support the amount of customization and advanced features we required. Having experienced some alternatives, we have no regrets choosing Ory! Review collected by and hosted on G2.com.

I would not suggest Ory for basic use cases because there are simpler options out there to get started Review collected by and hosted on G2.com.