Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Palumb review

Free#14 of 15 in Notification Infrastructure Software

Code-defined workflows with retries and self-hosting, using your own sending providers.

7.1/10Editor score
Palumb7.1 Visit Palumb

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Palumb gives developers a way to define notification workflows in code, with a managed cloud option or a self-hosted stack. It is aimed at teams that want notification logic in their own codebase and need workflows to wait for events or delays, collect events into digests, and fan out messages to topic subscribers. Its SDKs cover TypeScript, PHP, .NET, Python, Go, Java, and Rust, while dashboard, REST API, and MCP server access provide additional ways to interact with the service.

Durability and delivery controls are central to the product. Workflows can wait across crashes and deployments; retries use backoff, and duplicate-send protection reuses the same Message-ID. Palumb also records accepted, failed, and bounced delivery outcomes. Documented channels include email, SMS, Telegram, Slack, and push, and event collection windows support digest notifications. These features make it relevant to teams with event-driven notification logic, rather than only straightforward one-off sends.

Palumb sends through providers and credentials supplied by the customer, so teams need to bring their own sending setup. The ongoing beta is free, and the published description says it has no end date. Teams can choose managed cloud or self-hosting; the self-hosted stack uses the application, Restate, and PostgreSQL, and the delivery path is published under AGPL-3.0. Palumb is a fit for developers who value code-defined, durable workflows and want deployment choice. Teams seeking provider-supplied sending capacity or a workflow setup that does not rely on code should consider a different approach.

Palumb pros and cons

  • Where it wins
    • Waits for events or delays across crashes and deployments
    • Retries with backoff and duplicate-send protection
    • Offers SDKs for TypeScript, PHP, .NET, Python, Go, Java, and Rust
  • Where it doesn't
    • Sending depends on customer-provided providers and credentials
    • Workflow logic is defined in code rather than only through a dashboard
    • Self-hosting requires the application, Restate, and PostgreSQL

Palumb fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update