Log inStart free

Use case

upTake for open-source maintainers

You ship a release, write the notes, and announcing it is one more chore. Many releases never get a post at all.

When you do post, you cannot tell whether the Hacker News thread or the Mastodon post is the one that brought sponsors.

A project that pays for its own maintenance needs both: releases that get announced, and a way to see which announcement was worth writing.

What upTake measures for you

  • Releases, merged pull requests and commits on the main branch of the repositories you choose, sorted into features, improvements, fixes and internal changes.
  • Announcement drafts for features and improvements, each with its own tagged link.
  • Visits to your project site or docs from each post.
  • Sponsorship and sales through Polar or Ko-fi, matched to the visit behind them when possible.

What it does not measure

  • Stars, forks, clones and issues.
  • Your code: no files, no diffs, no commit contents.
  • Package downloads.

See the workflow before adding your site

Start with a release waiting in To post. Choose a visible change to announce, then measure visits or another goal even before you have revenue.

To post · Start with a release or an idea waiting in To post.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.
PostVisitsDocs visitors who signed upNew sponsorsRevenue
v2.0 release, announced on Hacker News3,200965$50
Same release on Mastodon410223$30
v2.1 release, not announced3510$0

The release nobody announced reached almost nobody.

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