> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognee.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Cognee Cloud
> Use the Cognee UI and pipelines hosted in the cloud, or run everything locally for free — no account required
Cognee Cloud gives you the full Cognee platform — a web UI, managed pipelines, and storage — as a hosted service. If you prefer to stay local, you can also **run the UI and all pipelines entirely on your own machine for free**, with no account required, using `cognee.start_ui()`.
## What Cognee Cloud provides
* **Managed infrastructure** — Preconfigured compute, storage ([PostgreSQL](https://postgresql.org/), [LanceDB](https://lancedb.com/), [Kuzu](https://github.com/kuzudb/kuzu)), and pipeline execution. No local installation required.
* **Pipeline execution** — Run [remember](/core-concepts/main-operations/remember), [recall](/core-concepts/main-operations/recall), [forget](/core-concepts/main-operations/forget), and the lower-level [add](/core-concepts/main-operations/legacy-operations/add), [cognify](/core-concepts/main-operations/legacy-operations/cognify), [search](/core-concepts/main-operations/legacy-operations/search) operations from the UI or API.
* **Web UI** — Upload data, explore knowledge graphs, run searches, and manage datasets through the browser.
* **Python SDK** — The [`cognee` package](/cognee-cloud/connections/cloud-sdk) connects to Cognee Cloud via `cognee.serve()`, using the same API as local Cognee.
* **Agent connections** — Connect agent frameworks, local instances, or external data sources. See [Integrations](/cognee-cloud/ui/integrations).
* **Multi-tenancy** — Dataset-level isolation with role-based access control. See [Permissions](/cognee-cloud/functionality/permissions-and-access-control).
## Hosted cloud vs. free local UI
| | Hosted Cloud | Local UI (free) |
| ------------------- | ------------ | --------------- |
| Account required | Yes | No |
| Infrastructure | Managed | Your machine |
| Collaboration | Yes | No |
| Same UI & pipelines | Yes | Yes |
* **[Hosted Cognee Cloud](/cognee-cloud/sign-up)** — Managed infrastructure, storage, and compute. Sign up at [platform.cognee.ai](https://platform.cognee.ai/).
* **[Local UI (free)](/cognee-cloud/local-ui)** — Run the full UI on your own machine with `pip install cognee` and one function call. No account, no cloud.
## Workspace sleep and wake
A hosted workspace that has been quiet for a while scales to zero — it goes to sleep. Nothing is lost while it sleeps, and you do not have to do anything to bring it back: opening it wakes it.
While it starts, the app shows a **Waking {workspace}** screen in place of the [Overview](/cognee-cloud/ui/dashboard): *It went to sleep after a quiet spell. Starting it back up usually takes under a minute, and nothing was lost.* A **RESTORING · m:ss** counter under the message tracks how long it has been going, and keeps counting across a reload or a route change rather than restarting. After about **75 seconds** the message changes to *Still waking up. This one is taking longer than usual, but your data is safe.*
A few details worth knowing:
* **Every way in wakes it.** Switching workspaces in the picker, reloading the page, and opening a direct URL all go through the same wake, and the wake survives a reload rather than treating a still-cold workspace as an ordinary reconnect.
* **A workspace that falls asleep mid-session is caught.** If it goes to sleep while your tab is open, the next request notices, wakes it, and retries once it is serving.
* **The wait is bounded.** A workspace that never comes back lands on an error within minutes rather than spinning forever: **{workspace} didn't wake up** — *It was asleep and we asked it to start, but it hasn't come online. Try again, or sign out and back in.*
* **The workspace badge says which state it is in.** A dashed, hollow badge means not running; its accessible label reads *running*, *asleep*, *waking up*, or *no active subscription*. In the workspace picker each row spells it out under the name — **Asleep · wakes when you open it**, **Waking up…**, **Didn't wake up**, or **No active subscription**.
* **Not every page takes over the screen.** The full **Waking {workspace}** screen replaces the content of the Overview and of every page that reads from the workspace: [Datasets](/cognee-cloud/ui/datasets), [Search](/cognee-cloud/ui/search), [Skills](/cognee-cloud/ui/skills), [Mindmap](/cognee-cloud/ui/knowledge-graph), [Sessions](/cognee-cloud/ui/sessions), [Analytics](/cognee-cloud/ui/analytics), [Activity](/cognee-cloud/ui/activity), and the [Graph Model editor](/cognee-cloud/ui/datasets#graph-model-editor). Pages that do not touch the workspace stay usable while it starts — [Memory Coverage](/cognee-cloud/ui/memory-coverage) is one of them, and shows only the provisioning banner.
A fetch that fails just after a wake names that as the likely cause rather than reporting a flat error: [Activity](/cognee-cloud/ui/activity) and [Analytics](/cognee-cloud/ui/analytics) both read *Couldn't load activity. If the workspace was asleep it may still be starting up; otherwise the activity endpoint is not answering.*
Sleep applies to hosted workspaces only. The [local UI](/cognee-cloud/local-ui) runs for as long as your own process does.
## Relationship to Cognee OSS
Cognee Cloud uses the same concepts, operations, and API patterns as [open-source Cognee](/core-concepts/overview). The difference is deployment:
* **Cognee Cloud** — Hosted persistence, managed compute, collaboration features.
* **Open-source Cognee** — Local development, custom infrastructure, air-gapped environments.
You can connect a local Cognee instance to Cognee Cloud using [`cognee.serve()`](/cognee-cloud/connections/syncing-local-instance).
## Get started
Run the Cognee Cloud UI on your own machine — no account required.
Sign up and generate an API key.
Upload data, build a knowledge graph, and run your first search.
Learn what each page in the Cognee Cloud console does.
Explore the API endpoints available in Cognee Cloud.
Connect agents, databases, or a local instance.
How managed compute, storage services, and datasets fit together.