Astrotalk Clone · Features

Astrotalk Clone Features: The Ledger Is the Hard Part

Anyone can generate a birth chart. What separates a spiritual-services business from a content site is whether it can meter a minute, split a commission, withhold tax and reconcile a month that spanned three currencies. Every capability below is built and demonstrable, and where one needs an outside account or ships partially implemented, that is stated against the feature rather than implied away.

Request a Live Demo →Full Overview
170 database tables
298 system flags
6 days to deploy
Every minute
Metered before service
What One Wallet Balance Pays For
01Chat, call and live minutes
02Ten metered AI verticals
03Paid kundali and match reports
04Remedies from the AstroMall
05Puja packages and course seats
06Gifts sent during a live stream
170
Database Tables
89
Admin Console Pages
298
System Flags
20
Gateway Configurations
By Role

Feature Set by Role

Six people touch this platform. All six read the same 170 table schema.

01

The Customer

Discovery by skill, language, price and rating, then chat, audio or video call, or a live stream, with every minute metered against a prepaid wallet and a mid-session top-up that does not drop the session. Messages are end-to-end encrypted with real-time translation, and the free kundali, guna milan, panchang and muhurta tools sit alongside as the reason to arrive at all.

02

The Astrologer

KYC gating before the profile goes public, availability windows, a request queue with automatic rejection of stale requests, and paid profile boosting for visibility. Earnings settle through a commission waterfall, and withdrawals run over UPI, bank transfer or PayPal against a configurable minimum with TDS applied and PAN captured at request.

03

The Assistant

Sub-accounts under a practitioner with their own permission set, so a busy astrologer can have someone else work the queue, answer chats or manage the schedule without handing over the earning account itself. This is the surface that lets a single high-demand practitioner scale past their own hours.

04

The Finance Desk

A commission waterfall resolving boost override, then the per-astrologer rate, then the system default, with an admin commission ledger written per event. TDS withheld at settlement with reports exporting to CSV and PDF, withdrawal approval queues, wallet bonuses issued singly or in bulk, and a conversion-rate snapshot on every transaction row.

05

The Moderator

Data monitoring across chats and calls, block-keyword moderation on messages, two-sided review moderation between customer and practitioner, and approval of astrologer-created puja packages before they reach the catalog. On a marketplace selling advice rather than goods, this is the surface that protects the brand.

06

The Operator

Eighty-nine admin menu pages across 151 Blade views, governed by team roles with per-page grants, sitting on 298 system flags in 47 groups. Section toggles for chat, call, live and AI, feature pricing for every paid surface, commission defaults, promotional offers, referral caps, withdrawal minimums and the TDS percentage are all form fields.

The profession vocabulary is a single token across more than forty routes, so relaunching the same deployment as a tarot, counselling or coaching marketplace is a flag change rather than a fork.

Compare

Clone vs Generic Script vs Building From Scratch

Most routes to a consultation marketplace hold up until the first payout run.

What decides itMiracuves Astrotalk CloneGeneric consultation script
Time to a working platformSix working daysUnknown, and largely do it yourself
How a minute is billedMetered against a prepaid wallet before serviceInvoiced after the session, and chased
Running out mid-sessionTop-up inside the session without dropping itThe call ends, and usually so does the sale
Practitioner commissionBoost override, then per-astrologer rate, then defaultOne global percentage, edited in code
Tax on payoutsTDS withheld at settlement, CSV and PDF reportsA spreadsheet, reconciled by hand
A second countryTwenty gateway configurations, currency per gatewayReopen the payments layer
Overnight demandTen wallet-metered AI verticals answerNothing answers, and the intent is lost
Changing a priceA form field among 298 flagsA release, and a developer
Source codeFull ownership, no runtime licence, no per-seat feeOften limited, sometimes encrypted

Astrotalk itself is the reference for what this category looks like; it is not a product you can buy or self-host. The commercially useful comparison is the second column against the third, and against a custom build, which is covered on the Development Cost page.

End to End

How It Works, End to End

Every step is enforced server-side rather than in the client, which is what makes the money reconcilable afterwards.

Step 1

A free tool brings them in

Kundali with seven report sections, guna milan matching, panchang with geolocation, a muhurta finder across six purposes, and daily, weekly and yearly horoscopes across a twelve sign catalog. None of it is metered, because its job is to attract intent rather than to earn.

Step 2

They find a practitioner

Discovery filters on skill, language, price and rating, against profiles that only appear publicly once KYC has cleared. Availability windows decide who is reachable now, and paid profile boosting decides who surfaces first, which is itself a revenue line rather than an algorithm nobody controls.

Step 3

The wallet is recharged

Money enters once, through any of twenty gateway configurations spanning India, the Gulf, Turkey, Africa, Europe, Latin America and the global rails. Each carries its own currency, symbol and test and live key pair, and every transaction stores a conversion-rate snapshot so a multi-currency month reconciles later against the rate that actually applied.

Step 4

The session is metered

Chat, audio, video and live stream all bill per minute against that balance, with media carried by Agora, Zego or 100ms behind one provider switch and an Exotel PSTN fallback dialing masked numbers. If the balance runs low the customer tops up inside the session rather than losing it.

Step 5

Or the AI answers instead

When no practitioner is online, ten wallet-metered verticals take the session: AI counsellors, a site-wide master bot, tarot on a 78 card deck, numerology, vastu, vision reading, transit analysis, paid ask-a-question, the remedy engine and paid AI remedy reports. Each is priced and toggled independently, and each debits the same wallet.

Step 6

The commission resolves

An append-only ledger row lands per consumption event carrying commission and tax context. The waterfall checks for an active boost override, then the per-astrologer rate, then the system default, and live sessions bill per minute against a default seventy percent practitioner share.

Step 7

The practitioner is paid

Withholding is applied at settlement with PAN captured at the withdrawal request, TDS reports export as CSV and PDF, and disbursement runs over UPI, bank transfer or PayPal Payouts with bulk support. This is the step homegrown builds usually get wrong, and it is the one practitioners judge you on.

The same balance also buys remedies from the AstroMall with GST-aware checkout, puja packages delivered over a live broadcast, course seats and gifts sent during a stream, each carrying its own commission treatment.

Justified

Every Feature Earns Its Place

Each row is here because a metered marketplace stops working without it, not because a competitor lists it.

ModuleWhy it is in the base build
Prepaid wallet, metered before serviceBilling after a consultation means chasing payment for advice already given. Metering against a balance that exists first removes the collection problem entirely.
Mid-session top-upA session that dies on an empty balance loses the minute, the sale and usually the customer. Topping up without leaving the session is the difference between a lapse and a renewal.
Commission waterfallA single global percentage cannot express a promotional boost or a star practitioner's negotiated rate. Three resolution levels is the minimum that survives contact with real supply.
Conversion-rate snapshot per rowReconciling a multi-currency month against today's rate produces numbers that do not match what happened. Storing the rate that applied is what makes the ledger auditable.
TDS withholding at settlementWithholding calculated after the fact is a reconciliation project every quarter. Applied at settlement with PAN captured, it is a report rather than an exercise.
Ten metered AI verticalsConsultation demand arrives at three in the morning when no practitioner is awake. AI covers those hours at near-zero marginal cost instead of losing the intent.
298 flags across 47 groupsFeature prices, commission defaults, section toggles and referral caps are the numbers your margin depends on. They belong in a form rather than in a deployment.
KYC gating before listingA marketplace selling personal guidance carries reputational risk from its supply side. Verifying before a profile is publicly reachable is cheaper than removing it afterwards.

Underneath sit 8 scheduler tasks and 6 queue job classes carrying horoscope generation, appointment and puja reminders, commission settlement and notification dispatch, none of which belongs in a web request.

Stack

The Technology Behind the Features

Deliberately unexotic, because the operator has to hire for it.

Application coreLaravel 10 on PHP with MySQL 8, Blade templating and a Vite build: 170 database tables with incremental migrations, 179 controllers and 133 models, 8 scheduler tasks and 6 queue job classes, with parameterized bindings across roughly 500 raw query fragments.
Surfaces and routingRoughly 191 customer and astrologer website routes, roughly 363 JSON API routes under a JWT guard serving both Android builds, and roughly 552 admin routes behind session-based role access, rendering 89 admin menu pages across 151 Blade views.
Real-time layerProvider-agnostic voice and video behind a single switch across Agora, Zego and 100ms, live streaming with RTMP fan-out and recording, an Exotel PSTN fallback dialing masked numbers, and Firebase Firestore carrying admin support chat.
AI layerOne provider interface with the provider, model and key held as system flags, so all ten verticals inherit a single switch between OpenAI and OpenRouter. Wallet metering is applied before every call, and history persists with PDF export.
Money and ledgerA dual-currency wallet operating in amount or coin mode across twenty gateway configurations, an append-only transaction ledger, a conversion-rate snapshot per transaction, the commission waterfall with TDS withholding, and withdrawals over UPI, bank and PayPal Payouts.
Configuration and storageA system flag store of 298 typed flags across 47 groups, a profession vocabulary swap reaching more than forty routes, 143 seeded languages with ten active app-side and five on web, five app design sets with dark mode, and storage selectable per deployment across local, AWS, GCS and DigitalOcean.

The interesting engineering here is not the framework. It is the flag store and the ledger: typed flags mean pricing and packaging change without a release, and an append-only ledger with rate snapshots means a multi-currency month reconciles against the rate that actually applied.

Honest Readiness

What Is Not Included in the Base Package

Named here rather than discovered after the invoice.

01

Payment verification covers three gateways

Twenty gateway configurations ship, but server-side payment verification is implemented today on three of them: Tap, Sadad and PhonePe. Those three are the template the rest are built against, and we would rather say that than let twenty configurations imply twenty verified integrations.

02

There is no audit trail

The security review rates audit logging weak, with no authentication-event log and no admin-action log, so operator actions are not currently reconstructable after the fact. On a platform moving money this is the item we would schedule first, and it is a named pre-launch gap rather than something to find in a review.

03

The CRM is five of twenty-five modules

The specification describes twenty-five. Five have functional implementations: a Customer 360 timeline, nine computed behavioural tags, health metrics covering lifetime value, retention and churn, a recommendation engine and a centralized notification engine. Lead management, pipelines, tasks and campaigns have no tables, models or routes yet.

04

Test hooks ship, and are removed

The audited codebase carries a test OTP bypass and test contact hooks. They are removed as part of the pre-production hardening pass we run with you before your domain is exposed, but they exist in the code you would be reading, so you should hear it from us first.

05

Nine outside accounts are yours

MSG91 for OTP, Agora, Zego or 100ms for real-time media, OpenAI or OpenRouter for the AI layer, Exotel for PSTN fallback, FCM and OneSignal for push, Firebase for admin support chat, Google Maps for geocoding, an astrology chart API, and a merchant account for every gateway you intend to run.

06

What is built is real

End-to-end encrypted chat with participant authorization and key versioning, which the security review calls the strongest control in the stack, parameterized bindings across roughly 500 raw query fragments, an append-only wallet ledger with conversion-rate snapshots, role-based access across all 89 admin pages, and both Android builds with their own store listings.

The full pre-launch hardening list, and what each item costs to close, sits on the Development Company page.

Development Company

See how Miracuves compares to agencies and freelancers

The deployment process, a modelled reference deployment for a metered marketplace, the pre-launch hardening list, and the nine questions worth asking before you hire anyone - on the Development Company page.

See the comparison →
FAQ

Frequently Asked Questions

What do the ten AI features actually do?
AI counsellor personas with admin-authored system prompts, a site-wide master chatbot, tarot on a 78 card deck with single and three card spreads, numerology across Chaldean and Pythagorean systems with gemstones and mantras, a vastu compass evaluating eight directions, vision reading from an uploaded palm or face photo, planetary transit analysis, paid ask-a-question routing between AI and a human astrologer, the remedy engine mapping weak planets and doshas to remedies, and paid downloadable AI remedy reports. Each is priced and toggled independently and each debits the wallet.
Does it handle practitioner payouts and tax properly?
Yes, and this is the part we would point at first, because it is where homegrown builds usually fail. Commission resolves through a waterfall: a boost-active override first, then the per-astrologer rate, then the system default, with an admin commission ledger written per event. Withholding is applied at settlement with PAN captured at the withdrawal request, and TDS reports export as CSV and PDF. Withdrawals run over UPI, bank transfer or PayPal with a configurable minimum, and PayPal Payouts supports bulk disbursement.
Can I run this in more than one country?
That is the design intent. Twenty gateway configurations cover India, the Gulf, Turkey, Africa, Europe, Latin America and the global rails, each carrying its own currency, symbol and test and live key pair. Add 143 seeded languages with ten active on the app side, per-market store listings for both apps, and a conversion-rate snapshot on every transaction, and the second country becomes a configuration exercise. You still need a merchant account per gateway you intend to run.
What can the operator change without a developer?
Most of it. There are 298 system flags across 47 groups covering section toggles for chat, call, live and AI, feature pricing for every paid surface, commission defaults, promotional offers and first-free-chat, referral rewards and caps, withdrawal minimums and the TDS percentage, currency and language, storage and streaming provider selection, rate limits, and the store links for both apps. The profession vocabulary is a single token, so relaunching as a tarot or counselling marketplace does not need a fork.
Is there a CRM, and how complete is it?
There is, and we will be precise rather than let the word carry more than it should. The specification describes twenty-five modules and five have functional implementations: a Customer 360 view with a unified timeline assembled from registrations, kundalis, sessions, orders, recharges and refunds, nine computed behavioural tags, customer health metrics covering lifetime value, retention and churn scoring, a recommendation engine, and a centralized notification engine. Lead management, sales pipelines, tasks and campaigns do not exist yet.
Do I get the source code and both mobile apps?
Yes to all of it: the Laravel application, the customer web portal, the astrologer portal, the JSON API, the admin back office, the 170 table schema with migrations, and both Android builds, the customer app and the separate astrologer app, each with its own store listing and package name. The documentation suite transfers too, including the schema reference, the entity relationship document, the API collection, the developer and security handbooks and the VAPT posture.

Run the money demo, not the feature reel

Recharge a wallet, start a chat and watch the per-minute deduction land in the ledger, then open the same session in the operator console and see the commission split and the tax withheld against it.

Money enters once. It is consumed many times.

A customer portal, an astrologer portal, a JSON API for both Android builds and an 89 page operations back office on one Laravel and MySQL core, with the full source on infrastructure you own.

Talk to Us →
Miracuves · Astrotalk Clone Solution Feature set, stack and stated limitations cross-verified against the hub, 2026-09-07
Disclaimer

Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by Astrotalk.

Why this name

Astrotalk Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to Astrotalk, and how clients search for it.

Who built this

The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from the Astrotalk website or applications.

Trademarks

Astrotalk and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.