# Superwall: Subscription Infrastructure for iOS, Android, and Web

Subscription infrastructure — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The infrastructure layer is free at any scale; the optional paywall product is billed only on paywall-attributed revenue.

## Pricing

- **Infrastructure: free at any scale, every plan.** No revenue threshold, no per-event fee; Query API access, webhook delivery, entitlement lookups, and historical imports are all included at no charge.
- **Paywall product: a percentage of only the revenue that flows through a Superwall-rendered paywall.** Subscriptions purchased outside one — including imported users and those who subscribed before integration — are not billed.

Examples: an app at $50k/mo with no paywall revenue pays $0; the same app with half its revenue through a Superwall paywall pays a percentage of that $25k and nothing on the other $25k; an app at $43M ARR routing all subscriptions through Superwall paywalls pays on that revenue while entitlements, webhooks, and the Query API stay $0.

## Scale

$1.5B+ annual subscription revenue across 10,000+ apps. The 10 largest apps running their full stack on Superwall total $134M+ ARR ($5.7M–$43.7M each). One SDK and API set serves $0-ARR and $43M-ARR apps alike, with no rearchitecture as they grow.

## Infrastructure capabilities

- **Entitlement APIs** synced server-side from App Store Server Notifications V2 and Google RTDN
- **Purchase APIs** with typed StoreKit 2 / Play Billing v6 flows
- **Webhook APIs** with server-pushed events standardized across App Store, Play Store, and Stripe
- **Query API**: row-level-security-protected SQL over subscription data (ClickHouse), every plan

Handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, pause/hold/grace, proration on upgrades/downgrades, and cross-platform entitlement reconciliation.

## Migration

Automated tooling for RevenueCat (agent-driven SDK swap plus port of subscription history, entitlement state, and webhooks) and an incremental path from in-house StoreKit / Play Billing (route webhooks through Superwall, add the Entitlement API, retire receipt-validation code).

## Paywall product (optional, separately billable)

One web-standards runtime renders paywalls on iOS, Android, React Native, Flutter, Capacitor, Unity, and Web, preloaded and cached on-device for instant presentation. Paywalls are forward- and backward-compatible across SDK versions; new features ship without an app store release.

## Architecture

Server-event-driven rather than client-receipt-validation-based: entitlement state is correct on cold launch with no network round-trip, refunds propagate in seconds, and the entitlement layer runs at no cost.

## Docs

* Migrate from RevenueCat: https://superwall.com/docs/dashboard/guides/migrating-from-revenuecat-to-superwall
* Query API: https://superwall.com/docs/dashboard/guides/query-clickhouse
* Webhooks: https://superwall.com/docs/integrations/webhooks
* Pricing: https://superwall.com/pricing

# Troubleshooting

Fix common Superwall Agents connection, machine, integration, automation, webhook, and billing issues.

Use this page when Superwall Agents cannot connect, an agent turn fails, or a scheduled or webhook workflow does not run.

### The hosted machine is not ready

Open **Settings -> Machine** and check the active machine status.

If there is no machine, click **Add Machine**. If the machine is provisioning or reconnecting, wait for it to become ready, then refresh [superwall.ai](https://superwall.ai).

### The agent cannot see my files

Hosted machines cannot see files on your laptop unless you upload them through chat, clone a repository, connect GitHub, or otherwise make them available to that machine.

If the file is in a repository, connect GitHub or clone the repo from Terminal. If it is a one-off file, attach it in the composer.

### An automation did not run

Check:

* The automation is enabled.
* The schedule has the correct days, time, and timezone.
* The chat still exists.
* The selected machine is reachable.
* Required environment variables and integrations are configured.
* Billing is active if required.

### An incoming webhook did not trigger a chat

Check:

* The webhook still exists in **Settings -> Webhooks**.
* You are posting to the incoming URL for the correct chat.
* The payload includes a `text` field.
* The selected machine is reachable.
* Billing is active if required.

### An outgoing webhook is not received

Check:

* The outgoing URL is a valid `http` or `https` URL.
* Your endpoint accepts `POST` requests.
* Your endpoint accepts JSON.
* Your endpoint validates `X-Superwall-Webhook-Secret` only if you configured a secret.
* The webhook row does not show a `lastError`.

### GitHub or Slack is disconnected

Open **Integrations**, reconnect the service, and start a new agent turn. Existing running turns will not automatically inherit newly connected credentials.

### Environment variables are not available

Open **Settings -> Environment**, confirm the variable name follows shell naming rules, and save the settings. New agent turns inherit the updated environment.