Fromly
vs

Fromly vs Plunk

Plunk and Fromly charge the same $0.001 per email, Plunk keeps 1,000 free emails every month where Fromly offers them once at sign-up, and Plunk adds open source, self-hosting, inbound email and published SDKs. Fromly is built around your Supabase users and Stripe billing, which arrive on their own instead of being sent from your code.

At a glance

FromlyPlunk
Best forSaaS teams on Supabase and Stripe who want emails driven by product data.Developers who want open source, or to host their email platform themselves.
Pricing$0.001 per email, first 1,000 free$0.001 per email, free plan up to 1,000
Starts atFree, then $0.001 per emailFree, then $0.001 per email
ContactsUnlimitedUnlimited

Fromly vs Plunk pricing

Pick a monthly volume to see both bills. Plunk's prices are the ones on its pricing page on October 10, 2026.

10,000

Fromly

$0.001 per email, first 1,000 free

$10

per month

Plunk

$0.001 per email, free plan up to 1,000

$10

per month

Same price at this volume.

How Fromly charges

  • Your first 1,000 emails are free. After that, every email costs $0.001, prepaid. Unlimited contacts.

How Plunk charges

  • Free up to 1,000 emails a month, with Plunk branding on every email.
  • The paid plan costs $0.001 per email, removes the branding and lets you set a monthly spend cap.
  • Contacts are unlimited on both plans, and every feature is on every plan.
  • Self-hosting is free: the code is open source and runs with Docker Compose.

Features compared

What each tool includes today. "Not stated" means Plunk's pages do not say, not that it is missing.

FeatureFromlyPlunk

Pricing

  • Billed on emails sent, not contacts$0.001 per email on the paid plan.$0.001 per email on the paid plan.
  • Unlimited contactsYesYes
  • Free plan1,000 free emails at sign-up, no credit card.1,000 emails a month, with Plunk branding.

Sending

  • Campaigns to a filtered audienceFilter by tags, plan, MRR or custom properties.To the full list or a segment.
  • Scheduled and spread-out sendsYesYes
  • A/B testingNoNot stated
  • Transactional email APITemplates with variables and idempotency keys.API and SMTP.
  • AttachmentsNoNot stated

Automations

  • Visual automation builderYesYes
  • Triggered by product and billing eventsSign-ups, Stripe events, tags and custom events from the API.Any event your code sends.
  • Conditions and branchesYesYes
  • Wait until an event happensNoNot stated

Data and integrations

  • SupabaseConnected in one click: new sign-ups arrive in real time, plus an hourly sync.Not stated
  • StripeMRR, plan and lifecycle on every contact, as tags you can target.Not stated
  • Other billing tools (Paddle, Lemon Squeezy…)NoNot stated
  • Zapier or n8nNoNot stated
  • CSV importYesNot stated
  • Signup forms and landing pagesNoNot stated

Developers

  • REST APIScoped API keys for contacts, events, emails, campaigns and flows.Yes
  • MCP server for AI agentsYesTwenty-three tools, with a read-only mode.
  • Official SDKBuilt, not yet published on npm.Node.js, Python and more.
  • Outgoing webhooksNoNot stated

Deliverability

  • Your own domain with SPF, DKIM and DMARCYesDKIM, SPF and DMARC set up automatically.
  • One-click unsubscribe (Gmail and Yahoo rules)YesNot stated
  • Campaigns pause on high bounce ratesYesNot stated
  • Reputation kept apart from other customersEach workspace sends under its own reputation.Not stated
  • Dedicated IPNoNot stated

Analytics and team

  • Opens, clicks and bounces per contactYesOpens, clicks, bounces and unsubscribes.
  • Revenue attributionNoNot stated
  • Team membersRoles exist; inviting teammates is coming.Not stated

Other channels

  • SMSNoNot stated
  • Shared inbox for repliesNoInbound email delivered to your app as a webhook.

Fromly or Plunk: which one should you choose?

Choose Plunk if

  • You want open source code you can read, fork or host on your own servers
  • You want to receive email on your domain and get replies as webhooks
  • You want an official Node SDK or SMTP for an existing app today
  • You would rather send every event from your own code than connect a database

Choose Fromly if

  • Your users live in Supabase and you want new sign-ups to arrive on their own, without setting up webhooks
  • You want Stripe MRR, plan and lifecycle on every contact, ready to target
  • You want campaigns to pause on their own when bounces climb, with each workspace sending under its own reputation
  • You want a smaller tool you can set up in an afternoon

How to switch from Plunk to Fromly

  1. 1Export your contacts from Plunk.
  2. 2Import them in Fromly as a CSV file: map columns to tags and custom properties as you go.
  3. 3Connect Supabase and Stripe so new users and billing changes keep flowing in.
  4. 4Verify your sending domain (SPF, DKIM and DMARC), then rebuild your workflows as Fromly flows.
  5. 5Point your transactional calls and custom events at the Fromly API.

Plunk checked on October 10, 2026 from pricing, home. Prices change: check the vendor's page before deciding.

FAQ

Fromly vs Plunk: questions, answered

Is Fromly cheaper than Plunk?
No. Both charge $0.001 per email on the paid plan, so 10,000 emails cost $10 and 100,000 cost $100 on either, but Plunk's free plan gives 1,000 emails every month where Fromly offers 1,000 once at sign-up. Both have unlimited contacts. Plunk puts its branding on free emails.
Which one is open source?
Plunk. It is licensed under AGPL-3.0 and can be self-hosted with Docker Compose, with no per-email cost. Fromly is a hosted service.
Does Plunk connect to Supabase and Stripe?
Plunk's pages do not mention a built-in Supabase or Stripe connection: its workflows start from events your code sends. Fromly connects to Supabase in one click, receives new sign-ups in real time with an hourly sync as a safety net, and puts Stripe MRR, plan and lifecycle on every contact.
Do both work with AI agents?
Yes. Plunk has an MCP server with twenty-three tools and a read-only mode. Fromly also has an MCP server, so agents like Claude or Cursor can manage contacts, emails, campaigns and flows.
Can I move from Plunk to Fromly?
Yes. Export your contacts from Plunk and import the file in Fromly, mapping columns to tags and properties. Unsubscribed contacts should stay unsubscribed: import them with that status or leave them out. Then rebuild your workflows and point your API calls at Fromly.

Turn your signups into customers with email

Connect Supabase and Stripe, let your agent draft your first flow, and send your first 1,000 emails for free.

Start with 1,000 free emails