Authress vs Keycloak

Learn how Authress and Keycloak differ in their key features like authentication, enterprise auth, security, user management and compliance, so you can decide which of these authentication providers is best for you.

Favicon of Authress

Authress

Complete authentication and authorization API solution
Details:
Authress screenshot
vs
Favicon of Keycloak

Keycloak

Secure apps with open source identity management
Details:
View Repository
Keycloak screenshot

Feature Comparison

Both tools offer comparable feature coverage, with Keycloak supporting 30 features and Authress supporting 27. Consider your specific needs regarding authentication, enterprise auth, security, user management and extensibility when making your decision. Keycloak fully covers user management, and both tools fully cover authentication and machine to machine (m2m) authentication and more.

Authress
Keycloak
Authress
Keycloak
Authress

Allows administrators to customise JWT and session lifetimes. Default tokens expire after 24 hours and sessions after 30 days but these limits can be increased

Keycloak

Session idle and max lifespans and offline sessions can be adjusted to keep sessions alive for longer periods

Authress
Keycloak

Admins can view and revoke user and client sessions, sign out all sessions, and configure session lifespans in the admin console

Authress
Keycloak

The UI is internationalized. Administrators can enable multiple languages and users can choose their language at login or in the account/admin consoles

Compliance Comparison

Both tools have similar compliance levels, with Authress supporting 1 certifications and regulatory frameworks and Keycloak supporting 0. Since Keycloak is open source and does not include compliance certifications, you’ll need to manage compliance yourself.

gdpr iconGDPRCompliant
Authress
Keycloak
,

Command Menu