18 posts filed under engineering.
MongrelDB Kit's three language surfaces are pinned to the same JSON fixtures, so the same query produces the same row or the same typed error in TypeScript, Rust, and Python, and this is how we keep three SDKs honest without writing the same test three times.
Three VisorCraft projects store their data as plain files in three different ways, and the reasons line up with three different access patterns, which is the actual decision framework for when the filesystem is the right database.
LinSight's remote monitoring path is an mTLS byte pipe between two processes you control, with no relay server and no account, and the honest answer is that most people should still use ssh -L instead.
LinSight's daemon serves its GUI and CLI over a postcard-framed Unix socket instead of HTTP, and the reason is that a monitoring hot path has no business parsing headers when it could be moving a number every 50 milliseconds.
Every VisorCraft app ships a CLI that exposes the full GUI feature set with stable exit codes and JSON output, and the reason is that GUI-driven testing is where CI budgets go to die.
LinSight loads metric sources as runtime .so plugins behind a stabby FFI vtable and an explicit ABI version, and the interesting part is the set of choices that keep the host alive across releases.
LinSight and LinSync write their QObjects in Rust and their UI in QML, glued by cxx-qt, and the interesting part is why the migration boundary sits exactly there.
Eight of our desktop apps and libraries are Rust now, and the reasons have less to do with the language's reputation than with what quietly matured between 2020 and today, plus an honest list of where it still hurts.
Three of our Linux desktop apps run the same Qt 6 / Kirigami QML interface on KDE Plasma, GNOME, and XFCE without a fork in the codebase, and the interesting part is why that stopped being a gamble.
underskrift signs and verifies PDFs at every PAdES level from B-B through B-LTA in pure Rust, and the hard part was PDF archaeology and conformance testing, not the cryptography.
How Mongrel unifies 30+ databases, terminals, APIs, containers, and Kubernetes while preserving engine semantics, safety, and platform limits.
MongrelDB-PHP is a pure-language HTTP client that targets PHP 8.5, uses no C extension, and leans on property hooks, readonly classes, and the pipe operator, because writing modern PHP in 2026 is genuinely pleasant and nobody is forcing it.
MongrelDB-Kit gives TypeScript, Rust, and Python the same schema-aware query builder, migrations, and constraint enforcement from one Rust core, and the interesting part is why one shared core beats three independent ORMs that slowly drift.
LinSync runs third-party document and image extractors inside a layered Landlock, seccomp, and bubblewrap sandbox so a compromised plugin cannot compromise the host.
LinSight is a system monitoring daemon that samples metrics on demand over a postcard-framed Unix socket, with a fully synchronous hot path, no Tokio, and no executor, and the absence of an async runtime is the design rather than the oversight.
IcefallDB stores tables as plain Parquet with JSON metadata and runs DataFusion on top, adding row-level mutations and warm aggregate caches to a file format that was never designed to support either.
grexa-db stores records as files and relational joins as directories of symlinks, turning every file-reading CLI into a database client without anyone knowing a database exists.
Arte Ogre's cut-and-paste correctness is pinned by a byte-identical round-trip test in CI. Here's why we test the data-model invariant and not the user-visible result.
