# Notifiable

> Developer-first notification infrastructure. Connect an app, register devices with a public key, then send, schedule, and automate notifications. A public key cannot send. A server API key can.

Marketing site: https://notifiable.sh
Product docs for agents: https://docs.notifiable.sh/llms.txt

## Prefer docs Markdown

For integration, SDKs, and the HTTP API, use the documentation llms index and the matching SDK guide:

- [Docs llms.txt](https://docs.notifiable.sh/llms.txt)
- [AI agents](https://docs.notifiable.sh/ai-agents.md)
- [Expo](https://docs.notifiable.sh/expo.md)
- [React Native](https://docs.notifiable.sh/react-native.md)
- [Flutter](https://docs.notifiable.sh/flutter.md)
- [Swift](https://docs.notifiable.sh/swift.md)
- [Kotlin](https://docs.notifiable.sh/kotlin.md)
- [Public API](https://docs.notifiable.sh/api/index.md)

## Marketing pages

- [Home](https://notifiable.sh) — Product overview and SDK quick starts.
- [Pricing](https://notifiable.sh/pricing) — Free, Starter, Pro, and Scale.
- [Resources](https://notifiable.sh/resources) — Guides for developers.

## Features

- [Subscribers](https://notifiable.sh/features/subscribers) — A Notifiable subscriber is one device that can receive a notification. The SDK registers it with a public key, and that key cannot send.
- [Notifications](https://notifiable.sh/features/notifications) — Compose a Notification once. Send it now, at a fixed time, or when that time arrives in each subscriber’s timezone. A public key cannot send.
- [Automations](https://notifiable.sh/features/automations) — Let an event send the next notification. A Notifiable automation stays a draft until you publish it.
- [Webhooks](https://notifiable.sh/features/webhooks) — Notifiable webhooks tell your server when a notification is delivered, fails, opens, or is clicked. Every call is signed.

## Resources

- [How to Add notifications to a React Native App (2026 Guide)](https://notifiable.sh/resources/react-native-push-notifications) — A practical guide to React Native notifications: ask the operating system, save the device with a public key, and send from a server API key.
- [Firebase Cloud Messaging (FCM) vs APNs: What's the Difference?](https://notifiable.sh/resources/fcm-vs-apns) — FCM vs APNs is a difference of tokens, credentials, and who delivers the message. Here is what each system expects, and what you can stop operating.
- [Best Notification Services for Developers in 2026](https://notifiable.sh/resources/best-push-notification-services) — The best Notification services are the ones that hide tokens and delivery without hiding how a message is sent. Here is how to choose in 2026.
- [How to Send notifications Without Managing FCM or APNs Infrastructure](https://notifiable.sh/resources/push-notifications-without-firebase) — You can send notifications without Firebase as the system you operate. Keep the permission prompt. Hand the token, the audience, and the delivery to one API.

## Legal

- [Privacy Policy](https://notifiable.sh/privacy-policy)
- [Terms of Service](https://notifiable.sh/terms-of-service)
- [Cookie Policy](https://notifiable.sh/cookie-policy)
- [Refund Policy](https://notifiable.sh/refund-policy)
- [Security Disclosure](https://notifiable.sh/security-disclosure)

## Rules for agents

1. Fetch the docs llms.txt and the matching SDK Markdown guide before writing code.
2. Work in development unless asked for production.
3. Never put a server API key in client code, logs, commits, or chat.
4. Do not invent public keys or endpoints.
5. Do not send notifications or change production without approval.