isdéjàvu.com

Is that bug new,
or déjà vu?

You can't always tell, and you pay either way. isdéjàvu checks every incoming ticket against your closed history and answers with proof: the original issue, and the commit that fixed it.

Works with Trello, Jira, Linear & GitHub Issues · 5-minute setup
isdéjàvu · Inbox
⌘K SearchDK
ACME-CORE
4,812 closed tickets indexed
9 repos · synced 2m ago
INCOMING · TODAY
ENG-3107filed by Priya V.
Webhook retries silently failing
Recurrence of ENG-110694% confidence
ORIGINAL TICKET
ENG-1106Closed · Mar 14
Webhook retry exceeds 30s limit
FIXED BY
a3f8c21PR #482 · Marcus K.
Increase webhook retry timeout window
CLASSIFICATION

Every ticket gets an answer. Not a guess.

Recurrence, genuinely new, or still under review: semantic matching against your full closed history, with a confidence score you can set thresholds on.

Webhook retries silently failingRecurrence · 94%
Rate limiter rejects burst trafficReviewing…
Search results duplicatedGenuinely new
When it isn't sure, it says so: no false confidence.
THE RECEIPT
a3f8c21Increase webhook retry timeout window
PR #482 · merged Mar 14 · Marcus K.
3 files · retry queue, timeout config, tests
Author context, even after they've left the team
COMMIT ATTRIBUTION

The fix ships with the flag.

Every recurrence links the exact commit and PR that resolved it last time. Your engineer starts from the answer, not from a blank investigation.

WHERE YOU WORK

It tells your tools, not just you.

High-confidence matches get commented straight on the ticket, so triage sees the answer before a human even opens it. Slack and Discord channel alerts are next.

DV
isdéjàvu BOT
Likely recurrence of ENG-1106 (94%). Fixed in a3f8c21 · PR #482.
#
#eng-triageCOMING SOON
⚑ ENG-3107 flagged · matches a ticket closed 9 months ago, fix attached.
LIVE DEMO

Don't take our word. Ask it.

Pick an incoming ticket: the scan runs against this demo workspace's closed history.

APP-33212 min ago
Checkout button unresponsive on Safari
filed by support
ENG-31078 min ago
Webhook retries silently failing
filed by on-call
WEB-225614 min ago
Search results duplicated after pagination
filed by QA
Select a ticket to run a scan
It will be compared against 4,812 closed tickets in this demo workspace.
0
tickets answered
0
recurrence catch rate
0
saved per engineer / month

“Half our ‘new’ incidents turned out to be regressions it could trace to a specific PR. What used to be a two-day investigation is now twenty minutes.”

JO
Jonas Okafor
Staff Engineer, Brightline
PRICING

Simple, flat pricing

Free
$0forever

For solo devs who want to try it out.

50 analyses per month
Automatic regression detection
Regression dashboard
Manual "caused by" linking
No auto-comments
No credit card required
Start free
Starter
$19per month

For small teams tired of repeating work without realizing it.

500 analyses per month
Automatic regression detection
Regression dashboard
Manual "caused by" linking
Auto-comments on flagged tickets so the whole team sees it
Email, Slack, and Discord alertsSoon
Thumbs up/down to tune accuracy over time
Start 14-day trial
Pro
$49per month

For engineering teams who need to know not just what regressed, but why and who caused it.

2000 analyses per month
Everything in Starter
GitHub attribution: see exactly which PR introduced the regression, which files changed, and who authored the original fix
Similarity score shown directly in ticket comments
Priority support
$0.02 per analysis above your cap
Get Pro
FAQ

Questions, answered

What counts as an analysis?

One analysis is a single ticket scanned against your history to check whether it is a regression. Scan a ticket again after new commits land and that counts as another analysis.

Which PM tools do you support?

Trello, Jira, Linear, and GitHub Issues. You connect your existing workspace in a couple of clicks: no new tool to learn.

How accurate is the detection?

Every flag comes with a similarity score so you can see how confident the match is. Thumbs up/down feedback tunes the detection to your codebase over time, so accuracy improves the more you use it.

Will it spam my tickets with false positive comments?

No. The Free tier never posts comments. On paid tiers, auto-comments only fire above a confidence threshold you control, so the team only hears about regressions worth looking at.

Is my ticket data stored? Is it safe?

We store the minimum needed to detect regressions, encrypted in transit and at rest. Your data is never used to train public models and is deleted when you disconnect.

What happens if I go over my analysis cap?

Nothing breaks. Analyses above your cap bill at $0.02 each, or you can upgrade to a higher tier. You will never be cut off mid-scan.

Can I cancel anytime?

Yes. Plans are monthly with no contract: cancel from settings whenever you want and you keep access through the end of the billing period.

Does it work with my current Jira/Trello setup or do I need to change anything?

It works with your setup as-is. Connect your existing workspace and isdéjàvu reads the tickets you already have: no migration, no new fields, no process changes.

Stop wondering.
Start knowing.

Connect your tracker and repo: isdéjàvu answers the question on the very next ticket.

14-day trial · No credit card · 5-minute setup