Where Pug is headed. This is a directional view — the shape of what we’re building next, not a dated commitment. Everything under Available today is shipped and documented; the rest is planned and lands here as it ships.
Our first priority is a rock-solid analytics core — events, profiles, insights, and dashboards you can trust. The bigger bets below build outward from that foundation.
Available today
Pug is a product analytics platform — capture events, identify the people behind them, and explore behavior through trends, funnels, retention, and segmentation, all on customizable dashboards. Client and server SDKs, plus a language-agnostic HTTP API:
| Platform | Package | Docs |
|---|---|---|
| Web | @pug-sh/browser |
Web SDK |
| Flutter | pug_flutter |
Flutter SDK |
| Node.js (server) | @pug-sh/node |
Node SDK |
| HTTP API | — | API reference |
You can also self-host the entire stack today, and capture is cookieless by default — no device identifier is stored until the reader consents.
Privacy & compliance
Pug is privacy-first by design — tracking-consent gating, no visitor-IP persistence, and GDPR/DPDP data-subject erasure are already in the product.
Cookieless capture has shipped, and it’s the default. The Web SDK’s
trackingConsent starts at 'cookieless': events flow from the first hit, but
nothing is written to the device until the reader answers your banner. Global
Privacy Control (respectGpc) and a bounded identifier lifetime (maxAgeDays,
default 365) landed alongside it. See
Tracking consent.
One area takes it further.
DPDP hardening
Deeper compliance controls for India’s Digital Personal Data Protection Act — consent records and withdrawal, data-principal rights (access, correction, grievance redressal), retention limits, and breach notification — building on the GDPR/DPDP data-subject erasure, export, and retention the compliance worker already runs.
More SDKs
Native and server-side libraries are in active development, built on the same event and identity model as today’s SDKs. Until each lands, the HTTP API works from any language or runtime.
Client SDKs
| Platform | What |
|---|---|
| Android | Native Kotlin SDK with provider-neutral push |
| iOS | Native Swift SDK for tracking and push |
| React Native | Cross-platform tracking for React Native apps |
Server SDKs
Idiomatic server-side libraries that send events and read analytics with your private key, the way the Node SDK does today. Go, Rust, Java, Python, and Ruby are in progress.
Customer engagement
Once the analytics core is stable, the next chapter is acting on your data, not just measuring it. Run multi-channel campaigns composed from the same profiles and events you already track — one composer, delivered to the channels your users are on.
Planned delivery channels:
| Group | Channels |
|---|---|
| Push | Web Push · Android Push · iOS Push |
| Messaging | Email · SMS · WhatsApp |
| Programmatic | Webhook |
The foundations are already shipping inside the analytics SDKs — so when the campaign composer lands, your events and devices are already wired up:
Shape the roadmap
Building something and need a platform sooner, or want a feature that isn’t here? Tell us — it genuinely moves priorities:
- GitHub — open or upvote a discussion at github.com/pug-sh/pug.
- Discord — join the community.
- Reddit — r/pug_sh.