One developer, several projects, one chat

Updated 1 October 2026 · BugsRadar team

You run three apps, two sites for clients and a bot, and you are the whole ops team. Nobody is going to open a dashboard on a Tuesday evening. What works is one chat that every project reports into, with the project name on every message, read on the phone like everything else.

One chat for everything

A BugsRadar channel is a chat plus the credentials to post into it, and one channel can serve several projects. Create a private Telegram group, add your bot, and connect that one channel to every project. Each message starts with the project name and the level, so "Shop API · Error" and "Bot · Warning" are told apart at a glance, and the first occurrence of every new error arrives with its stack trace: see What you receive.

Different stacks don't matter. A .NET service, a Node.js API and a Python script report the same way; the message in the chat looks the same whatever sent it. See Platforms.

What Free covers

The Free plan includes 2 projects and 3 channels, with no event quotas: two projects can report as much as they like. A channel for the group and a Pushover channel for your phone fit in the three. When the third project comes along, Pro is $5 a month or $50 a year for unlimited projects and channels, and it is one price, not a price per project: see Pricing.

When the chat gets busy

Repeats are never a flood: the first occurrence arrives in full and the next ones are counted in that message. If several projects still make the chat hard to read, split them: a channel per project is a chat per project, and with rules on Pro you can send only Critical errors to Pushover and leave the rest in the group. One group for everything is the right place to start, though; most solo developers never need more.

On the phone

Telegram already pushes to your phone. For the errors that should wake you, add a Pushover channel: it is a short notification without the stack trace, and repeats arrive as summaries. See Pushover alerts.

The scripts count too

Backups, imports and cron jobs on your VPS report with one HTTP request into the same chat: see the guides. A failed backup looks like any other error, with the host and the job name.

Where to go next

Set up the first project in Get started. If you run things on a VPS, Cron, backups and services on one VPS covers the rest.