Skip to main content
Observerbee is an AI web analytics platform. A lightweight browser SDK records user sessions, a backend pipeline turns those recordings into a deduplicated map of your product’s screens and the journeys users take through them, and an AI agent layer studies that map to produce insights, design proposals, and governed actions such as tickets and pull requests, always with human approval in the loop. Instead of watching hours of session replays yourself, you get a structural view of your product built from real traffic: which screens exist, how users move between them, where they succeed, and where they drop off.

​
How it works

1

Record

The SDK records sessions in the browser using rrweb: DOM snapshots, mutations, clicks, scrolls, and inputs. Recording is privacy-aware and resilient: events are persisted locally before they are sent, so flaky networks and closed tabs do not lose data.
2

Map

The state engine replays every session server-side, captures screens at meaningful moments, and deduplicates them across all sessions into canonical states. States form a graph whose transitions are weighted by real traffic.
3

Mine

The path engine mines the state graph for journeys and goals: the paths users actually take, validated against real session trajectories, with per-step drop-off rates from real traffic counts.
4

Act

AI agents analyze the graph and goals to produce insights and proposals. Governance policies control what each agent may do on its own; anything above its autonomy level waits for human approval. Code changes always arrive as pull requests.

​
Get started

Quickstart

Install the SDK and capture your first session in a few minutes.

SDK configuration

Every init option, with defaults, plus the runtime API.

Privacy and masking

What is masked by default and how to mask, block, or ignore elements.

Core concepts

Sessions, states, journeys, agents, and environments explained.

​
Privacy at a glance

Masking happens client-side, inside the recorder, while the DOM is serialized. Password, email, and telephone inputs are masked by default, and you can mask, block, or ignore any element with CSS classes or selectors. Masked content never leaves the user’s browser. See Privacy and masking for exactly what is and is not covered.

​
Integrations

Observerbee connects to GitHub for pull requests, Linear for ticket drafting, and Slack for notifications. All three connect over OAuth from the dashboard.