# Palumb > EU-sovereign notification orchestration. Workflows written in your own codebase, rendered by your own template engine, delivered through your own provider. Operated in the EU under a single EU jurisdiction, or self-hosted: the delivery path is open source. This file helps language models discover the most useful content on this site. ## Home - [Durable notification workflows, in your own code.](https://palumb.com/home.md): Notification workflows in your own codebase, rendered by your engine, delivered by your provider. Operated in the EU under EU law alone. ## About - [I build software you can walk away from.](https://palumb.com/about.md): Adriano Foschi: twenty years writing software and running the servers under it. Why I built Palumb, and why no vendor lock-in shows up in the product. ## Blog - [The Palumb blog: what ships, what changed, and what we decided.](https://palumb.com/blog.md): What we decided and why, what the beta ships with, and what is not there yet. Product news from the person building Palumb. - [Sovereignty is recursive, and my suppliers are my customers](https://palumb.com/blog/sovereignty-is-recursive.md): Jurisdiction follows the company, so it follows the whole chain. What I verify, what no page can, and why my sub-processor list read backwards is a list of the customers I want. - [What the beta ships with, and what it does not](https://palumb.com/blog/what-the-beta-ships-with.md): The waitlist is open. What is in the beta, what is declared for later, what one run means, and the one thing a Palumb workflow will never do. - [Introducing Palumb, and why I am building it](https://palumb.com/blog/why-i-am-building-palumb.md): The first post: who is behind Palumb, the problem it came out of, and why the control stays on your side of the line. ## Compare - [Who you should pick, including when it is not us.](https://palumb.com/compare.md): Six comparisons, each conceding first. The four notification vendors Palumb competes with, plus the in-house cron that beats every one of them for most teams. - [Palumb vs building it yourself: most teams should build this themselves](https://palumb.com/compare/build-it-yourself.md): Most teams should build notifications themselves. What changes that is waiting, tenants, and the record of every attempt. - [Palumb vs Courier: notification workflows that stay in your own code](https://palumb.com/compare/courier.md): Courier has the widest channel list and the cleanest prices here. It is a US corporation, its EU datacenter is Enterprise-only, and you cannot self-host. - [Palumb vs Knock: notification workflows that stay in your own code](https://palumb.com/compare/knock.md): Knock bills a message per channel and hosts your workflows as JSON in the US. Palumb bills the run, keeps it in your repository, and runs in the EU. - [Palumb vs MagicBell: notification workflows that stay in your own code](https://palumb.com/compare/magicbell.md): MagicBell is an in-app inbox whose workflow engine cannot wait for an event, and it bills one delivery per channel per user. Palumb counts the run once. - [Palumb vs Novu: notification workflows that stay in your own code](https://palumb.com/compare/novu.md): Novu is cheaper per run but meters workflows, seats, environments and history. It is an Israeli company, and its self-hosted edition is a reduced build. - [Palumb vs SuprSend: notification workflows that stay in your own code](https://palumb.com/compare/suprsend.md): SuprSend gates digest and preferences behind a $275 plan, bills per channel and processes data in the US. It also has the multi-tenancy Palumb has not built. ## Contact - [Write to us, and a person answers.](https://palumb.com/contact.md): Write to the person behind Palumb: a form or an email address, both answered by hand. No ticket queue, no chatbot, no autoresponder. ## Eu-jurisdiction - [The questions your legal team will ask.](https://palumb.com/eu-jurisdiction.md): Residency is where the data sits; sovereignty is which law reaches the company holding it. What we can answer for procurement, and what we cannot yet. ## Features - [Everything Palumb supports.](https://palumb.com/features.md): Multi-step workflows, durable waits, waiting on an external signal, sends on a schedule, digests, fan-out, retries and idempotent replay, through your own provider. ## Open-source - [Open source, the whole delivery path.](https://palumb.com/open-source.md): Open source notification orchestration: the core is AGPL-3.0, the SDK MIT. Run the whole delivery path on your own EU infrastructure, or let us operate it. ## Pricing - [You pay for what we run: nothing else is metered.](https://palumb.com/pricing.md): Pay per workflow execution, per recipient. Free up to 500 a month, then €19, €49 or €149. Unlimited workflows, and no feature gates. ## Privacy - [Privacy notice](https://palumb.com/privacy.md): What palumb.com collects when you join the waitlist: your email address, and nothing else. No cookies, no tracking pixels, no identifier stored. ## Self-hosting - [What you actually run, if you run it yourself.](https://palumb.com/self-hosting.md): Self-host Palumb on three services: the application, Restate and PostgreSQL. What you run, what you take on, and why we would not do it. ## Sub-processors - [Sub-processors](https://palumb.com/sub-processors.md): Every third party that processes data on Palumb's behalf, what it does, where it processes, and who owns it. Your sending provider is not one. ## Terms - [Terms of service](https://palumb.com/terms.md): Who publishes palumb.com, and the terms of the beta, published before the service exists so that joining the waitlist is a decision made knowing them. ## Use-cases - [Real problems, and the code that solves them](https://palumb.com/use-cases.md): Worked notification problems with the code that solves them. The problem first, then the workflow that answers it, in full. - [How do you nudge a user who signed up and never came back?](https://palumb.com/use-cases/activation-reminders.md): Three reminders over a week, each one preceded by a wait. The first sign of life ends the sequence, and the messages still to come never go out. - [How do you stop sending one email per comment?](https://palumb.com/use-cases/comment-bursts.md): The first comment opens a five minute window and the ones after it land in the same run. One email goes out with the lot, and the next burst gets its own window. - [How do you follow an order all the way to feedback?](https://palumb.com/use-cases/order-updates.md): Confirmation on the spot, tracking when the parcel actually ships, and a feedback request three days after that. One workflow, and the middle step waits for a real event instead of guessing. - [How do you warn before a trial ends, and stop the moment they upgrade?](https://palumb.com/use-cases/trial-ending.md): Nothing goes out for eleven days. Then three warnings, each one closer to the deadline, and an upgrade at any point stops the rest on the spot. - [How do you chase an unpaid invoice without chasing someone who paid?](https://palumb.com/use-cases/unpaid-invoice.md): A reminder when the invoice falls due, then a week of waiting that the payment ends on the spot. If it never comes, a final notice goes to the account owner. - [How do you send a weekly summary on a fixed schedule?](https://palumb.com/use-cases/weekly-summary.md): One run stays open for the week, gathers each deadline as your app reports it, and sends a single summary on Monday. Then it opens next week's window itself. ## Waitlist - [The beta is free, open, and it does not end.](https://palumb.com/waitlist.md): The Palumb beta is free, open to everyone, and it does not end: it is the free tier. No card, no sign-up form, and keys are issued by hand.