Beton Inspector vs MRR.io

Beton Inspector finds potential revenue signals in product data, checks them against historical records, and sends selected signals to a CRM. Its agent proposes hypotheses suited to a company’s schema; candidates are backtested before going live. Listed data sources are Postgres, PostHog, Stripe, and Firecrawl, while destinations include Attio, Apollo, and webhooks. For Attio, Beton can create or update records with field-level mapping and says it preserves user-entered data. Webhooks use HMAC-signed JSON, retries with backoff, and delivery logs. The maker says Beton reads events without storing customers’ product data, and that self-hosting keeps data on the customer’s infrastructure. It requires read-only access to a Postgres warehouse or PostHog project and does not write to source systems. The software is open source under AGPLv3 and can be modified and self-hosted. Self-Hosted is free, with weekly sync and detection; Cloud is $0.50 a month per tracked user, with daily runs. Enterprise is custom-priced and runs every four hours.

MRR.io tracks monthly recurring revenue and related subscription metrics for SaaS businesses, with web and API access. Measures include net revenue, MRR movement, revenue churn, annual run rate, refunds, average revenue per customer, customer churn, and lifetime value. Data can come from Stripe or Paddle, be entered manually, or be sent through a read/write API; other named processors can also be handled through manual entry or the API. Metrics refresh every few hours, and users can request a recalculation in the app. The free Basic plan is listed at free for up to 100 paying customers, three team members, and basic email reports. Pro is listed at $19 a month for 250 paying customers, with higher listed tiers from $39 a month for 500 customers through $299 a month for 10,000; unlimited paying customers are available within tier limits. Pro includes a 30-day trial without a credit card or obligation. After the trial, accounts above 100 paying customers lose access unless they upgrade. API responses use JSON, HTTP Basic Auth with account API keys, and HTTPS; the service is operated from London, United Kingdom.