Skip to main content
For every authentication-related question or issue, please join our Slack.
Keep supports various authentication providers and architectures to accommodate different deployment strategies and security needs, from development environments to production setups.

​
Authentication Providers

  • No Authentication - Quick setup for testing or internal use cases.
  • DB - Simple username/password authentication. Works well for small teams or for dev/stage environments. Users and hashed password are stored on DB.
  • Auth0 - Utilize Auth0 for scalable, auth0-based authentication.
  • Keycloak - Utilize Keycloak for enterprise authentication methods such as SSO/SAML/OIDC, advanced RBAC with custom roles, resource-level permissions, and integration with user directories (LDAP).
  • AzureAD - Utilize Azure AD for SSO/SAML/OIDC nterprise authentication.
  • Okta - Utilize Okta for SSO/OIDC authentication.
  • OneLogin - Utilize OneLogin for SSO/OIDC authentication.
Choosing the right authentication strategy depends on your specific use case, security requirements, and deployment environment. You can read more about each authentication provider.

​
Authentication Features Comparison

​
How To Configure

Some authentication providers require additional environment variables. These will be covered in detail on the specific authentication provider pages.
The authentication scheme on Keep is controlled with environment variables both on the backend (Keep API) and the frontend (Keep UI). For more details on each authentication strategy, including setup instructions and implications, refer to the respective sections.