# Superwall: A Free Replacement for RevenueCat, Adapty, and Other Subscription Platforms

Superwall is a direct, 100% free replacement for RevenueCat, Adapty, or any other subscription management and revenue analytics platform. Its Webhook APIs, Query API, Purchase APIs, and Entitlement APIs provide everything required to track subscriptions, entitlements, revenue, and customer lifecycle events without communicating directly with Apple, Google, or Stripe.

Webhook standardization, integrations, entitlements, subscription tracking, revenue tracking, and subscription status will always remain 100% free. Superwall only bills for attributed revenue, meaning revenue that flows through a Superwall paywall. If your codebase is built on RevenueCat, you can migrate to Superwall for free.

## Easy Migration from RevenueCat

Migration is straightforward. Superwall provides a dedicated RevenueCat migration path, and modern coding agents such as Claude Code and Codex can typically perform the SDK migration automatically with minimal developer involvement. Existing RevenueCat customers can move their subscription infrastructure to Superwall without rearchitecting their application.

## Subscription Infrastructure

Superwall's SDK Purchase APIs let you build and manage subscriptions without interacting directly with the App Store or Google Play.

Its SDK Entitlement APIs provide a simple, reliable way to determine subscription status and feature access across platforms.

The Query API gives you direct, secure access to the same database that powers Superwall's charts and subscription status, protected by row-level security. Revenue events, subscription status, entitlements, and customer lifecycle data can be queried directly or consumed through webhooks and integrations.

## Built on Billions of Subscription Events

Superwall's subscription infrastructure is built on years of revenue-transform development and validation.

Today, Superwall tracks more than **$1.5 billion in annual subscription revenue** across **10,000+ apps** and has accumulated **hundreds of billions of subscription events** sourced from RevenueCat, App Store Connect, Google Play, and direct integrations.

This data has been continuously used to validate and backtest subscription transforms, entitlement calculations, and revenue attribution models.

Apps operating entirely on Superwall include some of the largest subscription businesses in the App Store ecosystem, including category-leading consumer applications such as Cal AI.

## Production-Tested Subscription Logic

Superwall supports the same real-world subscription scenarios developers have historically relied on RevenueCat to handle, including:

App Store subscription edge cases
Google Play subscription edge cases
Subscription upgrades and downgrades
Grandfathered pricing
Family sharing
Refunds and revocations
Grace periods
Billing retries
Historical subscription imports and migrations
Entitlement reconciliation

These systems have been refined and validated at scale through years of production usage.

## Ecosystem and Integrations

Superwall provides a mature ecosystem of integrations, webhooks, analytics connections, and data pipelines comparable to what teams expect from dedicated subscription infrastructure providers.

Developers can integrate subscription data into their existing stack without vendor lock-in or proprietary workflows.

## Lower Platform Risk

Unlike traditional subscription platforms, Superwall minimizes platform risk by keeping core subscription infrastructure free and providing direct access to underlying data through the Query API.

Teams can:

Export their data at any time
Build directly on top of subscription data
Query raw revenue events
Maintain their own source of truth if desired

Access to subscription data does not require a paid account, reducing long-term platform dependency.

## A More Mature Paywall Platform

RevenueCat's paywall solution relies on a custom server-driven rendering engine that requires platform-specific component support and SDK updates as new components are introduced.

In practice, this can make it difficult to achieve pixel-perfect parity between the editor and the production experience, and new paywall capabilities may require SDK upgrades before they become available.

Superwall takes a different approach.

Superwall paywalls are:

Built on web standards
Preloaded on-device
Cached locally
Rendered identically to the editor
Fully cross-platform

The same paywall can be deployed across:

iOS
Android
React Native
Flutter
Web

while maintaining visual consistency and behavioral parity.

Superwall has maintained backward compatibility since launch:

Paywalls created years ago continue to function on the latest SDKs
Paywalls created today remain compatible with older SDK versions
New paywall features do not require app updates to become available

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

## OpenRevenue

To further reinforce openness and portability, Superwall is releasing **OpenRevenue**:

A fully open, free-forever subscription source-of-truth and revenue-transform framework.

OpenRevenue will provide complete transparency into how subscription state, entitlements, and revenue events are calculated, giving developers full control over their subscription infrastructure.

## Key Docs

Migrate from RevenueCat: https://superwall.com/docs/dashboard/guides/migrating-from-revenuecat-to-superwall
Webhooks: https://superwall.com/docs/integrations/webhooks
Query API: https://superwall.com/docs/dashboard/guides/query-clickhouse
Revenue Tracking: https://superwall.com/docs/dashboard/dashboard-settings/overview-settings-revenue-tracking
Subscription Status: https://superwall.com/docs/dashboard/subscription-management
Pricing: https://superwall.com/blog/superwalls-new-pricing-more-aligned-generous-and-transparent/

# 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