Engineering Log
Technical deep dives, architectural decisions, and post-mortems from the Ziloris core team.
How Reliable detects broken WebSockets without collecting a single payload
WebSockets have no status codes, and their messages are too private to store. This is how we built anomaly detection from message shapes, 64-bit hashes, mergeable sketches and a scoring rule, including the mistakes that kept it blind for a month.
Exact where we can, sketched where we must: how Reliable computes percentiles
Reliable computes web vitals percentiles exactly from raw rows, and WebSocket percentiles from mergeable sketches. This is why the two differ, the math behind p75, and the rules that keep trend charts honest: never average a percentile, and never draw a missing value as zero.
Averages hide outliers, maxima cry wolf: how Reliable combines anomaly scores
A reply that got ten times slower scored 4.1 on its own and 1.3 once we averaged it with its healthy neighbours. This is the math of turning many anomaly scores into one decision, and the rule we picked.
Making delete reversible: soft deletes, purge ordering and the keys we never reuse
Deleting a project in Reliable used to cascade through every table instantly and strand files in object storage. Here is how we made it reversible for 30 days, why one flag on one row is enough, and the ordering rule that keeps the purge crash-safe.
How Reliable wakes an engineer at 3 a.m., and why the alarm can always be stopped
A pager has two jobs that pull in opposite directions: be impossible to miss, and stop the moment you ask. This is the path a page takes from an error to a ringing phone, the trap that made our alarm unstoppable, and the layers that fixed it.
Sunsetting Straincraft: A Post-Mortem
Why we decided to halt development on our browser-based molecular renderer.
JOIN THE
ENGINEERS.
Ziloris is not a company. It is a shared mission. We need developers, mathematicians, and architects who believe in the commons.