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.
Public alpha honesty on ezkey.online, Integrity for Global Admins, and a community people can try — without production or SLA claims.
Radical simplification of the written corpus, three scanner-driven security passes, strict least-privilege boundaries for machine credentials and encryption keys, and a layered test pyramid for mobile.
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.
In April, the Ezkey Android app was advancing toward a Google Play technology-preview path for early adopters. The source was still private then, with a plan (at that time) to open the repository publicly around September 2026 alongside a first official release, subject to pre-release work. That timeline reflection is historical — see the detail page for the April narrative.
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. At that time, Ezkey was expected to ship in phases, with a first technology preview due in the following months — showing what the system can do, but not production-ready. On the activity side: a web Admin UI began taking shape that 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.