Why Minnie is local-first
Your financial life is unusually personal. We designed Minnie accordingly.
Most consumer software today is built around a familiar model: the application and its durable data live primarily in the company's cloud, while your phone or computer provides the interface.
For many products, that makes perfect sense. But a product that understands your whole financial life is different. Over time, Minnie could understand your income, spending, investments, debt, property, taxes, family finances, and how all of those things relate to one another.
That led us to a fundamental architectural question:
Does Minnie the company need to possess all of that information for the product to understand it?
We don't think it should.
Minnie is being built local-first. Your detailed financial history is designed to live encrypted on your device, where much of Minnie's financial model and computation can also happen.
Minnie still uses cloud infrastructure. Signing in, connecting securely to financial institutions, and some forms of remote processing require it. Local-first does not mean local-only.
Local persistence by default. Remote processing where necessary.
Minnie's cloud does not need to become the default home of your entire readable financial life.
How that changes the architecture
TRADITIONAL CLOUD-CENTRIC SOFTWARE
COMPANY CLOUD
┌──────────────────┐
│ Financial data │
│ Application │
│ Computation │
└────────┬─────────┘
│
│
┌─────┴─────┐
│ Your │
│ device │
└───────────┘
MINNIE'S LOCAL-FIRST MODEL
YOUR DEVICE
┌──────────────────┐
│ Encrypted │
│ financial history│
│ │
│ Financial model │
│ │
│ Local computation│
└────────┬─────────┘
│
when necessary
│
┌────────┴─────────┐
│ Minnie services │
│ │
│ Authentication │
│ Institution │
│ connections │
│ Scoped remote │
│ processing │
└──────────────────┘Your device is more than a screen
In a conventional cloud-centric application, the device often acts primarily as a window into state maintained by the service.
Minnie is designed differently. The detailed financial record can live locally, encrypted on your device. Minnie can build its financial model from that local state and perform many calculations there as well.
That means the product can understand information without automatically requiring Minnie the company to retain a complete readable copy of that information centrally.
We want the product to know more without requiring the company to know everything the product knows.
The cloud still has a job
Local-first doesn't mean removing servers from the architecture.
Minnie needs secure online infrastructure for things such as authentication and connecting to financial institutions. Some capabilities may also require remote computation.
The architectural principle is not to prohibit remote processing. It is to make it intentional and scoped.
When a feature requires information to leave the device, the goal is to provide the information necessary for that operation rather than treating the user's complete financial history as universally available remote context.
Local persistence by default. Scoped remote processing when necessary.
Why we chose this architecture
Privacy through less possession
Security is often framed as: How do we protect all of the data we've collected?
That's an important question. But there's another one:
How much of that data did we need to collect centrally in the first place?
A centralized readable database containing the complete financial histories of many users creates a particularly valuable target. Strong security controls matter, but possession itself creates exposure.
Local-first lets Minnie reduce the amount of complete readable financial information it needs to possess centrally by default.
More control
Your detailed financial state is designed to live with you rather than existing primarily as a record on Minnie's servers that your device requests permission to see.
That distinction becomes increasingly important as Minnie understands more of your financial life.
Intelligence doesn't have to mean accumulation
Personalization has traditionally had a fairly direct relationship with data accumulation: the more a service learns about you, the more information the company operating it tends to retain about you.
We're trying to separate those things.
A sophisticated financial model can potentially exist locally and become more useful without requiring an equally sophisticated centralized profile of the person using it.
What local-first does not mean
It does not mean Minnie is offline. Some functionality inherently requires network services.
It does not mean no financial information ever leaves your device. Connecting accounts and using remote functionality necessarily involves transmitting information.
It does not mean third parties disappear. Financial institutions and data providers involved in connected accounts still participate in those interactions.
It does not mean local-first is automatically more secure in every way. It changes the security model. A compromised device remains a serious risk.
And it does not mean “unhackable.” No serious software should make that claim.
Different architecture, different tradeoffs
Local-first removes some convenient assumptions of cloud-centric software and replaces them with genuinely hard engineering problems.
Device loss and recovery. How does someone recover their financial history without Minnie simply retaining the readable database?
Multiple devices. How can a user securely synchronize financial state while preserving the local-first trust model?
Encryption and key management. Where do keys live? How are they protected? How does recovery work without creating an easy centralized bypass?
Endpoint security. If a user's device is compromised while Minnie is unlocked, local encryption alone cannot protect everything.
Backup. A system that minimizes centralized readable possession still needs a reliable way to prevent the loss of years of financial history.
These aren't footnotes to the architecture. They're consequences of it, and they need to be solved well.
What exists today
Minnie is still being built. The architecture described here represents the system we're building toward, not a claim that every component is complete today.
Encrypted local financial storage is already in use in Minnie's Personal Sandbox. Complete provider ingestion, encrypted synchronization, backup, recovery, and multi-device behavior are still being developed.
As those systems are implemented, we'll update this page so it continues to describe how Minnie actually works—not merely how we intend it to work.