Drik Gaṇita
दृक् गणित

Positions, not approximations.

Drik Gaṇita is the observational method: a position worked out from where the sky actually is, rather than read off an inherited table. Drik Engine takes that literally — a calculation layer with no inference in the path, and an interpretation layer that cites its source or says nothing.

Query the engine Method

Latency

<200ms

Determinism

Byte-identical

Zodiac

Sidereal

Houses

Whole sign

Sidereal ecliptic · 0°—360°Lahiri

Specification

What the engine actually does

Not a feature list — the operating envelope. Every figure below is what the code does today, not a roadmap.

EphemerisGeocentric positions, converted to sidereal by the selected ayanamsa.Swiss Ephemeris

AyanamsaLahiri primary, plus True Chitra, Raman, KP, Pushya-Paksha, Surya Siddhanta.9 supported

VargasNineteen divisional charts. D60 computed at sub-degree precision, never rounded.D2 — D60

DashasFull 120-year sequence to pratyantardasha, plus Narayana and Shoola.Vimshottari +2

Yoga rulesDeterministic rule engine across fifteen classical categories.112

API surfaceOne versioned /v1 namespace over the whole engine.43 endpoints

VerificationPositions checked back to the chart; citations resolved against the corpus.Every claim

RegressionGolden dataset of practitioner-verified charts runs on every change.Blocks deploy

Products

Three ways in

All three read from the same core. A dasha boundary in a personal report, an API response and a practitioner’s timeline are the same number, because they are the same computation.

For individuals

Insights

Personalized Vedic reports written against your own chart, plus a portal that keeps the underlying calculations open to you — dashas, divisional charts, planetary strength, transits and panchang, all live.

6 report modulesChart portalRectification

For developers

Kalpa

One REST surface over the whole engine. Charts, dashas, divisional charts, yoga detection, doshas, strength, KP, panchang, muhurta, transits and citation-backed interpretation — all sidereal, all versioned, all deterministic.

43 endpoints9 ayanamsasVersioned contract

For practitioners

Drishti

A professional workbench for working Jyotishis. Every client, every chart, every consultation note and every case in one archive — with the calculation depth of the engine behind each screen.

Client vaultPattern searchPrashna & muhurta

Method

Why the numbers hold

Most astrology software is a black box and most astrology text is unsourced. Neither is true here.

Deterministic by construction

Positions come from the Swiss Ephemeris and a pure calculation layer with no inference anywhere in the path. The same birth data returns byte-identical output today, next year, and a decade from now.

Yogas are detected, not guessed

A rule engine reads the chart and applies classical combinations directly. Nothing in the interpretation path is free to invent a yoga that the rules did not find.

Every claim carries a citation

Interpretation is retrieved against a chunked corpus of classical texts and each statement resolves to a specific shloka. If no supporting verse retrieves, the claim is not made.

Verified against a golden dataset

A reference set of documented charts, cross-checked against established Jyotish software and signed off by practitioners, runs as a regression suite. A calculation regression blocks the deploy.

Output

The engine, speaking for itself

One canonical chart object, versioned, the same shape for every consumer. This is what a request returns.

chart.jsonschema 1.0

{
  "schema_version": "1.0",
  "lagna":   { "rashi": "Mesha", "rashi_number": 1, "degree": 14.72 },
  "planets": {
    "Sun": {
      "rashi": "Makara", "degree": 22.34,
      "nakshatra": "Shravana", "pada": 3,
      "house": 10, "is_retrograde": false,
      "dignity": "neutral",
      "d9_rashi": "Vrishchika", "d10_rashi": "Mesha"
    }
  },
  "dasha": {
    "current_mahadasha":  { "lord": "Jupiter", "start": "2019-03-14", "end": "2035-03-14" },
    "current_antardasha": { "lord": "Saturn",  "start": "2023-11-14", "end": "2026-07-14" }
  }
}

Questions

Asked and answered

01What does "Drik" mean?

Drik (दृक्) means sight, or seeing. In Vedic astronomy, Drik Ganita is the observational system of calculation — positions worked out from where the sky actually is, rather than read off inherited tables. That distinction is the whole thesis of this engine.

02Which ayanamsa do you use?

Lahiri is the default and the primary, matching the Government of India standard. True Chitra, Raman, KP, Pushya-Paksha, Surya Siddhanta and three Lahiri variants are all selectable per request.

03Is the interpretation generated?

Positions, dashas, divisional charts and yogas are calculated, never generated — they come from the ephemeris and a deterministic rule engine. Written interpretation is composed against those fixed facts and against a corpus of classical texts, then verified: every position it states is checked back to the chart, and every citation is checked to resolve to a real verse. If verification fails, it does not ship.

04How accurate are the calculations?

Positions derive from the Swiss Ephemeris. The engine is regression-tested against a golden dataset of documented charts cross-referenced with established Jyotish software, and a calculation regression blocks the deploy.

05Can I use the API for my own app?

Yes. Kalpa is the public API and is priced for it, from a starter tier through to enterprise and white-label. You get the same engine the other two products run on.

06Who owns the birth data I send?

You do. Birth data is treated as sensitive personal information: retained minimally, never sold, and never used to train anything without explicit consent.

Build on numbers you can defend.

Start with the API, or see what the engine produces for one chart.

Get an API key See Insights