dlogify docs

Plans and usage

What each plan includes and how to read your usage.

This page lists what each plan includes and what happens when a limit is reached.

Plans

Pro and Team are billed monthly in USD through Stripe; prices are on dlogify.com/pricing. See Billing to subscribe or change plan.

FreeProTeam
Events per minute1,00010,00050,000
Events per month5 million100 million500 million
Projects11050
API keys per project31025
Members1UnlimitedUnlimited
Channels per project21025
Channel typesEmailEmail, webhookEmail, webhook
Shortest digest interval24 hours1 hour1 hour
Retention7 days30 days90 days
Replay and group history7 days30 days90 days
INFO summary window60 minutes15 minutes5 minutes
AI-written tickets and summaries per day205002,500
Live tail sessions at once1520
Live tail lines per second50200500
Live tail session length15 minutes60 minutes60 minutes

Going over a count limit (projects, keys, members, channels, live tail sessions) returns plan-limit-reached; going over the event rate or the monthly quota returns rate-limited. A user can create one organization on the free plan (free-org-limit).

Billing

Only the organization's owner manages billing, from Billing in the organization. Admins and members see the plan and its state.

  • Subscribe. Pick Pro or Team and pay with a card. Sales tax is added where it applies. The plan changes as soon as Stripe confirms the payment, usually within seconds.
  • Upgrade (Pro to Team). Takes effect at once. You are charged the prorated difference for the rest of the period; the amount is shown before you confirm.
  • Downgrade (Team to Pro). Takes effect at the end of the paid period. Until then the organization keeps Team. Keep Team cancels the scheduled change.
  • Cancel. The plan stays until the end of the paid period, then the organization moves to Free. You can Resume until then.
  • Update card and Invoices. Invoices link to Stripe's invoice page and PDF.

Promotion codes

When you subscribe for the first time, choose Add promotion code on the checkout page and enter the code. The summary shows the discount and the new total before you pay. A link with a code, such as dlogify.com/pricing?promo=CODE, applies it automatically when you reach the checkout.

During a public offer, the pricing page shows the discounted price and the percentage off, and the checkout applies the offer automatically: there is no code to enter, and no other code can be added while the offer runs. Like any code, it applies only to an organization's first subscription; an organization that has paid before sees the offer on the pricing page but subscribes at the plan's price.

  • A code applies only to an organization's first subscription, not to plan changes or to a subscription that is already active, and not to an organization that has paid before.
  • The discount lasts as long as the code says: the first invoice, a number of months, or for as long as the subscription lasts. Billing shows the active discount and when it ends; after that you pay the plan's price.
  • A code may cover only some plans. If you upgrade to a plan the code does not cover, the new plan is charged at its full price.

When a payment fails

The plan stays while Stripe retries the payment over about two weeks, and Stripe emails the billing address. The dashboard shows a banner with Update card. If every retry fails, the subscription ends and the organization moves to Free.

Moving to a smaller plan

Nothing is deleted. Projects, keys, members and channels above the new plan's limits keep working, but you cannot add more until you are under the limit (plan-limit-reached). Channel types the plan does not include stop delivering. Ingestion limits, retention, the AI budget and digest frequency follow the new plan at once.

Usage

Usage in the organization shows the plan, the events received this month (UTC) against the monthly quota, the projects and members in use against their limits (paid plans have no member limit), the live tail sessions open now against the plan's limit, the API keys allowed per project, and the lines per second and minutes each live tail session gets.

Usage per API key

The By API key table on the Usage page shows, for the current month, how many events each API key sent. Create one key per service and this table tells you which service uses your quota.

Each key's events are counted in three ways:

  • Accepted: events taken for processing. These count against your monthly quota.
  • Rejected (quota): events refused because the organization had used its monthly quota (429 rate-limited).
  • Rejected (rate limit): events refused because the organization sent more events per minute than its plan allows (429 rate-limited).

Requests refused for other reasons, such as an invalid body, a batch that is too large, or dlogify asking you to retry later, are not counted.

Counts are grouped by UTC hour and appear within about 10 seconds. They are kept for 90 days on every plan. The sum of all keys can be a few events lower than the monthly meter above it: the meter is what your quota uses, and the per-key counts are statistics.

Daily AI budget

Each plan includes a number of AI-written tickets and INFO summaries per day (UTC). low tickets and INFO summaries can use at most 70 % of it, so critical, high and medium tickets always keep a reserve.

When the budget runs out, tickets and summaries are still written and delivered, built from the same facts (severity, service, occurrences, stack trace, surrounding log lines) but without the AI-written title, summary, probable cause and suggested fix. The budget resets at midnight UTC.

Retention

Error samples, tickets, INFO summaries, the log history behind replay and the group history are kept for the plan's retention period and then deleted. Error groups and their totals stay. Moving to a plan with shorter retention deletes what is past it at the next hourly run.

On this page