Evernote taught a generation to ‘remember everything’: clip it, file it into a notebook, tag it, trust the archive. Reloggly starts from the same promise and rejects one assumption—that a human will keep doing the filing. The comparison is not about storage; both store plenty. It is about who maintains the structure that makes storage useful.
Where Evernote is strong
Evernote remains a serious document archive: a powerful web clipper, text recognition inside PDFs and scans, notebooks, stacks, and tags, with two decades of accumulated workflows around them. If your material arrives as documents and you genuinely maintain your taxonomy, it holds up.
Manual structure sends a monthly bill
Notebooks and tags are promises of future discipline. Every note demands a filing decision at capture time, and every skipped decision weakens the whole system, because retrieval by structure only works where structure was applied. Taxonomies drift: ‘projects’ splits into ‘projects-2025’, tags multiply into synonyms, and the archive slowly becomes a place you search with guilt instead of confidence.
Reloggly extracts context instead of requesting it
The bet is that structure should be computed from the note, not demanded from the person:
- Chronology is the backbone—every item keeps its date, source, and original media with no filing step.
- Topics, people, and projects are recognized from content and can overlap; one note belongs to three contexts without being copied.
- A vague note triggers one clarifying question while you still remember what it meant.
Two meanings of ‘remember everything’
Evernote remembers everything you filed, the way a well-kept cabinet does. Reloggly aims at a different verb: not to store everything but to answer from everything—‘what did we decide about pricing’ assembled from a voice memo, a screenshot, and a typed line you never tagged. Test both with a question about last month, not with a filing session.
If you enjoy curating a taxonomy and your input arrives as documents, Evernote still earns its keep. If your input is fragments and the filing never happens, Reloggly's bet is that structure should be extracted, not enforced.