Sourcing note: Grounded in the live site at myastrova.com as observed on 2026-08-26 (public pages only; checkout, admin, and astrologer console were not inspected). Business scale figures (client counts, ratings) are marked [to confirm]. Payment provider is inferred from INR pricing and marked [to confirm].
How I built a Next.js platform that unifies real-time astrologer consultations (chat, call, and video), algorithmic Kundli tools, and a spiritual-products marketplace into one consumer experience for the Indian astrology market.
Featured outcome
A single consumer platform that combines three normally-separate product shapes — a real-time consultation marketplace (Chat / Call / Meet with astrologers), algorithmic tools (Kundli Matching, Horoscope), and a spiritual-commerce storefront (gemstones, Rudraksh, crystals, remedies from ₹79) with order management.
Executive Summary
MyAstrova blends two of the harder consumer-product domains — a live human-consultation marketplace and transactional e-commerce — into one platform, plus a layer of deterministic astrology tooling (Kundli matching, horoscopes). Each of those has a different technical shape: consultations are real-time and availability-driven, commerce is transactional and inventory-driven, and the astrology tools are computational. The product's job is to make them feel like one journey.
The frontend is built on Next.js (confirmed by its /_next/image optimization pipeline) talking to a decoupled API at api.myastrova.com — a headless split that lets the storefront and the consultation/commerce services evolve independently.
The Challenge
A credible astrology platform in this market has to do three things at once:
- Connect users to astrologers in real time — over chat, voice call, and video ("Meet") — which implies presence, availability, and session handling.
- Sell physical and consultation products — a catalog, product pages, cart, orders, and payments.
- Offer instant self-serve tools — Kundli matching and horoscopes that must feel immediate and authoritative.
Doing any one well is a project; doing all three under one identity and one checkout is the actual challenge.
Why the Naive Approach Fails
- A static "book an astrologer" form can't support live chat/call/video or real-time availability.
- Bolting a store onto a consultation site fragments identity, cart, and order history across two systems.
- Astrology tools that feel slow or generic erode the platform's core credibility, so they need a responsive, deterministic engine — not a third-party embed.
- Consumer acquisition in this category lives on WhatsApp and paid social, so growth instrumentation can't be an afterthought.
Architecture Direction
1. Next.js storefront with image optimization
The user-facing app is Next.js with server-optimized imagery (/_next/image), which matters for a media-heavy, SEO-driven consumer site (the homepage is explicitly optimized around "Talk to Astrologer Online in India").
2. Decoupled API backend
Product and media requests resolve against a separate api.myastrova.com service. This headless separation keeps the consultation/commerce domain independent of the presentation layer and allows the astrologer console and storefront to scale separately.
3. Real-time consultation surface
Primary navigation exposes Chats, Calls, and Meet (video) alongside Login — the live-consultation core of the marketplace, distinct from the browsing/commerce paths.
4. Algorithmic astrology tools
Dedicated routes for Kundli Matching (/Kundli-Matching/) and Horoscope (/Horoscope/) provide the instant, self-serve hooks that pull users in before they pay for a consultation.
5. Spiritual-commerce catalog
A product catalog and product pages power the "MyAstrova Mall" — Gemstone and Rudraksh consultations, Palmistry products, and Kundli matching priced from ₹79–₹199 — with MyOrders and Remedies completing the purchase-and-fulfilment loop. Payments are integrated via gateway supporting domestic INR checkout.
6. Growth instrumentation baked in
The live site loads Google Analytics 4 and Meta (Facebook) Pixel, and offers WhatsApp support (wa.me) as a first-class channel — the platform is instrumented for paid-acquisition and conversational support from the start.
Delivery Decisions That Mattered
- SEO-led positioning. The page is built around high-intent search ("Talk to Astrologer Online in India"), treating organic discovery as a primary acquisition channel.
- Low entry price. ₹79 starting products reduce first-purchase friction and create an easy path from free tools to paid consultation.
- WhatsApp as the support spine. Meeting users where they already are, rather than forcing an in-app-only support model.
Outcome
The platform successfully unifies consultation, commerce, and computational tooling under one identity and one Next.js frontend with a decoupled API — the hard integration is done.
What I'd Improve Next
- Fix a production polish bug. A developer comment —
// HeroSection component ke andar— was observed rendering as visible text in the live hero. Strip dev comments from the production build. - Unify identity across consult + commerce so a user's consultations, orders, and remedies live under one profile and history.
- Add social proof — verified reviews/ratings on astrologers and products to reinforce trust at the decision point.
- Performance — tighten the preload/
ashints to improve initial load.
Why This Case Study Matters
MyAstrova is a genuine multi-domain build: real-time consultation, transactional commerce, and deterministic astrology tooling stitched into a single consumer product with a headless Next.js + API architecture. It shows the ability to integrate fundamentally different technical shapes behind one coherent user journey.