The Problem
Most astrology products treat Jyotish as entertainment copy wrapped around ad inventory. Birth charts are approximated. Interpretations are shallow. Privacy is an afterthought.
We started with the opposite premise: what if the computation were genuinely precise, the interpretive framework were sourced from classical Sastra, and the product treated sensitive birth data with the same seriousness as a fintech handles money?
That is Vedic AI — a product company building serious Vedic astrology for the modern interface. Multi-engine AI synthesis. Observatory-grade ephemerides. A trust architecture that makes privacy, consent, and data controls visible from the first interaction.
Company details
Shiv Shankar Dev
Founder and product engineer. Shiv leads the core Jyotish engine, mobile app experience, AI product architecture, and public trust surface.
Nisha Kumari
Co-founder focused on marketing and growth. Nisha supports customer discovery, launch messaging, and community-led distribution for Vedic AI's India-first audience.
Private beta and waitlist
Vedic AI is preparing its Android-first mobile experience for early users while the public website documents the product, trust model, policies, and launch path.
Business contact
Program, partnership, and company-verification communication can be routed through support@vedicai.co.in.
Three Commitments
Precision first
Astronomical rigor at the foundation. Accurate ephemerides, disciplined computational methods, and clear boundaries around what the system can claim.
Sastra, not shorthand
Built around classical Jyotish source material — Brihat Parashara Hora Shastra, Jataka Parijata, Phaladeepika — not thin modern summaries.
AI with restraint
Better verification. Cleaner explanations. Fewer exaggerated promises. The product should feel serious because it is precise, not because it is loud.
Trust is product posture
Vedic AI handles birth data, chat history, and image-based readings. That level of sensitivity requires a trust architecture that goes beyond a buried privacy link. Data controls, consent flows, and policy surfaces are visible features — not compliance chores.