What this catalog is

This catalog collects indie SaaS products and apps shipped by solo makers and small teams. Each entry is a short card: what the product does, who it is for, which category it fits, and a link back to where the maker talked about it in their own words. That might be a launch post, a public repository, or a thread on X.

The point is not to rank anything. It is to give you a wide, browsable view of what people with limited time and no outside funding actually build, and how they describe it when they put it into the world.

A few ground rules shape every entry:

  • The source is the maker. Every card links to the maker's own post, repo or site. If you want the full story, follow the link. The card is a pointer, not a replacement.
  • Numbers are as reported. When an entry mentions revenue, user counts or growth, those figures come from the maker's public statement. The catalog does not audit them. Treat them the way you would treat any self-reported number: interesting, possibly rounded, sometimes optimistic.
  • Inclusion is not endorsement. A product appearing here means it was shipped and publicly described. It does not mean it is good, profitable, secure or still running.

How to browse

There are three ways into the catalog, and they combine well.

By use case

Categories group products by the job they do for their users, not by the technology inside them.

Category What you will find
AI Tools Products built around a model: writing aids, summarizers, assistants, classifiers
Developer Tools CLIs, libraries, hosted services and dashboards for people who write code
Productivity Task managers, note tools, calendars, focus and automation utilities
Marketing and Growth SEO helpers, social schedulers, analytics, email and outreach tools
Finance and Commerce Invoicing, budgeting, storefront add-ons, payment utilities
Design and Creative Image, video, typography, mockup and asset tools
Health and Lifestyle Habit trackers, fitness planners, sleep, food and wellbeing apps
Games and Fun Browser games, puzzles, toys and experiments built for enjoyment

Some products could reasonably sit in two places. Each is filed under the category that best describes its main user, so if you do not find something where you expect it, try search.

By source type

Every entry is tagged with the kind of post it came from. This changes what you can learn from it.

  • Launches are announcement posts on launch platforms. They tend to be polished and focused on the pitch. Good for studying positioning and how makers explain value in a sentence.
  • GitHub entries point to public repositories. You can read the code, the README and the issue tracker. Good for studying how something is built and how open-source makers handle a paid tier.
  • X posts are short updates, often part of a build-in-public thread. They are the rawest source: milestones, screenshots, honest bad weeks. Good for seeing how a product evolves over time.

By search

Search matches product names, descriptions and tags. It works best with concrete nouns ("invoice", "habit", "screenshot", "Postgres") rather than adjectives. If a search returns too much, add a category filter.

Reading paths

Different people come here for different reasons. Here is where to start depending on yours.

If you want to build your first product

You probably have more ideas than time, and the hardest part is picking one and finishing it.

  1. Browse two or three categories close to your own skills and note which products look small enough that one person could have built them in a few months. That is most of them.
  2. Read Validate Before You Build before you write code.
  3. Read From Side Project to SaaS for how to structure the work around a day job.
  4. Keep The Indie Launch Checklist open while you get close to shipping.

Be realistic about the odds. Most products in any catalog like this one make little or no money. The ones that do usually took longer than their makers expected. That is not a reason to skip it; it is a reason to pick something you would be glad to have built even if it stays small.

If you have already shipped

You have a product, maybe a handful of users, and you are wondering what to do next.

  1. Read Finding Your First 100 Users for channels that work at small scale.
  2. Read How to Price Your SaaS and What MRR Really Means to get your numbers straight.
  3. If people sign up and then leave, read Reducing Churn for Small SaaS.
  4. Browse the X posts source type for makers at a similar stage and see what they tried.

If you are just curious

You do not need a plan. Start at the catalog and click around. The Games and Fun and Design and Creative categories are good places to see what people build when they are not optimizing for revenue. The Indie SaaS Glossary will decode any jargon you run into.

Submitting a project

If you have shipped something, or you found a maker's post that belongs here, use the submit page. A good submission includes a link to the maker's own public post, a one-line description of what the product does, and the category you think fits. Submissions are reviewed by hand, so there may be a delay.

FAQ

Are the revenue numbers verified?

No. They are quoted from the maker's public post and labeled as reported. Some makers share dashboards or payment screenshots; many do not. Use them as rough signals, not facts.

Why is a product I know missing?

The catalog grows from submissions and from public posts that fit the format. If a product is missing, it most likely has not been submitted. You can submit it.

Does an entry get removed if the product shuts down?

Entries point to a moment when something was shipped and described. A product that later shuts down still tells you something useful about what was tried. Where a link has gone dead, the entry may be updated or removed.

Is this only for software?

Mostly. The focus is SaaS and apps, including web, mobile and desktop, plus developer tools and small games. Physical products and services are outside the scope.