This is what sits underneath the features. The calculation engine, the knowledge base, the AI, and the privacy model - explained plainly so you can decide if you trust it before you use it.
Every planetary position on this site is calculated using the JPL DE440 ephemeris from NASA's Jet Propulsion Laboratory, accessed through the Skyfield astronomy library. DE440 is the same dataset used by NASA for mission planning. It provides sub-arcsecond precision for planetary positions - meaning the coordinates are accurate to a fraction of a degree that no human eye or traditional table could distinguish.
This matters because Vedic astrology is sensitive to exact positions. A difference of one degree can shift a planet from one Nakshatra to another, change the Navamsa placement, or alter a dasa start date by months. Most astrology software uses simplified algorithms or pre-computed tables with limited precision. We compute positions directly from the ephemeris for every chart, every time.
The ayanamsha is the offset between the tropical zodiac (used in Western astrology) and the sidereal zodiac (used in Vedic astrology). Different schools use different reference stars to define this offset, which is why the same birth chart can show different positions depending on the software.
Our default is Pushya Paksha, which anchors the zodiac to the star Delta Cancri at a fixed point in Cancer. We compute this using the star's actual position from Skyfield, corrected for proper motion (the star's own drift over centuries). This is not a static table lookup - it is a live calculation against the star catalog for each chart.
We also support Lahiri (anchored to Spica), B.V. Raman (a linear formula), and Krishnamurti (KP). If you have seen slightly different planetary positions on another tool, the ayanamsha is almost certainly the reason. You can change this in your profile settings.
This is almost always an ayanamsha difference. If another tool uses Lahiri and we default to Pushya Paksha, positions can differ by roughly half a degree - enough to shift a borderline ascendant or Nakshatra. Check which ayanamsha both tools are using before concluding one is wrong. You can switch ayanamsha in your profile settings to match what you are used to.
Less commonly, the difference comes from birth time rounding (the ascendant moves about one degree every four minutes) or from the other tool using a less precise ephemeris. If you have checked the ayanamsha and the positions still disagree, reach out and we will help you trace the discrepancy.
All of the following are computed mathematically from the ephemeris. No AI is involved in any of these steps.
The AI does not make up astrological rules. It draws from a curated library of over 3,000 pages of Vedic astrology texts, indexed and searchable during every conversation.
This includes classical works spanning Rasi and Bhava analysis, Karakatvas, health and longevity, Panchanga and Muhurta, birth rectification, and Varga interpretation. Alongside these, we have compiled study notes, annotated references, and applied interpretations drawn from across the broader Jyotish tradition - old and new. The knowledge base is actively maintained and expanded as new material is reviewed and added.
When the AI makes an astrological claim - "Jupiter in the 5th house indicates..." - it is retrieving that principle from the library, not generating it from general language patterns. The system uses retrieval-augmented generation: the AI searches the knowledge base for relevant passages before writing its response. This grounds the output in specific sources rather than vague training data.
The language model is Google Gemini. It is responsible for reading your chart data, finding relevant rules from the knowledge base, and writing the analysis in plain language. It does not calculate anything.
This separation is deliberate. Planetary positions, dasa periods, and chart divisions are computed by the calculation engine with mathematical precision. The AI's job is to explain what those positions mean by applying classical rules to your specific chart. It synthesizes multiple factors - the house lord, the sign, the Nakshatra, the dasa period, the transit - into a coherent interpretation that a textbook cannot provide for your individual case.
The AI also decides which charts to examine. When you ask about career, it knows to pull the Dasamsa (D10). When you ask about timing, it fetches the Tithi Pravesh and current transits. It has access to calculation tools and calls them as needed during the conversation. You can see which tools were called in the chat interface.
Birth data is sensitive. Your name, date, time, and place of birth are personal information, and your questions and analysis results are private. Here is exactly what we do with that data.
Every user gets their own unique encryption key, generated the first time you sign in. All personal data - birth details, questions, analysis results, chat messages - is encrypted with your key using AES-256-GCM before it is written to the database. Your key is itself encrypted with a server-side master key and stored in your account metadata.
This per-user key architecture means that a database breach alone would not expose your data. An attacker would need both your individual key and the master key to decrypt anything. Each encryption operation uses a fresh random initialization vector, and the authentication tag ensures data has not been tampered with.
When you request your data, the system decrypts your key in memory, uses it to decrypt your data, and sends it to you over HTTPS. The decrypted data is never written to disk.
As with any web service, the platform operator holds the master key and could theoretically access encrypted data. In practice, the master key exists only as an environment variable in the production infrastructure - it is never stored in application code or the database, and production environment access is restricted. We do not access, read, or process your data outside of serving your requests.
If absolute zero-knowledge privacy is a requirement for you, no web-based astrology service can currently provide that - and we would rather say so plainly than pretend otherwise.
We do not sell, share, or use your birth data for any purpose other than generating your charts and analysis. Row-level security in the database ensures your data is only accessible to your authenticated session.
Vedic astrology is highly dependent on an accurate birth time. The ascendant changes roughly every two hours, and divisional charts shift with even smaller time differences. If your birth time is approximate - rounded to the nearest hour, or taken from memory rather than a birth certificate - the Lagna, divisional charts, and dasa periods may be inaccurate. The calculation engine will compute exactly what you give it, but the output is only as reliable as the input.
The AI model is not deterministic. If you ask the same question twice, you may get different phrasing, emphasis, or even slightly different interpretations. The underlying chart data will be identical - the calculation engine always returns the same positions for the same input. But the AI's synthesis of that data involves judgment calls about which factors to emphasize, and those can vary between runs. This is a property of language models, not a bug.
This is a tool for self-reflection and planning, grounded in a tradition thousands of years old. It is not a fortune-telling service. The analysis identifies tendencies, strengths, and timing patterns in your chart - it does not tell you what will happen. Planetary influences describe the terrain, not the destination. Treat the insights as informed guidance, not certainty.
Automated readings at six timescales - daily, weekly, monthly, yearly, dasa, and lifetime. Included with your account.
Deep, multi-chapter consultation for a specific life question. Uses the full calculation suite and produces a structured 5-chapter report.
Open-ended astrological Q&A. Ask about career, marriage, health, or timing and the bot fetches the relevant charts on the fly.