About Ohmnia
Ohmnia did not start as a product idea. It started as a spreadsheet that crashed at the worst possible moment.
The file that finally gave up
Before Ohmnia there was an Excel workbook with VBA macros. It did the job: a few invoices, some tracking, a handful of totals. Then it grew. Every new need added a column, a macro, a hidden sheet.
That kind of file always ends up untouchable. You no longer dare change it, for fear of breaking a formula you cannot find. You lose track of which copy is the right one. And the day it corrupts itself, there is nothing behind it.
Ohmnia was written to replace that file with something you can open without apprehension.
Why everything stays on your computer
The accounts of a self-employed person are their turnover, their client list, what has been paid and what has not. There is no reason for that information to live on somebody else's server.
So Ohmnia has no account, no server and no synchronisation. Everything fits in a database file on your disk, which you can copy, back up or carry away like any other file. The only possible network access is the update check, disabled by default.
There is a flip side, and it is deliberate: nobody can recover your data for you. No restore from a cloud, no forgotten password emailed back to you. The application makes automatic backups and offers an encrypted backup to external storage, but keeping a copy away from your computer remains your responsibility.
Code meant to be read again
Ohmnia is written by one person, who is not a professional developer. The main constraint was therefore neither performance nor elegance: it was being able to reopen the code six months later and understand it.
Hence choices that would look surprising in a corporate project: no ORM, no state manager, hand-written readable SQL, and all the vocabulary in French — variable names, comments, database columns. Every calculation lives in exactly one place in the code, so that a fix never has to be applied three times.
- ApplicationElectron and React, in TypeScript
- DataSQLite, one local file, with nothing to install
- DocumentsPDFs generated on the machine, never sent anywhere
- Backupstimestamped local copies, and AES-256 encrypted archives
- LanguagesFrench, with English being translated
What Ohmnia is not
It is not a guarantee of compliance. The tax rates, thresholds and legal wording it offers are starting points, not a certification. They change, and they depend on your activity and your country. The "Compliance" panel checks what software can check — statements present, numbering continuous — and nothing more.
It is not enterprise software with a support contract. There is no phone support, no availability commitment and no promise of being bug-free. Check your documents before sending them, and your figures before any filing.
All of this is written plainly in the terms of use, which are shown the first time the application is launched.
Where it goes next
Ohmnia today covers invoicing, quotes, time tracking, inventory, the income and expense journal, bank statement import and year-end closing. What a self-employed business actually needs.
What comes next depends on real needs met while using it, not on a roadmap drawn in advance. The English translation is progressing screen by screen. Other subjects are waiting their turn — the Swiss QR-bill, for instance — and will become relevant the day they genuinely are.
The code is public. If you want to see how it is built before installing anything, it is all there.