Astrotalk Clone App - White-Label Astrology Consultation Marketplace with Metered Billing

It is the codebase rather than a hosted service: a Laravel 10 application on MySQL 8 with 170 tables, 179 controllers and 133 models, a Blade customer portal across roughly 191 routes, a separate astrologer portal, a JSON API of roughly 363 routes serving both Android builds, and an admin back office of 89 menu pages across 151 views. Ownership transfers in full, which matters here because the commission rules and feature prices are your margin. There is no runtime licence and nothing is counted per seat.

This is the question the search demand asks most, so here is the direct answer. Money enters once as a wallet recharge through any of twenty gateway configurations, and the operator then takes a governed share of every consumption event against that balance. Consultation minutes settle through a commission waterfall of boost override, then per-astrologer rate, then system default. Live sessions bill per minute with a default 70 percent practitioner share. Each of the ten AI verticals is priced individually. The remedy marketplace earns product margin, puja packages and course sales settle through the same wallet, gifts carry a commission, and practitioners pay for 24 hour profile boosting. Every one of those rates is a setting rather than a contract.

The Miracuves Astrotalk Clone starts from $3,699 for a launch-ready white-label deployment. Final scope varies with how many payment gateways you run, which real-time and AI providers you wire, the pre-launch security hardening pass, and store publishing for the two mobile apps.

Six working days covers our part, which is rebranding the platform and deploying it to your infrastructure. What lengthens the timeline sits on your side and is almost always external rather than technical: a merchant account per gateway you intend to run, an MSG91 account for OTP, an RTC account with Agora, Zego or 100ms, an AI provider key, and a Firebase project if push and admin support chat must work on day one. The pre-launch security hardening pass is scoped alongside that. Brand assets, hosting access and enough practitioner supply to answer a consultation complete the list.

We would rather answer this plainly than reassuringly. The genuine strengths are 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 giving near-zero classic SQL injection surface, an append-only wallet ledger with conversion-rate snapshots, and role-based access across all 89 admin pages. The pre-launch list is equally real and is short: the audited codebase ships with a test OTP bypass and test contact hooks that are removed before deployment, live API keys sit in the database rather than in environment variables and need rotating, the system-flag endpoint and several user endpoints need auth middleware applied, the JWT secret needs rotation with blacklisting enabled, practitioner KYC documents need moving behind signed URLs, and server-side payment verification currently covers three of the twenty gateways with the rest to follow the same template. Audit logging does not exist yet and is the item we would close first after the auth gate. Every one of those is a configuration change or a code removal measured in developer-hours, and the pass is completed with you before your domain is exposed.

Yes, and this is the part we would point at first, because it is where homegrown builds usually fail. Commission is decided by 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. Every transaction stores a conversion-rate snapshot, so a month spanning several currencies reconciles against the rate that actually applied rather than today’s.

That is the design intent. Twenty gateway configurations cover India through Razorpay, Paytm, PayUmoney, Instamojo and PhonePe, the Gulf through Tap and PayTabs and SADAD, Turkey through Iyzico, Africa through Paystack and Ravepay, Europe through Mollie, LatAm through MercadoPago and PagSeguro, and global rails through Stripe, PayPal, Authorize.net and CoinGate. Each carries its own currency, symbol and test and live key pair. Add 143 seeded languages with ten active on the app side, and per-market store listings for both apps, and the second country becomes a configuration exercise. You still need a merchant account per gateway, which is the part nobody can ship for you.

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 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. On top of that sit five app design sets with dark mode and colour schemes, activated from the panel without a store release.

There is, and we will be precise about it rather than let the word carry more than it should. The specification describes twenty-five CRM modules. 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 producing astrologer, content and AI predictions, and a centralized notification engine. What does not exist yet is lead management, sales pipelines, tasks, campaigns, a lifecycle state machine, internal notes, workflow automation and audit logging, none of which have tables, models or routes. The add-on manager itself is a stub. If the full CRM matters to your operation, it is scoped work we quote rather than something already shipped.

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. You deploy on your own infrastructure under your own brand, with your own accounts for every third party. 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, which is what a procurement or security review will ask for first.