Insights
What is happening, and is it more than last week?
Any event, counted, split by any property, over any window. Save the ones you keep re-asking onto a Board.
Analytics
Product analytics on our own machines: drop in a Project token, watch the events land in the Live view, then ask the questions — who came back, where they dropped, what they did next.
One million events a month on the free plan. No card, no sales call.
Six reports, each answering a question someone actually asks out loud.
What is happening, and is it more than last week?
Any event, counted, split by any property, over any window. Save the ones you keep re-asking onto a Board.
Where do people fall out?
Order the steps that matter and see the drop between each one — by source, by plan, by whatever you send along with the event.
Do they come back?
Cohorts by the week they arrived, and how many of them were still doing the thing a month later.
What do they do next?
The real paths through your product, forwards from a starting event or backwards from the one you care about.
What should the team look at every morning?
Pin the reports that earned their place into one page, and let it refresh itself.
Who is this one person?
One profile, every event they sent, across the browser, your server and your connectors — stitched by identify.
Every way into a Project, with the documentation for it and where it stands today.
One script, a Project token, autocapture on if you want it.
Web SDK docs →Post a batch of events from anything that can make a request.
HTTP API docs →Point the iOS, Android, React Native or Flutter SDK at our host — one line.
Mixpanel-compatible SDKs docs →Server-side events with a Server key, batched and fire-and-forget.
Node SDK docs →Storefront, checkout and order webhooks from a store, stitched to one shopper.
Shopify docs →Payments, invoices and subscription changes as revenue events.
Stripe docs →A destination function that forwards what you already collect.
Segment docs →A webhook destination plus a transformation, cloud or device mode.
RudderStack docs →A web-container tag carrying the Project token, no code deploy.
Google Tag Manager docs →Track and identify steps in any Zap, authenticated with a Server key.
Zapier docs →Scheduled loads in from BigQuery, Snowflake or Postgres, and exports back out.
Warehouses docs →Your data, your VM
This is not a reseller of somebody else’s pipeline. The service, the durable log and the database are ours, and each Project gets its own database.
Nothing is acknowledged before it is written
Every accepted batch goes onto a durable log first and is only acknowledged after the database commits, so a restart replays instead of losing events.
One database per Project
A Project is isolated at the database, not by a column somebody has to remember to filter on. A Project token can only ever write to its own Project.
The browser credential cannot read
A Project token is write-only by construction. Reading a report needs a Server key or a signed session — a leaked snippet leaks nothing.
No third-party sharing, no ad pixels
Your events are not enriched, brokered or sold. Retention is a number you set, and Data Drop deletes by rule when you want it gone.
Pricing
Analytics is an add-on to your plan, metered on the events a Project takes in each month. Invite the whole team either way.
1M events / month
Included
Enough to instrument a product and watch it for real.
10M events / month
Credits
For a launched product with daily traffic.
100M events / month
Credits
For a business where analytics is how decisions get made.
Unlimited events / month
Talk to us
Volume, retention and residency on terms we agree in writing.
Over the quota we keep accepting for seven days and show the bar in Settings → Usage, then ingest answers 429 until the plan changes.
Documentation
The quickstart is a Project token, one script tag, and an event in the Live view.