SCM ARCHIVE

Why Your Search Should Never Leave Your Mac

Cloud search is a rental agreement on your own memories. Here's what changes when the index lives next to the files.

SEP 08 2026 SP 2 MIN PLAY

Every search box is a promise about where your data goes. Most of them are lying by omission.

When you type a query into a cloud-backed search, your words leave your machine, get matched against an index someone else built, on hardware someone else owns, under a retention policy you did not read. For a folder of stock photos, that trade is fine. For ten years of your family’s footage, it is a rental agreement on your own memories.

The index is the asset

People think of search as a feature. It is really an artifact: a set of vectors, transcripts, text regions, and scene boundaries that describe your archive. Build it once on your machine and it keeps paying out — every future query becomes cheaper, because the expensive part is already done.

That is also why the artifact should not live in a data center. An index is not a copy of your files; it is a description of them. It knows where you were, who was with you, what was written on screen. It is, in aggregate, more revealing than the media itself.

A search index is the most honest autobiography you will ever accidentally write.

What actually gets slower in the cloud

The usual objection is latency, and it lands harder than people expect:

  • Round trip. A local query resolves in tens of milliseconds. A hosted one waits on a network you do not control.
  • Upload. Indexing a terabyte over a home uplink is a multi-day commitment, and it runs again whenever you add footage.
  • Ceiling. Hosted pipelines cap resolution, frame rate, and clip length to keep unit costs sane. Your 4K rushes get sampled down to something cheaper to reason about.

Local inference inverts all three. The first index is expensive — that part is honest — but it happens once, on hardware you already paid for, and every later query is nearly free.

The honest cost

Local-first is not free. You pay in watts, in disk, and in a first run that can take hours on a large archive.

The fix is not to apologize for it, it is to make the wait legible: show coverage as it climbs, let search return partial results immediately, and never make someone choose between using the app and finishing the index.

That is the whole design brief. Everything else is a detail.

END OF TAPE