Questions, answered.

palumb is an EU-sovereign notification platform you program instead of configure. You write each notification workflow as plain TypeScript — own it, review it, test it — and palumb runs the managed, durable control plane that delivers it across email, SMS, push, in-app and webhook. The control plane and your data stay in the EU, run by an EU provider, and the core is open source and self-hostable.

Your app triggers a workflow at /v1/events; palumb runs your TypeScript workflow on its durable engine, makes the real provider calls, and records every attempt. You write the business logic behind one signed webhook; palumb holds the state, the secrets and the delivery. Neither side touches the other's job.

Developer teams — especially in the EU — who want to define notifications in code and need EU data residency. It's a strong fit if you value durable workflows, version-controlled logic and sovereignty. It's not the right tool if your notifications are authored by non-developers in a visual builder, or if EU residency genuinely doesn't matter to you.

A generic send API delivers a single message but leaves the hard parts — waiting, batching, retries, crash-safety — to you. A low-code builder owns the logic in a canvas you can't review or test. palumb keeps the logic in TypeScript you own and runs it on a durable runtime, so you get code ownership and managed durability at once, EU-sovereign by default.

Email (SMTP and providers), SMS, push (iOS, Android and web), an in-app inbox feed, and webhooks to your own endpoints. One workflow can fan out across every channel a subscriber opted into: your code names a channel kind, and palumb resolves the concrete provider, decrypts its credentials and looks up the subscriber's address.

A workflow is plain TypeScript you expose behind one signed webhook. The trigger names it directly, so there's no giant switch over event types. Inside it you can wait, batch, branch, loop and call your own APIs; it's just code you own, review and test like any other module in your repository.

palumb's runtime is durable, built on Restate: timers and state are persisted, so a workflow that says “wait an hour, then batch and send” survives a process crash or a deploy. Sends are idempotent — a retry after a crash never delivers twice. You write no checkpointing code and no idempotency keys; the runtime handles it.

palumb is built GDPR-by-design: data minimisation, EU residency and deletion on request are defaults, not add-ons. A Data Processing Agreement (DPA) and a current sub-processor list are available, and on Business and above we'll sign your paper.

In the EU — the control plane, the durable runtime and your delivery logs. By default data is resident in Paris (fr-par), run by an EU provider, with no transfer to the US. On the Custom tier you can pin a specific EU region or run dedicated.

It means EU-first, not a US service with an EU region toggle bolted on. The control plane, the durable runtime and your data all live in the EU and are operated by an EU provider — so there's no US data transfer and no foreign-jurisdiction exposure baked into the architecture.

Yes. The palumb core is open source. You can self-host the entire control plane and durable runtime on your own EU infrastructure for free — the same workflows, your hardware, zero licence cost. The managed tiers exist so you don't have to operate it yourself.

Plans are priced by active subscribers, not message volume: Free (€0), Starter (€49/mo, ~1,000 subscribers), Growth (€99/mo, ~3,000) and Business (€199/mo, ~10,000, with a signed DPA + 1-year delivery-log retention). Above ~10,000 active subscribers it's a Custom tier. Reliability is identical on every tier — EU-sovereign, guaranteed delivery — and we never meter or cap how many notifications you send. No per-seat fees; self-hosting the open-source core is free.

Install the SDK with npm i @palumb/sdk, write a workflow in TypeScript behind one signed webhook, and trigger it — you can send your first notification in about five minutes. The quickstart walks through it end to end.