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

# Editions and deployment models

> Compare OpenSource Edition, Enterprise Edition, and the planned MoleSignal Cloud operating model.

MoleSignal has one observability engine and three ways to adopt it. The editions differ primarily in
commercial entitlements, support, and who operates the platform—not in the telemetry model or query
semantics.

| Offering               | Availability                         | Who operates it                    | Commercial model                                       |
| ---------------------- | ------------------------------------ | ---------------------------------- | ------------------------------------------------------ |
| **OpenSource Edition** | Available                            | Your team                          | Apache 2.0, self-hosted                                |
| **Enterprise Edition** | Available by agreement               | Your team, with MoleSignal support | Self-hosted with a signed license and support contract |
| **MoleSignal Cloud**   | **Waitlist; not publicly available** | MoleSignal                         | Planned managed service with usage-based plans         |

<Warning>
  MoleSignal Cloud does not have a public launch date. Cloud descriptions in this documentation are
  planning guidance, not a current service commitment or SLA.
</Warning>

## Capability matrix

`Included` means the capability is part of the current open-source runtime. Enterprise capabilities
are enabled only when the active signed license contains the named entitlement. A license never
bypasses IAM permissions.

| Capability                                                                      | OpenSource          | Enterprise                       | Cloud                      |
| ------------------------------------------------------------------------------- | ------------------- | -------------------------------- | -------------------------- |
| Logs, metrics, traces, profiles, APM, and cross-signal query                    | Included            | Included                         | Planned on the same engine |
| Dashboards, streams, pipelines, functions, alerts, synthetics, and status pages | Included            | Included                         | Planned on the same engine |
| Mole Agent and Inbound MCP                                                      | —                   | `agent` entitlement              | Planned, plan-controlled   |
| SSO providers                                                                   | —                   | `sso` entitlement                | Planned, plan-controlled   |
| Federated multi-cluster search                                                  | Single cluster      | `federated_search` entitlement   | Planned, managed topology  |
| Managed organization domains                                                    | —                   | `domain_management` entitlement  | Planned, plan-controlled   |
| Enhanced profiling comparison workflows                                         | Core profiling only | `profiling_enhanced` entitlement | Planned, plan-controlled   |
| Infrastructure operation and upgrades                                           | Your team           | Your team, with vendor support   | MoleSignal (planned)       |
| Product billing and account support surfaces                                    | —                   | —                                | Cloud only (planned)       |

Entitlements can evolve independently of the documentation taxonomy. The server response and active
license remain authoritative for a particular deployment.

## How availability appears in these docs

* The main guide groups mirror the product menu: **Observe**, **Reliability**, **AI Ops**, **Data**,
  **Collaboration**, and **Admin**.
* A guide that is entirely license-gated carries an Enterprise label and an availability warning near
  the top of the page.
* When only one workflow is gated, the requirement appears beside that workflow instead of marking the
  entire guide as Enterprise-only.
* Cloud-only or future behavior is always labeled **planned** or **waitlist**.

## Choose a path

* [OpenSource Edition](/en-US/editions/open-source) — self-host the Apache 2.0 runtime.
* [Enterprise Edition](/en-US/editions/enterprise) — self-host with signed entitlements and vendor support.
* [MoleSignal Cloud](/en-US/editions/cloud) — understand the planned managed operating model.
* [Enterprise license management](/en-US/licensing) — upload, verify, and activate signed licenses.