Swiss Ephemeris is the astronomical library underneath most serious astrology and calendar software. It is worth understanding what it does and, more importantly, what it does not do for you.
What it provides
Swiss Ephemeris derives from the JPL DE ephemerides — the same numerically integrated planetary models used for spacecraft navigation. It gives you positions of Sun, Moon and planets for a given instant, to a precision far beyond anything calendar work requires.
It also handles the fiddly parts correctly: precession, nutation, light-time correction, and conversion between reference frames.
What it does not provide
This is the part that matters. Swiss Ephemeris knows nothing about tithis, nakshatras, festivals or muhurat. It gives you longitudes. Everything else — the twelve-degree segmentation, the ayanamsa offset, sunrise for a given latitude, the kala windows, the festival rules — is your own layer.
This is why "powered by Swiss Ephemeris" is close to meaningless as a differentiator. Nearly every credible provider uses it. The interesting question is what was built on top, and whether that layer can explain itself.
Where the real errors live
In our experience, essentially no calendar bug originates in the ephemeris. They originate in the layer above it.
- Using an approximation where an exact computation was available — for example, detecting a sankranti with a degree threshold rather than searching for the exact ingress instant.
- Applying the wrong ayanamsa, or applying it twice.
- Treating a tithi as a per-day label rather than an interval.
- Off-by-one weekday indexing, which is more common than anyone would like to admit.
The practical implication
When evaluating a calendar API, do not ask which ephemeris it uses. Ask whether it can show you the derivation, whether its rules are versioned, and whether it publishes its known differences. Those questions separate providers; the ephemeris does not.