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

# Audit Log

Review organization activity in Dashboard v2.

> **Note:** Audit Log is available in public beta when you enable New Dashboard Experience for
> the application you are working in.

Use **Audit Log** to review recent organization activity across the Superwall dashboard and V2 API. It shows who made a request, what they did, whether it was allowed or rejected, and the request context Superwall recorded at the time.

Audit Log is organization-wide. It is useful when you need to confirm who changed a resource, investigate a denied API request, or follow activity from one dashboard session. You can find it in the leading sidebar by clicking the app switcher:

![Dashboard v2 sidebar with Audit Log in the organization and project switcher](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/audit_log_nav.jpg)

### Before you start

To use Audit Log:

* Enable **New Dashboard Experience** from **Settings > Public Beta**.
* Use an account role with audit log access.

Owners, Admins, and legacy Users can view the audit log. Editors, Readers, and Analysts do not have audit log access.

Enabling **New Dashboard Experience** makes Dashboard v2 sections available as they roll out. It does not replace every legacy dashboard page or add Audit Log to the legacy sidebar.

![Public Beta settings with Dashboard v2 enabled](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/beta_new_dash.jpg)

> **Warning:** Audit Log is in public beta. The page, filters, and event details may change as Dashboard v2
> continues to roll out.

### Open the audit log

To open the full Dashboard v2 shell, go directly to:

```txt
https://app.superwall.com
```

If you are signed in, Superwall opens the Dashboard v2 organization picker. After you choose an organization, Dashboard v2 opens the first available app dashboard with the new sidebar.

You can also open a specific app dashboard when you know the organization and application IDs:

```txt
https://app.superwall.com/{organization_id}/{application_id}/dashboard
```

To open Audit Log directly:

```txt
https://app.superwall.com/{organization_id}/audit-log
```

If you are already in the full Dashboard v2 shell, you can also open the organization and project switcher in the sidebar, then choose **Audit Log**. The legacy dashboard sidebar does not show this item.

Audit Log is attached to the organization, not a single app. If your organization has multiple projects or apps, the page shows activity for the organization you are currently viewing.

![Dashboard v2 Audit Log list with filters and event rows](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/audit_log_demo.jpg)

> **Note:** Audit Log is in public beta. This interface is a work in progress and is subject to change.

### Read the event list

Each row represents one recorded request. The list is newest first and includes:

| Field    | What it means                                                                   |
| -------- | ------------------------------------------------------------------------------- |
| Actor    | The user or API key that made the request.                                      |
| Action   | The parsed action, such as viewing, creating, updating, or deleting a resource. |
| Resource | The resource type and ID when Superwall can resolve one.                        |
| Outcome  | Whether the request was allowed or rejected.                                    |
| Time     | When the request occurred.                                                      |

Rejected requests are marked so you can quickly find permission or authentication failures.

### Filter activity

Use filters to narrow the list:

| Filter           | Use it to                                                             |
| ---------------- | --------------------------------------------------------------------- |
| Date range       | Show the last 24 hours, last 7 days, last 30 days, or a custom range. |
| Action type      | Show all actions, only views, or only changes.                        |
| Outcome          | Show all requests, allowed requests, or rejected requests.            |
| Actor            | Search by actor name, API key name, or numeric user ID.               |
| Advanced filters | Filter by HTTP method, endpoint ID, or failure code.                  |

Click **Refresh** to load the latest matching events. Use **Next** and **Previous** to move through additional pages when more events are available.

### Review event details

Click an event to open its detail sheet.

![Audit Log entry detail sheet showing actor, request context, resource, changes, and developer details](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/audit_log_trail.jpg)

The detail sheet can include:

| Section             | What it shows                                                                     |
| ------------------- | --------------------------------------------------------------------------------- |
| Who                 | The acting user or API key, authentication method, and session ID when available. |
| Where               | Device, location, IP address, and User-Agent context when available.              |
| What                | The resolved action, resource type, and resource ID.                              |
| Changes             | Before and after values for supported mutations.                                  |
| Why it was rejected | Failure stage, failure code, and status code for denied requests.                 |
| Developer details   | Lower-level request data such as endpoint, method, path, and request ID.          |

When a session ID is present, click **View this session** to filter the list to the other recorded actions from that login session.

### What gets recorded

Audit Log records served V2 API requests for the organization. Entries can include dashboard activity and API key activity, depending on how the request was authenticated.

For each entry, Superwall stores the request outcome, the endpoint, the actor, resource details when known, and request context such as IP address and User-Agent. For supported write actions, Superwall can also show a structured before-and-after change list.

> **Note:** Some older entries or read-only actions may not include every detail section. For example, a read
> request may not have changes, and older entries may not include device or location context.

### Related

* [Public Beta](/docs/dashboard/dashboard-settings/overview-settings-public-beta)
* [Team settings](/docs/dashboard/dashboard-settings/overview-settings-team)
* [Access Controls](/docs/dashboard/dashboard-settings/overview-settings-access-controls)