R

RevenueCat

In-app subscription backend and analytics

Head of Customer Growth

Full-Time
$259k/yr+ Equity options
Expert
Remote in USA+2 moreMore locations: Europe | North America
Remote
Customer Experience & SupportCustomer Success

About the job

Requirements
  • Approximately 10 or more years in Customer Success, Customer Growth, strategic accounts, Growth Advisory, product growth, lifecycle, monetization, or an adjacent customer-facing function.
  • Five or more years leading customer-facing teams, including managers, senior team leads, or specialist groups.
  • Evidence of owning an entire function or multi-lane operating model, not only managing an individual CSM team.
  • Experience building or materially rebuilding segmentation, coverage, strategic-account, adoption, health, advisory, or scaled-customer systems.
  • Strong commercial judgment around NDR, renewal risk, expansion influence, customer value, and executive alignment.
  • Credibility with mobile apps, app monetization, in-app purchases, paywalls, checkout, pricing and offers, lifecycle, retention, experimentation, analytics, or a closely adjacent domain.
  • Enough product and technical fluency to lead around a developer-facing platform while preserving clear ownership for TAM, Support, and Engineering.
  • Experience managing both generalists and specialists.
  • Evidence of turning repeated one-to-one work into scalable systems.
  • Evidence of hiring, coaching, performance management, and raising the leadership and talent bar.
Responsibilities
  • Own Customer Growth strategy across the full customer base, including named accounts, high-potential customers, specialist-assisted customers, scaled customers, and the long tail.
  • Build segmentation and coverage using current value, future potential, adoption, intent, growth moments, risk, and strategic importance to determine appropriate customer support and guidance.
  • Lead through the CSM Team Lead by setting standards for customer context, account strategy, stakeholder management, growth diagnosis, adoption planning, commercial awareness, and follow-through; develop the Team Lead and build a leadership bench.
  • Identify high-potential customers early in partnership with Data, Product, Sales, Marketing, and Support.
  • Govern Growth Advisory by defining intake, qualification, expected impact, output quality, follow-through, and reuse.
  • Develop Growth Advocacy as a customer-education channel that turns customer learning into authoritative one-to-many education.
  • Build Customer Enablement and Scaled Growth through lifecycle programs, templates, office hours, documentation, automation, product nudges, and next-best-action guidance.
  • Drive meaningful product adoption in partnership with Product and Product Marketing.
  • Create clear cross-functional decision rights for Customer Growth's work with Sales, TAM, Support, Product, Marketing, and Data.
  • Build a customer-insight loop that turns repeated customer questions into product improvements, enablement, playbooks, benchmarks, documentation, lifecycle programs, and market education.
  • Own the function's metrics, operating cadences, headcount plans, budget, organization design, executive communication, and talent bar.
  • Meet directly with at least 15 customers across different sizes, growth stages, product footprints, and monetization models during the first month.
  • Take point on at least two live customer-growth situations, working with the relevant partners to diagnose problems, agree ownership, and move customers to a concrete next milestone.
  • Ship at least one improvement to a broken handoff, account motion, Advisory route, or customer experience during the first month.
  • Establish an operating agreement with the CSM Team Lead and address urgent customer, talent, or ownership issues.
  • Build a working view of the team, coverage, high-potential misses, lane boundaries, and metrics during the first month.
  • Act as executive sponsor for a small set of strategically important or high-potential customers and personally lead at least two customer-growth interventions through a measurable milestone within the first three months.
  • Put the first version of segmentation and coverage into production on real accounts and revise it based on evidence.
  • Run decision-oriented account reviews and a working Growth Advisory intake and follow-through process.
  • Ship the first scaled education or Customer Enablement program based on a repeated customer need.
  • Make initial material changes to ownership, operating cadence, or talent where the current model is not working.
  • Establish a customer-insight loop that turns frontline evidence into owned Product, education, lifecycle, or process actions.
  • Maintain direct customer contact every week, own selected executive relationships, and lead the wider system through the CSM Team Lead and specialist leaders.
  • Operate a multi-lane Customer Growth model with clear owners, live handoffs, and visible outcomes across CSM, Growth Advisory, Growth Advocacy, and Customer Enablement.
  • Ensure the CSM Team Lead independently owns daily CSM execution, coaching, and account quality.
  • Demonstrate measurable results from customer interventions and convert repeated one-to-one work into reusable Advisory output, education, enablement, or product insight.
  • Ship multiple scaled programs and make concrete hiring or investment decisions for the function.
  • Establish a trusted, actively used system for serving high-value, high-potential, specialist-assisted, and scaled customers.
  • Drive measurable improvement in customer outcomes, product adoption, account health, renewal readiness, expansion quality, and customer revenue outcomes.
  • Remain directly connected to customers and serve as a trusted executive partner for selected strategic accounts.
  • Turn successful customer work into reusable product, education, and market leverage.
Desired Qualifications
  • Have led CSMs and advisory, education, lifecycle, or enablement teams together.
  • Have scaled a customer-facing function through a major company-growth stage.
  • Have worked in a hybrid self-serve, product-led, and enterprise business.
  • Have firsthand experience as an app operator, growth leader, founder, or consultant.
  • Have built product-led or tech-touch Customer Success programs.
  • Have helped productize or commercialize an advisory or professional-services capability.

About the company

R

RevenueCat

View
cbWebsite

RevenueCat provides a backend and open-source SDKs that let app developers manage in-app subscriptions across iOS, Android, and web. It wraps Apple’s StoreKit, Google Play Billing, and web payments with a subscription backend, enabling developers to launch products quickly, reduce maintenance, and access reliable purchase data. The platform also offers real-time analytics and reporting for key subscription metrics, plus pre-built integrations and webhooks to connect revenue data and customer lifecycle events to other tools. RevenueCat differentiates itself with a developer-friendly experience, real-time insights beyond what App Store Connect offers, and an ecosystem of integrations that streamline subscription management. The company’s goal is to help developers ship subscription-based apps faster and more reliably by handling the complexity of in-app purchases and customer data.

Company Size

51-200

Company Stage

Series C

Total Funding

$106.6M

Headquarters

Brandon, Florida

Founded

2017

Get referred to RevenueCat

See people who can refer or advise you

Simplify Jobs

Simplify's Take

What believers are saying

  • RevenueCat raised $50 million in May 2025, extending cash for product and hiring.
  • AB180’s August 13, 2026 Korea partnership expands local distribution into high-spend mobile markets.
  • Replit’s April 2026 partnership and Shipaton 2026 expose RevenueCat to millions of new builders.

What critics are saying

  • Apple’s July 2026 anti-steering ruling commoditizes external checkout, weakening RevenueCat’s moat by 2027.
  • Adapty’s larger free tier and stronger A/B testing pressure RevenueCat on early-stage app builders.
  • OpenAI, Replit, and app stores can absorb monetization flows, making RevenueCat a feature inside platforms.

What makes RevenueCat unique

  • RevenueCat spans iOS, Android, web, Flutter, React Native, Unity, macOS, and Catalyst.
  • Its September 2, 2026 custom components make paywalls and funnels far more expressive.
  • RevenueCat’s Stripe Projects integration lets agents provision monetization in one terminal command.

Help us improve and share your feedback! Did you find this helpful?

Benefits

  • Fully remote work
  • Remote workspace budget
  • Learning & development budget
  • PTO

Growth & Insights and Company News

6 month growth

-1%

1 year growth

-1%

2 year growth

-4%
RevenueCat
Sep 2nd, 2026
Beyond the building blocks: custom components for Paywalls and Funnels.

Beyond the building blocks: custom components for Paywalls and Funnels. Custom components let you add self-contained HTML/CSS/JS to Paywalls and Funnels for animation and expandable content PublishedSeptember 2, 2026 Summary. RevenueCat now supports custom components for Paywalls and web-to-app Funnels, letting developers add self-contained HTML, CSS, and JavaScript for animations, icons, and expandable content like FAQs. Purchase buttons and checkout flows stay native. Arthur C. Clarke, the British science-fiction author and futurist behind 2001: A Space Odyssey, spent his career imagining what technology could make possible. As he put it: "The only way of discovering the limits of the possible is to venture a little way past them into the impossible." Even flexible visual builders have limits. You can arrange the available components in countless ways, but some ideas, such as a branded animation or expandable FAQs, don't fit neatly within a predefined set of building blocks. RevenueCat, Inc. want to give developers more freedom to push what their purchase experiences can do and bring their most creative ideas to life. That's why RevenueCat, Inc. introduced custom components for RevenueCat Paywalls and web-to-app Funnels. With custom components, you can bring self-contained HTML, CSS, and JavaScript into a paywall or funnel to create animated backgrounds and icons, accordions and expandable content, and experiences tailored to your app. Purchase-critical elements still rely on RevenueCat's native components and checkout flows. But the canvas around them just became much bigger. Here are two ways to put custom components to work. Bring your purchase experience to life with animation. Motion can add personality, reinforce your brand, and guide attention toward the most important parts of a paywall or web-to-app funnel. Custom components let you create animated backgrounds, icons, illustrations, and other visual treatments that go beyond static media. You can build animations directly with CSS or JavaScript, or use libraries such as Lottie and Rive by including them in your component bundle. For example, you could: * Add a subtle animated background behind your value proposition * Bring benefit icons to life as customers explore an offer * Use a looping illustration to demonstrate your app's premium experience * Add branded motion to connect the different steps of a web-to-app funnel Animation doesn't need to dominate the experience. Even small moments of movement can make a paywall or funnel feel more polished and connected to the rest of your brand. Let customers expand the details they care about. Customers often have questions before subscribing, but putting every answer on the screen at once can make a purchase experience difficult to scan. With HTML and JavaScript, you can create accordions and expandable sections that keep the initial experience focused while giving customers access to additional context. You might use expandable content for: * Frequently asked questions * More information about individual benefits * Explanations of how a feature works * Details about what's included with an upgrade * Supporting information within a web-to-app onboarding journey This creates a more layered experience. Customers can quickly understand the primary value proposition, then dig deeper when they need reassurance or clarification. In a paywall, expandable content can keep the offer focused without hiding useful details. In a funnel, it can add depth to an onboarding screen without turning every step into a wall of text. Build it with an agent or write it yourself. To get started, add a custom component in the RevenueCat Paywall or Funnel Editor and download the starter bundle. It includes an index.html entry point, a local preview, packaging tools, a getting-started guide, and instructions that coding agents can follow. You can give the folder to your coding agent of choice and describe the experience you want. Your coding agent can use the included instructions to build the component within RevenueCat's requirements. If you prefer to work directly with the code, you can edit the HTML, CSS, and JavaScript yourself. When the component is ready, preview it, package the files, and upload the resulting ZIP file. You can then place the custom component where you want it in your paywall or funnel. Creativity, with guardrails. Custom components are self-contained and run inside the area they occupy in your paywall or funnel. They're intended for decorative and supplementary experiences. They shouldn't contain interface elements required to complete a purchase. In Paywalls, packages and purchase buttons must remain native. In Funnels, custom components should complement RevenueCat's native purchase controls and checkout flow. Uploaded bundles must also follow RevenueCat's security, file structure, and size requirements. For in-app paywalls, your app needs a supported RevenueCat SDK version to display custom components. Review the custom component requirements and minimum SDK versions before publishing. Custom components open up a much broader creative canvas across RevenueCat Paywalls and web-to-app Funnels, from a single animated icon to an expandable experience that helps customers understand why they should upgrade. RevenueCat, Inc. can't wait to see what you create. * Blog post Gurwi: How to turn building in public into a Shipaton #BuildInPublic win How building in public can get strangers to give you money to build your dreams, capture the attention of politicians, and bring loyal customers * Blog post The late submitter's guide to getting through app review Everything you need to get your app approved by the App Store and Play Store review before the Shipaton deadline * Blog post RevenueCat and AB180 partner to support South Korea's app community South Korean app users are among the highest spenders - and now South Korean developers have dedicated help to capture that revenue.

RevenueCat
Aug 11th, 2026
RevenueCat and AB180 partner to support South Korea's app community.

RevenueCat and AB180 partner to support South Korea's app community. South Korean app users are among the highest spenders - and now South Korean developers have dedicated help to capture that revenue. PublishedAugust 11, 2026 Summary. RevenueCat has partnered with AB180, a South Korea-based MarTech company, as its exclusive regional partner in South Korea. AB180 will provide free, local-language support to all RevenueCat customers in South Korea starting August 13, 2026 - covering implementation, onboarding, day-to-day support, and growth strategy. South Korean app users are among the highest-spending mobile users in the world, with the average person spending $143 per year on apps. Now, developers in South Korea have dedicated support to capture more of that - more revenue, more retained subscribers, faster growth. RevenueCat, Inc. has partnered with AB180 to give South Korean developers hands-on local support and help getting the most out of RevenueCat's tools, backed by a team that already works with some of South Korea's biggest apps and games like NAVER WEBTOON, MUSINSA, Amorepacific, and Nexon. AB180 is a South Korea-based marketing technology company with over 10 years' experience in MarTech and AdTech, and the team behind the Airbridge attribution platform. The partnership makes it easier for South Korean app developers to get local support, expert guidance, and access to world-class tools for managing and optimizing in-app subscriptions. Local expertise, backed by a global platform. AB180 will support all RevenueCat customers in South Korea, from first integration through to scaling monetization, at no extra cost. It's included for every RevenueCat customer in the region. If you're building in South Korea, here's what AB180 can help with: * Setting up and integrating RevenueCat across iOS, Android, and the Web * Moving over from another provider or your own in-house system * Digging into your performance data to understand what's working and where you stand against benchmarks * Rolling out RevenueCat's growth tools: paywall builder, web-to-app funnels, and experiments * Joining a growing network of local developers building and scaling subscription apps With this step, RevenueCat is continuing to expand its global partner network and empowering developers everywhere to monetize smarter, scale faster, and focus on building apps users love. Ready to grow? Its partnership with AB180 is one more step in its mission to help app developers worldwide make more money. If you're a South Korea-based app builder, get in touch with AB180 through its form here to see how they can support your growth journey. * Blog post Recover churned subscribers automatically with win-back campaigns for web Win back subscribers who cancel, automatically. When someone's access expires, RevenueCat, Inc. send them an email with a discount offer. They resubscribe on the web, so you keep more of the money. * Blog post Announcing Shipaton 2026: Ship an app, win big, join the fun Shipaton 2026 - RevenueCat's global hackathon for mobile app builders, August 1 to September 30 * Blog post Why RevenueCat, Inc. removed "always decline" as a refund preference "Always decline" refunds is gone from RevenueCat. Here's why it was working against you.

App Builders PH
Aug 6th, 2026
AppBuildersPH holds its first-ever Show & Tell.

AppBuildersPH holds its first-ever Show & Tell. Around 140 Filipino app builders, developers, founders, and technology professionals gathered at the AWS Office in BGC for the first-ever AppBuildersPH Show & Tell, sponsored by RevenueCat Shipaton. On July 30, 2026, AppBuildersPH held its first-ever Show & Tell at the AWS Office in Taguig, BGC. Sponsored by RevenueCat Shipaton 2026, the event brought together around 140 app builders, developers, founders, designers, students, and technology professionals for an evening focused on learning, connecting, and celebrating Filipino-made apps. The event also welcomed attendees from major technology companies, including representatives from Apple and Huawei, reflecting the growing interest and support for the local app-building community. Opening the First AppBuildersPH Show & Tell The event officially began with opening remarks from Eric Jeremie Rotaquio, CEO of PocketDevs. He welcomed the participants and shared the importance of creating more spaces where Filipino builders can meet, exchange ideas, and support one another. Stories and Lessons From Filipino Builders The event featured talks from builders who shared practical lessons, personal experiences, and honest stories about creating and launching digital products. The speakers were: David Marquez Rod Alcantara Sharie Ingente The event was hosted by Darla David, who guided the audience throughout the program and kept the evening engaging and organized. The talks covered the realities of building apps, from transforming ideas into working products to finding users, improving through feedback, and continuing to ship despite challenges. The Show & Tell Segment One of the main highlights of the evening was the Show & Tell segment, where members of the community were invited to present the apps they had built. Each presenter had the opportunity to demonstrate their product, explain the problem it solves, and share the story behind its development. The winner was decided through an audience vote. Adrian Abelarde received the most votes for his app, Clucky, making him the winner of the first-ever AppBuildersPH Show & Tell. His presentation stood out to the audience and demonstrated the creativity, technical ability, and product thinking present within the Filipino builder community. A Community for Filipino App Builders The first AppBuildersPH Show & Tell was created to provide Filipino builders with a space to meet, learn from one another, share their work, and form meaningful connections. The event welcomed everyone, from experienced developers and startup founders to students, independent makers, designers, and first-time app builders. Seeing around 140 people come together for the first event showed that there is a strong and growing community of Filipinos who want to build products for both local and global users. Closing the Event The event concluded with closing remarks from Bryl Lim, founder of AppBuildersPH. He thanked the speakers, presenters, sponsors, partners, and participants who helped make the community's first event possible. He also shared a message for Filipino builders: the sky is the limit, and Filipino developers have the ability to create apps for users around the world. More Events Ahead The first AppBuildersPH Show & Tell was only the beginning. AppBuildersPH plans to continue creating events where Filipino builders can showcase their work, learn from experienced creators, meet potential collaborators, and become more confident in launching their own products. AppBuildersPH would like to thank RevenueCat Shipaton for sponsoring the event, AWS for providing the venue, the speakers and presenters who shared their experiences, and every participant who joined and supported the community. Filipino builders have the talent and potential to create apps for the world. Events like Show & Tell help transform that potential into real products, stronger connections, and new opportunities.

Spaceport
Jul 24th, 2026
RevenueCat vs Adapty: Picking a Subscription SDK for Your iOS App.

RevenueCat vs Adapty: Picking a Subscription SDK for Your iOS App. RevenueCat vs Adapty for iOS subscriptions. Free tiers, platform coverage, paywall A/B testing, and integrations, plus which one fits an indie app. RevenueCat and Adapty are direct competitors: both are subscription infrastructure for mobile apps, both handle receipt validation and entitlements, both take a percentage of your revenue, and both now ship a visual paywall builder. The short version is that Adapty's free tier is twice as generous and its paywall A/B testing is stronger, while RevenueCat covers more platforms and has a deeper integration ecosystem. Which matters more depends almost entirely on whether your bottleneck is conversion or cross-platform reach. This guide compares the free tiers and pricing, platform and SDK coverage, the paywall builders and experimentation, the integration ecosystems, and what Adapty has shipped recently, then gives a straight decision guide. One disclosure up front: Spaceport generates projects wired to RevenueCat, so I have a horse in this race. I have tried to be accurate about where Adapty is genuinely better, and it is, in a couple of places that matter. Prices and features are as of writing; both move fast. On this page. What they have in common. Unlike a paywall-only tool, these two overlap almost completely on the fundamentals. Both give you a hosted subscription backend so you are not hand-rolling receipt validation, and both answer the question your app actually asks: does this user have access right now. Both handle the unglamorous parts, verified transactions, entitlements, restores, refunds and revocation, grace periods, upgrades and downgrades. Both provide subscription analytics (churn, LTV, cohorts) so you are not rebuilding a reporting layer. Both use a percentage-of-revenue pricing model with a free tier, and both charge 1% on their paid tiers at time of writing. And both now ship a visual paywall builder, which used to be a real differentiator and is now table stakes. So the decision is not about whether the basics work. They both work. It comes down to the four areas below. Pricing and free tiers. This is the clearest practical difference, and it favors Adapty. Adapty's free tier covers up to 5,000 USD per month in tracked revenue. They doubled it in early 2026, replacing an older flat-fee plan. RevenueCat's free tier covers up to 2,500 USD per month. Both then charge 1% on the paid tiers. For an indie developer, that gap is not academic. It is the difference between paying nothing and paying a percentage during exactly the phase when revenue is small and every subscription matters. If you are somewhere between 2.5K and 5K a month in tracked revenue, Adapty is simply free and RevenueCat is not. Above that, the two converge and pricing stops being the deciding factor. Platform and SDK coverage. Here RevenueCat is ahead, and it is the single strongest argument for it. RevenueCat ships SDKs for iOS, Android, Flutter, React Native, Cordova, Unity, macOS and Catalyst, and Ionic. Adapty covers iOS, Android, Flutter, React Native, and Unity. For a pure iOS app that difference is irrelevant. It starts to matter the moment you have a Mac app, a Cordova or Ionic codebase, or a plan to expand beyond the two main mobile platforms. The bigger version of this is web. If your subscription business spans iOS, Android, and a web product, RevenueCat's native Stripe connection for web subscriptions means one subscriber identity and one entitlement system across all three. That is genuinely painful to assemble yourself, and it is where RevenueCat is hardest to beat. Paywalls and A/B testing. Here Adapty is ahead, and it is deliberate: Adapty has repositioned itself as the subscription SDK for teams that care about paywall conversion. Adapty's visual paywall builder has matured considerably. You can start from pre-made, industry-tested templates or from a blank canvas, and crucially it ships unlimited A/B testing with real-time analytics. If your growth motion is iterating on the paywall and measuring lift, that is the product built for you. RevenueCat's Paywalls v2 is a component-based editor that renders natively (SwiftUI on iOS rather than a web view) and is included free on all plans. It is good, and for most indie apps it is not the limiting factor. But if you intend to run continuous paywall experiments as a core practice, Adapty's experimentation story is stronger. Integrations and ecosystem. RevenueCat has the deeper ecosystem. It connects natively to Stripe for web subscriptions and to a long list of analytics and marketing tools including Amplitude, Mixpanel, Adjust, AppsFlyer, and Braze. This matters more than it sounds when your subscription data needs to reach the rest of your stack: attribution that ties a subscriber back to a campaign, product analytics that segment by entitlement, lifecycle messaging triggered by subscription events. If that plumbing already exists as a supported integration, you wire it up in an afternoon. If it does not, you build and maintain it. Adapty has integrations too, including marketing attribution, and its coverage is respectable. RevenueCat's is simply broader and more battle-tested, being the larger and longer-established platform. What Adapty shipped recently. Worth knowing if you last evaluated Adapty a year or two ago, because the picture has changed. Through early 2026 Adapty shipped a CLI, geo-pricing, Autopilot, and Apple Ads Manager support, alongside the free-tier increase and the paywall builder work. The geo-pricing piece is notable for anyone selling internationally, since charging one converted price everywhere leaves money on the table in both directions. It is also a reminder that the market is converging: features that were differentiators are becoming standard on both platforms, which pushes the decision back toward free tier, platform coverage, and ecosystem. How to decide. * You are a pre-revenue or early indie, iOS only. Adapty, on free-tier grounds alone. The 5K versus 2.5K threshold is real money during the phase where it hurts most. * You span iOS, Android, and web. RevenueCat. The native Stripe connection and single cross-platform entitlement system is the thing that is genuinely hard to replicate. * Paywall iteration is your core growth motion. Adapty, for unlimited A/B testing and the more mature experimentation workflow. * You need deep integrations with analytics, attribution, or lifecycle tooling. RevenueCat, for the broader supported-integration list. * You are on Cordova, Ionic, or macOS. RevenueCat, by SDK coverage. * You have no strong signal either way. Either is a defensible choice; both solve the hard part correctly. Pick on free tier if you are small and on platform coverage if you are not. Whichever you pick, remember that both sit on top of App Store Connect, and neither creates your products or sets your prices in each market for you. That layer has to be right first. See creating App Store subscriptions with the App Store Connect API and pricing across 25 countries. If you are also weighing a paywall-only tool, see RevenueCat vs Superwall, which is a different comparison because Superwall is not a subscription backend. Faq. Which has the better free tier, RevenueCat or Adapty? Adapty. Its free tier covers up to 5,000 USD per month in tracked revenue, versus RevenueCat's 2,500 USD. For an early indie app that gap is the difference between paying nothing and paying a percentage during the phase when revenue is smallest. Is Adapty a good RevenueCat alternative? Yes, it is a genuine competitor rather than a lesser option. It handles the same fundamentals (entitlements, receipt validation, analytics), has a more generous free tier, and has stronger paywall A/B testing. RevenueCat's advantages are platform breadth and integration depth. Which should I use for a cross-platform app? RevenueCat, especially if web is involved. It ships more SDKs (including Cordova, Ionic, and macOS) and connects natively to Stripe for web subscriptions, giving you one subscriber identity across iOS, Android, and web. Do both support paywall A/B testing? Both offer paywall builders, but Adapty's experimentation is stronger, shipping unlimited A/B testing with real-time analytics and template-based paywalls. RevenueCat's Paywalls v2 renders natively and is free on all plans, which is enough for most apps that are not running continuous experiments. How much do RevenueCat and Adapty cost? Both use a percentage-of-tracked-revenue model and both charge 1% on their paid tiers at time of writing, after their free tiers (2,500 USD per month for RevenueCat, 5,000 for Adapty). Verify current pricing before committing; both change it periodically. Can I switch from one to the other later? You can, but it is real migration work: both are the source of truth for entitlements, so you are moving subscriber state and re-validating transactions. Pick deliberately up front rather than planning to switch, and weigh the free tier against where you expect to be in a year. Spaceport generates a production-ready SwiftUI Xcode project with RevenueCat subscriptions already wired up, entitlements, paywall, and restore flow working on the first build, plus your products and prices created in App Store Connect across 25 markets. Spaceport ship RevenueCat because of the cross-platform and integration story above; the App Store Connect groundwork underneath is identical whichever SDK you choose. And before any of it matters, you need users: Lighthouse is the sibling toolkit for the waitlist and newsletter that get you your first hundred. From an indie iOS dev, for indie iOS devs.

RevenueCat
Jul 15th, 2026
We partnered with Stripe so your agent can monetize your app.

RevenueCat, Inc. partnered with Stripe so your agent can monetize your app. RevenueCat and Stripe Projects make app monetization setup as simple as one CLI command, so developers and coding agents can go from idea to payments faster. PublishedJuly 15, 2026 Summary. RevenueCat partnered with Stripe Projects to make app monetization setup available through a single CLI command, letting developers or coding agents create a RevenueCat account, provision a project, generate API keys, and write credentials to .env without leaving the terminal. With this integration, tools like Cursor, Claude Code, and Warp can treat monetization as a routine setup step, then use RevenueCat's SDK, dashboard, MCP server, and AI Toolkit to configure products, entitlements, offerings, paywalls, analytics, and webhooks so developers can move from idea to revenue faster. Your coding agent can now set up RevenueCat, provision a project, generate API keys, and get your app ready to accept payments. The whole thing takes just one CLI command. stripe projects add revenuecat/app RevenueCat, Inc. built this with Stripe as part of Stripe Projects. Before this, monetization setup was still manual. Every other piece of your stack provisions in seconds. Database? One command. Auth? One command. Hosting? Done. But until now, monetization required you to stop and spend an afternoon creating accounts, reading StoreKit documentation, figuring out which shared secret goes where, generating API keys, configuring sandbox environments, and setting up server-to-server notifications. It takes hours. Sometimes days. And you haven't written a single line of product code yet. That gap between "I have a working app" and "I can charge for it" is absurdly wide for something that should be a solved problem. So RevenueCat, Inc. fixed it. One command, working credentials. If you're starting a new project today, here's what this looks like in practice. You (or your agent) run one command. A few seconds later, you have a RevenueCat account, a configured project, and working API keys written directly to your .env file. You stay in the terminal the entire time. $ stripe projects add revenuecat/app | Created RevenueCat account | Created project "my-app" | Generated API keys | Wrote REVENUECAT_APP_UUID to .env | Wrote REVENUECAT_DASHBOARD_URL to .env | Wrote REVENUECAT_SECRET_API_KEY to .env Ready. Run `stripe projects open revenuecat` to view your dashboard. Products, entitlements, and offerings can be configured from the dashboard later, or your agent can handle them via its MCP server. Agents provision it automatically. If you build in Cursor, Claude Code, or Warp, the provisioning step is something your agent handles between writing your UI code and wiring up the SDK. You don't type the command. You just say "add monetization." You: "I want to add a $9.99/month subscription to this app." Agent: [runs stripe projects add revenuecat/app] Agent: [reads .env, configures Purchases SDK] Agent: "Done. I've added the Purchases SDK to your project and configured it with your API key. Want me to create a product and build a paywall next?" The agent doesn't need special RevenueCat knowledge. It picks up the Stripe Projects CLI and the skill files that stripe projects init already created. Monetization becomes a routine provisioning step, same as adding a database or setting up auth. Account, project, keys, full platform. When you run stripe projects add revenuecat/app, the CLI provisions: * A RevenueCat account (or links to your existing one) * A new project with sandbox and production environments * API keys synced to your local .env * Access to the full platform: paywalls, entitlements, offerings, analytics, webhooks, and its AI Toolkit for ongoing management You'll still need Apple and Google developer accounts to go live on those stores. But RevenueCat itself (the account, the project, the API keys, the entitlement configuration) provisions from the terminal. And with RevenueCat's test store, you can test monetization on a real device without those store accounts. From there, you integrate the Purchases SDK for iOS, Android, React Native, Flutter, KMP, or web. That's the path from "I have an idea" to "I'm making money." Try it. * Install the Stripe CLI with the Projects plugin: stripe plugin install projects * Initialize your project and add RevenueCat: stripe projects init my-app stripe projects add revenuecat/app * Your REVENUECAT_SECRET_API_KEY is in .env. Integrate the SDK and start making money. For the full lifecycle, check its documentation or ask your coding agent to handle product creation, paywall configuration, and entitlement management using the RevenueCat AI Toolkit. This is a developer preview. Give it a try and tell RevenueCat, Inc. what you think, especially if you're building with agents. * Blog post Understanding Google Play's Billing Choice: a complete guide to offering alternative billing Billing Choice comes down to two decisions - who renders the choice screen and where payment happens - over one shared setup and one mandatory sale report. * Blog post Move your rating prompt out of onboarding - or risk rejection Apple is rejecting apps that ask for ratings during onboarding. * Blog post Launch Party June '26: The New Features You Should Know A recap (and videos) of its latest launch party demos.