The 1% Revenue Tax is a Success Penalty: Why We Built a Flat-Rate Billing Orchestrator

If you have built a cross-platform app in the last five years, you already know the pain of mobile billing. Managing identical subscriptions across Apple StoreKit, Google Play Billing, and Stripe is a fragmented nightmare of edge cases, asynchronous webhooks, and double-charging risks.

Tools like RevenueCat and Adapty solved a genuinely hard technical problem. But in doing so, they normalized a business model that is fundamentally hostile to developers: the 1% revenue tax.

We believe that billing orchestration is infrastructure. And infrastructure should be priced based on the computational load it generates, not as a royalty on your gross margin.

Here is why the percentage-based pricing model is broken, and how we are fixing it with Orca.

The Math Problem with Percentage Pricing

When a platform charges 1% of your Monthly Tracked Revenue (MTR), it creates a dangerous misalignment of incentives. Let’s look at the actual unit economics of receipt validation.

Imagine you run a B2B SaaS app. You decide to raise your subscription price from $10/month to $100/month.

• The Server Load: Validating that receipt with Apple’s API requires the exact same database lookup and the exact same bandwidth as before. The cost to the infrastructure provider is identical.
• Your Bill: Your RevenueCat bill just went up 10x.

At a small scale, this feels invisible. But look at the math as you scale into the power-law curve of app success:

• At $14,000 / month MRR: You are paying ~$140/month. Annoying, but manageable.
• At $100,000 / month MRR: You are paying $1,000+ every single month just to validate receipts and route webhooks.

You are effectively paying a venture-scale tax on your own success. They are capturing the upside of your pricing power, your marketing efforts, and your product development, while providing a static infrastructural utility.

The Solution: Pricing by "Active Entitlements"

We built Orca to be a single master catalog for iOS, macOS, Linux, Android, Windows, and Web. But technically solving the cross-platform routing wasn't enough; we had to fix the business model.

Instead of taxing your revenue, Orca charges flat SaaS brackets based on Active Entitlements.

An Active Entitlement is simple: it is an unexpired recurring subscription, or a one-time/consumable purchase made within that specific billing month. We don't charge ongoing fees for historical one-time purchases, and we don't care if you charge $1 or $1,000 for your product.

• Up to 500 Active Entitlements: Free. (This covers most apps up to ~$3,500 MRR).
• Up to 10,000 Active Entitlements: $299 / month.

If you have 10,000 users paying you $10/month, you generate $100,000 in MRR. RevenueCat takes $1,000. Orca takes $299. It is a predictable, capped operational expense that your CFO will actually sign off on.

Built for AI-Native Engineering Teams

If we were going to build a new orchestrator, we also couldn't rely on legacy SDK architectures.

Orca is built from the ground up for modern, cross-platform stacks. It ships with a deep, native Flutter/Dart SDK to handle all six platforms immediately.

More importantly, it is the first billing orchestrator to ship with a native Model Context Protocol (MCP) server. Instead of manually configuring complex product SKUs, trial periods, and pricing tiers in a clunky web dashboard, you can expose your master catalog to your AI agents and automate your entire subscription setup autonomously.

Infrastructure Should Be Predictable

We don't want to be partners in your profits. We just want to provide rock-solid, cross-platform financial infrastructure and get paid a fair, flat rate for the database compute we provide.

You can check out the docs, play with the MCP server, and launch on all 6 platforms for free today at orca.maxint.com.