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

# Paywall Localization

To localize your paywall, **click** on the **Localization** button from the **sidebar**:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/localizeSidebar.png)

There are two ways to localize your paywall:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/pe-editor-localize-modes.jpeg)

1. **Simple**: Here, you can use AI to localize your paywall into any language. You can manually refine each value at any point. Quick and accurate.
2. **Advanced**: User external .strings files to localize your paywall. This is ideal when you are using external localization services.

> **Note:** You can switch between the two methods at any time.

### Simple localization

Simple localization covers all translatable content on your paywall, including text elements and [multiple choice](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-multiple-choice-component) labels. Choice labels are treated the same as text: they appear in the translation panel, are included in CSV exports, and are covered by AI auto-translate.

Once enabled, a new side panel will present to help you localize you paywall:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/pe-editor-simple-ui-localize.jpeg)

You can control localization with the options at the top:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/pe-editor-top-options.jpeg)

Here's what each options does, left-to-right:

| Name          | Description                                                                                                             |
| ------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Localization  | Opens a menu with options to access AI localize settings, switch to advanced localizations, or clear all localizations. |
| Missing Only  | Filters the list to show only keys that have no localized value.                                                        |
| Import/Export | Allows importing or exporting localization data as a `.csv` file.                                                       |
| AI Localize   | Starts the AI-powered localization process for selected keys.                                                           |
| Add Language  | Lets you specify a new language to add for localization.                                                                |

To start the AI localization process, **click** on the **Add Language** button. Then, choose **AI Localize**. Superwall will being to localize each value, while respecting the AI Localize settings in place:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/pe-editor-localize-in-progress.jpeg)

Once finished, you'll see all localized values:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/pe-editor-localize-done.jpeg)

> **Tip:** You can click on any value to edit it manually.

#### AI localization settings

You can customize how AI localization behaves by changing the settings in the **AI Localize Settings** menu:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/pe-editor-localize-settings.jpeg)

The **Formality Style** lets you toggle between formal and informal language. Use the **Localization Style Guide** to provide specific instructions to your brand's voice accurately.

#### Managing languages

To remove or reset a language, **click** on the **three dotts** button next to the language:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/pe-editor-localize-remove-reset.png)

To switch back and forth between languages, simply **click** the language at the top:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/pe-editor-localize-change.jpeg)

### Advanced localization

After opening the localization panel referenced above, **click** on the **Add Language** button. Choose the language identifier of the locale you're localizing for, and **click** on **Add**:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/localizeAddLanguage.png)

If there are any existing text components on your paywall, all of them with currently *unlocalized* strings will populate in the sidebar (in this example, we're localizing our text for Spanish speakers):

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/localizeMissingStrings.png)

Click on the **Localize** button on any of them to enter in localized values. When you're done, click **Save**:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/localizeModalExample.png)

From there, go through and localize all of the values. Keep an eye on the progress bar at the top to see how far along you are. Remember to **click** on the **Publish** button at the top right of the editor to commit any localization edits.

> **Tip:** When you are localizing strings, the editor will reflect the locale you're editing against so you
> can see a live preview of how the text will appear.

#### Associating localized strings to new or existing text components

When you add new text components, or need to associate a different localization to an existing one — **click** the **Localize** button when the text component is selected. You can either use an existing localized string, or add a new one by clicking the plus button:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/localizeViaTextStep1.png)

When a text component has a localized string attached to it, you'll see the localized string's key in place of the localize button:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/localizeViaTextStep3.png)

> **Tip:** You can use variables with localized strings, too. Simply use liquid syntax within your localized
> string values to access any variable. Currently, variables themselves are not able to be
> localized. Learn more about using variables [here](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-variables).

#### Using .strings files

You can download and import .strings files to speed up your translations. This is ideal when you are using external localization services or have a large number of strings to localize.

#### Exporting .strings files

Select **Localization** from the left sidebar, **click** on the **Import** button. Choose "Download template" and the .strings file will be downloaded with all of your currently localized strings:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/overviewLocalizationImportExport.jpeg)

#### Importing .strings files

Select **Localization** from the left sidebar, **click** on the **Import** button.  Choose "Import Strings File" and select your local .strings file to upload. Then, all of the updated values will be reflected in the editor.

### Localizing period lengths

Superwall will automatically localize period lengths for products. Simply use any of the period-based variables in your text:

![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/auto-localize-period.jpeg)

For example:

```liquid
Analyze the math of caffeine this {{ products.primary.period | locale: "en" }}

// English, French, and any or any other localized regions you support...
Analyze the math of caffeine this year
Analysez les chiffres de la caféine ce année
```

You can override and remove auto-localization on specific items by setting a `locale` filter:

```liquid
Analyze the math of caffeine this {{ products.primary.period | locale: “en” }}

// Now, it'll show in English in every language 
Analysez les chiffres de la caféine ce year
```

### Testing localized strings

You can preview how localized strings will appear on device. To set this up:

1. Make sure you've got [in-app previews](/docs/sdk/quickstart/in-app-paywall-previews) configured.
2. Open the paywall editor and click "Preview":
   
![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/localizePreview.jpeg)

3. When it opens, tap the menu located at the top left and choose "Localization":
   
![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/localizeMenuButton.jpg)

4. Then, select the language to display and the preview will reload with it:
   
![](https://2b27b750-superwall-docs-staging.staffbar.workers.dev/docs/images/localizeResult.jpg)