Crickets
Sign in

Stop asking your team for updates.

Built for engineering managers and tech leads who need to know what's blocking their team, without living in GitHub. Open it in the morning, see what needs your attention, close the tab.

Get started freeFree for 1 repo | Pro coming soon

Here's what you'd see this morning

Aperçu du dashboard Crickets
01

Install in two minutes

Connect Crickets to your GitHub organisation and pick the repos to monitor. No code changes, no migration, nothing to ask your developers.

02

We watch. You don't have to.

Crickets tracks issues, pull requests, and replies automatically. No more Slack messages asking for status. No more stand-ups just to find out what's slipping.

03

Open it, know where things stand

Every morning, a clear picture: what's blocked, what's overdue, what needs your attention. Ranked by urgency. Nothing buried.

Features

One view. Every signal that matters.

You shouldn't have to dig through GitHub to know if something is slipping. Crickets surfaces everything that needs your attention, ranked by urgency, ready in 30 seconds.

Know where things stand, instantly.

No reading through threads. No asking around. At a glance: is the team on track, or does something need you right now?

Needs attention4
A few things to address2
All clear

Inbox alerts

Unassigned bugs

A bug with no owner is a bug that might never get fixed. Crickets surfaces them before you hear about it from a customer.

PRs without review

Work that is written but not reviewed is work that isn't shipping. Crickets flags it by name so one message from you unblocks it.

Pending replies

When someone opens a support issue, how long before your team replies? If it takes too long, you see it here. Before they lose patience.

Zombie issues

Open issues with no activity for weeks hurt team credibility and hide real problems. Crickets flags them so you can close, plan, or re-engage.

Production errors with no ticket

Connect Bugsnag and Crickets will flag any production error that has no GitHub issue linked. No more errors falling through the cracks.

Repository health

Review throughput

Is your team reviewing code as fast as it writes it? When the gap grows, quality suffers quietly and shipping slows. Crickets shows you the ratio before it becomes a problem.

created0
reviewed0

Tech stack detection

Crickets detects what your repos run on and flags versions that are no longer maintained. Know about it during planning. Not when a security patch breaks everything.

PHP 8.3Supported until Nov 2027
Symfony 4.4End of life. Upgrade to 7.x
Node.js 20LTS until Apr 2026

Bus factor

If one person left tomorrow, would your team be blocked? Crickets shows you when one developer carries too much of the load. Fix that before it becomes your problem.

Repo hygiene

No automated tests? No dependency alerts? Crickets flags the missing safety nets. The kind of gaps that only get noticed after something breaks in production.

Good to know

Your thresholds, not ours

You decide what counts as overdue. A two-week-old PR might be fine in one org and a red flag in another. Crickets adapts to your pace.

No access to your code

Crickets reads issues, pull requests, and comments only. Source code is never accessed or stored. Any admin can verify permissions before installing.

Soon

Slack notifications

A daily digest or instant alert in your team channel when something needs attention. Without opening the dashboard.

Coming soon

Crickets Pro

The free plan covers one repository. Pro removes that limit and adds the features engineering teams actually need at scale.

Unlimited repositories
1 repo
Slack notifications
—
Urgency inbox
Tech stack & EOL alerts
Bus factor & repo hygiene
Production error tracking
FreePro

Common questions

They do, and most have them muted or read in bulk. Crickets isn't for developers. It's for the person responsible for the whole picture, who shouldn't have to dig through notification threads to know if something is slipping.

The opposite. Instead of checking in manually, you see the situation in 30 seconds and move on. Fewer interruptions for your team. Less anxiety for you. Crickets is about not dropping the ball, not watching individuals.

Those tools are great for planning. Crickets watches what actually happens on GitHub: is a user waiting on a reply, does a bug have no owner, is a PR blocking someone. It's complementary, not a replacement.

No. Crickets reads issues, PRs, and comments, and a small number of config files (package.json and composer.json) to detect your tech stack. Source code is never read or stored. Any admin on your org can verify the exact permissions directly in GitHub before installing.

About two minutes. Install the GitHub App on your organisation, pick the repos you want to monitor, and you're done. No migration, no code changes, no config files.

Especially for small teams. With fewer people, there's less chance someone notices what's slipping. A bug without an owner for two weeks in a team of four is less visible than you'd think.

Crickets scans your repos for the frameworks and runtimes you depend on (PHP, Node.js, React, Laravel, Next.js, and more) then cross-references them against end-of-life schedules. If a version is no longer maintained, you see it flagged immediately. No more discovering a critical dependency is EOL when you're planning a sprint.

The bus factor is the number of people whose departure would seriously hurt your project. Crickets shows you when one developer accounts for a disproportionate share of commits over the last 30 days. It's not about blame. It's about knowing where to invest in knowledge sharing before it becomes a crisis.

Yes. Every item in your inbox has a dismiss button. Dismissed items don't disappear: they collapse into a quiet drawer at the bottom, excluded from all counts. You can restore them any time. Useful for zombie issues your team has consciously decided to leave open.