A day's decision score
An exampleA favourable day for a bold move
- Career86%
- Relationships64%
- Health72%
| Day 1 | 62 |
|---|---|
| Day 2 | 58 |
| Day 3 | 71 |
| Day 4 | 83 |
| Day 5 | 76 |
| Day 6 | 69 |
| Day 7 | 74 |
- Moon in Pushya
- Jupiter in the 10th
- Saturn Mahadasha
Vedic astrology, numerology and AI - read together, in real time - so you know not just what is happening in your life, but when to act on it.
A favourable day for a bold move
| Day 1 | 62 |
|---|---|
| Day 2 | 58 |
| Day 3 | 71 |
| Day 4 | 83 |
| Day 5 | 76 |
| Day 6 | 69 |
| Day 7 | 74 |
What you get
Every answer comes from your own chart, and the working behind it is shown rather than hidden.
AI Chat
The answer is built from your real chart - and it opens that chart up to show you.
Astro Clock AI AI
onlineA sample conversation on one example chart, not a live reading. Your own answer is built from your birth details.
Birth Chart
North Indian or South Indian - read the chart in whichever style you already know. Touch any house and its life area, sign and grahas come forward.
Hover a house, or reach each one with Tab - Enter pins it open.
This is an example chart, not anyone's real one. Your own chart is computed from your birth details.
| House | Life area | Sign | Grahas |
|---|---|---|---|
| 1st house (Ascendant) | Self, body, vitality | Mesha | No grahas |
| 2nd house | Wealth, speech, family | Vrishabha | Moon 7°38′ exalted |
| 3rd house | Courage, siblings, communication | Mithuna | Rahu 5°11′ |
| 4th house | Home, mother, peace of mind | Karka | Jupiter 3°47′ exalted |
| 5th house | Children, learning, creativity | Simha | Mars 11°52′ |
| 6th house | Health, debts, competition | Kanya | Sun 22°14′, Mercury 9°03′ own sign |
| 7th house | Marriage, partnership | Tula | Venus 19°26′ own sign |
| 8th house | Longevity, upheaval, hidden things | Vrischika | No grahas |
| 9th house | Fortune, father, dharma | Dhanu | Ketu 5°11′ |
| 10th house | Career, action, standing | Makara | Saturn 14°22′ own sign |
| 11th house | Gains, income, networks | Kumbha | No grahas |
| 12th house | Expenditure, release, solitude | Meena | No grahas |
Dasha timeline
Vimshottari splits a life into nine fixed periods. The lengths are fixed, the starting point comes from the Moon's nakshatra at birth, and together they say which stretch opens when.
The lower strip opens the running Rahu Mahadasha into its nine Antardashas - which is why its scale is not the scale of the strip above.
Antardasha
Running now
Mercury
inside the Rahu Mahadasha
Aug 2025 - Mar 2028 · 2.6 yrs
Subject
Business, study, negotiation and communication.
Hover or tap any bar - its dates, length and subject open below. The keyboard works too: Tab through them, Enter to hold one.
The lengths are fixed and never vary: Ketu 7, Venus 20, Sun 6, Moon 10, Mars 7, Rahu 18, Jupiter 16, Saturn 19, Mercury 17 - 120 years in all.
The subject is fixed; which way a period actually runs is not. That depends on where the graha sits in the chart, which the app works out from real birth details - not from the lord alone.
The app reads this one level deeper as well - Pratyantardasha inside the Antardasha, three levels in all.
This is an example chart, not anyone's reading: 14 August 1999, Moon at 7°38′ Taurus (Krittika, Lahiri ayanamsa) - which is why the cycle opens on the Sun. Every boundary here is computed from those details. A period shorter than about a year is drawn at a readable minimum width; every other bar is exactly to scale.
| Period lord | Level | Window | Length | Status |
|---|---|---|---|---|
| Sun (balance at birth) | Mahadasha | Aug 1999 - Sept 2000 | 1.1 yrs | Completed |
| Moon | Mahadasha | Sept 2000 - Sept 2010 | 10 yrs | Completed |
| Mars | Mahadasha | Sept 2010 - Sept 2017 | 7 yrs | Completed |
| Rahu | Mahadasha | Sept 2017 - Sept 2035 | 18 yrs | Running now |
| Jupiter | Mahadasha | Sept 2035 - Sept 2051 | 16 yrs | Still ahead |
| Saturn | Mahadasha | Sept 2051 - Sept 2070 | 19 yrs | Still ahead |
| Mercury | Mahadasha | Sept 2070 - Sept 2087 | 17 yrs | Still ahead |
| Ketu | Mahadasha | Sept 2087 - Sept 2094 | 7 yrs | Still ahead |
| Venus | Mahadasha | Sept 2094 - Sept 2114 | 20 yrs | Still ahead |
| Rahu | Antardasha (inside the Rahu Mahadasha) | Sept 2017 - May 2020 | 2.7 yrs | Completed |
| Jupiter | Antardasha (inside the Rahu Mahadasha) | May 2020 - Oct 2022 | 2.4 yrs | Completed |
| Saturn | Antardasha (inside the Rahu Mahadasha) | Oct 2022 - Aug 2025 | 2.9 yrs | Completed |
| Mercury | Antardasha (inside the Rahu Mahadasha) | Aug 2025 - Mar 2028 | 2.6 yrs | Running now |
| Ketu | Antardasha (inside the Rahu Mahadasha) | Mar 2028 - Mar 2029 | 1.1 yrs | Still ahead |
| Venus | Antardasha (inside the Rahu Mahadasha) | Mar 2029 - Mar 2032 | 3 yrs | Still ahead |
| Sun | Antardasha (inside the Rahu Mahadasha) | Mar 2032 - Feb 2033 | 0.9 yrs | Still ahead |
| Moon | Antardasha (inside the Rahu Mahadasha) | Feb 2033 - Aug 2034 | 1.5 yrs | Still ahead |
| Mars | Antardasha (inside the Rahu Mahadasha) | Aug 2034 - Sept 2035 | 1.1 yrs | Still ahead |
Planetary strength
Shad Bala scores a graha from six separate sources of strength - positional, directional, temporal, motional, natural and aspectual. Each graha has its own minimum to clear, so strength is read against that requirement rather than against the other six.
Jupiter
0.00×
above its required minimum
Saturn
0.00×
below its required minimum
The rings sit at 0.50, 1.00 (dashed) and 1.50 times each graha’s own requirement - so one ring, seven different rupa values.
A sample chart, not anyone’s reading. Your own figures are computed from your birth date, time and place.
| Graha | Strength (rupas) | Required (rupas) | Ratio |
|---|---|---|---|
| Sun | 5.6 | 5.0 | 1.12× - above its required minimum |
| Moon | 7.4 | 6.0 | 1.23× - above its required minimum |
| Mars | 4.3 | 5.0 | 0.86× - below its required minimum |
| Mercury | 6.2 | 7.0 | 0.89× - below its required minimum |
| Jupiter | 8.3 | 6.5 | 1.28× - above its required minimum |
| Venus | 6.4 | 5.5 | 1.16× - above its required minimum |
| Saturn | 4.1 | 5.0 | 0.82× - below its required minimum |
Transit alerts
An exampleThe grahas move on their own schedule, and the dates they change can be worked out in advance. The ones that touch your chart can arrive as a note.
Saturn turns direct in the seventh - the tangle in a relationship starts to clear.
worth watchingIn five daysNewest
Mercury turns retrograde - read contracts and dates twice.
worth watchingNext week
A full Moon in the fifth - a good pull for anything you are making.
openingIn three days
Venus enters its own sign - an easier stretch for talking and settling things.
openingThis month
Timing windows
The next three months, one score a day. Different kinds of work suit different days, so the colours change when you change the category.
Scores for the next ninety days, for Career
From 15 Oct to 12 Jan, for Career: 19 strong days and 30 favourable ones.
Best
strong
Thu, 15 Oct, 2026
Why this day
Counted from the birth nakshatra, this is the Sampat tara.
The day lord is strong
Move to any day, with a keyboard too, and its reason appears.
A day's score is built from that day's transits, choghadiya and hora - the same arithmetic the panchang calculators run.
This ranks days, not hours. For an hour, read that day's choghadiya.
This is an example. The same arithmetic runs on your own transits once your chart exists.
Positions are computed with the standard Meeus and JPL/Standish algorithms, using the Lahiri (Chitrapaksha) ayanamsa. The charts above are examples. What is offered is guidance, not a guarantee.
How it works
Three fields, and a place that resolves to real coordinates.
Your own chart, computed from your data - never a template.
Lahiri ayanamsa
Ask in plain words. Every answer shows what it rests on.
Is this a good year to change jobs?
An exampleAll three panels are illustrations with sample values. A place must resolve to real coordinates - without them there is no ascendant, so house-based readings are left out rather than estimated.
Try it before you sign up
Three calculators run in full without an account, and your details are not saved.
Every placement is explained in plain language, then tied to a number from your numerology profile - so the two systems agree with each other rather than contradict.
AI Life Chat · Flagship
Based on your Venus Mahadasha (career houses activated), Jupiter transiting your 10th house from October, and your Personal Year 5 favouring change.
Decision check
Ask about a launch, a proposal, a resignation - and get a clear YES / WAIT / NO, checked against your Dasha, transit and numerology cycle.
Kundali and numbers
Missing numbers, dominant numbers and your Personal Year, explained simply.
Muhurat and compatibility
Marriage, business and friendship - scored and explained.
27/ 36 Ashtakoot + numerology match
The panels above show example output, not live data. Your own reading is generated from your birth details.
What people use it for
Asked
The answer is built from the tenth house, its lord, and the dasha running now - along with the windows where a change finds support. What comes back is a read on timing, not an instruction.
Read from
Asked
Ashtakoota runs on eight measures totalling thirty-six points. Each koota is broken out below, so where the score is low is visible too - not just the total.
The Ashtakoota total for an example pair
Bhakoot's zero is shown, not hidden. A single low koota tells you more than the total does, and this is how it surfaces.
Asked
The second and eleventh houses, their lords, and the wealth yogas - both the ones found and the ones not. No figure or amount is offered.
Read from
Asked
The twelfth house for foreign ties, the fourth for roots, and the transits crossing both. What comes back is whether the timing supports a move, not where to go.
Read from
Asked
The sixth house, its lord, and the numbers missing from the numerology grid, read against the transits running now. No diagnosis, and no medical advice.
Read from
Asked
The fifth house for learning, the benefics aspecting it, and the dasha running now. It reads when effort finds support, not what you should study.
Read from
Asked
The fourth house for property, the dasha running now, and the transits crossing it. A read on timing only - never a valuation, and never advice to buy.
Read from
Asked
The fifth house, and the Saptamsa (D7) the classical texts assign to children, read with the dasha running now. A read on timing, never a promise.
Read from
Swipe for more
Why it reads differently
The difference isn't more features. It's that every insight here is generated for you, at this moment, not written once for a whole zodiac sign.
Tells you the reasoning behind the answer
Leaves room for the next question
Remembers what you said before
Shows the calculation, not just the conclusion
Available at any hour
Names the text and chapter a rule comes from
Costs nothing today
Billing is not live yet - there is no payment integration, so nothing is charged and no payment details are collected.
FAQ
Everything else depends on your own chart. It takes about two minutes to build, and after that you can ask as much as you like.
Build your chartYour birth details are used only to generate your own readings. We never sell them and never show them to other users, and you can delete your account and everything in it at any time from account settings. The values calculated from your chart are sent to the AI providers named in our privacy policy to write each reading - that policy sets out exactly what leaves and what does not.
Vedic. Your chart is calculated sidereally (Lahiri) - Kundli, Vimshottari Dasha, transits and divisional charts - and read together with your numerology profile. There is no Western astrology engine here.
Nothing today. Every feature is free for everyone, there is no payment integration in the product, and no payment details are collected. If that ever changes we will say so plainly before anything is charged.
Yes. The site and the app run in three languages - English, Hinglish and Hindi - and you can switch at any time from the language menu at the top of the page. English is the default, and a signed-in account keeps the language you choose. Articles on the Insights page are in English only for now.
How this works
What follows is the part that usually goes unsaid: which calculations run, which texts they come from, what you do not get without a birth time, and what this tool flatly refuses to do.
10 chaptersWhat runs, what it rests on, what it refuses to do
No pre-made charts - the positions are computed, and the algorithms that compute them are named.
Your local birth date, time and timezone offset are first collapsed into one UTC instant, and that instant becomes a Julian Day. The Sun's apparent geocentric longitude then comes from the standard Meeus series; the Moon's from 35 principal periodic terms of Meeus Table 47.A, with the eccentricity correction applied to the terms involving the Sun's anomaly. Mercury, Venus, Mars, Jupiter and Saturn use JPL/Standish Keplerian elements valid for 1800 to 2050, Kepler's equation solved by iteration and Earth's own heliocentric position subtracted to make the result geocentric.
Those longitudes are tropical as computed, so each is converted to sidereal by subtracting the Lahiri (Chitrapaksha) ayanamsa - the standard virtually all Indian Vedic astrology uses. Rahu is the Moon's mean ascending node; Ketu sits exactly 180 degrees opposite it. The Ascendant needs two inputs the planets never touch: local sidereal time, which is Greenwich sidereal time plus your birth longitude, and your latitude, which enters the rising formula separately. The obliquity of the ecliptic used in that formula is a function of the Julian Day alone.
Houses are whole-sign. The rising sign becomes the first house and each of the twelve houses is exactly one sign, in order, so no cusp degree is calculated at all. Every point is then described identically: its sign, its degree within that sign, which of the 27 nakshatras of 13 degrees 20 minutes it falls in, that nakshatra's lord, and which of its four padas. Degrees are shown to the arc minute and no finer, because the ayanamsa choice and a remembered birth time each move a chart by more than an arc second.
Where a rule comes from a named book, the citation sits in the code beside the function that uses it.
The birth-chart engine names its authorities. Brihat Parashara Hora Shastra supplies the Yoga Karakas for each of the twelve rising signs and the five Panchamahapurusha Yogas. Kalyana Varma's Saravali supplies the Lunar and Solar Yogas, the Nabhasa chart-shape yogas and the Planetary Rays score. Bhrigu Sutras sits behind the planet-in-house table. Jyotisha-Siddhanta-Sara gives the Navamsa method and all twenty-seven Janma Nakshatra temperaments. S. Kannan's Fundamentals of Hindu Astrology gives Shad Bala, the dignity and friendship tables, the Bhinnashtakavarga contribution tables and the Gochara transits read from your natal Moon.
The numerology engines are kept separate by book rather than merged into one score. Advanced Vedic Numerology by Pankaj Chauhan supplies the Vedic Grid combinations and a numerology dasha timing layer. Dr. Oliver Tan's Power of Numbers contributes its own inverted-triangle chart and Root Number, a different construction from Mulank or the Lo Shu grid. Sepharial's grid and the Chaldean name numbers come from Rrachita Gupta's Life With Number Magick. The Chaldean letter table sits in its own file, because the name table used elsewhere is Pythagorean, not Chaldean.
Naming a source also means recording what was not taken from it. Of Daivajna Vallabha's fifteen chapters the Prashna feature implements six; the warfare, death-prediction and rainfall chapters are excluded by decision, not oversight. Saravali names thirty-two Nabhasa Yogas and all are built; where Saravali and BPHS word a shape differently, the engine follows BPHS and records Saravali's reading beside the code. Bhrigu Sutras' own disease predictions and death-timing passages were dropped on the way into the planet-in-house table, and the code records that beside it.
Without a birth time there is no ascendant, and the code returns nothing rather than estimating one.
A birth date, a place and a name are enough to compute a great deal. computeChart() derives all nine grahas from the Julian day - sign, degree, nakshatra, pada and retrograde motion - and seeds the whole Vimshottari Dasha timeline from the Moon's longitude. Gochara reads today's transits counted from your natal Moon sign, so it needs no ascendant. Numerology reads the calendar date and your name. None of that is degraded, and none of it is a consolation prize.
The ascendant is where it stops. Thirteen functions in kundaliEngine.js share the same guard - if (!chart.ascendant) - and then return null or an empty list; among them Shad Bala strength, the yoga and dosha scans, the aspect tables, Arudha Lagna, the Bhava and Graha Padas, Argala, Ashtavarga. The Blueprint's strength and risk indices withhold themselves too, with a written reason: houses need an ascendant, and an ascendant needs a birth time, so rather than estimate one both indices are withheld. An empty field here is a refusal, not a gap in your data.
Something still has to be computed, so a missing time defaults to 12:00 noon, and the app tells you what that costs. timePrecision() recomputes your chart at both ends of the birth day and compares the results: whether the Moon holds its sign, whether it holds its nakshatra, whether the running Mahadasha lord is the same, and how far that period's dates move. When the two ends agree, it says so plainly.
Two of the layers behind this app's dated windows are described here - a Vimshottari timeline seeded at birth, and today's sky read against it - and they are computed separately.
The Vimshottari timeline is keyed to a single number: your Moon's sidereal longitude at birth. Which of the 27 nakshatras it falls in picks the first of nine planetary lords, and the fraction of that nakshatra already crossed is subtracted from that lord's period - so the first Mahadasha is partial, and every later date shifts with it. The nine fixed lengths total 120 years, so the sequence runs from birth to roughly 120. With no birth time on file, noon is assumed, and the chart is recomputed at both ends of the birth day to see whether both ends give the same running Mahadasha.
Below the Mahadasha the same arithmetic runs twice more. A parent period is split between the nine lords in the ratio of their own year-lengths, starting from the parent's own lord - one function applied at both levels, not two implementations to keep in step. The middle level is still wide: an Antardasha inside the nineteen-year Saturn Mahadasha runs a little over three years. The Pratyantardasha below it is weeks to months, which is the scale a real decision sits on. All nine Mahadashas are published with their Antardashas nested.
Transits are the second layer, and they move no dasha date. Gochara reads where all nine grahas are today, counted from your natal Moon's sign rather than the ascendant. Saturn's own positions are named separately: the twelfth, first and second from the Moon are Sade Sati's rising, peak and setting phases; the fourth is Ardha Ashtama Sani, the eighth Ashtama Sani.
Numerology here is several distinct methods running side by side - and where two of them disagree, neither is merged into the other.
Numerology needs the calendar date you were born on. A name is optional. No birth time, no birthplace. The free numerology calculator returns its result marked complete, while the birth-chart calculator beside it has to report how certain the Moon is and leaves out houses and yogas when no time was given. The date is read as the digits you typed, anchored at midnight, not as a UTC instant: a 02:00 IST birth on 17 April 1991 would otherwise slide back to the 16th and turn a Mulank of 8 into a 7.
The methods sit in separate files because they genuinely are separate methods. Mulank and Bhagyank come from reducing the date's own digits. The Vedic Grid tests 47 geometric combinations across the nine cells of a grid cast the book's way - century left out, Moolank and Bhagyank added. A second table of 51 rows reads the same nine-cell layout, filled from the plain count of every digit in the date, through a different author's planetary framing. A third method builds an inverted triangle from the date's digit pairs and reduces it to one Root Number, keeping no master numbers at all. Chaldean name values run on a letter table in which no letter is worth 9, with its own rule for when Y and W count as vowels.
Nothing is merged into a consensus figure. The 51-row table lands on several of the same cell-sets as the Vedic Grid's arrows; only the planetary framing and the wording differ, and it is kept as a second reading rather than a replacement. Where a source book contradicts itself, that is recorded too - one worked example in the Power of Numbers book does not match its own arithmetic.
The product runs independent systems over one set of birth details, and the design decision that matters is what it does when they do not agree.
Two calculations run over the same birth record and never touch each other. The astrology side reads the Vimshottari Mahadasha derived from your Moon's position at birth; the numerology side reads your Personal Year, derived from your birth day and month against the calendar year. A tone rule that already existed for each side sorts a period into a tone, and those tones are renamed, not recalculated, onto one three-word axis: expand, build, hold. Because both halves land on the same three words, agreement becomes a literal equality check between two separately computed values rather than a claim you have to take on faith.
The axis is ordered, so the gap between the two stances is a distance: nought, one or two. Nought is reported as agreement. A gap of one is reported as a partial split, naming which side read what, and the more cautious of the two stances is the one put forward to act on. A gap of two is reported as a contradiction, in those words, with the suggestion that the year be treated as one to test small in rather than commit large. Neither reading is averaged into a middle answer; both stay on the page with their own stance.
No confidence percentage is attached to the verdict. What the page reports instead is how far the answer leans on information you did not give: with no birth time, the chart is recomputed at 00:00 and at 23:59 and the page states whether the ruling Mahadasha actually changes across that day, naming both candidate rulers when it does and saying so plainly when it does not. The separate track-record engine keeps to the same rule: three feedback measures held apart, never averaged into one score, with nothing quoted until at least five entries sit behind it.
A product is easiest to judge by its refusals, so here are ours.
There is no Gemstone Recommender here, and no Rudraksha Recommender. The remedies this app issues are behavioural by the remedy engines' own stated design - something you could do at a desk or in a conversation - because, as the remedy engine's own shipped text puts it, a remedy you have to buy or believe in cannot be checked. A lucky gemstone and an associated deity did once ship here. Both were removed, and an API assertion now fails if either field comes back. Refusing them is the position, not an omission.
The remedy endpoint's weekly and yearly horizons are scanned by an assertion in the test suite - every title, action and reason those horizons publish - and the run fails if a threatening word appears in them. The promises run out in the other direction too: the terms state plainly that no prediction, timing window, compatibility score or verdict is warranted to be accurate or to come true, and that every decision remains yours.
The career and money read does not fill in a number when the data for it is missing. Without a birth time the Ascendant cannot be computed, and with it no house, Shad Bala or Ashtakavarga figure - so that engine returns unavailable and names exactly that, rather than a dignity-only number dressed up as the full read. Where a reduced read is still possible, the behavioural engine names the direction of its own error: the mental clarity index is labelled biased high without a birth time, because aspects, where strain usually shows, cannot be read at all, and the Moon and Venus read asks you to treat a positive result as unconfirmed rather than confirmed.
The public calculators need no account and write nothing to the database; what an account does store is listed field by field, and one control in Settings deletes the account and every collection keyed to it.
The public calculators and the Convergence page run on unauthenticated routes, and their handlers persist nothing - no document is created and no counter on any model is incremented, so an anonymous visitor leaves no trace in the database. You can type a birth date, read the whole result rather than a teaser, and close the tab. The birth-place field is the one exception, and it is not a single request. From the second character you type, and until you pick a suggestion, that text goes to our own server to look up matching places; unless the bundled city list alone fills the suggestions, our server forwards it to Open-Meteo. A wrong latitude would quietly corrupt the ascendant and every house built on it, which is why the lookup exists.
An account stores more, and the privacy policy inventories it field by field rather than by category: sixteen fields you give us, thirteen derived values, and eight things collected automatically. The account record itself holds your name, email, your language and your goal, and a birth record - the date and time exactly as you typed them, whether a time was given at all, the place label, latitude, longitude, timezone offset, and the UTC instant derived from those.
Deletion is a real route, not an email address. Settings, under Data & privacy, asks you to confirm and then calls DELETE /auth/account. That handler walks one declared list of ten collections - profiles, chat, life events, practice logs, Prashna questions, share links, composed messages, delivery settings, WhatsApp consent and insight reactions - and removes the account row last, so a failure part-way through leaves an account that can retry rather than rows nobody can find. The list is declared rather than hand-written because three collections were once missed; an API test writes a real row into each of those three and fails if any of them is still there afterwards.
Nothing is charged today - every feature is open on every account, and no payment details are collected.
The tier structure exists in the code: four named tiers, each with its own feature matrix behind it. But isFreeForAll() reads one environment value, and unless that value is the string 'false' the free-for-all mode is on - which is how this deployment ships. With it on, featuresFor() returns the top tier's feature set for every account, before it even looks at the account's own tier. So you get unlimited AI chat at the advanced reasoning level, the full Kundali, the deep numerology sections, all Muhurat windows, the full eight-koota compatibility breakdown, unlimited profiles, unlimited Prashna questions, and every report from daily through career.
None of the paid structure was deleted to get there. The four tiers, the per-tier feature matrix and the thirteen-row comparison table are all still in the code, and every gate - chat replies, reasoning depth, the full Kundali, numerology, Muhurat, compatibility, Prashna, profiles and reports - still routes through featuresFor(), on the server. The test suite reads which mode is live from the API rather than assuming it, and in the free mode it asserts that no price and no Unlock link stays visible. That is the current position of one value, not a promise about next year - and no tier could be bought today, because the product contains no payment integration.
This is built for someone weighing a real decision who wants a structured second read - not for someone who wants to be told what will happen.
The clearest fit is someone with a specific decision in front of them - a launch, a resignation, a proposal - who wants a second read before committing. Ask, and you get YES, WAIT or NO with a confidence figure built from exactly two terms: how your current Mahadasha reads for that kind of decision, worth up to sixty points, and the Shad Bala strength of the planet ruling the relevant house, worth up to forty. Both terms are named on screen. You can log the verdict, then record later what actually happened.
It also suits the reader who would rather check the work than take it. Chapter references are printed beside the readings and deliberately left in English in all three languages, because a translated book title finds no passage - "BPHS Ch.68, Sloka 1-6" is meant to be looked up.
It is a poor fit for three people. Anyone wanting a guaranteed outcome: asked to compare two options of the same kind, it refuses, because the same category means the same house, the same lord and the same figures, and a winner picked between them would be a coin toss with a chart drawn on it. Anyone wanting a remedy to buy: the gemstone and deity fields that once shipped were removed. Anyone wanting a diagnosis or an investment call: the body section names no condition, and money timing states in its own words that it is timing quality, not financial advice.
Your first reading takes about two minutes.