NativePilot

Ship mobile subscriptions with confidence.

Validate your Expo/EAS, RevenueCat, GitHub, and mobile subscription configuration before launch.

Early accessBuilt for Expo & React Native teams.
nativepilot validate

Repository       matched Expo app config
EAS production   public SDK keys detected
RevenueCat       offerings and packages aligned
Launch checklist 8 ready, 2 need review

Problem

Subscription launches fail in the gaps between systems.

Mobile subscription configuration spans app source, Expo and EAS settings, RevenueCat projects, app identifiers, entitlements, products, offerings, packages, and environment variables. Small mismatches can block a launch or create confusing runtime behavior.

Workflow

How NativePilot works

1

Connect

Discover configuration from supported providers and repository sources.

2

Validate

Compare configuration across the workspace and connected sources.

3

Fix

Surface actionable mismatches and official documentation.

4

Launch

Review generated artifacts and the launch checklist.

Integrations

Available validation sources

GitHub

Repository scanning and configuration discovery.

Available

Expo / EAS

EAS project metadata, build profiles, and environment variable checks.

Available

RevenueCat

Project, app, product, entitlement, offering, and package validation.

Available

App Store Connect

Direct provider validation is planned for a future release.

Coming soon

Google Play

Direct provider validation is planned for a future release.

Coming soon

Read-only positioning

Inspection-focused validation

NativePilot uses read-only access where applicable to inspect configuration required for validation. It does not modify RevenueCat customers, purchases, products, offerings, entitlements, or provider configuration through the current validation integrations.

Validation capabilities

Checks for the configuration that matters before launch

Repository configuration
EAS environments
RevenueCat configuration
App identifiers
Entitlements
Products
Offerings & packages
Environment variables
Generated artifacts
Launch readiness

Official documentation

Findings point developers to provider sources.

Validation findings can link developers to relevant official documentation from Expo, GitHub, RevenueCat, Apple, and Google so fixes can be reviewed against provider guidance.