Cognee Cloud

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, LanceDB, Kuzu), and pipeline execution. No local installation required.
• Pipeline execution — Run remember, recall, forget, and the lower-level add, cognify, 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 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.
• Multi-tenancy — Dataset-level isolation with role-based access control. See Permissions.

​

Hosted cloud vs. free local UI

• Hosted Cognee Cloud — Managed infrastructure, storage, and compute. Sign up at platform.cognee.ai.
• Local UI (free) — 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 screen in place of the Overview: 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: 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 screen replaces the content of the Overview and of every page that reads from the workspace: Datasets, Search, Skills, Mindmap, Sessions, Analytics, Activity, and the Graph Model editor. Pages that do not touch the workspace stay usable while it starts — 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 and 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.

​

Relationship to Cognee OSS

Cognee Cloud uses the same concepts, operations, and API patterns as open-source Cognee. 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().

​

Get started