Engineering & SDK deep-dives
How Pug is built: the SDKs, event delivery, and the design decisions behind them. For concept guides and benchmarks, see Learn.
Inside the Pug Web SDK
Autocapture, identity, consent, and reliable delivery: the developer story end to end.
ReadHow we deliver events reliably
Batching, a durable queue, sendBeacon on unload, and permanent-vs-transient retry classification.
ReadWell-known events: why standard names matter
How standard, typed event names keep your data clean, portable, and useful.
ReadProduct analytics for developers
SDKs, autocapture, a typed API, and self-hosting, analytics built for engineers.
ReadCookieless identity, built on a self-deleting salt
The HMAC construction, why deletion beats rotation, and the type that caught a silent bug.
ReadServer-side event tracking in Ruby and Rails
A track call that never blocks or raises, well-known events checked in-process, and batching that survives a fork.
ReadSend your first event.
Create a project, add the snippet, and watch the Live view fill up. Or open the demo first: the real dashboard on a sample pet shop, with no sign-up.
Questions? Email hello@pug.sh