The short version
What is genuinely the same
Both apps read the same source of truth — the changelog Jira already keeps — and neither modifies your issues. Both aggregate across a project, break results down by fields like assignee or issue type, put a summary on a dashboard, and export to CSV.
And both run in-tenant. We checked SaaSJet's listing on the Marketplace in August 2026 and it carries the Runs on Atlassian badge, the same as Dwell's. If you arrived here looking for a no-egress alternative to something else, SaaSJet already qualifies, and we would rather say so than let you buy Dwell for a reason that is not true.
For scale: roughly 5,400 active installs and 207 reviews averaging 4.54 out of 5 for SaaSJet when this page was written. Dwell is new and has neither.
Where Dwell differs
The statistic the report is built on
This is the substantive difference. Dwell's reports lead with the median and p85 rather than the average. An average cycle time is pulled around by outliers — one issue that sat in the backlog for a year moves it more than fifty issues that flowed normally. The median tells you what a typical issue takes; p85 tells you the number you can commit to and be right about six times in seven. Every Dwell report, the weekly trend and every group-by is built on those.
Aging work in progress
Dwell compares each open issue against your own finished-work p85 and lists the ones already past it. It is the only report here that points forwards: those issues have not stalled yet, and you can still do something about them.
Flow efficiency, blocked time, time between two statuses
Per-status totals tell you how long each step took. They do not tell you how much of that time was queueing rather than work. Dwell reports flow efficiency (active time as a share of elapsed time), how long issues sat flagged as blocked, and the time between any two statuses you name — for example Backlog to In Progress, which is usually where the waiting actually is.
A free surface that does not expire
Dwell's per-issue panel — the time in each status plus lead time — is free on every issue at any team size, permanently. The licence covers the project reporting layer. That means anyone on the site can answer “why has this ticket taken so long?” without a licence discussion.
Where SaaSJet is the better fit
- Price from 250 users up. SaaSJet is cheaper at every tier above 100 users — meaningfully so at 1,000, where it is roughly 30% less per user. See the table below.
- Track record. Thousands of installs and 207 reviews. Dwell has no reviews at all yet, and no amount of copy substitutes for that.
- Cloud Fortified. SaaSJet holds it; Hullara does not. It covers operational maturity — reliability commitments, incident response, a bug bounty — and if your procurement checklist includes it, that decides the matter.
- Breadth of reporting. Its listing leads on sprint-oriented views and dashboard “control centre” reports. Dwell deliberately ships a narrower set.
- Support at scale. SaaSJet is a company with a support team. Hullara is one person who answers email.
Pricing side by side
Both are sold through Atlassian with per-user monthly pricing, and both are free for sites of 10 users or fewer. Read from the Marketplace pricing API in August 2026; verify current prices before buying.
If the decision comes down to cost per user, SaaSJet wins it from 250 users up and we are not going to pretend otherwise. Dwell's argument is what the reports tell you, not what they cost.
Questions
Also worth reading: Dwell compared with Timepiece · what “no data egress” actually means · how to see time in status in Jira.