Behind the Scenes: SavePoint Architecture

Behind the Scenes: SavePoint Architecture

When I started building SavePoint, I had one non-negotiable requirement: your financial data stays on your computer. Period. This wasn't just a privacy preference. After 12 years of tracking my own finances in spreadsheets, I understood exactly how sensitive this information is and how uncomfortable it felt trusting it to cloud services.

That decision shaped everything about how SavePoint is built.

The Technical Foundation

SavePoint uses a local database stored entirely on your device. When you enter a transaction, update an account balance, or run a Monte Carlo simulation for your FIRE planning, all of that processing happens locally. The application doesn't phone home, doesn't sync to the cloud, and doesn't require an internet connection after the initial license activation.

This architecture means SavePoint works exactly the same whether you're connected to WiFi or sitting in an airplane with no internet. Your financial data is always accessible because it's always right there on your machine.

Performance Considerations

Running everything locally does create some interesting engineering challenges. Monte Carlo simulations for FIRE planning, for example, run thousands of scenarios to project your retirement outcomes. Making that fast enough to feel responsive on typical consumer hardware required careful optimization.

The same goes for generating reports like Sankey flow diagrams or multi-year cash flow analyses. These need to process potentially years of transaction data quickly while keeping memory usage reasonable. We put significant effort into making these features feel snappy even with substantial data sets.

Data Security and Backup

Your SavePoint database is a file on your computer, which means your existing backup solution protects it. If you use Time Machine, Windows Backup, or any other backup system, your financial data gets backed up along with everything else.

For users who want an additional layer of protection, we offer an optional encrypted cloud backup service. Your data gets encrypted locally on your device before being uploaded. We never see your financial information in plain text. But this is entirely optional. The core application works perfectly without it.

Multi-Currency and Internationalization

SavePoint supports 150+ currencies and 8 languages because financial tracking isn't just an English-speaking concern. Implementing proper internationalization meant handling date formats, number formats, and currency symbols correctly across different locales. A balance of €10.000,00 needs to display properly in Germany while appearing as $10,000.00 in the United States.

This sounds straightforward, but the edge cases multiply quickly when you're dealing with real financial data across multiple currencies and time zones.

The Tradeoffs

Offline-first architecture does come with limitations. There's no automatic sync between devices. We can't offer a mobile app that shares data with your desktop version without adding cloud infrastructure. Real-time bank connections would require internet access and third-party services.

These tradeoffs are intentional. Every feature request gets evaluated against our core principle: does this require compromising user data privacy? If the answer is yes, we look for alternative approaches or accept that some features aren't right for SavePoint.

Looking Forward

The architecture decisions we made at the start continue to guide SavePoint's development. New features get built within the offline-first framework, ensuring that the privacy guarantees users depend on remain intact as the software evolves.

Building software this way takes longer and requires saying no to features that would be easier with cloud infrastructure. But for financial software handling your most sensitive personal data, we believe it's the right approach.