Yes! You can configure multiple providers per channel and Zyphr will automatically failover between them. For example, use AWS SES as your primary email provider with SendGrid as a backup.

Simply configure the new provider in your Zyphr dashboard and update the priority order. No code changes needed — your API calls stay exactly the same.

Yes, you need your own accounts with the providers you want to use. Zyphr connects to them using your API keys, giving you full control over your accounts and billing.

Zyphr monitors provider health in real-time. If a provider fails, messages are automatically routed to your backup provider within seconds. You can configure failover priorities per channel.

The Zapier integration is coming soon! Once available, you'll be able to connect your Zyphr API key in Zapier to use Zyphr as a trigger (react to email events, new users, etc.) or an action (send notifications from any of Zapier's 7,000+ apps). No code required.

The Zyphr MCP Server is an npm package (@zyphr-dev/mcp-server) that turns Zyphr into a tool any MCP-compatible AI client can call — Claude Code, Cursor, Cline, Claude Desktop, and others. Drop a single config block into your client, restart it, and the AI can install the SDK into your project, write the code, send messages, render templates, and debug webhooks without you ever leaving your editor.