Neshama
Never let a yahrzeit be forgotten.
Keep every date, every relative and every reminder in one place, on the Hebrew calendar, so the right families hear from you on the right day each year.
The free tier described on this page is in development. Joining the waitlist tells us you want it and costs nothing.
Where this stands, plainly
We would rather tell you exactly what exists than have you discover it after importing your list.
Yahrzeit tracking on the Hebrew calendar, recipients with their own timing, your own templates, and a review of every message before it sends. Delivered over WhatsApp, and it requires a connected WhatsApp channel.
The free tier: email reminders with no WhatsApp needed, CSV import of yahrzeit records, recipient groups on records, and a free record allowance. Not open for signup yet.
The problem
A spreadsheet forgets. The Hebrew calendar does not forgive.
Yahrzeit dates move against the civil calendar every year, leap years add a month, and some months lose their thirtieth day. A list of civil dates quietly drifts until a family is missed.
The date moves every year
A Hebrew date lands on a different civil date each year. Keeping civil dates in a spreadsheet means re-deriving all of them, every year, by hand.
Leap years add a month
Seven years in nineteen carry a second Adar. A date in Adar has to know which Adar it means, and a plain calendar reminder does not.
Some months lose a day
Cheshvan and Kislev sometimes have no thirtieth day. Someone has to decide, per person, whether that year is observed on the twenty-ninth or on the first of the next month.
The list outlives the person keeping it
When the list lives on the computer of one gabbai, it leaves when they do. A shared record with named recipients does not.
Available today
What Yardsites already does
Available nowThis is the shipped product, available now inside Spun as the Yardsites extension. It sends over WhatsApp, and it requires a connected WhatsApp channel.
Yahrzeit tracking on the Hebrew calendar
Entries hold a Hebrew name, an English name, the Hebrew date and notes. Each year resolves on its own, leap years included, and a date on a thirtieth that some years lack observes the twenty-ninth or the first of the next month, by your choice on the entry.
Recipients with their own timing
Subscribe a contact to one entry or to a whole group of entries, each with their own reminder days, so one person hears a week ahead and another on the day itself. Relations are rendered in Hebrew or English.
Your own templates, Hebrew or English
Messages render from templates you write, in either language, and can carry a Dvar Torah or a Segula.
Nothing goes out unseen
Reminders are generated ahead of time and sent inside the send window your organization sets. Every scheduled message can be reviewed, edited, paused or skipped before it goes.
A curated tzaddikim catalog
Installing seeds a prepared catalog of tzaddikim in three groups, so a community can track those dates without entering them.
Hebrew birthdays too, and no record limit
Hebrew birthdays are tracked the same way as yahrzeits, and there is no cap on how many entries an organization may keep.
The plan
What the free tier is meant to be
In developmentUseful on its own, not a crippled sample. If it is not worth the effort of entering your records, it is not worth building.
Store yahrzeit records
Hebrew name, English name, the Hebrew date and your own notes, kept as a record rather than a calendar entry.
Hebrew and civil date calculation
Each year resolves on its own, leap years included, with an explicit choice for dates that fall on a thirtieth that some years lack.
Annual reminder scheduling
A reminder is generated ahead of the date, every year, without anyone re-entering it.
Recipient groups
Group the people who should be told, such as a family, the shul office, or a notification list, and attach the group to a record instead of adding each person by hand.
Several relatives per yahrzeit
A single yahrzeit can reach a son, a daughter and a grandchild, each with their own relation and their own timing.
Email reminders
The free delivery channel. Enough to be genuinely useful on its own for a community that just needs the date to arrive.
CSV import
Bring an existing list in rather than retyping it. Nobody adopts a system that starts with a blank page and four hundred names.
A meaningful number of records
Enough for a small community to run its whole list on the free tier, not a teaser that runs out mid-import.
How it would work
From a list of names to a family being told
In developmentFive steps, each one useful by itself. You are never asked to commit to the last one to benefit from the first.
- 1
Bring your list in
Import the records you already keep, rather than starting from an empty page.
- 2
Say who should be told
Build recipient groups: the family, the shul office, whoever needs to know.
- 3
Reminders go out by email
Free, and enough on its own if that is all your community needs.
- 4
Add WhatsApp when email is not enough
The same records and the same groups, reaching families where they actually read.
- 5
Grow into the full inbox
Replies, team access and the rest of Spun, only if and when you want them.
Beyond the free tier
Where Spun earns its keep
WhatsApp is the reason most communities upgrade, because it is where people actually read messages. It is deliberately not the only reason.
WhatsApp reminders
The channel families actually open. This is the upgrade most communities come for.
SMS reminders
For the people who are not on WhatsApp, and for the ones who never check email.
Personalized wording per relative
A son and a granddaughter do not need the same sentence. Templates carry the relation.
Reminder timing you choose
Thirty days ahead for the one who needs to book a flight, the evening before for the one who needs to be reminded.
Replies land in your inbox
When a family answers, it becomes a conversation your team can see and continue, not a message lost on one phone.
Team access and follow-up
More than one person keeps the list, work can be assigned, and nothing depends on a single gabbai being available.
Who this is for
Built for whoever keeps the list
Synagogues and batei knesset
A yahrzeit list that survives a change of gabbai, with the office and the family both told.
Chevra kadisha and funeral homes
The families you served once, remembered every year afterwards without anyone rebuilding the list.
Community organizations
One shared record instead of a spreadsheet emailed between three people with four versions.
Families keeping their own dates
The Hebrew date, the relatives who should hear, and a reminder that arrives without being maintained.
Roadmap
Not built yet, and listed here so you can hold us to it
In developmentEverything in this section is work we intend to do. None of it exists today. Waitlist members hear when each piece lands.
A free tier that does not need WhatsApp
Today the yahrzeit feature requires a connected WhatsApp channel before it can be installed at all. The free email-first tier requires removing that requirement.
Email, SMS and Spun delivery
Per-person channel choice, so one relative is reached by email and another on WhatsApp. Built, not yet released.
Recipient groups on yahrzeit records
Attaching a whole group to a record instead of adding each person individually. Built, not yet released.
CSV import of yahrzeit records
Contacts can be imported by CSV today, but yahrzeit records cannot. This is the single biggest obstacle to adopting the free tier, and it does not exist yet.
Delivery reporting
Today a reminder is recorded as sent, failed or skipped. Whether it was delivered, read or replied to is not tracked at all.
Yahrzeit dates on your calendar
Placing an occurrence on the Spun calendar with your own reminder offsets. Built, not yet released.
Straight answers
The things you would find out eventually
The free tier is not open yet
There is no free yahrzeit signup today. The waitlist is the only thing this page offers, and it is genuinely just a waitlist.
Today, reminders go out over WhatsApp
The shipped Yardsites extension sends over WhatsApp and requires a connected WhatsApp channel to install. Email delivery is in development.
Yahrzeit records cannot be imported yet
Contacts can be imported by CSV. Yahrzeit entries are added one at a time, which we know is the hardest part of adopting this.
WhatsApp carries a connection risk
Spun connects to WhatsApp without the official business API. We treat that seriously, and it is why the paid plan is not built on WhatsApp alone.
Frequently asked questions
Can I sign up for the free yahrzeit manager right now?
No. The free tier described on this page is in development and has no signup yet. You can join the waitlist, and we will contact you when it opens. If you need yahrzeit reminders today, the Yardsites extension is available inside Spun and sends over WhatsApp.
What can Spun do for yahrzeits today?
The Yardsites extension tracks yahrzeits on the Hebrew calendar with Hebrew and English names, handles leap years and months without a thirtieth day, lets each recipient have their own reminder days, renders messages from your own Hebrew or English templates with an optional Dvar Torah or Segula, and lets you review, edit, pause or skip every scheduled message before it sends. It delivers over WhatsApp and requires a connected WhatsApp channel.
Will email reminders really be free?
That is the intent, and it is why the free tier is worth building at all. A yahrzeit database nobody can send from is not useful. We are not taking payment for it now, and the waitlist does not ask for a card.
Can I import my existing list?
Not yet for yahrzeit records. Contacts can be imported by CSV inside Spun today, but yahrzeit entries have to be added one at a time. CSV import of yahrzeit records is on the roadmap on this page, and it is one of the first things we intend to build, because it is what stands between a community and actually using this.
Does it handle a yahrzeit on the thirtieth of a month that some years do not have?
Yes, and this already works today. You choose on the record itself whether those years are observed on the twenty-ninth of the same month or on the first of the next month, and the Hebrew date picker asks as you enter the date.
Will you tell me whether a family actually read the reminder?
Not today. A reminder is currently recorded as sent, failed or skipped, and sent means it was handed to WhatsApp without an error. Delivered, read and replied are not tracked at all yet. That reporting is on the roadmap and we would rather say so than imply otherwise.
Do I have to use WhatsApp?
Today, yes, for the shipped product. The whole point of the planned free tier is that you should not have to, and paid value is deliberately not limited to WhatsApp alone. It also covers SMS, higher limits, personalized wording, team access and replies landing in a shared inbox.
How many records will the free tier hold?
Enough for a small community to run its real list, in the range of a hundred records, so it is useful rather than a teaser. The exact number is not fixed yet, which is part of what we want waitlist feedback on. The shipped product today has no record limit at all.
More on what Spun does: Features, Pricing, the Extension Marketplace, and Privacy and security.
Put your yahrzeit list somewhere it will be remembered
Join the waitlist and we will tell you when the free tier opens. If you need yahrzeit reminders on WhatsApp today, Yardsites is already available inside Spun.
Join the waitlistNo credit card, no obligation, and no import required to sign up.