SubSovereignConsole

Insights

Analytics & intelligence

Overview

OverviewLive revenue and subscription metrics AcquisitionWhere installs and trials come from RetentionRenewals, churn and win-back CohortsBuild and compare user cohorts

Intelligence

AI InsightsAsk your own data, answered by Merlyn Subscriber TwinsInterview a cohort of your own subscribers GEO StudioAI revenue attribution and the GEO loop AI UsageMerlyn usage against your plan allowance

Customers

Customer LookupFind any customer's entitlements Subscriber MigrationBring subscribers across from Stripe or an export HealthIntegration health per app

Monetization

Convert & protect revenue

Convert

PaywallDesign and publish paywalls, no app release ExperimentsA/B test paywalls through to a winner FlowsAutomated lifecycle and win-back flows

Revenue

Refund ShieldApple consumption-data defence MarketplaceConnectors and integrations

Developers

Build & integrate

Build

AppsApps, SDK keys, tiers, products and store credentials Getting StartedIntegrate in three calls SDKsClient SDKs for every platform

Learn & get help

GuidesIntegration, migration and concepts, in your language How It WorksWhat SubSovereign is and how the pieces fit SupportAsk Merlyn, or reach a human FeedbackFeature requests and the roadmap

Admin

Platform operations & trust

Account & security

SecurityTwo-factor, password and active sessions

Subscriber Migration

Bring existing subscribers into SubSovereign — read straight out of your Stripe account, or from an export from RevenueCat, Adapty, Qonversion or your own backend. A dry run is always the default: nothing is written until you ask for it.

App