AstroSage Clone App - White-Label Astrology Tools, Content & Consultation

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 reader portal across roughly 191 routes, a separate practitioner 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 boundary between your free surface and your paid one is a setting rather than a vendor’s decision. There is no runtime licence and nothing is counted per seat.

They are the same software at the same price, and we would rather say that plainly than pretend otherwise. What differs is the problem each one is configured and written around. The Astrotalk Clone is built for an operator whose question is how to bill a consultation minute: metering, the commission waterfall, TDS and practitioner payouts. This page is built for an operator whose question is how to make existing free-tool traffic pay: the astrology engine set, the twelve-sign content surface, the paid report tiers and the AI verticals, with consultation switched on later. Tell us which of those describes you and we configure the same deployment accordingly.

This is the question the search demand asks most often, so here is the direct answer. Free by default: kundali generation with its seven report sections, north and south chart styles, guna milan matching with match reports, panchang resolved by geolocation, the muhurta finder across six purposes, and the daily, weekly and yearly horoscopes across all twelve signs. Paid by default: downloadable kundali PDF reports in three tiers, each of the ten AI verticals, the paid ask-a-question, transit analysis, remedy reports, the remedy marketplace, puja packages, courses and any per-minute consultation. Every one of those is a section toggle and a price field in the console, so the line above is the shipped default rather than a fixed rule, and moving it is a form submission.

The Miracuves AstroSage Clone starts from $2,499 for a launch-ready white-label deployment. Final scope varies with how much of the surface you switch on: a portal launching on free tools and paid report tiers needs one gateway and a chart API, while adding AI verticals, consultations and several payment rails increases integration work. The pre-launch security hardening pass and store publishing for the two mobile apps are quoted alongside.

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: an astrology chart API account for the engines, a merchant account for whichever gateway takes the first report payment, an AI provider key if the verticals are live at launch, MSG91 for OTP and a Firebase project if push must work on day one. The pre-launch security hardening pass is scoped alongside that. Brand assets and hosting access complete the list, and note that a content-led launch needs no practitioner supply at all.

They matter more on this configuration than on a consultation-led one, because they are how a portal with far more readers than practitioners answers anybody at all. The ten are: counsellor personas driven by system prompts the operator writes, a site-wide master chatbot, tarot across a 78 card deck with single and three card spreads, numerology in both Chaldean and Pythagorean systems returning gemstones and mantras, a vastu compass reading eight directions, vision reading from an uploaded palm or face photograph, planetary transit analysis, a paid ask-a-question that routes to either AI or a human, the remedy engine translating weak planets and doshas into remedies, and downloadable AI remedy reports. Each carries its own price and its own on-off switch, and each checks the balance before it runs. Vendor and model sit behind one interface with OpenAI and OpenRouter implementations, so swapping either is a flag change. For completeness: an AI Pandit persona family exists in the code with its web routes disabled in the current build.

No, and that is the main practical difference between this configuration and a consultation marketplace. The free engine set, the twelve-sign content surface, the three paid PDF tiers, the ten AI verticals and the remedy marketplace all operate with no practitioner on the other side, which means the portal can earn before you have recruited anybody. The consultation layer, with per-minute chat, call and live streaming and the commission waterfall behind it, sits behind section flags and is switched on when your audience justifies recruiting supply.

We would rather answer this plainly than reassuringly. The genuine strengths are real: parameterized bindings across roughly 500 raw query fragments giving near-zero classic SQL injection surface, end-to-end encrypted chat with participant authorization and key versioning for when consultations are live, 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, practitioner KYC documents need moving behind signed URLs, and server-side payment verification currently covers three of the twenty gateways. Audit logging does not exist yet and is the item we would close first. One point specific to this configuration: the free tools collect birth date, time and place from anonymous visitors, so retention, export and deletion policy are decisions to settle before launch rather than after a request arrives.

Yes, and for a content-led portal the language packs usually matter before the payment rails do, since the free surface has to read naturally in a market long before anyone there buys a report. There are 143 seeded languages with ten live on the app side and five on the web, and the per-sign horoscope pages and CMS content follow whichever are activated. On the money side, twenty gateway configurations span India via Razorpay, Paytm, PayUmoney, Instamojo and PhonePe, the Gulf via Tap, PayTabs and SADAD, Turkey via Iyzico, Africa via Paystack and Ravepay, Europe via Mollie, LatAm via MercadoPago and PagSeguro, and global rails via Stripe, PayPal, Authorize.net and CoinGate, each with its own currency, symbol and key pair. What nobody can ship for you is the merchant account behind each one.

All of it transfers: the Laravel application, the reader portal, the practitioner portal, the JSON API, the back office, the 170 table schema with its migrations, and both Android builds with their own store listings and package names. It runs on your infrastructure, under your brand, against your own third-party accounts. The eleven documentation files come too, and on this configuration the ones buyers reach for first are usually the schema reference and the VAPT posture, because a portal collecting birth data from anonymous visitors tends to face a privacy review before a security one.