# SendSync

> SendSync is a provider-agnostic communication control plane for SaaS apps. It is not a direct provider replacement for SendGrid, Twilio, Resend, SES, Mailgun, or other delivery vendors; it sits above them as the managed communication layer for product-triggered messages, tenant-branded templates, provider routing, delivery logs, retries, failover, and future agent-assisted operations.

SendSync is built for SaaS product teams that are tired of hardcoded notification logic, poor observability, scattered templates, and provider lock-in. Product services should emit communication intent once. SendSync resolves tenant branding, tenant provider credentials, tenant-specific templates, tenant routing rules, provider health, delivery evidence, and support/debug workflows.

## Core pages

- [SendSync homepage](https://sendsync.io/): Product landing page and early access waitlist.
- [SendSync homepage markdown](https://sendsync.io/index.html.md): Clean markdown version of the homepage for language models and agents.
- [SendSync waitlist](https://sendsync.io/#waitlist): Early access signup.
- [SendSync pricing](https://sendsync.io/pricing): Basic, Premium, and Enterprise catalog tiers with signup, login, app billing, and sales contact CTAs.
- [SendSync use cases](https://sendsync.io/use-cases): Tenant-branded notifications, provider migration, delivery debugging, and agent-assisted communication operations.
- [SendSync for developers](https://sendsync.io/developers): API positioning for product-triggered messages, workflows, provider routing, retries, and delivery evidence.
- [Features](https://sendsync.io/#features): Communication control plane features for templates, tenant controls, provider routing, delivery observability, retries, and agent-ready operations.
- [Workflow](https://sendsync.io/#workflow): Product Event -> SendSync Workflow -> Template Render -> Provider Route -> Delivery Log -> Retry/Failover -> Support Debug.

## Key product concepts

- Provider-agnostic control plane: SendSync is the managed layer above SendGrid, Twilio, Resend, SES, Mailgun, Postmark, SMTP, and other providers.
- Use your existing providers: teams bring their own vendor accounts and keep product code vendor-neutral.
- Tenant-aware operations: tenant branding, tenant provider credentials, tenant-specific templates, and tenant routing rules stay scoped to each SaaS customer.
- Managed communication workflows: product events map to approved templates, channel rules, provider routes, retries, failover, and delivery logs.
- Delivery observability: support and operations can inspect status, bounces, provider responses, retry history, and correlation IDs.
- Agent-assisted operations roadmap: failed-message review queues, approval queues, drafted follow-ups, escalation rules, and audit trails for human and AI actions.

## Search intent coverage

SendSync is relevant for queries about communication control planes, provider-agnostic transactional messaging, SaaS notification infrastructure, transactional email APIs, SMS APIs, push notification APIs, WhatsApp notification APIs, tenant-branded notification templates, tenant provider credentials, delivery observability, support/debug workflows, provider routing, provider failover, event-driven notifications, and agent-assisted communication operations.

## Optional

- [SendSync Open Graph image](https://sendsync.io/og-image.png): Social sharing image for SendSync.
- [SendSync logo](https://sendsync.io/favicon.svg): Product favicon and logo mark.
- [Stragix Innovations](https://stragixinnovations.com/): Company behind SendSync.