Most analytics products aggregate on the way in, which is why every interesting question is one you cannot ask any more. This one stores the event with every property you attached, and answers new questions about last quarter without you having re-instrumented anything.
Funnels, retention and segmentation are not three products here. They are three shapes of question asked of the same rows.
Every property, kept, with no cardinality bill
Send the plan, the feature flag, the deploy sha, the workspace id. Nothing is dropped for being high-cardinality and nothing costs more for being interesting. The question you will want in March is answerable in March because the data was never thrown away in January.
Funnels defined after the fact
Pick four events in an order. No funnel to declare in advance and no re-instrumentation to add a step.
Retention by any cohort
Anyone who has ever sent a property can be a cohort. Signed up in a week, on a plan, in a country.
A spend ceiling you set
At the ceiling ingest samples rather than stops, and you are warned at 70, 90 and 100 percent. Analytics that go dark on a big month go dark in the month that matters.
Asking
A query language you can read out loud, and SQL underneath it.
The builder is for the question you ask weekly. When you need something it cannot express, the escape hatch is real SQL against the same rows, not a support ticket asking us to build a report.
Every chart shows its queryClick a chart, read the query that made it, edit it. There is no chart whose definition is hidden in our code.
SQL is not a paid tierIt is on every plan including the free one, because a product that gates the escape hatch is betting on you never needing it.
Answers leave the toolAny query is an endpoint, so a number you check daily can live on your own dashboard instead of in a tab.
Against the two obvious alternatives
What each of these actually costs you.
Page-view analytics
A warehouse plus BI
Piskes Analytics
New question about last quarter
Not answerable
Answerable
Answerable
Time to first funnel
Not supported
A data engineer and a fortnight
An afternoon
High-cardinality property
Dropped
Fine, and billed
Fine, not billed
Raw SQL
No
Yes
Yes, on every plan
Who maintains it
Nobody
Someone, permanently
Nobody
How events get in
JavaScriptNodePythoniOS and AndroidHTTPPiskes Workflows
Pricing
By events, with a ceiling you set.
Per-seat pricing on analytics is how a company ends up with three people who can see the numbers.
Free
For one product finding out whether the numbers are worth having.
Prices in USD, billed monthly. Extra events are charged per million, and the ceiling is yours to set before that happens.
Questions
The ones asked on the second call, not the first.
Do we have to re-instrument to move?
If you send a plain event with properties today, changing the endpoint is most of it. We will read your current event schema with you before you commit to anything.
Is this GDPR-workable?
Events are workspace data with a documented erasure path, and you choose whether to send anything identifying at all. Plenty of teams run it entirely on pseudonymous ids.
What happens at the spend ceiling?
Ingest samples at a declining rate rather than stopping. You keep the shape of your traffic in the month you most want to see it.
Can I get the raw events out?
Yes, as an export on Business or over the query API on any plan. They are your events.
Send one event. Query it fourteen seconds later.
That is the demo and it is the whole product in miniature — the event you sent, with the properties you attached, answerable by a question you had not thought of when you sent it.