Crypto in the core
The crypto behind Nitva and TerraCrypt exists once — in Rust — and iOS, Android and desktop call it through a C ABI. No four implementations drifting apart.
RustC ABISQLCipherpost-quantumProducts on my own hardware: a post-quantum messenger, a video platform, a fiscal POS for cafés, a media server, and the servers underneath them all. One person, several languages, no framework where the language is enough.
Every system, ordered by the year it started. Each row opens a page of its own: what it does, what it is built on, and where it stands today.
Four fields, one pair of hands. Under each sits the kind of work that actually ships, with the tools it is done in.
The crypto behind Nitva and TerraCrypt exists once — in Rust — and iOS, Android and desktop call it through a C ABI. No four implementations drifting apart.
RustC ABISQLCipherpost-quantumGo with no framework over PostgreSQL/PostGIS, SQLite where it is enough, my own nginx. Fiscal flows to ESIR and LPFR.
GoPostgreSQL/PostGISSQLitenginxiOS and Android natively, desktop through Tauri. One protocol, three clients, one source of truth.
SwiftSwiftUIKotlinTauriPHP 8.3 applications, static frontends and admin panels with metrics and logs — no heavy CMS.
PHP 8.3TypeScriptJavaScriptSQLCounted from the index, not from a pitch deck.
The rules that decide what gets written and what gets thrown away.
The crypto behind Nitva and TerraCrypt exists once, in Rust, and every client calls it through a C ABI. No four implementations drifting apart.
The servers are mine: Go, PostgreSQL/PostGIS, SQLite, CoTURN, MinIO, nginx. When something breaks I don't wait on someone else's status page.
SQLite on-device and per tenant where it's enough, PostGIS when geometry is involved, PostgreSQL when concurrency is. No database "just in case".
The iOS and Android apps are native (Swift, Kotlin, Compose), not web in a shell. Tauri where the desktop app should stay small, not Electron.
PQXDH and Double Ratchet in Nitva, SQLCipher in TerraCrypt, open_basedir tenant isolation, BLAKE3-hashed VPN credentials. All of it lives in code, not in copy.
Every system above follows the same five rules.
For work, a collaboration, or a question about any of the systems above.
Open to work, collaboration and hard problems.
github.com/fvaha