Blog

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.

Read

How we deliver events reliably

Batching, a durable queue, sendBeacon on unload, and permanent-vs-transient retry classification.

Read

Well-known events: why standard names matter

How standard, typed event names keep your data clean, portable, and useful.

Read

Product analytics for developers

SDKs, autocapture, a typed API, and self-hosting, analytics built for engineers.

Read

Cookieless identity, built on a self-deleting salt

The HMAC construction, why deletion beats rotation, and the type that caught a silent bug.

Read

Server-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.

Read

Browse the Learn library See the SDKs

Build on open analytics

Pug ships Web, Flutter, Node, and Ruby SDKs over a typed, reliable pipeline. Self-host under AGPL-3.0, or use Pug Cloud, free up to 100k events a month.

Start free

Questions? Email hello@pug.sh