Plausible?

YESA focused first version is a sensible AI-assisted build. Keep the first release narrow and polish the workflow people repeat.

BUILD FIRST

One defined user and a repeatable end-to-end job
A small, clear data model with sign-in only if it is genuinely needed
Loading, empty, error, and success states that make the workflow feel complete

LEAVE FOR LATER

Large integration marketplaces
Multi-region scale and enterprise administration
Every power-user setting from the established product

RESEARCH NOTES

What this tool actually does.

Checked 2026-09-06

Plausible is privacy-focused web analytics that reports aggregate page views, unique visitors, referral sources, top pages, countries, devices, and browsers without cookies or persistent identifiers. Its docs also describe per-site settings, goals, custom events, reports, shared links, and access control.

SOURCES

RESEARCHED BUILD PROMPT

Give this to your coding agent.

Build a privacy-first web analytics service for one small website. Do not copy Plausible's brand, proprietary assets, or UI.

Core workflow
- Provide a lightweight tracking script and a server endpoint that records only aggregate page-view data: site, day, path without sensitive query parameters, referrer domain, coarse device/browser/OS, and broad country when available.
- Do not use cookies, persistent visitor IDs, cross-site identity, ad profiles, or raw IP storage. Document the unique-visitor approximation and make data retention/deletion explicit.
- Build a compact dashboard with date filters, page views, unique-visitor estimate, top pages, referrers, countries, devices, and browsers. Add named custom events and goals with a simple integration snippet and show conversion counts.
- Add per-site timezone, traffic exclusions, retention, a read-only shared dashboard link, and a data-export/delete action. Use synthetic data for local demos.

Implementation and scope
- Use a small ingestion API, daily aggregate tables, and a React dashboard. Protect ingestion from abuse with rate limits and reject malformed or oversized payloads.
- Out of scope: session replay, individual visitor timelines, cross-site attribution, advertising audiences, demographic inference, real-time guarantees, multi-region enterprise infrastructure, and legal/compliance certification.
- Prefer a single deployable region and make the privacy model inspectable in the README.

Include a README with setup, script installation, event format, aggregation logic, retention/privacy choices, and important limitations.

Visit the official product page