Yajña Today

Yajña Today

A yajña, and the priest who performs it.

Yajña Today matches somebody who needs a saṁskāra performed with a purohita who can perform it, works out from the Gauḍīya pañcāṅga when it may be performed, and carries the arrangement from the first request through to an accepted date.

What this is

A saṁskāra needs three things that rarely arrive together: somebody who wants the rite performed, a purohita who performs it, and a day on which it may be performed. Yajña Today is where the three meet — a calendar that answers the third question, a search that answers the second, and a thread between two people that settles the first.

The two sides have names, and the app uses them. The yajamāna is the person on whose behalf the rite is performed — you, or somebody in your family. The purohita is the priest who performs it. One account holds one of those roles, and the screens you see are the ones your role has.

If you already have a family purohita, the half of this app that tells you when is useful on its own and asks nothing of you: no search, no request, no message. The pañcāṅga does not care whether you found the priest here.

What it does

The calendar that says when

A month at a time for the ceremony you have chosen and the place you are in: which days the source allows, which it forbids, and — to the minute — the hours inside them.

Purohitas near you

Search by distance and by ceremony. Only approved purohitas appear, and only those whose service area actually reaches you.

Request, accept, reschedule

A request names a ceremony, a date and a window. The purohita accepts it, declines it, or proposes another day — and an accepted date sits in both calendars.

Talk it through

One thread per arrangement. A rite takes preparation, and preparation takes questions that a date field cannot hold.

Family, and their saṁskāras

Enter each family member once, then record which rites have been performed for them and when. The calendar reads from that, so a request already knows whom it is for.

Approved purohitas only

A purohita signs up, applies, and waits. Until an administrator approves them they are invisible to search and cannot accept anything — and that is a condition in the database, not a hidden button.

How it works, on both sides

Two audiences, two paths through the same five screens. Read the one that is yours.

Yajamāna the one for whom the rite is performed

  1. Enter the family member the rite is for, once. Their date and place of birth is what the app needs, and it stays with the account.
  2. Choose the ceremony and read its calendar for your place. Green days carry an auspicious window, red days a forbidden one, and a day can carry both.
  3. Search for a purohita within a distance you set, for that ceremony. Every result is an approved purohita whose own service radius reaches you.
  4. Send a request naming a date and a window. It goes to that purohita and to nobody else.
  5. From there it is a thread between the two of you. When the date is accepted it appears in both calendars, and afterwards you can rate the purohita — who can reply.

Purohita the priest who performs it

  1. Sign up as a purohita and apply. You land in pending, and pending is a real state rather than a formality.
  2. An administrator approves or rejects the application. While it is pending you do not appear in anybody’s search and cannot accept a request — enforced in SQL, which is the only place a rule of this kind is worth enforcing.
  3. Once approved, set your service area: where you are, how far you travel, and which ceremonies you perform. The search reads all three.
  4. Requests arrive in an inbox with the ceremony, the date and the muhūrta the yajamāna was looking at. Accept, decline, or propose another day.
  5. Accepted dates become your calendar. Ratings from the people you have served are public, and so are your replies to them.

One account holds one role. A purohita who also wants to arrange a rite of their own needs a second account, and that is a limitation rather than a design — it is written down here so it is not discovered later.

The day it may be done

This is the part of the app with a right answer, so it is the part described in the most detail. The rules come from the śāstra as the tradition has them — for vivāha, from Appendix VII of the Bhaktivedanta Academy’s own compilation — and the app names its source on screen beside every verdict, so a rule can be checked rather than trusted.

A tithi is 12° of separation between the moon and the sun; a nakṣatra is 13°20′ of the moon’s sidereal longitude. Neither is a property of a date. Each is a property of an instant, and a boundary falls where it falls — often in the middle of an afternoon. So the app does not colour a day and stop: it finds the boundaries by bisection and reports them to the minute.

Three states, and not a scale. A day is auspicious if every limb the source requires is satisfied at the same instant and nothing forbidden applies; it is inauspicious wherever a forbidden limb applies at all; and it is unmarked otherwise. An unmarked day carries no colour, because the source says what is auspicious and what is forbidden and is silent about everything else — and an app that filled that silence with a shade of green would be inventing.

A day can hold both kinds of window at once, and when it does you get both. A usable morning under a forbidden evening is exactly the case a single colour per day would hide, so that cell is split at the boundary minute instead.

What the colours mean

  • An auspicious window, from the limbs the source requires
  • A forbidden window — this one wins wherever the two overlap
  • Both, split at the minute the one becomes the other
  • Unmarked: the source says nothing about this day

Expect an empty calendar for most of the year, and read it as correct rather than broken. For vivāha the source lists four months — Māgha, Phālguna, Vaiśākha and Jyeṣṭha — and forbids the four of cāturmāsya outright. The two sets do not overlap, so most of the year holds no auspicious window at all. A calendar that has nothing green in Kārtika is telling you the truth.

When a day is blank or red the app says why, in as many words as it takes: this month is not one the source lists, or the sixth of the waning fortnight is forbidden, or the tithi and the nakṣatra never overlap on this date. A calendar that only tints cells is not much use to somebody trying to choose a date.

Times are reckoned on standard time, never summer time, because that is what the reference pañcāṅga does — and where the difference matters the app says so on the row rather than leaving you to work it out. A wedding time an hour out is a worse failure than a reading an hour out.

The arithmetic is the same engine that Saṅkalpa Today reads, pinned to the same library at a verified tag, so the two apps never disagree about which day a rite falls on. It runs on your device, offline, against a place table built into the app.

What the server can read

Yajña Today is not end-to-end encrypted. Your data is stored in plain text on a server run by the developer, and it could be read by whoever runs that server. That sentence is first on purpose, because a page like this one is where a claim to the contrary would be easiest to make and hardest for you to check.

The reason is in what the app does, not in what was easier to build. Four of its features are readable-by-the-server by construction:

  • Finding a purohita near you is a comparison of latitudes and longitudes. A sealed value cannot be compared, sorted or indexed — a distance filter over ciphertext is not a slower search, it is not a search.
  • A chat between a yajamāna and a purohita is two strangers who met through this app, on two devices, with no shared secret between them. Exchanging keys between them safely is a different product with a different set of things to get wrong.
  • Sharing family details so a rite can be prepared is precisely the act of granting another account read access — that is the whole feature, not a side effect of it. Under end-to-end encryption it would mean re-wrapping a data key for every grant to every member, and revoking one would mean re-wrapping the rest.
  • Feedback and ratings are moderated, and a purohita can reply to a rating in public. Nobody can moderate ciphertext, and three parties reading one row is not a secret.

So what protects your data here is stated rather than cryptographic, and that is worth reading as exactly as strong as it sounds. The API is the only reader. Every request is scoped to the account its token belongs to and re-checked against the role that account holds, on the server, every time. A message is readable by its two parties because that is a condition in the query, not a decision a screen makes. The app itself holds no database credentials.

What that means for you, plainly: put nothing into this app that you would not put in an email. Names, dates, places, and the messages between you and your purohita are all readable by the operator. If a later version adds a private ceremony note — a field genuinely belonging to one account and compared with nothing — that field can be sealed. Nothing in the list above can be.

One part does stay on your device, and it is the part you use most. The muhūrta calculation is done locally against a place table built into the app, so choosing a ceremony and paging through a year does not tell the server which dates you were considering. Only a request you actually send leaves the device.

Its sibling My Sādhana Today does encrypt everything before it leaves the device, and that is the right design there, because nothing in it has to be compared between two accounts. Copying that sentence onto this page would have been false, so it is not here.

Get the app

One Tauri shell, one frontend, five platforms. Everything is in the free download — nothing is locked and nothing expires.

The desktop builds are unsigned, so Windows and macOS will warn about an unidentified developer before the first launch. The Android APK is a sideload: allow installs from your browser, then open the file.

Support

Yajña Today is free. Every feature is there from the first launch — nothing is locked, nothing expires, and there is no paid tier.

It is written and looked after by one person, and there are bills behind it — the developer accounts, the signing certificates, the hosting, and the server that carries the matching, the requests and the messages. If the app is useful to you and you would like to help carry that, a donation is warmly welcome. It buys nothing extra, because nothing is held back. 🙏

And to be clear about the money that is not here: the app takes no commission on anything arranged through it, charges a purohita nothing to be listed, and does not rank one purohita above another for payment. There is no transaction inside this app at all — what you agree with your purohita is between the two of you.

Crypto

Tap an address to copy it.

    Thank you — your support keeps this going. 🙏

    Say something

    A bug, an idea, or anything else. This reaches the developer as an email and nothing else happens to it: it is not published, it is not a review of a purohita, and there is no account behind it.

    Only used to reply to you. Leave it empty and the message arrives anonymously — there is then no way to answer it.