Updates, technical deep dives, and thinking from the Inkury team.
Every cloud editor we used had the same failure mode: your work is at the mercy of a network round-trip. This is the engineering decision tree that put the document on your device first and the server second — and why that order matters more than it sounds.
Inkury computes a Blake3 content hash on every save and verifies it on every load. The mechanic is simple; the consequences are not. A short tour through invariant INV-13 and the bug it has caught for us in production.
How the admin panel’s permissions model evolved from "admin can do anything" to a 6-role, permission-driven matrix with both server-side enforcement and client-side gating — and the audit lock that keeps it from drifting.
Want every release as it ships? Read the changelog.