A user-research archive that answers questions
Every interview quote, queryable by theme — linked to the features it shaped.

Without memory
You’ve run fifty user interviews and can’t answer “what have users said about onboarding?” without someone spending a day re-reading transcripts. Research gets done, synthesized once for one deck, and then effectively deleted.
With Rekall
Interviews become queryable memory: quotes linked to themes, themes linked to the decisions and features they influenced. “What did enterprise users say about SSO?” is a ten-second recall, not a re-research project.
How it works
Ingest transcripts
Interviews go in via API; entity and theme extraction links each insight to who said it and what it concerns.
Themes emerge in the graph
Recurring pain points cluster across interviews — with the receipts (actual quotes) one hop away.
Decisions cite the evidence
When research drives a product decision, the decision graph records which insights motivated it — closing the loop from quote to shipped feature.
See it in action
> what have enterprise users said about SSO?rekall.recall("SSO", hive: "user-research")→ 9 insights across 6 interviews:"We can't even trial without SAML" — P14, CTO"Okta or it's a no" — P22, IT lead (similar: P8, P17)Theme: SSO is a trial blocker, not a close blocker→ informed Decision (Apr 2): move SSO to Team tier(outcome: +3 enterprise trials in May)
Related use cases
The “why” archive — decision memory
“Why is auth done this weird way?” finally has an answer.
Team onboarding that compounds
A new hire’s AI already knows the team’s conventions on day one.
Compliance-grade audit memory
Who decided what, when, on what evidence — and what you believed at the time.