English · Français
Newest first. Each month, a distilled look at where the work actually went — from Git history, broken down by subject. Kept separate from long-form articles. When public releases begin, versioned technical release notes will live on the changelog.
Security closed in volume, hygiene turned into lanes, and documentation consolidation began — with more of that review likely ahead.
A more useful admin console, a broad maintenance and upgrade wave, security fixes, and a steadier method.
Method and specification upfront, mobile ready for testers, public API portal, and steady dependency maintenance.
The Ezkey Android app is being submitted to Google Play as a technology preview for early adopters. The source code is currently kept private while we finalize hardening and documentation. The current plan is to open the repository publicly in September 2026, with the first official release, subject to the usual pre-release work.
The admin UI is about 90% complete. The mobile app is being rewritten, and the crypto APIs are under review. QA is getting more thorough and surfacing many issues to fix before a release. Progress is steady, and the product is starting to take shape.
Building an authentication system is challenging. Making it safe and reliable is harder. Ezkey will ship in phases; the first is due in the coming months. It will be a technology preview: it will show what the system can do, but it will not be production-ready. On the activity side: a web Admin UI began taking shape this month — initially scoped to tenant administration — alongside audit log integrity through HMAC-signed chains, admin deactivation, and a non-blocking authentication option. The construction had begun in earnest.
The admin console started as a text TUI — the chosen operator surface, not a web UI bet yet — alongside JDK 25 groundwork, Crypto API endpoints, and a pragmatic documentation consolidation.