Marketing + transactional

Plunk Cloud

Hosted open-source platform for transactional email, campaigns and automation.

Official documentation ↗Add to a comparison →

WHEN TO CONSIDER IT

Consider when campaigns, automation and an open-source platform fit the project.

WHAT TO CHECK FIRST

Attachments use double credits. Inbound messages are dropped when a billing cap is reached; hosted SLA and dedicated-IP terms need confirmation.

Editorial interpretation of the sourced facts; not hands-on testing.

Pricing

Billing model: Free and usage-based paid optionsSource ↗
Selected paid rateSelected plans, not equivalent baskets. USD unless stated; taxes, add-ons and regional terms may differ.: USD 0.001/email (USD 1/1,000) on hosted paid plan.Source ↗
Free tier / trial: 1,000 emails/month; Plunk branding.Source ↗
Overage: Usage-based paid sending at USD 0.001/email.Source ↗
Data / attachment charges: Emails with attachments cost 2 credits instead of 1, independent of attachment size.Source ↗
What counts as an email: Transactional/campaign sends per recipient; workflow sends and inbound emails share usage.Source ↗
Credit expiry: Usage limits reset each billing period; paid plan is metered, without a monthly subscription fee.Source ↗

Reliability

Official incident historyProvider-reported status, not independent monitoring or a live health indicator.: Official status pageOpen ↗
Contractual uptime SLAA service commitment, not observed uptime. Eligibility, exclusions and credit rules differ.: Not stated in reviewed docs
Review details
No email-specific numerical contractual uptime commitment was established in the reviewed materials.
Reviewed 2026-09-08
Reviewed source 1 ↗Reviewed source 2 ↗
Measured uptime: Not measured
Measured delivery latency: Not measured
Measured inbox placement: Not measured

Sending & features

HTTP API: AvailableSource ↗
SMTP relay: AvailableSource ↗
SDKs: Node.js and Python SDKs listed; REST API available.Source ↗
Templates / editor: Reusable templatesSource ↗
Webhooks: Outbound event webhooks with documented payloads and endpoint configuration.Source ↗
Inbound processing: Domain-wide inbound via MX; parsed headers, body and attachments delivered as JSON; workflow triggers supported.Source ↗
Campaigns / automation: Broadcasts, segments and event-triggered workflows.Source ↗
Analytics: Opens, clicks, bounces, unsubscribesSource ↗

Operations & security

Suppression management: Permanent bounces and complaints automatically unsubscribe contacts; soft bounces do not.Source ↗
Daily / request limits: Per-category caps supported; outbound returns 402 at cap, inbound is dropped until reset.Source ↗
Log / activity retention: Email metadata/metrics indefinite; rendered HTML 90 days; API request logs 30 days.Source ↗
Dedicated IP: Not stated in reviewed docs
Review details
Current dedicated-IP availability and eligibility were not established in the reviewed product documentation.
Reviewed 2026-09-08
Reviewed source 1 ↗Reviewed source 2 ↗
Hosting / region notes: Vendor describes hosted service as EU-hostedSource ↗
Sending domains: Custom sending domains supported; numeric domain cap not specified on pricing page.Source ↗
Sender authentication: Custom domains with DKIM, SPF and DMARC setup.Source ↗
SSO: Not stated in reviewed docs
Review details
External identity-provider SSO protocols and plan eligibility were not established for this product.
Reviewed 2026-09-08
Reviewed source 1 ↗Reviewed source 2 ↗
Support channels: Documentation, GitHub and Discord community support listed.Source ↗
Setup requirements: Verify sending domain via DNS: DKIM CNAMEs, SPF TXT and bounce MX; inbound MX is separate.Source ↗

Resources

Website: Official resourceOpen ↗
Documentation: Official resourceOpen ↗
Pricing page: Official resourceOpen ↗

Sources & review scope

Reviewed 2026-09-08. Values are taken from official materials; plan restrictions may apply. Delivery speed, observed uptime and inbox placement have not been independently measured.

Official references (8)

How this comparison is maintained →