EUR 29
USD 35 · CHF 29
Per team, per month · flat
How it works
Replaces the weekly Jira sweep, not your stack.
Most engineering managers and tech leads already do an informal pass over Jira and pull requests before standup. Gabel runs that pass for you and posts the result — same data, on schedule.
What you do today
- Open Jira and scroll the active sprint and backlog.
- Wonder whether cycle time or bug volume is worse than last time you checked.
- Check the pull request queue — or skip it altogether.
- Walk into standup without a reliable view of what changed.
What Gabel will do for you
- Five signals with clear thresholds and the week-over-week change.
- Direct links to affected Jira stories and PRs when reviews fall behind.
- One prioritized action for you to focus on this week.
- A flag when last week’s fix didn’t actually move the number.
Jira and one git host (Bitbucket or GitHub) stay where they are. EUR 29 / USD 35 / CHF 29 per team, per month. Team-level signals only — never used for individual developer scorecards.
Methodology
Predictable rules. Transparent thresholds.
No black-box scoring. Each signal is a simple threshold on data you already have, and the narrative is templated from which signals fired and how the numbers moved week-over-week.
- What we read — Jira issue metadata, sprint fields, status transitions, and pull request open / merge / review timestamps. Read-only API access.
- What we never store — source code, ticket descriptions, attachments, or any customer PII.
- When a signal fires — the 85th-percentile cycle time drifts more than 20% from its 4-week baseline; work in progress exceeds 1.5× team size; bugs exceed 25% of completed work; sprint-to-sprint velocity varies by more than 35%; average pull request merge time exceeds 2 calendar days (plus the count of PRs waiting 24+ hours for a first review).
-
How it arrives — Slack incoming webhook or HTML email. Optional 12-week trend page on
a secret URL, no login required.
- Optional mid-week alert — covers work-in-progress and pull request lag only, silent when both are within target
Pricing
EUR 29 · USD 35 · CHF 29 per team, per month.
Flat per team — not per developer seat. Covers one Jira board, the repositories you connect, and any delivery destinations (Slack channel, email address). A second team or board is a second subscription.
The five signals
Five thresholds. Linked issues when they fire.
All five are computed from Jira board metadata and pull request history. Read-only access; Jira stays the system of record.
Cycle time drift
85th-percentile cycle time pulling away from the 4-week baseline. Names when the drift began and the change from last week.
Next: pull cycle time back to baseline — review intake and items stalling in review.
Too much work in flight
Active work in progress exceeds 1.5× team size. Linked Jira keys for any item sitting 5+ days.
Next: unblock the named items and pause new intake until work in progress drops below team size.
Bug ratio rising
Share of bugs in completed work, plus the rework rate from issues that regressed out of Done.
Next: inspect regressions from Done — rework may be driving the number more than new defects.
Velocity inconsistency
Sprint-over-sprint delivery is swinging. Names the outlier sprints and shows delivered-vs-committed counts.
Next: set the next sprint commitment to a median number that the team can more confidently deliver.
Pull request merge lag
Average open-to-merge time, slowest repos, count of PRs waiting 24+ hours for a first review, and the slowest merges.
Next: route review requests in the repo where merges are stalling.
To Do
When several signals fire at once, Gabel picks the one to tackle first — with deep links to the slowest PRs when review lag is the bottleneck.
Role: tells you what to fix first when the board is noisy.
Getting started
Self-serve setup in the app. First brief on your schedule.
Open the app, sign in, and walk through the setup wizard. Connect Jira and your git host with OAuth, choose your board and repos, and set when the weekly brief should arrive in Slack or email.
Open the app and create your workspace
Sign in, name your team, and pick your delivery weekday and timezone. No sales call required.
Connect Jira and git
OAuth into Jira Cloud, GitHub, or Bitbucket. Choose your board, repos, and optional Jira filters.
First brief in your channel
Your first digest runs on the schedule you set. Send a test digest anytime from settings to verify delivery before Monday.
FAQ
Frequently asked questions
Is this an AI copilot or agent platform?
No. Gabel runs fixed thresholds and deterministic rules over Jira and git metadata. The narrative is templated from which signals fired and how the numbers moved — no open-ended chat, no autonomous agent. You read one brief, not a new workspace.
What makes this different from LinearB or Swarmia?
Those are dashboards you log into, usually priced per seat. Gabel is a single weekly brief pushed to your channel with one prioritized action — no charts to interpret, no per-seat math, no weekly login habit to build.
Do you require Jira?
Yes. All five signals are board-driven, so Jira Cloud or Jira Server with API access is required. Linear and Shortcut are not supported yet.
Does this work with GitHub or only Bitbucket?
Both. One git provider per subscription: a GitHub organization or a Bitbucket workspace.
Do we need to create a Slack bot?
No. Trials use a standard Slack incoming webhook to your channel. If webhooks are restricted in your workspace, email delivery works just as well. No OAuth app to build or approve.
Is the trial free? What happens after?
Four weeks free, no credit card. After the trial, EUR 29 / USD 35 / CHF 29 per team, per month if you opt in. Nothing converts automatically.
What data leaves our environment?
Issue metadata, sprint fields, and pull request metadata only. Read-only access. We never read source code or ticket bodies.
Can we see a sample shaped to our board before committing?
Yes. Use the sample brief above as a reference, or send a test digest from the app after connecting your board. For a redacted sample before you connect anything, use the contact form.
Contact
Questions, custom setup, or anything else?
Most teams start straight in the app. If you need help, want a redacted sample before connecting Jira, or have a security or procurement question, send a note here.
- We reply within one business day.
- Prefer email? [email protected]
- Ready to try Gabel? Open the app
