About BugsRadar
BugsRadar brings the errors of your applications to the chat you already read. It is a small product with one job, made by a small company that has been shipping software since 2014.
What BugsRadar is
An alert, not an archive. Add a package for .NET, Node.js or Python, or send one HTTP request from any script, and every new error lands in Telegram, Discord or Pushover: the first occurrence at once, in full, and repeats as a live count in that same message. Events are never stored: an event stays in memory only until it is delivered to your channels.
There are no event quotas and no per-seat fees. The Free plan is a real plan, not a trial; Pro, at $5 a month, is how the servers get paid for.
What it refuses to be
BugsRadar does not try to be an error tracker. It keeps no history, has no dashboard and no search. If you need to browse last month's errors, you need a tracker; many teams run one next to BugsRadar and use BugsRadar for the moment an error first appears. We say this on every platform page on purpose: the wrong tool wastes your evening, and we would rather you knew before signing up.
Who makes it
BugsRadar is made by Bistriy Sp. z o.o., a software company registered in Kraków, Poland. Since 2014 the company has built desktop, mobile and online products; BugsRadar is one of them. The service has been running since 2016, and its current version, with API v3 and packages for three platforms, launched in September 2026.
The docs, the guides and these pages are written and kept up to date by the BugsRadar team, the same people who run the service and answer at support@bistriy.com.
How we work
- Your bot, your webhook. Alerts go through credentials you own, so you decide who reads the chat, and you can revoke them at any time. Delete a channel, and nothing of yours stays with us except what the account needs to run.
- Honest limits. Every platform page says what BugsRadar doesn't do. Rules, bundles and the live count exist so that a bad day stays readable, not so that the product looks bigger than it is.
- Plans differ by features, not by volume. We don't meter your errors. A crash loop is a bad night for you, not a bill from us.
- Written by the people who run it. Questions that reach support become docs. If a page here doesn't answer yours, write to us and it will.
Company details
Bistriy Sp. z o.o.
ul. Królewska 65A/1, 30-081 Kraków, Poland
KRS: 0000529467
Email: support@bistriy.com
How we handle data: Security and data and the Privacy Policy. The rules of the service: Terms of Use.