Grape
Backups and version history for developers

Every day ends with a backup of everything.

Grape backs up a pile of runbooks and notes 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.

Made daily without asking

The device you use writes a copy, so there is always one from yesterday.

A backup crosses platforms

One made on a Mac restores onto Windows with no conversion step.

One archive, everything in it

Notes, attachments and structure in a single file you can put anywhere.
Results

Three things that stop being a problem

Feature lists are easy to write and hard to care about. This is what changes for developers.

Stop solving the same bug twice

Describe the symptom in search and get the note where you already worked it out.

Keep decisions where you can defend them

Ask what you decided about a service and get the note, the date and the reasoning.

Point the AI at your own stack

Bring your own key, or run a local model through Ollama, and keep the workspace on disk.
In practice

What that looks like for developers

A few moments in a normal week where the app earns its place.

Debugging

Write the symptom, the theory and the fix in one note, with the log you kept attached.

Architecture review

Record the conversation and keep the decision log next to the diagram.

New project

Keep the setup steps in a runbook that actually gets found again.
FAQ

Questions Before You Install It

The rest of them live in the help center.

Find it next time it breaks.

Runbooks, architecture decisions and the fix you worked out at midnight, in a local library you can search by meaning and keep offline.