invisit vs Plausible

Which Plausible plan do you need: Starter, Growth or Business?

You need Plausible’s Business plan for funnels, revenue, custom properties or the Stats API. invisit includes all four on every plan, the free one too (revenue as totals and charts; the list of charges needs a paid plan). Plausible’s self-serve plans share the same pageview tiers and differ in features, sites and seats (Plausible’s pricing, as of November 2026):

Growth adds shared links, with an optional password, and embedded dashboards. Business adds user journeys and a consolidated view across sites. Past 10 sites or 10 members you need a custom Enterprise plan, which is also where SSO and a managed proxy live (plan guide).

Since invisit has one feature set on every paid plan, the fair comparison is Plausible Business. invisit also has a free plan, 20,000 events a month on 4 sites with no time limit; Plausible has no hosted free plan.

How much does Plausible cost at 300K page views a month?

A SaaS with 300K page views and 20K custom events a month pays $99 on Plausible Business and $49 on invisit. Plausible bills pageviews plus custom events across a team’s sites, and outbound link clicks, file downloads and form submissions count as custom events. 320K lands in Plausible’s 500K tier (Starter $49, Growth $74, Business $99) and in invisit’s 1M step at $49.

The price table above stops at 10K, 100K, 1M and 10M. The steps in between, on monthly billing:

invisit costs less than Plausible Business at every volume. Plausible Starter is cheaper from 2M up, if one site, one login and no funnels are enough, and Growth edges under invisit at 5M.

Neither charges overage fees. After two months in a row over your tier, Plausible asks you to upgrade and locks dashboards a week later if you have not, while it keeps collecting. invisit records the first month over in full, and in a second month over in a row pauses new events at the limit until you upgrade or the month turns. A year costs ten months’ price on Plausible and nine on invisit (invisit billing).

Plausible revenue tracking vs reading Stripe and Paddle directly

Plausible records revenue your own code sends, on its Business plan. invisit reads revenue from your payment provider on every plan, with no code in the checkout.

With Plausible’s revenue goals you send revenue: { amount, currency } with an event from your success page or the checkout’s success callback. Each purchase is credited to the source, campaign and landing page of that visit. Renewals, refunds, chargebacks and payments confirmed after the visitor leaves, such as SEPA debits, cannot be tied to a visit, so Plausible’s docs say not to send them and to expect lower revenue than your billing tool shows.

invisit connects to Stripe, Paddle, Polar, Lemon Squeezy, Creem or Dodo Payments and reads payments, refunds, disputes, fees and net, and charts them beside your traffic (connect a provider). If first-purchase revenue per campaign is the number you manage by, Plausible answers it directly. If you want what your account actually received, read it from the provider.

Does Plausible need a cookie banner? Privacy and EU hosting compared

Neither Plausible nor invisit sets cookies, so neither needs a consent banner for analytics. Both tell visitors apart with a hash that changes daily, and neither stores raw IP addresses.

Plausible’s data policy hashes a daily salt, the site domain, the IP address and the User-Agent, and deletes the salt every 24 hours. On top of its daily hash, invisit can honour Global Privacy Control and Do Not Track (respectGpc and respectDnt), strips sensitive URL parameters, redacts email addresses in values, and offers a consent mode for sites whose policy wants one.

Both keep analytics data at Hetzner in Falkenstein, Germany. Plausible is an Estonian company and only European-owned providers touch its visitor data: Hetzner, UpCloud (Finland) and Bunny (Slovenia) as its CDN (Plausible’s EU hosting). invisit runs DNS and CDN through Cloudflare, a US company. If your legal review requires EU ownership of every provider, Plausible meets it and invisit does not. Both offer a DPA (invisit’s).

What Plausible leaves out: heatmaps, visit timelines, web vitals and crawler reads

Plausible has no heatmaps, no per-visit view and no web vitals, and invisit has all three. Plausible’s when not to use Plausible page rules out heatmaps and individual session views by design: it keeps no user profiles and records no individual sessions.

Plausible offers automatic scroll depth instead, and on Business, user journeys: aggregate paths before or after a page or goal. invisit keeps each visit’s pages and events in order (live visits in the dashboard, any visit through the API and MCP), next to where it came from, click and scroll heatmaps over your real pages, and LCP, INP, CLS, FCP and TTFB from real visitors, never billed.

On AI, both see referrals. Plausible has an AI Assistants channel for ChatGPT, Claude, Perplexity, Gemini, Copilot and others, and filters AI crawlers out. invisit recognises 19 assistants by referrer and utm_source (AI assistant traffic), and @invisitdev/server also records crawler reads, including fetches like ChatGPT-User, unbilled.

Neither has session recordings or retention cohorts. invisit adds short links, an on-page feedback widget, and alerts for spikes, drops and silence to Slack, Discord, ntfy or a webhook, where Plausible sends spike and drop emails.

Can you self-host Plausible? Community Edition vs Plausible Cloud

Yes. Plausible Community Edition is free under AGPLv3 on your own server, while invisit cannot be self-hosted. invisit’s tracker and SDKs are MIT, but its dashboard and backend are proprietary.

Plausible’s own comparison lists the trade. Community Edition ships about twice a year (v3.2.1 in May 2026), leaves out funnels, user journeys, revenue goals, SSO and the Sites API, filters bots by User-Agent and referrer spam only, and has community support only. You own the server, backups and security updates. If you can run that and the core dashboard is enough, Community Edition costs you only the server.

When Plausible is the better choice

Plausible is the better choice when one of these is a requirement, not a preference.

• Self-hosting. Community Edition is the only way in this matchup to run analytics on your own servers.
• EU ownership end to end. Every provider that touches Plausible’s visitor data is European-owned, CDN included; invisit sits behind Cloudflare.
• The lightest tracker. Plausible’s script is about 2.5 KB gzipped; invisit’s core invisit.js is about 8.5 KB, with heatmap and feedback modules loading only when used.
• Search Console queries, clicks and positions inside the dashboard. invisit has no Search Console integration.
• Weekly or monthly email reports, also to Slack. invisit has no scheduled email reports; a public dashboard or the MCP server come closest.
• Your Google Analytics history. Plausible imports GA4 properties and CSV files. invisit cannot import history.
• One site at high volume with core stats only: Plausible Starter is $89 at 2M and $169 at 10M, against $99 and $199 on invisit.

Switching from Plausible to invisit

Run both trackers side by side, move your events, connect your payment provider, then remove Plausible.

1. Install invisit next to the Plausible snippet, or add @invisitdev/web to your bundle (frameworks).
2. Replace each plausible() call, or track() from @plausible-analytics/tracker, with invisit’s track(). Properties lose the props wrapper, and names use letters, digits and _ . : -, so Sign Up becomes sign_up.
3. Drop the revenue option and connect your payment provider.
4. If you proxy Plausible, use @invisitdev/server to serve invisit from your domain.
5. Compare both dashboards for two to four weeks, then remove the Plausible snippet.

// Before: Plausible (script tag, or track() from @plausible-analytics/tracker)
plausible('Sign Up', { props: { plan: 'pro' } })
plausible('Purchase', { revenue: { amount: 49, currency: 'USD' } })

// After: invisit
import { identify, init, track } from '@invisitdev/web'

init({ site: '<site id>' })
track('sign_up', { plan: 'pro' })
identify(user.id)
// No purchase call: invisit reads payments from Stripe, Paddle or Polar

invisit cannot import your Plausible history, so export it first. In Plausible’s site settings, Imports & Exports, Export to CSV queues a ZIP and emails you the link: one CSV per report, a row per day for each page and source (export guide). It works after a trial or subscription ends, until Plausible deletes the stats, but leaves out data you imported from Google Analytics.

Expect small gaps between the two while both run: they filter bots differently and define a visit their own way.