DMPR is a personal knowledge tool — bookmarks first, then notes, snippets, and analytics — built to be fast, private, and available on every device.

It started as a single-purpose bookmark manager and grew into a small suite of tools that share one backend and one design language. The goal has stayed constant: a calm, quick place to dump links and ideas, and find them again later without friction.

DMPR is a static web app — plain HTML, CSS, and JavaScript, no build step, no framework. It's hosted on Netlify at dmpr.link. That simplicity is deliberate: the whole app is a handful of files you can open and read, which keeps it fast to load and easy to maintain.

Authentication is Google Sign-In only. No passwords to manage, no separate accounts — if you have a Google account, you're in. Everything is designed around working seamlessly across a desktop, a laptop, and a phone throughout the day.

DMPR originally stored everything in a Google Sheet, driven by Google Apps Script. It was a clever, zero-cost way to get a real backend with no server — and it worked well for a long time. But at scale it grew fragile: sync race conditions, row limits, and an awkward auth model for the save bookmarklet.

So DMPR is migrating to Supabase, a managed Postgres database with a direct REST API. It keeps the same simplicity — the frontend still just talks to an API over fetch() — but with a real database underneath: precise single-row writes, no row limits, and row-level security ready for the future. The move is happening in dual-mode, so both backends stay switchable until the new one is fully proven.

The long arc is from a personal tool to a small multi-user platform — where anyone can sign in with Google and get their own private DMPR at a personal URL, while the core experience stays exactly as simple as it is today.

See the full roadmap for the detailed path.

This page will grow over time with more of the story behind DMPR — the why, not just the what. For now, this is the tech at a glance.