Peeko vs Plausible, compared from each tool's own docs and pricing

You are probably here because both tools say the same thing in their first line: privacy friendly analytics, no cookie banner, one script. That is true of both, and it is not a reason to pick either. This post compares the parts that differ, using Plausible's own documentation and pricing for its side and Peeko's product facts for ours. We did not run both tools on one site, so there is no benchmark here and no claim about which one counts a given visit differently.

What the two tools share

Plausible's data policy says "We do not use cookies, browser cache or local storage" and that you do not need a cookie banner for analytics (Plausible data policy). Peeko is one script tag with a site key, sets no cookie, and needs no configuration once it is on the page.

Neither tool stores an IP address. Plausible says raw IP addresses and user agent data are never stored, and that its daily identifier is a hash of a daily salt, the site domain, the IP address and the user agent. The salt is rotated and deleted every 24 hours. Peeko never writes the address to a database or a log either, and the visitor is the first part of a one way keyed hash of address and browser string.

The differences start with what each tool does after that.

Pricing, as of October 2026

Plausible's pricing page lists three self serve plans at its 10,000 pageview tier: Starter at $9 a month, Growth at $14 and Business at $19, plus a custom Enterprise plan (Plausible pricing). Starter covers one site. Growth covers 3 sites and 3 team members. Business covers 10 sites and 10 team members.

The plan decides features, not volume. Plausible's plan documentation says all plans start at the same pageview tiers and "The difference is features and team size" (Plausible plans). Funnels, user journeys, ecommerce revenue, custom properties, the Stats API and the Data Studio connector sit on Business. The Sites API, SSO, managed proxy and raw data exports sit on Enterprise.

Source: Plausible, Plausible Analytics pricing, Oct 2026. Retrieved Oct 12, 2026.

The chart shows only the 10,000 pageview tier. The higher tiers are set by a slider on Plausible's page, and we could not read those prices from the page text, so check the slider for your own volume before comparing.

Peeko has one plan on a slider from 100,000 to 10,000,000 events a month, from 9 to 199 dollars monthly, with yearly billing at two months free (Peeko pricing). Every feature is on every size, with unlimited sites and unlimited team seats. The smallest Peeko step is 100,000 events, ten times Plausible's smallest listed tier, at the same $9 as Plausible Starter. That does not make Peeko cheaper: we have no Plausible price at 100,000 to set beside it.

What counts toward the bill is similar in shape. Plausible bases a tier on pageviews and custom events across all sites in a team, and custom events include outbound link clicks, file downloads and form submissions. Peeko counts a page view, an outbound click or a custom event over the UTC calendar month. AI crawler hits are never billed on Peeko.

Both tools are gentle about going over. Plausible's billing FAQ says "An occasional traffic spike won't trigger extra charges or stop your stats from being counted" (Plausible billing). Its documented limit: after two consecutive months over your tier it asks for an upgrade, and dashboards lock if you do not upgrade within a week, while collection continues. On Peeko, nothing stops recording when you pass your limit.

Trials differ. Plausible offers 30 days with no credit card, with access to Business plan features during the trial. Peeko's trial is fourteen days with no card, starts when you create your account, and covers one site.

How each tool tells one visitor from another

This is the real design difference, and it cuts both ways.

Plausible's identifier is built from a salt that is deleted every 24 hours, so by its own description it prevents cross-day tracking. A visitor on Monday and the same person on Tuesday are two unrelated records.

Peeko uses the same idea for the number it calls People: the hash mixes in the date and is re salted every day, so nobody can be followed from one day to the next. Peeko then keeps a second hash without the date. That second hash is what tells a returning visitor from a new one, strings a person's page views into a journey, and carries goals, funnels and revenue. It is still a hash, still no cookie, and still no stored address.

So the trade is plain. If your rule is that no analytics tool should be able to recognize the same browser on two different days, Plausible's design is the stricter one and Peeko's is not. If you want a funnel that follows a person across a 7 or 30 day window, you need an identity that lasts longer than a day, and Peeko built one for that purpose.

AI crawlers and AI referrals

Plausible's bot filtering is built to keep bots out of your numbers. Its documentation says it blocks known bots and crawlers by user agent, filters referrer spam, filters traffic from known data center IP ranges and uses its own algorithm for unnatural patterns (Plausible bot filtering). For a tool that reports human traffic, that is the right behavior. The page we read does not describe AI crawler reporting or a way to view the filtered hits, and it says new bots appear faster than filters catch them.

Peeko treats the same traffic as data. Crawlers do not run JavaScript, so tracking them is a separate server side path: the @usepeeko/bot-track middleware is ESM only, needs Node 20 or newer, has zero runtime dependencies and weighs under 3 KB gzipped. Peeko matches a user agent against a curated list of 55 agents from 21 companies and files each recognized hit under AI answers, Search indexing, AI training or Other AI bots. No address and no visitor hash exist on that path, and the raw user agent is kept up to 512 characters so old hits can be reclassified as the list grows. We wrote up what that looked like on a new domain in AI crawlers on a new site, the first 30 days.

Visits that arrive from ChatGPT, Claude, Perplexity, Copilot and Gemini are counted from ordinary page views by their referrer, with no middleware. The method is in how to count visits from AI assistants by referrer, and the step after it, tying a visit to a signup, is in following an AI referral to a signup without cookies. One limit applies to every tool: an answer fetch says a page was read while an assistant was replying to somebody, and the question itself never reaches your server, so nobody can report it.

Goals, funnels and revenue

Plausible's funnels, user journeys and ecommerce revenue are Business plan features on the cloud service, and its documentation index lists custom properties for attaching metadata to events.

On Peeko a goal is a definition rather than a counter, so a goal written today counts over months before it was written, and a site can hold twenty. Five kinds of click are recorded with no code at all: outbound, phone, email, whatsapp and form. Anything else is a data-peeko-event attribute or a window.peeko.event call:

<button data-peeko-event="pricing-cta">See pricing</button>
<script>window.peeko.event("signup", "newsletter")</script>

A funnel holds two to five steps, a completion window of 1 hour, 1 day, 7 days or 30 days, covers at most 90 days and follows a person rather than a visit. A site can hold ten. Revenue arrives either through a one line window.peeko.revenue call or a verified Stripe webhook, and the two totals are never added together. Peeko never holds a Stripe API key, only the webhook signing secret. Cookie free attribution works through a page token minted per page view and good for 48 hours, passed into Checkout as metadata.

Note the limit in that custom event call: one name and one optional string, with no properties object. If you need to attach several properties to an event, that is a point for Plausible.

Getting data out, and getting an agent in

Plausible's export docs describe CSV downloads, with dashboard CSV files limited to 300 entries each and page reports to 100, and an "Export all stats to date" option in site settings. The Stats API is a Business feature at 600 requests per hour, and raw event exports are Enterprise (Plausible export, pricing).

Peeko hosts an MCP server at usepeeko.com/api/mcp. It is read only except for one tool that creates a site, it is reached with a bearer API key, and it is scoped to the sites of the teams you belong to. The command line needs no install and speaks the same endpoint an agent does, so a command and a tool call return the same numbers:

npx @usepeeko/cli

Peeko also connects Google Search Console and Bing Webmaster Tools read only, with encrypted tokens, and keeps their rows for sixteen months. Page views, events and crawler hits are kept three years by default, and the site owner can set that anywhere from 30 days to ten years. A share link is a page with no sign in behind a 32 character token, up to ten per site, served noindex, and it never shows goals, funnels, individual visitors or the AI crawler tab.

Where Plausible is the better choice

Pick Plausible in these cases:

• You want to self host. Plausible Community Edition is free, AGPLv3 and runs on your own server (Plausible self hosting). Peeko is a hosted service. Know the cost: Plausible says the work it does for cloud customers becomes yours, CE is a release published twice a year, and funnels, user journeys, ecommerce revenue goals, SSO and the Sites API are cloud only.
• You never want a visitor recognized across days. Plausible's single daily identifier is the stricter design, as covered above.
• You need a Stats API with a long track record, a Data Studio connector or custom properties. Plausible documents all three, and Peeko's event has no properties object.
• You want a longer trial. 30 days against fourteen, with Business features unlocked during it.
• You are moving from Google Analytics. Plausible's documentation lists importing from Google Analytics and importing stats from CSV. Check that page before you switch.
• You want a single tool for humans only. If AI crawler hits are noise to you, Plausible's job of keeping bots out is the whole point.

Where Peeko is the better fit

Pick Peeko if you want to see which AI crawlers read your pages without running anything but a small middleware, if you want funnels and revenue without moving up a plan, or if your analytics reader is increasingly an agent. A related case: you need to know which crawler belongs to which company without keeping an address, which naming the operator of an AI agent without IP addresses covers.

How to decide in ten minutes

1. Write down your monthly pageviews and custom events, then read both pricing pages at that volume.
2. Decide whether a visitor may be recognized across days. If not, Plausible. If you need multi day funnels, Peeko.
3. Decide whether AI crawler traffic is something you want to see. If yes, Peeko.
4. Decide whether you will run your own server. If yes, Plausible Community Edition.
5. Start both trials. Plausible's runs 30 days and Peeko's fourteen, and neither asks for a card.

Both tools are small, both skip cookies, and either one is a sound way off Google Analytics. The deciding questions are what you want counted and who you want reading it.