Simple, transparent plans.
Choose the plan that fits your business. Toggle yearly billing to save 20% instantly across all premium tiers.
Starter
For personal blogs, side projects, and basic live support.
- 1 Widget instance
- 100 conversations / mo
- Basic visitor inbox
- Snooze conversations
- Native WebRTC voice calling
- Sound notifications
Growth
For growing makers and small business customer workflows.
- 2 Widget instances
- 1,000 conversations / mo
- 1 Centralized AI Employee
- WebRTC video calling
- 2 Active workflows
- Email notification alerts
Pro
For fast-scaling startups and dedicated support teams.
- 5 Widget instances
- 5,000 conversations / mo
- 3 Centralized AI Employees
- WebRTC screen sharing
- 5 Active workflows
- Slack & MS Teams alerts
- CSAT email surveys
Business
For custom scale, developer webhooks, and high volumes.
- Unlimited widgets
- Unlimited conversations
- Unlimited AI Employees
- Full AI fallback chain router
- Unlimited workflows
- Full-text search (FTS)
- Outbound HMAC webhooks
- 10 Ecosystem integrations
Enterprise
For high security, absolute reliability, and custom tools.
- Everything in Business
- Dedicated support & SLAs
- Custom STUN/TURN servers
- Audit logs telemetry router
- 2FA TOTP administration
- Custom integration services
Frequently Asked Questions
Can I upgrade or downgrade my plan at any time?
Yes! You can upgrade or downgrade instantly inside your dashboard Settings page under the Billing section. All payments are securely processed via Razorpay.
How are automated workflow limits enforced?
Our limits are strictly enforced server-side. Starter includes 0 workflows; Pro includes up to 5 active workflows; Business includes unlimited active automation workflows.
Can I connect my own custom AI model endpoint?
Absolutely! Under App Settings, you can configure a custom fallback endpoint with OpenAI-compatible API base URLs and keys, or add multiple API providers for automatic load balancing.
How does the Outbound Webhooks HMAC signing work?
When Pulse fires a webhook payload, it hashes it using SHA-256 HMAC and attaches it to the 'X-Pulse-Signature-256' header. Receivers can verify the signature using the secret key.