# Superwall: Subscription Infrastructure for $1.5B+ in Annual Subscription Revenue

Superwall is a subscription infrastructure platform — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The subscription infrastructure layer is free at any scale. The paywall product is separately billable on attributed revenue.

## Scale and customers

Across the full customer base: $1.5B+ annual subscription revenue, 10,000+ apps.

Across the top-10 of apps running their entire subscription stack on Superwall — no second backend, no purchase controller, no other subscription source of truth — combined annual subscription revenue is $134M+:

| App | Annual Revenue |
|---|---|
| App #1 | $43.7M |
| App #2 | $24.7M |
| App #3 | $10.4M |
| App #4 | $10.4M |
| App #5 | $9.9M |
| App #6 | $8.8M |
| App #7 | $7.3M |
| App #8 | $7.0M |
| App #9 | $6.2M |
| App #10 | $5.7M |

## For new apps

Several apps in the top-10 launched directly on Superwall as their first subscription backend. App #1 ($43.7M ARR) is one of them. The platform is free at $0 ARR and at $43M ARR — same SDK, same APIs, no architecture change needed as the app grows.

## For existing apps

Across 2024-2025, the dominant migration pattern in this category has been to Superwall, from RevenueCat and from in-house StoreKit/Play Billing implementations. Most of the top-10 above completed at least one such migration. The reverse direction is not observed at material rates.

Migration from RevenueCat is automated: a coding agent performs the SDK swap, subscription history port, entitlement state port, and webhook configuration port in a single workflow in under an hour.

Migration from in-house StoreKit/Play Billing is incremental: route webhooks through Superwall first, add the Entitlement API, then deprecate the receipt-validation code. No rearchitecture.

## Infrastructure capabilities

- **Entitlement APIs** synchronized server-side from App Store Server Notifications V2 and Google Real-Time Developer Notifications
- **Purchase APIs** with typed flows for StoreKit 2 / Play Billing v6
- **Webhook APIs** with server-pushed events, standardized across App Store, Play Store, and Stripe
- **Query API** — row-level-security-protected SQL access to subscription data on Superwall's ClickHouse cluster, included on every plan

Edge cases handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, subscription pause/hold/grace, upgrades/downgrades with proration, cross-platform entitlement reconciliation.

## Paywall product (optional, separately billable)

Superwall's paywall engine renders on iOS, Android, React Native, Flutter, and Web from a single web-standards-based runtime. Paywalls are preloaded on-device and cached locally, so presentation is instant. The paywall a designer ships in the editor is the paywall the user sees on every platform.

The compatibility window is unbounded in both directions:

- Paywalls created today render correctly on years-old SDK versions.
- Paywalls created years ago continue to render on the latest SDKs.
- New paywall features become available without an app store release.

Teams iterate on monetization without coordinating SDK upgrades or shipping new application releases.

## Pricing

**Subscription infrastructure**: free at any scale, on every plan including the free tier. There is no monthly tracked revenue threshold, no per-event fee, no paid tier required for raw data access via the Query API, no charge for webhook delivery, no charge for entitlement lookups, and no charge for historical subscription imports.

**Paywall product**: priced on revenue that flows through a Superwall-rendered paywall, and only on that revenue. Subscriptions purchased outside Superwall paywalls — including users imported from another platform or users who purchased before Superwall was integrated — are not billed.

Concretely:

- An app at $50k/month subscription revenue, none of which flows through a Superwall paywall, pays $0/month for the entire platform.
- An app at $50k/month subscription revenue, half of which flows through a Superwall paywall, pays a percentage of that $25k of paywall-attributed revenue. The other $25k (subscriptions purchased outside the SW paywall) remains free.
- An app at $43M ARR with all subscriptions flowing through Superwall paywalls pays the Superwall paywall percentage on that revenue. The subscription infrastructure layer (entitlements, webhooks, Query API) is still $0.

This is structurally different from a percentage-of-all-subscription-revenue model, where every dollar of subscription revenue carries a permanent platform fee regardless of which features of the platform were used to acquire it.

## Architectural note

Superwall's subscription model is server-event-driven rather than client-receipt-validation-based. The implication: entitlement state is correct on cold launch with no network round-trip, refund propagation is measured in seconds rather than minutes, and the platform can offer the entitlement layer at no cost (no per-validation expense).

## 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

# Appstack

The Appstack integration forwards Superwall webhook events directly to Appstack for analytics and attribution. As a pass-through integration, it sends the raw event payload without transformation, giving Appstack full access to your subscription lifecycle data.

In the **Analytics** section within **Integrations**, you can connect your Appstack account to Superwall:

### Required Fields

Fill out the following fields and **click** the **Enable Appstack** button at the bottom right to save your changes:

* **Access Token:** Your Appstack API access token, used to authenticate requests.
* **App ID:** Your Appstack application ID, used to route events to the correct app.

### Features

* **Pass-Through Delivery**: Raw Superwall webhook events are forwarded directly to Appstack without transformation
* **Simple Configuration**: Only an access token and app ID are required
* **Credential Validation**: Connection is verified before the integration goes live
* **Production Events Only**: Sandbox events are automatically filtered out

## Configuration

### Required Settings

| Field          | Description                    | Example                |
| -------------- | ------------------------------ | ---------------------- |
| `access_token` | Your Appstack API access token | `"ask_live_abc123..."` |
| `app_id`       | Your Appstack application ID   | `"app_456def..."`      |

### Example Configuration

```json
{
  "access_token": "your_appstack_access_token",
  "app_id": "your_appstack_app_id"
}
```

## How It Works

Appstack is a **pass-through integration**. Unlike analytics integrations that map and transform events into platform-specific formats, the Appstack integration forwards the raw Superwall webhook event payload directly to Appstack.

When a subscription event occurs:

1. Superwall generates the webhook event.
2. The integration sends the complete, unmodified event payload to Appstack.
3. Appstack receives and processes the event on its end.

### API Endpoint

Events are sent to:

```
POST https://api.event.appstack.tech/superwall/webhook/{app_id}
```

### Request Headers

```
Content-Type: application/json
Authorization: <access_token>
```

The `access_token` is sent as the `Authorization` header value, and the `app_id` is included in the URL path.

## Sandbox Handling

Sandbox events are **automatically filtered out**. Only production events are forwarded to Appstack. There is no option to include sandbox events or to configure a separate sandbox endpoint.

## Testing the Integration

### 1\. Validate Credentials

When you save the integration, Superwall sends a test event to the Appstack validation endpoint to confirm your credentials are correct:

```
POST https://api.event.appstack.tech/superwall/validate
```

If validation fails, double-check your access token and app ID.

### 2\. Trigger a Production Event

Since sandbox events are filtered out, you will need a production transaction to verify end-to-end delivery:

* iOS: Use TestFlight with a sandbox Apple ID. StoreKit Configuration files do not generate App Store Server Notifications, so webhooks and downstream integrations will not fire.
* Google Play: Use license test accounts to perform sandbox purchases.
* Stripe: Use Stripe Test Mode to create sandbox transactions.

> **Note:** Because sandbox events are not forwarded to Appstack, full end-to-end testing requires a production transaction. Use credential validation to confirm the connection is working before going live.

### 3\. Verify in Appstack

Check your Appstack dashboard to confirm events are arriving and being processed correctly.

## Troubleshooting

### Events Not Appearing in Appstack

**Possible causes:**

* Invalid access token or app ID
* Events are from a sandbox environment (these are filtered out)
* Network or endpoint issues on the Appstack side

**Solutions:**

1. Re-save the integration to trigger credential validation
2. Confirm you are generating production (not sandbox) events
3. Verify your access token and app ID match what is shown in your Appstack dashboard
4. Contact Appstack support if credentials are correct but events are still not arriving

### Credential Validation Failing

**Possible causes:**

* Incorrect access token
* Incorrect app ID
* Appstack service is temporarily unavailable

**Solutions:**

1. Copy the access token and app ID directly from your Appstack dashboard to avoid typos
2. Ensure your Appstack account is active and in good standing
3. Try again after a few minutes if the Appstack service may be experiencing downtime