Blog
Notes from the build.
Engineering and product notes on building activity logging infrastructure — written by the founders, as it happens.
How to add an audit log to your SaaS in 30 minutes
A copy-paste tutorial: instrument eight security-relevant events in a Node backend, mint a feed token, and ship a customer-facing audit page — before your coffee goes cold.
Read post →Audit log vs activity feed vs analytics: which one do you need?
Three features that look identical in a database and serve completely different masters. How to tell which one your customers are actually asking for — and why analytics tools make bad audit logs.
Read post →Build vs buy: audit logs for B2B SaaS
What an audit log API actually costs to build in-house — the schema, the ingest path, the read path, the retention job — and when buying is the smarter call.
Read post →Designing an activity event schema (actor / action / target)
The event schema behind every good activity feed: naming rules, denormalization decisions, and the anti-patterns that quietly ruin your audit trail.
Read post →What a customer-facing audit trail needs before SOC 2
Completeness, immutability, retention, scoped access, export — the concrete requirements, with code instead of compliance-speak.
Read post →Why every SaaS ends up rebuilding the same activity log
Event tables, ad-hoc schemas, brittle timelines — we kept building the same infrastructure at every company. Here is why we decided to build it once, properly, for everyone.
Read post →