Blog
Practical posts from the Blackglass team — about drift detection, security tool design, and the small decisions behind a product that’s deliberately calmer than the category norm. New posts when there’s something worth saying, not on a content calendar.
How we document maximum lag between a host scan and the dashboard, why auditors care, and what happens when push agents miss a heartbeat — without pretending we're real-time where we aren't.
A practical note on RLS as the last line of defence, why every bypass is greppable with // RLS-BYPASS:<reason>, and what we don't pretend RLS solves (compromised superuser credentials still win).
The design rules that keep cloud janitor features from deleting the wrong snapshot: read-only default, tag-based protect lists, idle-score floors, and versioned webhook envelopes.
What it actually takes to ship credible structured data, dynamic OG images, and a sitemap that respects per-page freshness — for an engineering audience that distrusts marketing.
The product reasoning behind Charon — a paid add-on that scans cloud accounts for waste — and why it's the right shape for a tool that's primarily about server-side configuration drift.
New to the vocabulary? See the glossary. Subscribe to the changelog RSS feed — a dedicated /blog RSS will follow once we're past a handful of posts.