Overview
How Pushizo works — the organization, app, channel, user and subscription model; which guide to start with.
In Pushizo, an organization contains one or more apps. Each app is connected to channel credentials (APNs, FCM, HMS, VAPID, SMTP/SES/Resend, Twilio/Netgsm, WhatsApp, RCS); client SDKs work with the App ID only and register devices as subscriptions. Your server sends messages with an API key, updates user data, and receives delivery events via webhooks.
Your server ──(API key)──▶ api.pushizo.com/v1 ──▶ queue ──▶ providers (APNs/FCM/HMS/Web Push/SMTP/SES/Twilio/…)
▲ │
Client SDK ──(App ID + ownership)─────────┘ ▼
device / mailbox / phone ──▶ received/opened feedback
Webhooks ◀──(Pushizo-Signature)──────── delivery, subscription, user, event, campaign, journey eventsWhich guide should you start with?
Quickstart
Sign-up, app, channel, SDK and first test push — the common flow for all platforms (≈15 minutes).
Web
Browser push via script tag or npm; service worker and permission prompt.
iOS
APNs key, SPM/CocoaPods, AppDelegate and Notification Service Extension.
Android
Firebase service account, Gradle dependency, Android 13+ permission.
Flutter
The pushizo_flutter plugin, native Android/iOS setup steps.
React Native, Capacitor, Cordova, MAUI, Unity
Common setup order for bridges that wrap the native SDKs.
Server side
API key, your first POST /v1/notifications, Node/PHP/Python/Go/Java/.NET/Ruby SDKs.
Availability
Available today: Web script tag (/sdk-web/PushizoSDK.js), Google Tag Manager, WordPress, REST API (cURL), npm 0.1.0, Maven Central 0.1.0, Go module, iOS SPM, NuGet Pushizo 0.1.0, Packagist pushizo/pushizo-php 0.1.0, pub.dev pushizo_flutter 0.1.0, PyPI pushizo 0.1.0, RubyGems pushizo 0.1.0 and OpenUPM com.pushizo.unity 0.1.0. CocoaPods and NuGet Pushizo.Maui are not published yet; until then you can build them from the monorepo. The SDK Setup wizard in the dashboard shows the same distinction with a "Coming soon" badge.
Environments
| Production (pushizo.com) | Self-hosted | |
|---|---|---|
| Dashboard | https://app.pushizo.com | APP_URL |
| API | https://api.pushizo.com | API_URL / PUBLIC_API_URL |
SDK apiUrl | optional (default) | required |
| Data region | chosen when creating the organization (if EU/TR is configured) | single cell |
For local development, npm run dev in the monorepo starts the API (http://localhost:4000, OpenAPI at /openapi.json, interactive docs at /docs), the dashboard (http://localhost:3100) and the worker; this site runs at http://localhost:3300. Seed login: admin@pushizo.test / Pushizo!2026.
Next steps
- Channel setup and provider requirements: Channels
- User identity, tags and segments: Users & segments
- Sending API and campaigns: Messaging
- Plans, quotas and billing: Plans and quotas
Pushizo documentation
Pushizo developer documentation — getting started, channel, SDK, API and operations guides for the multichannel push, email, SMS, WhatsApp, RCS, in-app notification and customer engagement platform.
Quickstart
Sign-up, app creation, channel setup, SDK installation and your first notification — a test push in 15 minutes.