Skip to content
Orca
Get started

SOLUTIONS

Start from your situation, not from our feature list.

Each journey below says what to do first and what to expect. Then a short guide helps you decide whether you need managed subscription infrastructure at all.

Journeys
5
new, cross-platform, migration, lifecycle, risk
Decision guide
8
questions, visible scoring
Time to sandbox
1 day
with one store connected

01 · NEW SUBSCRIPTION APP

You are about to add your first subscription

For Indie developers, first paid feature

Start with one store in sandbox. Create one entitlement, link one product, buy it from your own app. If it takes more than an afternoon, something is misconfigured and the guide says where to look.

First sandbox purchase

DO THIS FIRST

  1. 01Create an account and an app
  2. 02Connect App Store Connect or Play Console
  3. 03One entitlement, one product
  4. 04First sandbox purchase
  5. 05Add a server check before launch

02 · CROSS-PLATFORM

You ship to iOS, Android and the web from one codebase

For Flutter, Swift + Kotlin + TypeScript, Tauri

Flutter gets one package that routes to native IAP on mobile and desktop macOS, and to Stripe or GoCardless checkout on web, Windows and Linux. Native and web teams get one SDK each with the same identify → products → purchase → entitlements shape.

Check your stack

DO THIS FIRST

  1. 01Decide the customer identity (email) and pass it to identify() everywhere
  2. 02Link each store's product to the same entitlement
  3. 03Handle purchase events asynchronously on every platform
  4. 04Test a restore on a second device
  5. 05Gate server-side with getActiveEntitlements

03 · MIGRATION

You already have subscribers somewhere else

For Custom backends, other providers

A bulk import brings your existing customers and entitlements across. Store subscriptions belong to Apple and Google, not to your current provider, so Orca reads them once your store credentials are connected; Stripe and GoCardless subscriptions stay in your own accounts.

Migration guide

DO THIS FIRST

  1. 01Inventory products per store and map to entitlements
  2. 02Connect stores to Orca in sandbox first
  3. 03Bulk-import customers and entitlements
  4. 04Run both systems in parallel and reconcile
  5. 05Cut over client builds gradually, keeping a rollback build

04 · LIFECYCLE INFRASTRUCTURE

You need renewals, grace periods, refunds and restores handled correctly

For Teams who have been burned by edge cases

Orca pushes a signed webhook on each change and answers getActiveEntitlements live. Your code gates on the entitlement's active flag, never on ‘cancelled’, and treats refunds as the only immediate revocation.

Lifecycle guide

DO THIS FIRST

  1. 01Verify webhooks with constructWebhookEvent
  2. 02Store entitlement state keyed by email
  3. 03Fall back to a live check when in doubt
  4. 04Test cancel, grace, refund and restore in sandbox
  5. 05Alert on webhook failures

05 · OPERATIONAL RISK

You are the person who signs off on infrastructure

For Technical evaluators, CTOs

A 99.9% uptime commitment with service credits in the Orca Product Terms for Scale accounts, Maxint's SOC 2 Type II verification and published security practices, scoped API keys, and store-side ownership of subscriptions so an outage cannot lose a subscriber.

Trust page

DO THIS FIRST

  1. 01Read the Orca Product Terms at maxint.com/legal/orca and the Maxint Terms of Service at maxint.com/legal/terms
  2. 02Read Maxint Security; request the SOC 2 report under NDA
  3. 03Confirm the exit path on the migration guide
  4. 04Run the sandbox with your own stores
  5. 05Confirm Orca is in your SOC 2 scope questions to security@maxint.com

06 · DECISION GUIDE

Do you need subscription infrastructure at all?

Eight questions, a simple visible score, and a recommendation, including native billing when that is the better fit.

DO YOU NEED THIS

0/8 answered

  1. 01How many stores will you sell through?

  2. 02Must a purchase on one platform unlock another?

  3. 03Do you run a backend that can verify receipts and store entitlements?

  4. 04Do you need subscription analytics (MRR, churn, cohorts) inside the tool?

  5. 05Do you want remote paywalls and A/B experiments in the same product?

  6. 06Which client stack?

  7. 07How much engineering time can you spend on billing per quarter?

  8. 08Which pricing model do you prefer?

Answer all 8 questions to see a recommendation.