Keep the data separate
The application should not trap the user's data inside a service. JSON files make the records portable, inspectable, and easy to back up or transform.
Spbook is a lightweight accounting tool for solo entrepreneurs. It stores your data as JSON files in your Google Drive, so the application stays simple and the data stays yours.
In March 2026, I started working as an s.p. in Slovenia. I tried some of the products already on the market, but they did not feel right for the way I work. Most of them seemed heavier than necessary for a solo business with a very small number of accounting records per year.
I work with PostgreSQL every day, so a database was the obvious first idea. But then came the usual questions: hosting, backups, maintenance, and operational complexity. All of that for a system used by one person, with no real need for concurrent multi-user editing.
Spbook is intentionally designed around a small, practical use case: personal bookkeeping for a solo entrepreneur. The goal is not to mimic enterprise accounting software. The goal is to stay understandable, maintainable, and useful.
The application should not trap the user's data inside a service. JSON files make the records portable, inspectable, and easy to back up or transform.
A solo business with hundreds of records per year does not need database infrastructure by default. The system should match the real volume of work.
A folder structure and plain files are easier to reason about than hidden application state. The model should stay understandable for years.
{
"id": "inv-2026-0001",
"type": "invoice",
"issueDate": "2026-04-01",
"client": {
"name": "Example OÜ",
"country": "EE"
},
"currency": "EUR",
"amount": 4523.75,
"status": "paid"
}
Google Drive is not presented here as a universal answer for every application. It is a practical storage layer for a small personal accounting tool: familiar, accessible, backed up, and already good enough for structured files and directory-based organization.
This project is being built for personal use first. It may or may not become useful to others, but that is exactly why it makes sense to build it in the open. The architecture is interesting on its own, and anyone should be able to study it, adapt it, or reuse the ideas.
Spbook starts with bookkeeping for one user, then may grow into invoice generation, administrative workflows, and mobile applications. The foundation should remain the same: simple data, clear structure, and no unnecessary infrastructure.