# Errora documentation

> https://docs.errora.org/en/

Errora (ارورا) is an **alternative to Sentry**: error monitoring, tracing,
structured logs, session replay, cron and uptime monitoring, user feedback, profiling,
application metrics, dashboards — plus an **MCP server** and **AI auto-fix** that opens
merge requests for you.

Errora is **Sentry-wire-compatible**. You instrument your app with the **official Sentry
SDK** for your platform and point its DSN at Errora. There is no Errora-specific client
library to install, and no vendor lock-in: the same code sends to Sentry or Errora
depending on one environment variable.

## Start here

<div className="product-grid">
  <a className="product-card" href="/en/getting-started/quickstart">
    <h3>Quickstart →</h3>
    <p>Create an organization and project, grab your DSN, and see your first error in five minutes.</p>
  </a>
  <a className="product-card" href="/en/getting-started/concepts">
    <h3>Core concepts →</h3>
    <p>Organizations, projects, DSN keys, events, issues, traces, environments and releases.</p>
  </a>
  <a className="product-card" href="/en/platforms/overview">
    <h3>SDK setup →</h3>
    <p>JavaScript, Node.js, Python, PHP/Laravel, Go and every other Sentry platform.</p>
  </a>
  <a className="product-card" href="/en/getting-started/product-tour">
    <h3>Product tour →</h3>
    <p>The in-app guided tour of the dashboard — and how to replay it whenever you want.</p>
  </a>
</div>

## Products

Every feature below has its own setup guide — what to enable in the SDK, what to configure
in the UI, and how to verify data is arriving.

| Product | What it gives you |
| --- | --- |
| [Error monitoring](/en/products/issues) | Grouped exceptions, stack traces, trends, assignment, workflow |
| [Performance & tracing](/en/products/performance) | Transactions, spans, waterfalls, throughput and latency |
| [Structured logs](/en/products/logs) | Severity levels, typed attributes, trace correlation, full-text search |
| [Session replay](/en/products/session-replay) | rrweb recordings of the sessions that produced an error |
| [User feedback](/en/products/user-feedback) | The widget, the crash-report modal and the server-side report API |
| [Cron monitoring](/en/products/crons) | Check-ins against a crontab/interval schedule, missed & timed-out jobs |
| [Uptime monitoring](/en/products/uptime) | Scheduled HTTP checks with assertions and downtime issues |
| [Profiling](/en/products/profiling) | Sampled stack profiles, flamegraphs and slowest-function rankings |
| [Metrics](/en/products/metrics) | Counters, distributions, gauges and sets over `trace_metric` or statsd |
| [Dashboards](/en/products/dashboards) | Custom charts, tables and big numbers across every dataset |
| [AI monitoring (Insights)](/en/products/insights) | `gen_ai.*` / `mcp.*` spans → agent runs, token usage, tool calls |
| [Security policy reports](/en/products/security-reports) | CSP / Expect-CT / HPKP `report-uri` endpoint |
| [Source maps & releases](/en/products/source-maps) | Upload artifacts, symbolicate minified JavaScript frames |
| [AI auto-fix](/en/products/ai-autofix) | Draft a patch from a stack trace and open a merge request |
| [Alerts & notifications](/en/products/alerts) | Webhook, Mattermost, Telegram, Bale, Email, SMS |
| [Integrations](/en/products/integrations) | GitLab/GitHub repositories and external issue tracking |
| [MCP server](/en/products/mcp) | Let Claude, Cursor and friends query and triage your issues |

## How Errora fits together

```text
Your app ──(official Sentry SDK, your DSN)──▶ Errora
                                               │
             ┌─────────────────┬───────────────┼───────────────┬──────────────────┐
             ▼                 ▼               ▼               ▼                  ▼
      Issues (grouped   Performance,     Logs, metrics,   Cron & uptime    Alerts → Telegram,
      exceptions)       profiles,        replays,         monitors         Bale, email, SMS,
                        AI monitoring    user feedback                     Mattermost, webhook
```

Your app sends; Errora accepts the payload immediately and does the grouping and storage on
its own time, so instrumentation never adds latency to your requests.

## Getting help

- **API reference** — [REST API](/en/api/rest), [ingestion endpoints](/en/api/ingest); the live
  OpenAPI schema is at `/api/schema/` and Swagger UI at `/api/docs/` on your Errora backend.
- **Account & organization** — [organizations and roles](/en/account/organizations),
  [projects and DSN keys](/en/account/projects-and-keys), [access tokens](/en/account/tokens).
- **Billing** — [wallet and pay-as-you-go pricing](/en/billing/wallet).