Local-First Apps in 2026: The Case for Offline by Default
Every VisorCraft app works fully offline, with no account, no cloud, and no telemetry, and this is what that constraint actually buys you once the cloud is just one option among many.
Engineering
37 posts filed under engineering.
37
Posts
Sep 2026
Latest
Cross-Language Conformance: Testing One Schema in TypeScript, Rust, and Python
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.
Self-contained Rust workspaces: one repo per app, not one repo per crate
Grexa and Arte-Ogre each ship as one Cargo workspace holding every crate the app needs, and the layout decisions behind that, shared version metadata, single dependency pins, and path-dependency layering, are what keep a Rust desktop app maintainable as it grows.
The filesystem as a database: SQLite, IcefallDB, and grexa-db
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.
mTLS for a desktop monitoring tool (and why you shouldn't use a cloud)
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.
Postcard over a Unix socket: a tiny RPC for system monitoring
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.
Why our CLI does everything the GUI does
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.
Building a plugin host without recompiling the daemon
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.
cxx-qt: how a Qt codebase becomes a Rust codebase without rewriting
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.
Mongrel vs Quest Toad: Specialist Database Depth or One Systems Workbench
Comparing Quest Toad's specialist database editions against Mongrel's unified workbench for engineers managing multiple engines and surrounding systems.
Why We Picked Rust for Desktop Apps in 2026
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.
Mongrel vs Aqua Data Studio: Database IDE or Systems Workbench
Compare Aqua Data Studio's database IDE with Mongrel's broader systems workbench for databases, terminals, containers, Kubernetes, and APIs.
Mongrel vs the Multi-Tool Stack: DBeaver, Postman, Termius, and Lens
Compare Mongrel's unified workbench against a multi-tool stack of DBeaver, Postman, Termius, and Lens across workflows, safety, and operations.
Why We Picked Kirigami for Our Linux Desktop Apps
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.
Mongrel vs Lens Desktop: Kubernetes in the Full Investigation Context
Comparing Lens Desktop's Kubernetes focus against Mongrel's cross-system investigation workbench, including database context, safety controls, and integrated tooling.
Mongrel vs Postman: API Work Beside the Data and Infrastructure
Mongrel brings HTTP, GraphQL, WebSocket, and gRPC requests into a unified workbench alongside databases, terminals, containers, and file operations.
underskrift: PAdES B-LTA Signatures in Pure Rust
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.
Mongrel vs MobaXterm: Remote Sessions Meet Databases and Clusters
Mongrel consolidates SSH, databases, containers, and APIs in one cross-platform desktop workbench, contrasting with MobaXterm's Windows-focused remote-access breadth.
Mongrel vs Termius: The SSH Session or the Systems Behind It
Comparing Termius's cross-device session management with Mongrel's integrated desktop workbench for databases, APIs, and surrounding systems.
Mongrel vs SSMS, pgAdmin, Compass, Workbench, and Redis Insight
Five vendor tools cover five engines well, but polyglot stacks multiply windows, settings, and mental models. Mongrel brings 30+ engines into one workbench.
Mongrel vs Beekeeper Studio: SQL Client or Full Debugging Trail
Compare Beekeeper Studio's approachable SQL client with Mongrel's broader workbench for databases, terminals, containers, Kubernetes, APIs, and team connection workflows.
Mongrel vs DbVisualizer: Beyond the Universal JDBC Client
Mongrel and DbVisualizer both connect across database engines, but their architectures, safety models, and system coverage diverge significantly across operational workflows.
Mongrel vs TablePlus: A Focused Database Client or a Broader Workbench
Comparing Mongrel and TablePlus for database workflows, focusing on scope, safety controls, and when consolidation across databases, terminals, and APIs makes sense.
Mongrel vs Navicat Premium: From Database Suite to Systems Workbench
Comparing Navicat Premium's mature database suite against Mongrel's integrated systems workbench for developers managing databases and surrounding infrastructure.
Mongrel vs DataGrip: Database IDE or Database and Systems Workbench?
Compare DataGrip's database IDE depth with Mongrel's database, terminal, API, container, and Kubernetes workbench for cross-system investigations.
Mongrel vs DBeaver: When the Database Client Becomes the Whole Workbench
Comparing Mongrel and DBeaver: database clients, architecture tradeoffs, workflow depth, and when a full-stack workbench makes sense.
Inside Mongrel: Engineering One Workbench for Many Systems
How Mongrel unifies 30+ databases, terminals, APIs, containers, and Kubernetes while preserving engine semantics, safety, and platform limits.
A Database Client With SSH Tunneling Built In, and Why the Bastion Should Be a Dropdown
Every production database lives behind a bastion, and most database GUIs treat SSH tunnels as an afterthought, so here is how tunneling actually works, why the port-forward incantation rots, and what it looks like when the tunnel manager and the database client are the same app.
MongrelDB-PHP: A Modern PHP Client for a Rust Database
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: One Schema, Three Languages, One Rust Core
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: Sandboxing 200 Plugins with Landlock, seccomp, and bubblewrap
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: The Hot Path Has No Async Runtime
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: Time Travel on Plain Parquet Files
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: a database where joins are directories of symlinks
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: Why We Test Image Editors with Byte-Identical Round-Trips
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.
Eight New MongrelDB Clients, One Design Decision
Eight new pure-language HTTP clients shipped this week for MongrelDB. The total is now twelve. Here's the design call behind shipping them as HTTP, and what the C ABI means for the next wave.
Building in the Open: Why VisorCraft Maintains Multiple Open Source Projects
We keep dozens of public repositories under GPL-3.0, Apache-2.0, and MIT. Here is some of what we open source, and the one thing we don't.