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

# aciona.me

> On-call management, alert routing and incident response for teams that need to respond fast.

Your alerts already fire. aciona.me makes sure they **reach the right person**, that someone **takes ownership**, and that the whole path is **on the record**.

aciona.me sits between your monitoring tools and the people responsible for them. It receives the alert, figures out which service is affected, finds the responsible team and the person currently on call, opens an incident, notifies whoever needs to act, and escalates automatically if nobody responds.

## Start here

<Columns cols={2}>
  <Card title="Receive your first alert" icon="rocket" horizontal href="/en/getting-started/first-alert">
    From zero to your first acknowledged incident in about 10 minutes.
  </Card>

  <Card title="How aciona.me works" icon="route" horizontal href="/en/introduction/how-it-works">
    The full path from an alert to a resolution.
  </Card>

  <Card title="Connect your tool" icon="plug" horizontal href="/en/alert-sources/overview">
    Grafana, Prometheus, Datadog, CloudWatch, Zabbix, New Relic and generic webhook.
  </Card>

  <Card title="Core concepts" icon="book-open" horizontal href="/en/introduction/concepts">
    Organization, team, service, schedule, alert source and incident.
  </Card>
</Columns>

## The problem it solves

In most teams the critical alert already exists — it just has no owner. It lands in a Slack channel at 3 a.m., nobody gets paged on their phone, nobody knows whether someone is already looking at it, and there is no record of who responded or how long it took.

aciona.me replaces that with an explicit flow:

<Steps>
  <Step title="Alert received">
    Your monitoring tool sends the alert to an aciona.me alert source.
  </Step>

  <Step title="Responder identified">
    aciona.me resolves the affected service, the responsible team and who is on call right now.
  </Step>

  <Step title="Incident created">
    An incident is opened with its own severity, context and history.
  </Step>

  <Step title="Person paged">
    Notifications by email, push, Slack and Microsoft Teams — according to what you configured.
  </Step>

  <Step title="Response tracked">
    Acknowledgement, ownership, escalation and resolution all land on the timeline.
  </Step>
</Steps>

## Explore the documentation

<Columns cols={3}>
  <Card title="On-call" icon="calendar-clock" href="/en/on-call/schedules">
    Schedules, rotations, timezones, overrides and escalation.
  </Card>

  <Card title="Incidents" icon="siren" href="/en/incidents/lifecycle">
    Lifecycle, ACK, assignment and resolution.
  </Card>

  <Card title="Notifications" icon="bell" href="/en/notifications/overview">
    Email, push, Slack and Microsoft Teams.
  </Card>

  <Card title="Teams and services" icon="users" href="/en/teams/overview">
    Who answers for what.
  </Card>

  <Card title="Troubleshooting" icon="life-buoy" href="/en/troubleshooting/overview">
    Alert did not arrive? Start here.
  </Card>

  <Card title="Reference" icon="list" href="/en/reference/generic-webhook-payload">
    Payloads, severities, statuses and limits.
  </Card>
</Columns>