Why Pushizo?
Why Pushizo?
Pushizo is built for teams that care where data is processed, want to run several channels from one place and need predictable costs.
In short
Pushizo is a customer messaging platform documented with OpenAPI that brings push, email, SMS, WhatsApp, RCS and in-app messages together on the same user profile and can run in the EU (Frankfurt) or TR (Istanbul) data region.
Data sources
- Your website (SDK)
- Your mobile app (SDK)
- Your server (REST API)
- Segment, Amplitude, Mixpanel
- CSV import
Pushizo
- User profiles
- Segments
- Journeys
- Templates and Liquid
- Analytics
Channels
- Push notifications
- SMS
- RCS
- In-app messages
Why Pushizo?
You choose the data region
Organization data is processed in the EU (Frankfurt) or TR (Istanbul) cell; requests that arrive at another cell are rejected.
- Region isolation with a cell architecture
- Controlled move tool between regions
- Object storage and analytics data in the same region
Self-hosting option
Pushizo is packaged with Docker Compose and a Kubernetes Helm chart. Talk to sales about running it on your own infrastructure.
- Docker Compose production configuration
- Helm chart and scale components
- Backup and monitoring scripts
Ready-made KVKK and GDPR tools
Endpoints to export, delete and anonymise user data and category-based communication preferences come out of the box.
- Data export and deletion APIs
- Data retention periods by plan
- Hosted preference center
Transparent pricing
Plan prices and limits are published openly on the site; push notifications are included in every plan.
- Free plan
- 14-day Starter trial
- Side-by-side plan comparison
Easy migration from OneSignal
The migration tool imports subscribers; most notification fields and SDK methods use the same names.
- npm run migrate:onesignal tool
- Notification fields with the same names
- Familiar SDK methods
Six channels on one platform
Push, email, SMS, WhatsApp, RCS and in-app share the same segments, templates and journey editor.
- One user profile
- Shared quiet hour and frequency rules
- One inbox
Developer-friendly
The public REST API is documented with OpenAPI; server SDKs are generated from it and an MCP server connects AI assistants.
- OpenAPI and Postman collection
- HMAC-signed webhooks
- MCP server (OAuth 2.1)
Local infrastructure for Türkiye
Netgsm SMS and iyzico payment support; a Turkish dashboard and Turkish documentation.
- Netgsm SMS provider
- Payments with iyzico
- Dashboard in English and Turkish
Comparison
Pushizo, single-channel tools and an in-house stack
This table compares product categories in general terms; it makes no claim about any specific product or price.
| Capability | Pushizo | Single-channel tools | In-house stack |
|---|---|---|---|
| Push, email, SMS, WhatsApp, RCS and in-app on one profile | Included | Usually one channel | Each channel built separately |
| Multichannel journey automation | Visual editor | Limited to the channel | Needs to be built |
| Segmentation and A/B testing | Included | Varies by product | Needs to be built |
| Choice of data region | EU (Frankfurt) or TR (Istanbul) | Depends on the vendor | Your own servers |
| KVKK/GDPR data rights endpoints | Ready-made API | Varies by product | Needs to be built |
| Encryption of provider credentials | AES-256-GCM envelope encryption | Depends on the vendor | Your team's responsibility |
| AI assistant and MCP server | Included | Varies by product | Needs to be built |
| Maintenance, scaling and provider changes | Managed by Pushizo | Managed by the vendor | Managed by your team |
Evaluate it against your own requirements
Create a free account to try every channel, or read the documentation for the technical details.