Who it is for

Skomi for indie makers

A side project cannot carry three subscriptions or an afternoon of consent-banner work, and it usually gets no analytics at all as a result. This page is about what the free plan actually covers, and what happens on the day something takes off.

What you get

A free plan that does not expire and takes no card. A small allowance, with every product included. Not a trial with a clock on it. If your project stays small, it stays free.

No cookie banner to build. Nothing is stored on the visitor's device, so there is no consent flow to write, no library to add, and nothing to maintain on a project you touch once a month.

One script instead of three tools. Traffic, heatmaps and recordings, and a feedback widget come from the same tag and the same allowance. The alternative is three accounts, three scripts and three renewal dates for a project earning nothing yet.

A launch day you can watch live. Live view shows what is happening now, which on the one day it matters is the only report anybody looks at.

An MCP server. Ask the numbers in a sentence from your editor instead of learning a dashboard. There is a page about it, and for a solo maker it is often the difference between checking and not bothering.

The demo needs no signup. Traffic, heatmaps, recordings and feedback are all running on a real shop, with a real app beside it, before you decide anything.

What Skomi will not do for you

The free plan will not cover a portfolio. If you run five side projects, and most people reading this do, that means a paid plan or some projects with no analytics; the pricing page has the site count for each plan. Being clear about it here is better than you finding out while adding the next one.

It is metered, so a good day has a cost. Skomi counts usage against your allowance, and the front page of a news aggregator is exactly the traffic that uses it up. The default protects your money, not your data: collection stops when the allowance runs out and starts again next month, and the free plan cannot overspend at all. If you switch overage on, set the cap in the same sitting. A spike should cost you a number you chose in advance, not a number you discover.

It is not open source and you cannot self-host it. For a lot of makers that is the end of the conversation, and fairly. If it is, Umami and Plausible are both open source and both good; the comparison pages are honest about where they beat us.

History is capped by your plan. When a window passes that data is deleted rather than archived, so "the same week last year" is not a question the smaller plans can answer.

Nobody is coming to set it up for you. There is documentation and there is email, and for a free plan that is the support model.

Setting it up the way you work

Start on the free plan and skip the card. There is nothing to unlock later; the paid plans are more allowance, not more product.

Install once with the snippet, or use the guide for whatever you built it on: Next.js, Astro, WordPress and the rest are all a paste and a deploy.

Exclude yourself. On a small site your own visits are a meaningful share of the numbers, and excluding traffic takes a minute.

Set a spend cap before you post anywhere. The day you need it is the day you will not be watching.

Check the traffic alert after a spike. A launch is many people and raises none. One address sending an implausible number of hits raises one in the site's settings, and excluding it takes one click.

One script, or one SDK. The same reports either way.

Create an account, register a site, and switch on what you need.