Finance and accounting decision

Revone

A competent developer can build a useful personal revenue aggregator (ingest + local UI) in a few weeks, but reproducing the vendor's native macOS polish, packaged app, and ongoing connector maintenance is non-trivial — consider self-hosted analytics projects as starting points.

Visit website

Built by Solt Wagner, who ships 7 products in this index

You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off108 h to build

$0/mo6 h/mo upkeep

No published price to break even against.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Connect provider APIs, ingest transactions, normalize and store revenue events, surface unified timelines and dashboards in a native UI, and run background sync + notifications.

What it still won’t have

  • Polished native macOS packaging and one-click installer
  • Ready-made macOS widgets, menu-bar integration and system-level polish
  • Ongoing connector maintenance and quick fixes for provider API changes
  • The vendor’s branded UI/UX and support

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Revone does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a personal revenue-aggregation app using Tauri (Rust) + React for UI, Node.js server-process for connector tasks, and SQLite for local storage. In scope: OAuth/API connectors for Stripe, Gumroad, Lemon Squeezy, Paddle, RevenueCat, Shopify/WooCommerce; background sync worker, normalization pipeline (transactions, subscriptions, customers), a menu-bar/dashboard UI showing revenue calendar, timeline of orders, country breakdown, simple 3D globe purchase visualization (canvas), native macOS notifications and widgets, manual revenue entry, and import CSV. Out of scope: hosted multi-user backend, analytics at enterprise scale, session replay. Deliverables must include error handling for API failures/rate limits, automated tests for connectors and normalization, README with build and packaging steps, and CI to produce a signed macOS build.
How we checked2 sources · 3/3 runs agreed · evidence score 60

How the score was reached

  • Partly verdict base52
  • 2 cited sources+1
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • Evidence score60

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 2

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded