> ## 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.

# Introduction

> Operate logs, metrics, traces, APM, profiles, alerts, automation, and access control in one self-hosted observability platform.

**MoleSignal** is a self-hosted, OpenTelemetry-native observability platform. MoleSignal combines four
telemetry signals with trace-derived APM, a shared data plane, cross-signal investigation, alert
response, reporting, Mole Agent, and organization-aware administration.

Logs, metrics, and traces are stored as Parquet in object storage and queried through
DataFusion and Arrow. Profile metadata uses the same organization and stream model while canonical
pprof blobs remain in object storage. PostgreSQL stores schemas, file metadata, users, policies,
dashboards, alerts, reports, and other control-plane resources.

<Note>
  MoleSignal is under active development. Review the changelog before upgrading and
  [open an issue](https://github.com/molesignal/molesignal/issues) when behavior differs from this
  documentation.
</Note>

## From telemetry intake to incident response

From OpenTelemetry intake through cross-signal investigation, real-time response, and controlled
automation, every workflow shares the same organization, time, and storage context.

<CardGroup cols={2}>
  <Card title="Unified telemetry data plane" icon="database" href="/en-US/intake">
    Send logs, metrics, traces, and profiles through OTLP and compatible protocols, then store them
    under one organization and stream model.
  </Card>

  <Card title="Cross-signal investigation" icon="magnifying-glass" href="/en-US/correlation">
    Drill from metrics into traces, logs, hosts, and RUM sessions within one time window without
    copying correlation identifiers by hand.
  </Card>

  <Card title="APM and continuous profiling" icon="gauge-high" href="/en-US/apm">
    Use trace-derived performance metrics and service topology to find slow services, failing
    transactions, expensive dependencies, and code hotspots.
  </Card>

  <Card title="Programmable telemetry pipelines" icon="code-branch" href="/en-US/pipelines">
    Route, normalize, redact, enrich, and backfill data with pipelines and reusable functions.
  </Card>

  <Card title="Real-time detection and incident response" icon="bell" href="/en-US/alerting">
    Run scheduled, real-time, and anomaly rules connected to incidents, schedules, escalations,
    silences, and subscriptions.
  </Card>

  <Card title="Dashboards, reports, and sharing" icon="chart-line" href="/en-US/dashboards">
    Turn investigation results into dashboards, saved views, scheduled reports, exports, and
    restricted shares.
  </Card>

  <Card title="Evidence-backed AI investigation" icon="robot" href="/en-US/agent">
    With the Enterprise `agent` entitlement, let Mole Agent collect evidence while risk levels and
    approvals protect write operations.
  </Card>

  <Card title="Multi-tenant governance and access control" icon="shield" href="/en-US/administration">
    Govern access through organization isolation, roles, service accounts, SSO, auditing, licensing,
    and the protected platform scope.
  </Card>
</CardGroup>

## Start here

1. Follow the [Quickstart](/en-US/quickstart) to run a local instance and send telemetry.
2. Read [Core concepts](/en-US/concepts) for signals, streams, organizations, permissions, and
   storage.
3. Use the [User guide](/en-US/user-guide) to learn navigation and the investigation workflow.
4. Choose a production topology in [Deployment](/en-US/deployment) and
   [Distributed deployment](/en-US/distributed-deployment).

## Editions

Choose **OpenSource Edition** for self-hosting the Apache 2.0 runtime, **Enterprise Edition** for
self-hosting with signed entitlements and vendor support, or join the waitlist for the planned
**MoleSignal Cloud** managed service. Compare them in
[Editions and deployment models](/en-US/editions).