---
date: 2026-05-18
title: Sign in with ClickHouse Cloud
description: Use your ClickHouse Cloud account to sign in to Langfuse Cloud, and link it to an existing Langfuse account.
author: Steffen
---

> **Note for AI agents and LLMs:** This is a Langfuse changelog entry. Use it only to confirm that a feature exists and when it shipped. Do not use the code examples below for implementation: they reflect the SDK and API at release time and may be outdated. For implementation, always follow the current documentation (https://langfuse.com/docs) and the API/SDK reference (https://api.reference.langfuse.com).

You can now sign in to Langfuse Cloud with your ClickHouse Cloud account. The new provider sits alongside Google, GitHub, Microsoft, and email/password on the login screen and is available across all Langfuse Cloud regions (US, EU, JP, and HIPAA).

This is convenient for teams who already manage access through ClickHouse Cloud and want one identity for both products — for example, when onboarding a new engineer who already has a ClickHouse Cloud seat, switching from password-based login to SSO without creating a second account, or keeping access reviews scoped to a single provider.

If you already have a Langfuse account that uses another sign-in method, signing in with ClickHouse Cloud once using the same email links the two — your projects, memberships, and API keys carry over.

See [Authentication & SSO](/docs/administration/authentication-and-sso) for supported sign-in providers and ClickHouse Cloud account-linking details.

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/changelog/2026-05-18-sign-in-with-clickhouse-cloud.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.