ONLINEREV · 2026-06-23§ GUIDEFORMAT · PDFPAGES · 15PRICE · FREE
§ Free DownloadPDF · 15 pages · 12 sections

The Self-Hosted Evernote Replacement Playbook

How I moved 12,690 notes to Joplin on a Mac mini, built a local AI that answers questions about them, proved nothing was lost — and cancelled a $250/yr subscription.

§ 01

A real system, documented end to end

This isn't a listicle of “best Evernote alternatives.” It's the full build log of a single-user system I run every day: the decisions, the failure modes, and the architecture — enough that you could rebuild it, adapt it, or decide it's not worth the trouble.

The spine of it is one principle: adopt vanilla Joplin for the hard 90% (editor, sync, offline clients), and build only the high-leverage 10% it can't do — AI search that works on the iPhone, voice transcription, a real Home, and large-file serving — as one small companion service. No forks. No second subscription.

§ 01
12,690 notes, 0 lost

A custom ENEX converter preserved every note, all five highlight colors, and the real dates — then audited to prove it.

§ 02
AI that reads your notes

A local-embeddings, agentic 'ask my notes' assistant on native iOS, macOS, and Android — your data never leaves your hardware.

§ 03
$250/yr → ~$0

Self-hosted on a Mac mini you already run, with encrypted off-site backups you can actually restore.

§ 02

What's inside the guide

  1. § 01
    Why I left Evernote

    The $250 trigger, fifteen years of lock-in, and the five hard requirements that shaped everything.

  2. § 02
    Build vs. buy

    Adopt the hard 90% that already exists; build only the high-leverage 10%. And why not to fork.

  3. § 03
    The architecture

    Joplin Server in Docker, Tailscale with a real cert, the always-on workhorse, offline-first.

  4. § 04
    The migration

    Why off-the-shelf importers silently lose ~11% of your notes — and the custom converter that didn't.

  5. § 05
    Proving nothing was lost

    A full content-fidelity audit of all 12,690 notes, the two converter bugs, and the rule they taught.

  6. § 06
    The AI companion

    Local embeddings + an agentic 'ask my notes' assistant that answers, aggregates, and cites sources.

  7. § 07
    Voice, Home & big files

    Local Whisper transcription, an Evernote-style Home, and serving the files phones can't sync.

  8. § 08
    Backups & disaster recovery

    Encrypted off-site backups through restic → R2 — and an actual, verified restore test.

  9. § 09
    Economics & trade-offs

    $250/yr → ~$0 recurring, and an honest ledger of what you give up to get there.

  10. § 10
    Should you do this?

    A genuine decision framework — who this fits, who should walk away, and the order to build it in.

  11. § A
    Appendix: hard-won gotchas

    The Joplin Data API, import, and multi-client sync lessons that each cost a debugging cycle.

  12. § B
    Appendix: the stack at a glance

    Every component, and the one reason it's there — a single-page reference.

§ 03

Who it's for

If you're a single user who values owning your data, has (or doesn't mind running) an always-on machine, and will actually test your backups — this is for you. If you need sharing, collaboration, handwriting, or zero maintenance, the guide is honest about why this isn't your path.

It's free because the best way to understand what we build at Slick Engineering & Consulting, Inc. is to see a complete system, decisions and trade-offs and all — not a sales page.

§ Acquire

Own your notes. And teach them to answer.

15 pages. 12 sections. The architecture, the migration, the AI layer, and every gotcha that cost me a debugging cycle.