Not reallyCan Grok Bot build Hotjar?
What you're paying for isn't code. No bot conjures a panel, a bank feed or a benchmark.
- Price
- —
- You'd save
- —
- Who runs it
- The bot
- Category
- Analytics
Session replay looks like it should be a weekend project and it is one of the nastiest things on this list. You are serialising a live DOM, capturing every mutation, and replaying it faithfully across browsers you've never tested - while not capturing the password field, not capturing the credit card, not blowing up the user's bandwidth, and not tanking the page's performance budget. rrweb exists and is good, but the operational load is real and the privacy exposure of getting masking wrong is a genuinely bad day. Use PostHog's replay if you want this. Don't hand-roll it.
The prompt
Written for a bot that already has a browser, a terminal and your logins · paste it in whole.
Don't hand-roll session replay. Masking mistakes leak passwords and card numbers into a database, and that is a bad day you can avoid entirely. Use something that already handles it, and check the free tier before deploying: - PostHog Cloud is free for 5,000 session replays a month, no card. - Self-hosted PostHog is officially unsupported by them and wants about 4 vCPU, 16GB RAM and 30GB+ disk. Only worth it if the recordings genuinely cannot leave my infrastructure. You have a computer and a browser. - Ask me which of those applies. Default to the hosted free tier and deploy nothing. - Either way, before a single real visitor is recorded, do the masking work properly: - Mask all input fields by default. Opt specific ones in, never out. - Add data-ph-no-capture to anything showing an email, a card, an address or a name. - Load my own site, fill every form with fake sensitive data, watch the recording back, and confirm none of it is visible. Show me that recording. - Sample at 20% of sessions, not 100%. You do not need all of them and the storage is real. - Set retention to 30 days and enforce it. - Re-run the masking test after any upgrade.
What you lose
- replay that works in browsers you never tested
- input masking that has been battle-tested against real leaks
- heatmap aggregation across thousands of sessions
- the storage bill being somebody else's problem
The numbers
Hotjar's pricing page now redirects to Contentsquare, which acquired it, and standalone pricing is no longer published. That alone is worth knowing before you build on it.
hotjar.com/pricingChecked against the live page on 2026-08-23
Why we think that
The load-bearing claim behind this verdict, and where it comes from.