Insights from the team. Mostly Gary.
On the morning of March 11th, node-04 (Brenda) accessed the ticket cabin through the door Gary had left ajar and consumed approximately 40% of the printed session confirmations for the month. This post covers root cause analysis, impact assessment, and the new door-latch protocol (close the door).
Read more →In Q4 2025 we made the decision to upgrade our perimeter access control unit from a Raspberry Pi 3B+ to a Raspberry Pi 4 (8GB). This post documents the migration, what went wrong, what went right, and why Gary should not be allowed to run firmware updates unsupervised.
For years, ElkScale described its organic nodes simply as "the elk." Following customer feedback that this lacked precision, we are proud to introduce our formal Antler-Class tiering system, ranging from 2-point Starter nodes all the way to the 12-point Enterprise configuration. (Gerald.)
Our analytics infrastructure runs on a single Google Sheet, manually updated by Gary every Friday afternoon. This post is a response to the seventeen customer emails asking us to "expose this via an API." The answer is no. The reasons are Gary's.
I've been asked to write a "thought leadership" piece by Callum. I don't know what that means. Here is what I know: elk do not follow instructions, they have variable uptime, and the one you trust most (Brenda) will occasionally eat your paperwork. I am told this maps onto microservices architecture somehow.
Get new posts delivered to your inbox. Engineering deep-dives, infrastructure retrospectives, and the occasional update on what Kevin has been doing in the treeline. Posted irregularly. Gary writes when he has something to say. Callum writes when Gary won't.
No tracking pixels. No growth loops. Gary will add your email to a spreadsheet and send you a message himself. The spreadsheet is not the same spreadsheet as the analytics one, but it is also a Google Sheet.