> ## Documentation Index
> Fetch the complete documentation index at: https://docs.recallium.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Recallium Cloud and Community

> Compare the managed and self-hosted options and understand what the client sends

Recallium is available as a managed Cloud service and as a local Community edition. Both editions expose the core project and memory workflow through MCP.

## Edition comparison

| Capability                               | Recallium Cloud | Recallium Community |
| ---------------------------------------- | --------------- | ------------------- |
| Projects, workstreams, and saved context | Yes             | Yes                 |
| Semantic and file-aware memory search    | Yes             | Yes                 |
| Rules, tasks, and working state          | Yes             | Yes                 |
| Managed service and browser sign-in      | Yes             | No                  |
| Team recaps and team membership tools    | Yes             | No                  |
| Cross-project team insights              | Yes             | No                  |
| Local self-hosted server                 | No              | Yes                 |

## Memory content

Memory content is sent to the Recallium server for the edition you connected. This happens when your agent explicitly saves a memory on your behalf.

Choose the project and server that match the sensitivity of the work you want Recallium to retain.

## Client telemetry

The Cloud client can send edit metadata that helps Recallium connect memories to the work performed in a session. The sensor sends metadata such as:

* File paths
* Hashes
* Edit and activity counts
* Git branch and commit provenance

The sensor does not send source file contents. It supports file-link suggestions and provenance for memories created through MCP.

<Info>
  Memory text is separate from sensor telemetry. Your agent sends memory text when it uses a Recallium memory tool.
</Info>

## Community behavior

Community connects to a server on your own machine or network. It does not use Recallium Cloud sign-in. The Community client does not provide the Cloud sensor enrollment commands, team tools, or generated insights.

Community's local server and storage remain under your operational control.

## Inspect your connection

Use the CLI to see which edition and server your installed client is using:

```bash theme={null}
recallium status
```

Use the diagnostic report to inspect each connected agent:

```bash theme={null}
recallium doctor
```