ProKerala: Correct Time Handling, and What the Rs 999 Report Really Is

A fair review — we verify that ProKerala's ephemeris gets daylight saving right, then look honestly at what its paid in-depth report contains and how it is organised.

1. Introduction

ProKerala (prokerala.com) is a pan-India, Kochi-rooted astrology and general-information portal with a large, free tool set: nakshatra finder, kundli, panchang, and matching across the Kerala, Tamil and North-Indian systems. It is deservedly popular: the tools are free, multilingual, and — importantly — they return the computed nakshatra and rasi, which makes their output verifiable rather than opaque. This review does two things. First, it verifies ProKerala's astronomical correctness on the exact failure mode that trips other tools — daylight saving. Second, it examines the product ProKerala charges for, the Rs 999 in-depth horoscope, and asks not "is it accurate?" (it is) but "is it usable?"

As with our other reviews, this is written from the standpoint of an engineer building a matching and jātaka engine, not a critic. Credit is given where the computation is sound; the critique is reserved for organisation.

2. Strength: correct time handling (verified)

2.1 The test that other tools fail

Our reviews of ePanchang and srirangaminfo documented two distinct time-handling defects: ePanchang omits the daylight-saving hour for summer births in DST-observing countries, and srirangaminfo over-corrects clock-recorded births with a forced Local-Mean-Time shift. Both can move a boundary birth into the wrong nakshatra or rasi. The natural question is whether ProKerala — which serves the same diaspora — makes either mistake. It does not.

2.2 The boundary case

We take a deliberately unforgiving birth: New York City, 4 June 1990, 7:38 AM. In June, New York observes Eastern Daylight Time (EDT, UTC−4), not Eastern Standard Time. This birth sits in the last pada of Chitra, about half an hour before the Moon crosses into Swati — precisely the kind of edge where a one-hour error flips the star. ProKerala returns:

Our engine, independently, computes the same birth as Chitra pada 4, Thula, Monday — an exact agreement. Better still, ProKerala publishes the window during which the Moon occupies Chitra, and that lets us compare the two ephemerides directly, second by second:

Figure 1. ProKerala's published Chitra window vs. juno.date's JPL DE440 + Lahiri computation, in EDT. Agreement to ~15 seconds across a 27-hour span. Birth: New York, 4 Jun 1990, 7:38 AM EDT.

Fifteen seconds over a twenty-seven-hour window is not "close" — it is two high-precision ephemerides landing on the same instant. It tells us two things at once: ProKerala is running a modern, accurate ephemeris (not an old Vākya table), and it is applying the correct daylight-saving offset. We state this without reservation, because it is the honest result — and because it is the opposite of what we found in the two reviews above.

2.3 Why this birth is the proof

The Chitra→Swati boundary here falls at 12:08:26 UTC (08:08 EDT). The correct birth, 7:38 AM EDT, is 11:38 UTC — thirty minutes before the boundary, so Chitra. A daylight-saving-blind tool would treat the same clock time as EST and compute 12:38 UTC — thirty minutes after the boundary, and would report Swati, the wrong star. That is exactly the error ePanchang's model makes. ProKerala avoids it. On accuracy and time handling, ProKerala passes the test cleanly.

2.4 A note on location vs. time

One caution for readers verifying such tools themselves: the nakshatra, pada and rasi are geocentric — the Moon's position is essentially identical viewed from anywhere on Earth — so a correct nakshatra proves only that the time (and ephemeris) is right. It says nothing about whether the location was cast correctly. The location-sensitive output is the Lagna (ascendant) and the houses. A tool can get the right nakshatra from the wrong coordinates. The proper location check is therefore the ascendant, computed from the birthplace's latitude and longitude — which for this birth our engine places in Mithuna.

2.5 A precision check against Astro-Vision's own arc-second output

ProKerala's charts are produced by the Astro-Vision LifeSign engine. When that engine prints positions to the arc-second (as its detailed report does), we can hold it directly against the truth. Here is every graha for a sample birth — a 1999 Mumbai chart — from Astro-Vision, next to the JPL DE440 truth and juno.date's live output (all sidereal, Lahiri):

Figure 2. Every graha for one birth, in degrees:minutes:seconds. Astro-Vision (ProKerala's engine) lands within about one arc-second of DE440; juno.date lands on it.

This is the honest, complete picture — and it settles the matter in ProKerala's favour on accuracy. Astro-Vision's ephemeris sits within about one arc-second of DE440 across the whole chart: a genuinely modern, accurate engine. juno.date sits at 0″. For every practical purpose, both are at the truth — which is exactly why we credit ProKerala's accuracy without reservation. (Where a ProKerala summary chart looks half an arc-minute off, that is its arc-minute display rounding, not its engine — as the arc-second output above proves.) Our only edge over it in the sky is that last fraction of an arc-second, and that we show positions to the second. The real difference between us is not the sky at all — it is what each of us does with the report, which is the rest of this review.

3. What Rs 999 buys: the in-depth report

ProKerala's free tools are the front door; its paid product is a ~50-page "in-depth horoscope." The sample we examined is, by its own header and reference code, an Astro-Vision LifeSign report — Astro-Vision being the Kochi software house whose engine powers a number of Indian astrology sites (its consumer brand is Clickastro). In other words, the paid deep report is a packaged LifeSign document. Its contents are genuinely comprehensive:

Figure 3. The sections of the Rs 999 Astro-Vision LifeSign report packaged by ProKerala.

Roughly forty of the fifty pages are deterministic computation — charts, longitudes, dasa dates, ashtakavarga points, strengths — and about ten are interpretive prose. The computation is accurate. There is nothing to fault in the numbers.

4. The real weakness: it is a data dump

The problem is not correctness; it is organisation. The report is ordered the way the software computes — sphuta, then upagraha, then ashtakavarga, then dasa tables, then shadbala, then bhava, then remedies — mechanism by mechanism, front to back, for fifty pages. That is the order convenient for an engine, not for a reader. A family evaluating a proposal has to hunt through a dense, undifferentiated PDF to find the one thing they care about, and the interpretive sections are long, generic, canned blocks that read the same for large classes of charts.

Two further frictions: it is paid (Rs 999 per report), and it is a static PDF — there is no "you are here" on the 120-year dasa timeline, no way to expand one section and collapse the rest, no visual for a strength table that is printed as raw numbers. The depth is all there; the usability is not.

5. What juno.date offers: the same depth, reorganised, free

Our position is not to offer less than a paid report — it is to offer the same information and every chart, better organised, at no cost. We keep all of it: the D1 and D9 (already live) and the wider divisional set, the Nirayana sphuta, the full Vimshottari dasa down to antara, ashtakavarga, shadbala, the yogas, every dosha, the transits, the house readings. Nothing is dropped. What changes is the arrangement and the depth-layering.

Instead of fifty pages by mechanism, one page organised around the six questions a reader actually has:

Figure 3. juno.date's report re-organises the identical content into six reader-facing sections.

Each section shows a one-line, plain-language takeaway; the reader expands what they care about, and the raw degrees-and-minutes tables sit behind a "show details" link for enthusiasts. Casual readers get summaries and visuals; serious readers get the exact numbers — on the same page. It is computed with JPL DE440 (the ephemeris we just showed matches ProKerala to seconds), delivered in fifteen languages, and it is free and shareable rather than a Rs 999 PDF.

6. Conclusion

ProKerala earns its reputation. Its free tools are accurate, its ephemeris is modern, and — unlike the two tools in our earlier reviews — it handles daylight saving correctly, agreeing with our independent DE440 computation to about fifteen seconds on a deliberately hard boundary birth. Its paid Rs 999 in-depth report, an Astro-Vision LifeSign document, is comprehensive and computationally sound. Its one real shortcoming is that it is organised as a fifty-page data dump: everything is present, little is findable. juno.date's answer is not to compete on correctness — ProKerala is correct — but to take the same complete body of information and every chart, reorganise it around the questions a reader actually asks, layer the depth so one page serves both the casual and the serious, and give it away in the reader's own language.