← Back to home
Comparison · Infra & APIs

Dokku vs Resend

A side-by-side editorial comparison of Dokku and Resend — release velocity, themes, recent moves, and the top alternatives to consider.

Dokku vs Resend: at a glance

FeatureDokkuResend
SectorInfra & APIsInfra & APIs
Velocity score5.06.3
Sparks · 30d01
Top themespaas, kubernetes, k3s, cli-automationagent-integrations, mcp, oauth, developer-experience
Last editorial update5d ago2h ago
WebsiteVisit →Visit →

What is Dokku?

Dokku is quietly turning into a k3s front-end with a JSON-first CLI.

The 0.38 patch line keeps shipping small releases with real features in them. v0.38.27 drops the local-image requirement for k3s deploys, reports Traefik DNS-provider variables as global keys, adds storage directory mode and removal flags, and introduces a vector-cron-sink so scheduled cron output has somewhere to go. It follows v0.38.26, which brought wildcard domains, custom cert issuers, and kernel sysctls to the k3s scheduler.

Read the full Dokku trajectory →

What is Resend?

Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.

Most recent entries are about who or what can call Resend rather than about email delivery itself: OAuth 2.1 with PKCE, a remote MCP server tracking the current spec, a Codex plugin, a one-click Claude connector, and support for the Agent Plugins Standard. The email product still gets attention — suppressions, template folders, a compatibility checker in the code editor, and now cancellation of scheduled or queued Broadcasts from the API. Entries are terse one-liners, so the shipping cadence reads faster than the surface area actually changing.

Read the full Resend trajectory →

Dokku vs Resend: editorial side-by-side

D
Dokku
INFRA · APIS
5.0

Dokku is quietly turning into a k3s front-end with a JSON-first CLI.

◆ Current state

The 0.38 patch line keeps shipping small releases with real features in them. v0.38.27 drops the local-image requirement for k3s deploys, reports Traefik DNS-provider variables as global keys, adds storage directory mode and removal flags, and introduces a vector-cron-sink so scheduled cron output has somewhere to go. It follows v0.38.26, which brought wildcard domains, custom cert issuers, and kernel sysctls to the k3s scheduler.

◆ Where it's heading

Two threads run through almost every release: closing the gap between the k3s scheduler and the classic single-host path, and making every command machine-readable. The k3s work has moved from basic scheduling to the operational details — certificates, DNS, sysctls, and now deploys that no longer assume a local Docker image — which is the sequence a project follows when it expects the Kubernetes path to become the default rather than the alternative.

◆ Prediction

Expect the remaining k3s parity gaps to keep closing one release at a time, and expect the logging work started with vector-cron-sink to extend to other task types that currently have no sink.

R
Resend
INFRA · APIS
6.3

Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.

◆ Current state

Most recent entries are about who or what can call Resend rather than about email delivery itself: OAuth 2.1 with PKCE, a remote MCP server tracking the current spec, a Codex plugin, a one-click Claude connector, and support for the Agent Plugins Standard. The email product still gets attention — suppressions, template folders, a compatibility checker in the code editor, and now cancellation of scheduled or queued Broadcasts from the API. Entries are terse one-liners, so the shipping cadence reads faster than the surface area actually changing.

◆ Where it's heading

Resend is treating agents as the next class of sending client and building the authorization and discovery plumbing they need before that traffic arrives. The progression is legible: authenticate third parties (OAuth), be callable (MCP), be installable per vendor (Codex, Claude), then be installable by standard. The Cancel Broadcast API is the first sign of the next phase — once non-human callers can schedule sends, the ability to revoke one programmatically stops being a convenience.

◆ Prediction

Authorization and discovery are covered and reversibility has now started; the remaining gap is what an agent is permitted to send in the first place, so scoped per-agent sending limits or approval gates before dispatch are the natural next piece.

Alternatives to Dokku and Resend

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Dokku or Resend.

See all Dokku alternatives → · See all Resend alternatives →

Recent activity from Dokku and Resend

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoResendCancel Broadcast API
  2. 6d agoResendAgent Plugin Support
  3. 7d agoDokkuk3s deploys drop the local-image requirement; cron output gains a sink
  4. 7d agoResendEmail Compatibility Checker
  5. 10d agoDokkuWildcard domains and custom cert issuers land on k3s
  6. 13d agoResendRemote MCP Supports the 2026-07-28 Spec
  7. 16d agoResendTemplate Folders
  8. 22d agoResendEmail Suppressions
  9. 28d agoDokkuCommand injection fix, plus per-app Let's Encrypt on k3s
  10. 1mo agoDokkuDependency bumps and buildpack documentation
  11. 1mo agoDokkuCertificate CN parsing fixed for OpenSSL 3.x
  12. 1mo agoDokkuJSON output spreads across reports and plugin lists

Frequently asked questions

What is the difference between Dokku and Resend?

They serve adjacent needs but don't currently overlap on shipped themes. Resend is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Dokku better than Resend?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Resend is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Dokku?

Top Dokku alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dokku alternatives" section above for the current picks, or visit /alternatives/dokku for the full list with editorial commentary on each.

What are the best alternatives to Resend?

Top Resend alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Resend alternatives" section above for the current picks, or visit /alternatives/resend for the full list with editorial commentary on each.