Sendy

Sendy is built for bulk/marketing sends via SES; it is not a transactional email API product.

Sendy is not itself an SMTP relay — it sends through a connected provider (natively Amazon SES, or SendGrid/Mailjet/Elastic Email).

HTTP POST-based API, not strictly RESTful.

Rules engine can trigger a webhook, e.g. when an autoresponder is sent.

Time-interval drip campaigns, 'send annually', and 'send on date' autoresponders with segment targeting; no visual multi-branch workflow builder.

Segment-based targeting and exclusion rules for campaigns and autoresponders.

Not a built-in feature as of this check; long-requested by users on the official forum.

No native landing-page builder; third-party builders (OptimizePress, Growform, Carrd) connect via embed code.

Native subscribe-form HTML snippet plus a hosted subscription page URL.

Built-in bounce and complaint handling; relies on the connected SES/SMTP provider for sender reputation and inbox-placement tooling.

Dedicated sending IPs are a function of the connected SES/SMTP account, not a Sendy feature itself.

No native Shopify app; connected via third-party automation platforms (Zapier, Make, n8n).

Third-party WordPress/WooCommerce plugins connect to Sendy's API; not a first-party integration.

Third-party plugins connect to Sendy's API; not a first-party integration.

No evidence of this feature found, but absence was not positively confirmed by a first-party source. See reports/needs-verification.md.

No native ecommerce platform sync was found, which would be required for cart-abandonment triggers, but absence was not positively confirmed by a first-party source. See reports/needs-verification.md.

No information found either way. See reports/needs-verification.md.

Official forum plus direct email; support covers only the latest software version.

Sendy has no free plan — one-time paid license only.

Self-hosted: Sendy Ltd does not process end-customer subscriber data, so a traditional vendor DPA relationship may not apply — but no first-party statement confirming this could be verified. See reports/needs-verification.md.

Self-hosted architecture: the operator deploys Sendy on their own server, so data residency is entirely determined by where that server is hosted.

No first-party statement found. A SOC 2 report would typically apply to whichever hosting provider the operator chooses, not to Sendy Ltd itself. See reports/needs-verification.md.