GrapeGrape
Backups and version history for researchers

Every day ends with a backup of everything.

Grape backs up a literature review automatically every day on the device you use. One archive restores everything, and version history covers the smaller slips.
One archive with notes, attachments and structure
Made daily on the device you use, not synced between devices
Restore across platforms, so a Mac backup opens on Windows
Backups kept for thirty days and cleared automatically after that
Version history on every note for rolling back a paragraph
Moving to a new machine
Make a backup, install Grape, restore. That is the whole migration.
The paragraph you deleted
Version history brings it back without touching the rest of the note.
Before anything risky
Grape saves a version before the agent edits a note for you.
Results

Three things that stop being a problem

Feature lists are easy to write and hard to care about. This is what changes for researchers.
Stop rereading papers you already annotated
Ask what your notes say about a method and get the answer with the note it came from, ready to cite.
Turn interviews into text the same day
Record the session, get a transcript in the note, and code it while it is still fresh.
See how the threads connect
Link notes to each other and use the graph view to spot the argument forming across a year of reading.
In practice

What that looks like for researchers

A few moments in a normal week where the app earns its place.
Reading a new paper
Drop the PDF into a note, write alongside it, and tag it into the theme it belongs to.
Fieldwork day
Record on the phone, add photos, and let it all sync back to the desk copy.
Writing up
Ask for every note that touches a concept, then pull the quotes into the draft.
FAQ

Questions Before You Install It

The rest of them live in the help center.

Ask what you already read.

Papers, interviews, field notes and half formed arguments in one local library you can question in plain language, months after you filed them.