# dlogify: AI log triage for developers

> dlogify groups your errors, classifies them with AI and delivers a full-context ticket by email or webhook.

New: [Replay: see how the system got to the error.](https://dlogify.com/whats-new/replay.md)

**Log triage, on autopilot.** Thousands of logs a day. dlogify reads them all, finds the errors that matter, and sends you a ticket with the context to fix them.

[Start free](https://dlogify.com/sign-up)

## How it works

### 1. Ingest: REST and OpenTelemetry

One API key. Send JSON batches or OTLP over HTTP and gRPC, from the Node, Python or Go SDK or an OpenTelemetry Collector.

### 2. Classify: Groups, severity, cause

Errors are redacted before anything is written to the database, fingerprinted into groups, and each group is classified by severity and category.

### 3. Deliver: Email, Slack, Discord and signed webhooks

Critical, high and medium tickets arrive within seconds. Everything else waits for your digest.

## The ticket

Context first. The stack trace is still there when you need it.

**Payment provider timeouts in billing** (high, dependency)

- Ticket: `tkt_01k8f3w2q9e6t1r5y7v3h0n2pa`
- Service: billing, 214 events
- Top frame: `createCharge@src/billing/stripe.ts:88`
- Summary: charges.create calls to the payment provider time out after 30 s and the retry queue grows.
- Probable cause: Upstream latency at the payment provider; the client timeout equals the request timeout, so retries pile up.
- Suggested fix: Lower the client timeout to 10 s, add a circuit breaker around charges.create, and alert on queue depth.

_Example ticket, as delivered by email and webhook._

## Integrations

Two lines in your deploy, no code changes.

### Node.js

```bash
npm i @dlogify/node
LOGIFY_API_KEY=lgf_live_… node --import @dlogify/node/register server.js
```

### Python

```bash
pip install dlogify
LOGIFY_API_KEY=lgf_live_… logify run -- python app.py
```

### Go

```bash
go install dlogify.com/sdk/go/cmd/logify@latest
LOGIFY_API_KEY=lgf_live_… logify run -- ./server
```

### OpenTelemetry Collector

```yaml
exporters:
  otlphttp:
    endpoint: https://api.dlogify.com
```

Setup guides in the [documentation](https://docs.dlogify.com/llms.txt).

## Security

Your logs carry your users' data. We treat them that way.

- **PII redacted before storage.** Emails, tokens, card numbers and similar values are masked before a sample is written to the database.
- **Tenant isolation in the database.** Every tenant-owned row is protected by PostgreSQL row-level security, and each service has its own database role.
- **Signed webhooks.** Each webhook delivery carries an HMAC signature with a per-channel secret, stored encrypted.

[How dlogify handles data](https://dlogify.com/security.md)

## Pricing

Start free. Upgrade when you outgrow it.

- **Free** (free): One project, daily digest, email delivery.
- **Pro** ($14 / month for 3 months (30% off), then $20 / month, plus tax (Offer ends December 31, 2026)): Teams shipping several services, with webhooks and hourly digests.
- **Team** ($42 / month for 3 months (30% off), then $60 / month, plus tax (Offer ends December 31, 2026)): Higher limits and longer retention for larger organizations.

[Compare every limit](https://dlogify.com/pricing.md)

Source: https://dlogify.com