# Retainza

> Retainza is a customer engagement and retention platform for apps: push notifications, email, in-app messages and deep-link navigation, driven by segments, campaigns and event tracking, with an AI assistant (Ask AI) that drafts campaigns, segments and templates for review. It is developer-first: messages go out through the customer's own Firebase (FCM) project and SMTP provider, so the customer keeps control of deliverability and sending cost. Pricing: a free plan (1,000 MTU), then Starter $50/mo (10,000 MTU), Growth $70/mo (25,000 MTU), Scale $100/mo (50,000 MTU); limits are hard caps with no overage billing. It suits startups and growth teams that want push, in-app and lifecycle messaging without enterprise-suite pricing.

Cheapest paid plan: Starter, $50/mo. Contact: hello@retainza.com.

## Product

- [Home](https://retainza.com/): What Retainza is, the Ask AI campaign assistant, and how an integration goes.
- [Features](https://retainza.com/features): Push, email, in-app messages, deep links and Ask AI in detail.
- [Pricing](https://retainza.com/pricing): Free plan and the three paid tiers, with every limit, plus top-up packs.
- [Retainza vs others](https://retainza.com/retainza-vs-others): Feature and price comparison with other engagement and attribution platforms, with sources.
- [Integrations](https://retainza.com/integrations): FCM, APNs, SMTP and the SDKs, with setup steps.
- [Use cases](https://retainza.com/use-cases): Onboarding, cart abandonment and trial-ending campaigns, step by step.
- [Blog](https://retainza.com/blog): Guides on push, email, in-app messaging and retention.
- [About](https://retainza.com/about): Why Retainza exists and who builds it.

## Developers

- [Developer docs](https://developer.retainza.com/): SDK guides for React Native/Expo, iOS (Swift), Android (Kotlin), Flutter (Dart) and server-side (Node), plus the full SDK and HTTP API reference.
- [Developer docs for LLMs](https://developer.retainza.com/llms.txt): the docs index in llms.txt format; every page is also served as Markdown.
- Docs MCP server: https://api.retainza.com/v1/mcp — read-only, no API key; tools search_docs, get_docs_section, get_docs_page, list_docs_pages. Setup: https://developer.retainza.com/ai/

## Comparisons

- [Alternatives hub](https://retainza.com/alternatives): Retainza compared with other engagement and attribution platforms. Every claim about another product links its public source and the date it was checked.
- [Retainza vs OneSignal](https://retainza.com/alternatives/onesignal): Retainza vs OneSignal, with sourced pricing and features: flat $0–$100/mo plans, your own FCM and SMTP, push, email and in-app. When OneSignal fits better, and how to migrate.
- [Retainza vs MoEngage](https://retainza.com/alternatives/moengage): Retainza vs MoEngage, with sourced facts: Retainza's published $0–$100/mo plans vs MoEngage's sales-led plans, push, email and in-app, your own FCM and SMTP, and how to migrate.
- [Retainza vs CleverTap](https://retainza.com/alternatives/clevertap): Retainza vs CleverTap, with sourced pricing: Retainza from $0 with Growth at $70/mo vs CleverTap Core at $85/mo. Push, email, in-app, your own FCM and SMTP, and how to migrate.
- [Retainza vs Braze](https://retainza.com/alternatives/braze): Retainza vs Braze, with sourced facts: Retainza's published $0–$100/mo plans vs Braze's MAU-based quoted pricing. Push, email, in-app, your own FCM and SMTP, and how to migrate.
- [Retainza vs WebEngage](https://retainza.com/alternatives/webengage): Retainza vs WebEngage, with sourced facts: Retainza's published $0–$100/mo self-serve plans vs WebEngage's demo-led buying. Push, email, in-app, your own FCM and SMTP.
- [Retainza vs Insider One](https://retainza.com/alternatives/insider): Retainza vs Insider One, with sourced facts: Retainza's published $0–$100/mo plans vs Insider One's quote-based pricing. Push, email, in-app, your own FCM and SMTP.
- [Retainza vs AppsFlyer](https://retainza.com/alternatives/appsflyer): Retainza vs AppsFlyer, sourced: AppsFlyer is an attribution and deep-linking suite; Retainza is push, email and in-app messaging at $0–$100/mo. How they differ and when to use each.
- [Retainza vs Adjust](https://retainza.com/alternatives/adjust): Retainza vs Adjust, sourced: Adjust is install attribution and deep linking; Retainza is push, email and in-app messaging at $0–$100/mo. How they differ and when to use each.
- [Retainza vs Branch](https://retainza.com/alternatives/branch): Retainza vs Branch, sourced: Branch is deep linking and attribution; Retainza is push, email and in-app messaging at $0–$100/mo. How they differ and when to use each.

## Integrations

- [Firebase Cloud Messaging](https://retainza.com/integrations/firebase-cloud-messaging): Connect your own Firebase service account to send Android and iOS push through Retainza. You keep the project, the quota and the delivery reputation.
- [APNs](https://retainza.com/integrations/apns): Reach iOS devices through FCM's APNs relay, one credential to manage instead of two, using your own Apple push key.
- [SMTP](https://retainza.com/integrations/smtp): Send transactional and campaign email over any SMTP provider, SendGrid, SES, Postmark, or a server you run. Your reputation, your cost.
- [React Native](https://retainza.com/integrations/react-native): Identify users, track events, register push tokens and render in-app messages in a React Native app, with your own UI components.
- [Expo](https://retainza.com/integrations/expo): An Expo config plugin that applies push's native prerequisites, so you do not hand-edit native project files.
- [Node](https://retainza.com/integrations/node): Create campaigns and segments, count audiences and send now from your backend, using the secret key.

## Use cases

- [Automated onboarding emails](https://retainza.com/use-cases/onboarding-emails): Trigger a welcome sequence from a signup event, delay each step, and stop sending the moment the user finishes onboarding.
- [Cart abandonment push and email](https://retainza.com/use-cases/cart-abandonment): Fire a reminder a set time after an abandonment event, deep-link straight back to the cart, and cap how often it can repeat.
- [Trial ending reminders](https://retainza.com/use-cases/trial-ending-reminders): Segment on days remaining, remind across push, email and in-app, and respect quiet hours so a reminder never arrives at 3am.

## Blog

- [Cart abandonment with push and email](https://retainza.com/blog/cart-abandonment-push-and-email): Fire one well-timed reminder after someone leaves a cart, deep-link them back, and cap how often it can repeat.
- [Automated onboarding emails that know when to stop](https://retainza.com/blog/automated-onboarding-emails): Trigger a welcome sequence from signup, delay each step, and drop people the moment they finish onboarding.
- [Trial-ending reminders without a 3am push](https://retainza.com/blog/trial-ending-reminders): Segment on days remaining, remind across push, email and in-app, and respect quiet hours so a reminder never arrives overnight.
- [Bring your own FCM: why you should keep the credential](https://retainza.com/blog/bring-your-own-fcm): If a vendor owns your Firebase project, they own your quota and your sending reputation. Here is why that is a bad trade.
- [Deep links that open the right screen](https://retainza.com/blog/deep-link-routing): A notification that dumps someone on the home feed wasted the tap. Carry a route, a screen plus parameters, and let your own navigator handle it.
- [In-app messages: modal, banner, sheet, pick one on purpose](https://retainza.com/blog/in-app-message-layouts): Five layouts cover most jobs. The mistake is using the loudest one for everything, or sending in-app at the same moment as a push.
- [Frequency caps and quiet hours are the real retention features](https://retainza.com/blog/frequency-caps-and-quiet-hours): The most underrated part of an engagement stack is the ability to not send. Caps, cooldowns and quiet hours keep the channel alive.
- [What is SMTP, and why does your app still need it?](https://retainza.com/blog/what-is-smtp): SMTP is the protocol that actually moves email between servers. Here is what it does, what it does not do, and how it differs from an email API.
- [Mobile app retention: what actually moves the number](https://retainza.com/blog/mobile-app-retention-strategies): Most retention advice is about notifications. The bigger levers are onboarding, timing and knowing when not to send. A practical guide.
- [How push notifications actually work on Android and iOS](https://retainza.com/blog/how-push-notifications-work): A clear walkthrough of the push pipeline, tokens, FCM, APNs, and what happens between your server calling send and a notification appearing.

## More pages

- https://retainza.com/privacy

## Optional

- [Everything above in one file](https://retainza.com/llms-full.txt)
- [Sitemap](https://retainza.com/sitemap.xml)