Skomi
website analytics, app analytics, google analytics alternative, cookieless analytics, analytics without cookie banner, privacy friendly analytics, heatmap tool, session recording, session replay, webs
About
Skomi is one place to understand a website and the app that goes with it.
Most site owners end up with four tools. An analytics product counts the visits. A heatmap product shows the clicks. A widget collects the feedback. A crawler checks whether search engines can read the page. Each one arrives with its own login, its own bill and its own idea of what a page is. Skomi puts all four behind one account, and adds the same analytics for a mobile or desktop app.
The site products answer four questions, in order. Analytics answers how many: traffic, sources, devices, geography, and the business events your site already emits, held in a column store so the dashboard stays fast as the history grows. Behavior answers what they did: where people clicked, how far they read, where they gave up, recordings of the page as it looked while it happened, and a live view of who is on the site now. Feedback answers what they said, attached to the exact thing on the page the visitor was looking at and waiting in one inbox. SEO answers whether they can find you. Skomi walks the site the way a search engine does, reads what every page says about itself, and reports what would stop it being indexed, ordered by the traffic those pages actually get rather than alphabetically.
One script covers the first three, and the whole thing is 11.7 KB gzipped. SEO needs nothing on the page at all, because the crawl runs from Skomi's side. Turning on a second product changes what your existing snippet does, so there is nothing new to paste and no second vendor to bring in. An app is read by an SDK instead and reports the same way: which screens people reached, how long a session lasted, which release they were on, and whether it crashed.
Nothing is stored on the visitor's device, so most sites need no cookie banner. Every visit is counted at any size, with no sampling.
Products are switched on per site, so a capability can earn its place on one site and stay off everywhere else. Billing follows the same idea: analytics, recordings, feedback and app analytics draw on one shared allowance, so you decide what to spend it on instead of buying four products at four prices.
It replaces Google Analytics on your site and in your app, and it replaces the heatmap tool and the feedback widget you were about to buy alongside it.
Ready to launch?
Submit your product and get discovered by builders and creators worldwide.
Launch Now
FounderPlaybooks.
What other founders did to grow.
2722 dispatches from hundreds of founders, pulled from the week's best podcasts.
your MVP doesn't have to be perfect try to nail design and usability make sure that your core feature works well in the case of Yodafone that was plainly making an outbound call from the app
Ship a Working Core Feature First and Ignore Everything Else
Dennis built his entire MVP over a single weekend, guided by one constraint: the core feature had to work. He used Cursor and Next.js and accepted that everything else could be imperfect at launch. The result was a product people paid for the same day he posted it.
We had two customers. My only goal was to get a third. Once we got a third, my goal was to get a fourth, a fifth. So when you get to three customers you're like 'oh wow, I got a new customer.' You're not like 'damn this company has 20,000 customers, how will I ever get there?' It's not your job to get there right away.
Set goals one customer at a time — going from 2 to 3 beats chasing 20,000
Sean reframed the gap between two customers and competitors' thousands as an n+1 problem. Each new customer was a discrete milestone whose learnings funded the next, which both protected morale and produced compounding insight instead of overwhelm.
There's a play for whatever you're stuck on.
Read all 2722 playbooks