Keep home page
Search...
⌘K
Platform
keephq/keep
keephq/keep
Search...
Navigation
Authentication
No Authentication
Overview
Introduction
Playground
Use Cases
Key Concepts
Support
FAQ
AIOps
AI
Non-AI Correlation
Deduplication
Extraction
Mapping
Maintenance Windows
Service Topology
Workflows
Alerts
Overview
Alert Table
Action Menu
Alert Sidebar
Customized Presets
Sound Notifications
Incidents
Overview
Facets
Workflow Automation
Overview
Syntax
Examples
Alert Evaluation Engine
Overview
Examples
Providers
Overview
Linked Providers
Provider methods
Supported Providers
Adding a New Provider
Deployment
Configuration
Monitoring
Authentication
Overview
No Authentication
DB Authentication
Auth0 Authentication
Azure AD Authentication
Keycloak Authentication
OAuth2Proxy Authentication
Provision
Secret Store
Deploy On
Local LLM
Specifications
Development
Getting started
Keep with an external URL
Keep CLI
Overview
Installation
Sync Keep Workflows With Github Action
Commands
On this page
Setup Instructions
Implications
Authentication
No Authentication
Using this configuration in production is not secure and strongly discouraged.
Deploying Keep without authentication is the quickest way to get up and running, ideal for local development or internal tools where security is not a concern.
Setup Instructions
Either if you use docker-compose, kubernetes, openshift or any other deployment method, add the following environment variable:
Copy
# Frontend
AUTH_TYPE=NOAUTH
# Backend
AUTH_TYPE=NOAUTH
Implications
With
AUTH_TYPE=NOAUTH
:
Keep won’t show any login page and will let you consume APIs without authentication.
Keep will use a JWT with “keep” as the tenant id, but will not validate it.
Any API key provided in the
x-api-key
header will be accepted without validation.
This configuration essentially bypasses all authentication checks, making it unsuitable for production environments where security is a concern.
Overview
DB Authentication
Assistant
Responses are generated using AI and may contain mistakes.