15 one-person SaaS companies with public revenue

SaaS companies do not have to look like Salesforce. The 15 examples below are software operations whose public profiles list one person and attach revenue to a connected payment provider. They range from $23,533 MRR to no active subscriptions. That range is the point: “one-person SaaS” describes an operating constraint, not a guaranteed income, growth curve, or quality bar.

A dated list, not a leaderboard

Every row is a snapshot, not a ranking. The linked page states the payment provider, the revenue field, and when it last synced. The same page supplies the one-person team label, but that label is profile metadata: it does not tell us whether the operator uses contractors, agencies, or support from another business.

The snapshot runs from 2026-09-23 through 2026-09-26. Revenue can change after those dates, so the link belongs beside the number rather than in a source list at the bottom.

One-person software companies in the snapshot

The list includes subscriptions, mobile apps, a directory, analytics tools, documentation software, and a hybrid service-and-tool offer. That is useful because the phrase “software as a service companies” hides several different obligations. The service may recur, but support, data sources, distribution, and billing can recur in completely different ways.

It also shows why a company list should include small numbers. A profile with one or two active subscriptions is evidence that somebody paid, not evidence that acquisition repeats. A page with no active subscriptions is evidence that software exists and revenue occurred at some point, not that the current recurring exchange works.

What the examples have in common

The products are different, but each promise can be written as one repeated job. Sonar tracks app-store visibility. Dewstack maintains documentation. Mirage lets a prospect try a product on a landing page. IGMsg moves a social interaction into a message workflow. The names are less useful than that compression.

For a solo operator, the repeated job has to close across four systems:

The recurring-service boundary matters. A directory selling placements once can be a software business without having active subscription revenue. A mobile app can carry hundreds of small subscriptions. A business-to-business documentation product can carry only a few accounts at a higher price. For the definition behind that distinction, see what SaaS means. For the solo economics, use the micro-SaaS model.

What public revenue does not tell you

It does not show profit. Hosting, model usage, refunds, app-store fees, contractors, tax, and the founder's unpaid time sit outside an MRR field.

It does not show durability. A synchronized month is current evidence, not a promise that the same subscriptions renew or that the acquisition channel keeps working.

It does not verify headcount. The payment connection can support the revenue field. It cannot prove the profile's team-size answer or reveal help that sits outside payroll.

It does not show support load. Two products with the same MRR can create very different weeks. The useful question is how many accounts, incidents, permissions, and urgent failures sit behind the number. The support-load guide models that separately.

It does not prove your copy of the idea. These companies have their own timing, distribution, reputation, and buyer access. Their revenue is evidence about their operation on the source date, not evidence that another analytics tool or directory has demand.

Use the list as an operating map

Choose an example with a buyer you understand and rewrite it without the product name: who returns, what recurring job they need, why software must stay operated, how they find it, and what failure creates a support request. If one of those lines is blank, the missing line is a research task.

Then discard the example. Find the same kind of job in a market you can reach and ask that buyer for costly action before building. The lesson from a one-person SaaS company is not that one person can copy the feature. It is that one person has to carry the entire recurring exchange.