> ## Content Index
> Fetch the complete content index at: https://www.stirup.si/llms.txt
> Use this file to discover other available public pages before exploring further.

# Pug.sh Analytics Platform Overview and Features
- URL: https://www.stirup.si/pug-sh-analytics-platform-overview-and-features-488a3751/
- Published: 2026-11-20T16:17:08.000Z
- Updated: 2026-11-20T16:17:08.000Z
- Description: Pug.sh provides an open-source analytics platform that automatically generates insights from user events, offering metrics like visitors, sessions, and traffic sources without manual setup.
- Author: Satish Das
- Tags: Community, News, Stirup Research

## Overview of Pug.sh's Analytics Features

Pug.sh offers an open-source product analytics platform that automatically generates insights from user events. The **Overview** section provides a web-analytics view that includes metrics such as visitors, sessions, pageviews, bounce rate, and traffic sources, all derived directly from your event data without requiring manual setup. This feature is highlighted in [Hacker News Show](https://github.com/pug-sh/pug?ref=stirup.si), which describes how the analytics dashboard is auto-built from events. Additionally, [Hacker News Show](https://github.com/pug-sh/pug?ref=stirup.si) notes that the Overview section includes a comparison with the previous period, enabling users to track changes over time. The **Insights** section allows for deeper exploration through trends, filters, and breakdowns, such as splitting product views by country, as described in [Hacker News Show](https://github.com/pug-sh/pug?ref=stirup.si). These features are designed to help developers and product teams understand user behavior with minimal configuration.

## Model Context Protocol (MCP) Server and Integration

Pug.sh introduces a Model Context Protocol (MCP) server, enabling AI assistants to query analytics data directly. This server operates locally, typically accessible via `http://localhost:3000/mcp`, and allows integration with tools like Claude through its connectors directory. A self-hosted setup requires configuring the `PUG_API_BASE_URL` environment variable to enable sign-in functionality. This approach emphasizes control and privacy by keeping data on-premises while still allowing AI systems to interact with analytics in real time. The MCP server is open-source, aligning with Pug.sh's commitment to transparency and customization. Users can deploy the server independently, ensuring that their analytics remain secure and accessible only to authorized systems. Integration details are outlined in the project's documentation, providing developers with the necessary tools to connect AI models with their analytics infrastructure.

## Technical Stack and Infrastructure

Pug.sh is built on a robust technical stack designed for scalability and performance. The backend services and workers are implemented in **Go** and communicate over **Connect RPC** (HTTP/2). For data storage, **PostgreSQL** serves as the relational database, managing entities such as organizations, projects, dashboards, and authentication. **ClickHouse** is used for analytical storage, handling events, insights, and user profiles. **NATS** acts as the messaging backbone, facilitating communication between ingestion pipelines and workers. The platform supports self-hosting, with detailed instructions available in the self-hosting guide. For demonstration purposes, the `./bin/pug seed` command populates a "Pug & Pals" demo project with approximately six months of historical data, ensuring that dashboards, insights, and profiles display meaningful content. Profiles are only seeded for users who have generated events, maintaining internal data consistency as noted in the project's documentation.

## Self-Hosting and Demo Data Configuration

Pug.sh allows users to self-host its open-source product analytics platform, offering flexibility in deployment and data management. The system includes configurable demo data, which can be adjusted using command-line parameters such as `--count` (default 500,000 events) and `--batch` (default 10,000 events per insert), as noted in the source. For demo purposes, two read-only accounts are pre-seeded: `woof@pug.sh` has ownership of the demo organization and its data, while `snoop@pug.sh` is a viewer with no password. To access the demo, users must set the environment variable `PUG_DEMO_ENABLED=true` and navigate to the `/demo` endpoint. These configurations are specific to the demo setup and do not apply to production environments.

## Development and Licensing Details

Pug.sh is developed as an open-source product analytics tool, with its source code available for inspection and modification. The project is licensed under the GNU AGPL v3.0, or any later version, granting users the freedom to use, modify, and distribute the software while ensuring that any modifications made to the code are also shared with the community.

The demo organization, admin@pug.example, is seeded with an admin account only when the `PUG_DEMO_ADMIN_PASSWORD` environment variable is set. This password must be between 16 characters and 72 bytes, with no surrounding whitespace. It is important to note that the password is not logged, and subsequent runs of the application will not alter it. Users are advised to change the password in the dashboard to a value of 16 characters or more and update the variable accordingly, as the seeder only restores the admin's role when the password matches.

## Sources and reporting notes

- [Hacker News Show](https://github.com/pug-sh/pug?ref=stirup.si)

Based on published source material. No independent hands-on testing is claimed.