Log inStart free

Use case

upTake for makers of developer tools

Developers find tools through a Show HN, a README, a Dev.to article or a release note, often without a referrer: the visit lands in direct and the source is lost.

Your best channel may be your own changelog or README, and without a tag on its links you would never know it.

What upTake measures for you

  • Visits from each post, README and release note, through a tag on your own link: yoursite.com/?ut=github-readme.
  • Your Hacker News submissions with their points and comments, next to the signups of the same days.
  • Releases and merged pull requests from GitHub, with drafts to announce them.
  • Payments from Stripe, Polar or Paddle, matched to the visit behind them; estimated matches are marked.

What it does not measure

  • Usage of your API or CLI after signup.
  • Stars and forks as a measure of users: upTake counts visits, signups and payments.

See the workflow before adding your site

Follow one post from its tagged link to recorded visits, signups and payments. Compare the result with the next post before deciding where to spend your time.

Home · Compare visits, signups and traced revenue, then decide what to try next.Actual interface · fictional IndiePDF data · captured October 30, 2026Explore this view →

Connectors that help

See every integration, and what upTake reads from each.

What a week can look like Example

Example figures, invented to illustrate. Not a real customer.
PostVisitsSignupsPaying usersRevenue
Reddit post in r/SideProject1,204889$431
X thread on pricing410191$45
LinkedIn carousel9600$0

One community post did more than the network with the most followers.

These figures are an example, invented to show what the table looks like. They are not a customer's results. Open the live demo to see a full example project.

See which of your posts bring customers

Free plan · No card · 5-minute setup

Create your projectSee a live demo