Why We Built Orca

1. The Origin at Maxint

Maxint began as an engineering team building high-performance, cross-platform software. Like thousands of developers worldwide, we loved the promise of the modern cross-platform stack: write your core application once using React Native, Flutter, Tauri, or C++, and ship seamlessly to iOS, Android, macOS, Windows, and Linux.

However, the moment we tried to implement paid subscriptions across platforms, that cross-platform dream shattered into a fragmented nightmare.

• iOS: We wrestled with StoreKit 2, App Store Connect, receipt validation, and JWS signature verification.
• Android: We managed Google Play Billing Library APIs, AIDL limits, and store webhooks.
• Web & Desktop: We stitched together Stripe webhooks, tax compliance tools, and custom license key servers.
• Linux & Direct Debit: We were entirely on our own, with zero SDK support from legacy providers.

2. The Gross Revenue Tax Crisis

When we evaluated existing subscription wrapper SDKs like RevenueCat and Adapty, we discovered another major problem: the gross revenue tax.

Legacy payment wrappers charge an extra 1% gross revenue cut on top of Apple and Google's 15%–30% store fees. As an app scales to $50,000 or $200,000 in Monthly Recurring Revenue (MRR), developers end up paying $1,000 to $4,000 every single month just for webhook forwarding and database checks.

3. The Four Pillars of Orca

In 2026, we built Orca to solve these fundamental flaws once and for all:

4. Engineering Principles & Open Ecosystem

At Maxint, we operate on four fundamental engineering principles:

• Developer Sovereignty: You own 100% of your transaction data. Orca streams normalized JSON webhook events directly to your database (PostgreSQL, Supabase, Firestore, BigQuery) with zero vendor lock-in.
• Open Source Commitment: All of our client SDKs (Flutter, React Native, Swift, Kotlin, TypeScript, Python) and our Model Context Protocol (MCP) server are fully open-source and audited on GitHub.
• Zero Downtime Fallbacks: In-app entitlement validation features multi-layered edge caching and offline cryptographic verification so customers never lose access even during app store downtime.
• Security & Compliance: End-to-end cryptographic verification (JWS StoreKit 2 tokens, RTDN Google Cloud Pub/Sub, Ed25519 webhook signatures). Review our practices on our Security Page.