Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

if you only want to provide access to your own frontend for your own API, you only need kratos and not hydra

<https://www.ory.sh/oauth2-openid-connect-do-you-need-use-cases-examples/>

ahh, so Hydra is more for the machine based auth to my api.
which i don't need, since this api isn't public it's only for my own project/product.

so I basically only need Kratos &amp; Keto.

hydra is to allow users to delegate access to a third-party to access your API on their behalf, so if only your own applications will access your API then you likely don't need that delegation

nip: Hydra implements OIDC/OAuth2 flows, which as <@U02AY3MNVKP> has written you most probably only want to use if you open your APIs to third parties want your users to delegate access on their behalf. Kratos implements proprietary flows for first-party access, which is what you typically want to have in 99% of the cases.