Why I Made My Mac Dashboard Local-First

Almost every dashboard app I tried wanted an account before it would show me a single number. When I set out to build a desktop dashboard for my Mac, the first decision I made was that it would be a local-first Mac app — a private dashboard with no account, no server, and no analytics. This is the reasoning behind that choice, including the tradeoffs I had to accept to make it work.

The default I didn't want

The usual architecture for a "dashboard" product looks like this: you sign up, you hand over your API keys to a cloud service, that service fetches your data on a schedule, stores it, and renders it back to you. It's convenient for the company. It's also a lot of trust to ask for.

When the data is your revenue, your customer counts, and your private repos, that model has real costs:

• A breach somewhere else becomes your problem. Your keys sit on a server you don't control.
• You depend on someone staying in business. If the service shuts down, your dashboard goes with it.
• You can't fully verify what happens to your data. You're trusting a privacy policy, not the architecture.

None of that is hypothetical. It's the standard tradeoff people make for convenience. I wanted to see if I could remove the tradeoff instead.

What local-first actually means here

Local-first means the app does its work on your machine, and your data stays there. Concretely, for the dashboard I built — Orbl — it means:

• No account. You install it and use it. There's nothing to sign up for.
• No server in the middle. When a widget needs your Stripe MRR or GitHub stars, the request goes directly from your Mac to that provider. Orbl is never a hop in between.
• Keys in the Keychain. API keys are read-only and stored in the macOS Keychain, the same vault your system uses for passwords — not in a config file, not in our cloud.
• No analytics. The app doesn't phone home about how you use it, because there's nowhere for it to phone.

You can read the full breakdown on the privacy page. The short version: the only computer that ever touches your data is the one in front of you.

The tradeoffs I had to accept

Local-first isn't free. Being honest about the costs is part of earning the trust:

1. No cross-device sync. Without a server, there's no central copy to sync between machines. Your dashboard lives on each Mac independently. For a wallpaper you look at on one computer, I decided that was an acceptable loss.
2. Permissions can't be silent. A cloud app asks for keys once and runs unattended. A local app has to ask your Mac for permissions — location for weather, accessibility for rhythm tracking — and it asks lazily, only when a widget needs it. That's a few more prompts, but each one is honest about what it's for.
3. No server-side history. I can't pre-compute years of trend data on a backend. The app works with what your providers expose, live.

I think these are the right tradeoffs for a private dashboard. You give up some convenience and get, in return, an app that can't leak data it never collected.

Why it's also better for me, not just you

There's a selfish reason a local-first architecture appealed to me as a founder. A product that holds no user data is a product with a dramatically smaller attack surface and no compliance overhead. I don't run servers that can fall over. I don't have a database of customer API keys that keeps me up at night. The privacy guarantee and the operational simplicity are the same decision viewed from two sides.

It also shaped the business model honestly. With no servers to pay for, there's no recurring cost to pass on — which is why Orbl Premium is a one-time purchase rather than a subscription. The architecture and the pricing line up.

Who this is for

If you want a dashboard that syncs across five devices and remembers everything forever, a cloud service is the better fit, and that's fine. But if you'd rather your revenue, repos, and metrics stay on your own machine — visible to you and no one else — a local-first approach is worth the small frictions. I wrote more about the people this suits on the privacy-first Mac dashboard page, and you can see how the live wallpaper dashboard renders all of it locally.

Orbl connects to plenty of services through its integrations — it just does so directly, from your Mac, with nothing stored anywhere else.

The app is free to try. If the local-first idea resonates, Orbl Premium is a one-time, no-subscription unlock — details on the pricing page.