Skip to main content

Indie hackers

Ship one script. See what makes money.

You do not have time for a tag manager and a consent stack. Vero is one tiny script that ties traffic to revenue and answers questions from your editor.

The problem

  • Heavy analytics + consent stacks are overkill for a solo product.
  • You want to know what converts to revenue, not bounce-rate trivia.
  • Context-switching to a dashboard breaks your build flow.

How Vero helps

One tiny script

The core weighs 1.2 KB gzipped, is served from the edge and sets no cookies. Paste one tag and you are measuring.

Query from your editor

The MCP server lets Claude or Cursor query your revenue and stats without leaving your workflow.

Free to start

Hobby costs €0: 10,000 pageviews and custom events a month, one site, 30 days of history. Every account opens with 14 days of Pro, so you see revenue attribution before you decide.

What you use

  • Hobby at €0, no card: 10,000 events, 1 site, 30-day retention
  • MCP server: Claude/Cursor query your stats
  • Custom events via vero.track()
  • Modular tracker from 1.2 KB, no cookies

Worked example from the public demo

What a launch week actually paid

The public demo is a fictional SaaS in its launch week: Hacker News front page on Tuesday, Product Hunt on Thursday. It closed at €18,423, +34% on the week before. Two launches in one week, and the revenue chart alone cannot tell you which one paid. Revenue by source can.

  1. Hacker News paid the most

    news.ycombinator.com sent 3,420 visitors and €7,124, 39% of the week’s revenue, with no tag at all: the referrer was enough. Product Hunt, on Thursday, sent 1,632 visits and €1,845. Plenty of traffic, but it converted below the site’s own rate. The upvote count on launch day never tells you that, and the revenue row does.

  2. Twitter paid the most per visitor

    Twitter sent fewer people, 1,245, and €4,821: €3.87 per visitor against €1.25 for the whole site. The source with the most visitors is not the one that earns the most from each, and only revenue per source shows the gap. Twitter also carried €1,200 of ad spend, and after it the source still left €3,621.

  3. One visit, from click to sale

    Sessions shows one visit from news.ycombinator.com: 7 events that end in a purchase of €99. Open it and you read its events in order, ending with the sale. No cookie and no login tie those events together, they belong to one visit. On your own site, the sale comes back through your payment provider’s webhook with that visit attached. The visit that arrived from Hacker News is the same one that paid, so the credit is not a guess.

For your next launch: post where your buyers already read, push the channel that pays per visitor, and put no money on a source like the demo’s Reddit ads, 421 visits and not one sale. Then read the week after: a source that only sells on launch day is an event, not a channel.

Figures from the public demo: launch week for a fictional SaaS, not Vero’s data or a customer’s. Open this screen in the demo

Frequently asked

Is there a genuinely free tier?

Yes. Hobby costs €0 and needs no card: 10,000 pageviews and custom events a month, one site, 30 days of retention. Revenue attribution is a Pro feature, and every new account starts on a 14-day Pro trial.

Can I query stats from Claude or Cursor?

Yes. The MCP server exposes your stats and revenue to AI dev tools.

How fast is setup?

One script tag, and it sets no cookies: live in minutes.

More use cases

Start free and see what earns

By joining you agree to receive launch updates and accept our Privacy Policy.

See the demo