SQLite or PostgreSQL? Picking the Database for an App You Run Yourself
Most self-hosted apps need one file, not a database server. How we choose between SQLite and PostgreSQL, and what it means for cost, backups and your data.
Who Reads Your Code? Why We Keep Ours Off GitHub
Code is company data. Why we host our own Git server instead of GitHub or Bitbucket, why Codeberg suits open source better, and where GitHub still wins.
Privacy and security are one promise: why you need both
A company can guard your data well and still sell it, or mean well and still leak it. Why privacy and security only work together, and what to ask a vendor.
"Free" apps: who actually pays, and with what
Most free apps are paid for by advertisers and data buyers. How your taps and location turn into revenue, who ends up holding them, and what that costs you.
Metadata is data: what leaks even when messages are encrypted
Encryption hides what you say, not who you talk to, when, how often or from where. Why metadata reveals more than content, and what apps can do about it.
Data that is never collected cannot leak
Encryption, firewalls and audits all help, but the strongest security control is simpler: don't keep the data. Why data minimisation beats every defence.
What is inside our apps: a dependency audit
We say our apps have no tracking, no ads and no crash reporting. Here are the real dependency lists of three shipped apps, so you can check that claim.
F-Droid and what it means to own your data
Owning your data is not a setting you switch on. It starts with where the app came from, what it stores, and whether it needs an account at all.
Why OxiSoft Apps Don't Track You
Privacy-first app development isn't a feature you add. It's an architecture choice that rules out entire categories of revenue, SDKs, and convenience.