Seentics

---

Most teams pay for a traffic tool, a replay and heatmap tool, a popup tool and a conversion tracking tool, and send visitor data to all of them. Seentics does all of that in one place, on your own servers: see what visitors do, capture them before they leave, and send every conversion to your ad platforms.

Features

Understand visitors

• Real-time analytics: live visitor map, active pages, traffic as it happens
• Session replays: full recordings, grouped by what needs a look: errors, rage clicks, dead clicks, abandoned forms and U-turns
• Heatmaps: click maps, scroll depth, captured page screenshots, AI findings per page
• Funnels and paths: multi-step conversion analysis with drop-off rates, and the routes visitors take
• Revenue: orders, AOV, ARPU, UTM channel attribution
• Events and goals: page, event or CSS-selector conversions
• Error tracking: JavaScript errors grouped by fingerprint, each linked to the replay where it happened

Capture and convert

• Behavioral automations: popups, forms, spin-to-win wheels, banners, webhooks and redirects triggered by behavior
• Leads: every form submission in one place, and the contacts behind them, with status, tags and notes; view them as a list, a table or a pipeline board; import and export CSV
• Integrations: send leads to Zapier, any webhook, Mailchimp, Klaviyo and HubSpot, with automatic retries and credentials encrypted at rest
• Server-side conversions: purchases, leads and sign-ups sent to Meta, Google Analytics 4, TikTok and LinkedIn from your server, matched and deduplicated, for consenting visitors only

AI

• Seentics AI: ask questions in plain English and get charts back (⌘K)
• AI reports: unusual activity, daily insights and what to fix next, with the measured results of changes you made
• MCP server: connect Claude, Cursor, VS Code or any MCP client to your data with a read-only API key

For developers and agencies

• API and API keys: read your data from your own tools, with scoped keys
• Install anywhere: a script tag, Google Tag Manager, a WordPress plugin, Shopify and WooCommerce, or served from your own domain through a proxy
• Embeddable charts: @seentics/ui React blocks for putting Seentics charts in your own app
• Agency workspace: run every client site from one workspace, with clients, install checks, white-label branding and embed links

How it compares

	Seentics	Plausible CE	Umami	PostHog (self-hosted)	Hotjar
Open source	✅ AGPL-3.0	✅ AGPL-3.0	✅ MIT	✅ MIT	❌
Self-hosting	✅ Supported	✅	✅	⚠️ Hobby deploy, officially unsupported	❌
Minimum infrastructure	PostgreSQL + S3	PostgreSQL + ClickHouse	PostgreSQL	4 vCPU / 16 GB RAM VM	—
Cookie-free by default	✅	✅	✅	❌	❌
Traffic analytics	✅	✅	✅	✅	❌
Session replay	✅	❌	✅	✅	✅
Heatmaps	✅	❌	✅	✅	✅
Funnels	✅	Cloud only	✅	✅	✅
Revenue tracking	✅	Cloud only	✅	✅	❌
On-site popups and forms	✅	❌	❌	Surveys only	Surveys only
Ask questions in plain English	✅	❌

Compiled in October 2026 from each product's public docs. These products change fast, so if a cell is wrong, open an issue and we will fix it.

Quick Start

git clone https://github.com/Seentics/seentics.git
cd seentics
docker compose up -d --build

Brings up PostgreSQL, objex (S3-compatible storage), the API on :8001 and the dashboard on :4000. Create a website in the dashboard, then add the tracking script below.

For production, see DEPLOYMENT.md.

Tracking

To test real tracking across the full OSS stack, see Session recording E2E or Heatmap E2E. From web/, run npm run test:e2e:recording or npm run test:e2e:heatmap; each creates an isolated test stack and removes its disposable data afterward.

Add to your <head>:

<script
  defer
  src="https://your-seentics-domain.com/trackers/seentics.js"
  data-website-id="YOUR_WEBSITE_ID"
></script>

Pageviews, scroll depth, exit intent and rage clicks are captured automatically. YOUR_WEBSITE_ID is the id shown on your website's settings page.

JavaScript API

// Custom event, with optional properties
seentics.track('signup_click');
seentics.track('purchase', { value: 49.99, currency: 'USD', order_id: 'ORD-1234' });

// Identify a visitor. Note the argument order: id first, then traits.
seentics.identify('user_123', { email: '[email protected]', plan: 'pro' });

seentics.page();   // manual pageview, if auto-tracking is off
seentics.flush();  // send queued events immediately

Revenue reporting keys off value and currency on any event; goals are configured in the dashboard rather than in code.

Project Layout

seentics/
├── core/            Bun + Hono API — a modular monolith
│   ├── app/         Composition root, where the graph is wired
│   ├── modules/     Domain modules, one table each
│   ├── platform/    Cross-cutting; owns no table
│   └── db/          Drizzle schema and migrations
├── web/             Next.js dashboard, plus public/trackers/seentics.js
└── ui/blocks/       @seentics/ui — embeddable React blocks (MIT)

Modules talk to each other through explicit interfaces, injected at startup; there is no event bus. Read core/ARCHITECTURE.md before changing core/ — it covers the module boundaries, why the event bus and outbox were removed, and the known gaps.

Architecture

Browser ──┬─ tracker ──▶ POST /api/v1/tracker/collect ─┐
          └─ dashboard ─▶ Next.js :4000 ───────────────┤
                                                        ▼
                                              Bun API :8001
                                                 │        │
                                          PostgreSQL   S3 / objex
                                        (events, meta) (replays, heatmaps)

Tracker events are buffered in memory and flushed in batches, so /collect returns without waiting on the database. Replay chunks and heatmap screenshots go to S3-compatible storage.

Layer	Stack
API	Bun · Hono · Drizzle ORM
Dashboard	Next.js 15 · Tailwind · shadcn/ui
Data	PostgreSQL 16 · S3-compatible object storage
Replays	rrweb

Contributing

cd core
bun install
bun run check   # typecheck — expected to be clean
bun test        # ~630 tests, no database or S3 required
bun run dev

CI runs check and test on every pull request, and both are expected to pass. Tests use in-memory doubles of the module interfaces, so no services are needed.

Two things worth knowing before you write tests: mock.module is process-global in Bun, so an incomplete stub becomes the real module for every later test file — make stubs complete. And core/ARCHITECTURE.md lists the current known gaps if you are looking for something to pick up.

See CONTRIBUTING.md for the PR process.

New here? Issues labelled good first issue are scoped to a single file or two. Adding an integration provider, for example, means adding one file under core/modules/integrations/providers/ and one line in its registry.ts. The roadmap lists what is planned, and Discussions is the place for questions and ideas.

License

GNU AGPL v3.0 — self-host freely; modifications must be released under the same license. The @seentics/ui package is separately MIT.

---