AstroSage Clone Features: The Free Surface Is Generated
A portal competing on horoscopes has to publish every day, forever, and doing that by hand does not scale. Here the chart engines answer on demand and a scheduler writes the twelve-sign horoscopes across three cadences, so a small team can hold a large organic footprint without a content department behind it. Below is everything that ships, with every outside account named against the feature rather than implied away.
Request a Live Demo →Full OverviewFeature Set by Role
Six people touch a content-led portal. All six read the same 170 table schema.
The First-Time Reader
Arrives from search for a birth chart and gets one: kundali with seven report sections in north or south chart style, guna milan matching with a full match report, panchang resolved against their location, a muhurta finder across six purposes, and their sign's horoscope. None of it asks for payment, because none of it is the product.
The Returning Reader
Comes back for the daily horoscope and finds a priced step next to it: the same chart as a downloadable PDF in three tiers, ten wallet-metered AI verticals, transit analysis, remedy reports and a remedy marketplace. A prepaid balance means the second purchase does not re-enter card details, which is where the habit forms.
The Editor
A blog desk carrying per-post reader analytics, a news feed, CMS pages served through a slug catch-all route, website FAQs and a help-centre tree with chat handoff, plus email templates and training videos. This is the surface that turns a calculator into a destination people return to rather than use once.
The Practitioner
KYC gating before the profile is publicly reachable, author profiles feeding the discovery grid, stories and blogs published under their own name, two-sided reviews with moderation and paid profile boosting. Per-minute chat, call and live streaming sit behind section flags for whenever supply is ready.
The Pricing Desk
One screen sets what every paid surface costs: the three report tiers, each of the ten AI verticals independently, the paid ask-a-question, remedy reports and the consultation rates. The boundary between what is free and what is not is a section flag, which means it is a decision you revisit against real behaviour.
The Operator
Eighty-nine admin menu pages across 151 Blade views behind team roles with per-page grants, so an editor can be given the blog desk and nothing else. Underneath sit 298 typed system flags in 47 groups covering section toggles, feature pricing, promos, referral caps, currency, language and provider selection.
The profession vocabulary is a single token reaching more than forty routes, so the same deployment can present as a tarot, numerology or vastu portal without a fork.
Clone vs Generic Script vs Building From Scratch
Most routes to an astrology portal hold up until somebody has to publish tomorrow's horoscopes.
| What decides it | Miracuves AstroSage Clone | Generic astrology script |
|---|---|---|
| Time to a working portal | Six working days | Unknown, and largely do it yourself |
| Daily horoscope content | Generated across twelve signs on a scheduler | Written by hand, every day, forever |
| The free tool set | Kundali, matching, panchang, muhurta, transit | A birth chart, and a roadmap for the rest |
| First revenue | Paid PDF tiers, with no practitioner needed | Advertising, or nothing at all |
| The free and paid boundary | A section flag you move against real behaviour | Hard-coded, and a release to change |
| Content surface | Blog with reader analytics, news, CMS, help centre | A blog plugin, if that |
| Answering at volume | Ten metered AI verticals, priced independently | Nothing answers, and the visit ends |
| Source code | Full ownership, no runtime licence, no per-seat fee | Often limited, sometimes encrypted |
AstroSage 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.
How It Works, End to End
The loop starts where the search traffic actually lands, and only asks for money once the reader has had something useful for nothing.
They arrive for a free chart
The kundali form returns seven report sections in north or south chart style, computed against a chart API on demand rather than accumulating rows. That last detail is what keeps an unmonetized acquisition surface cheap to run at volume: cost scales with use rather than with stored history.
The rest of the tool set is free too
Guna milan matching with a full match report, panchang resolved against the reader's geolocation, a muhurta finder across six purposes, and the twelve per-sign horoscope pages. None of it is gated, because a paywall in front of a calculator is what stops the traffic arriving in the first place.
The scheduler keeps it fresh
Eight scheduled tasks regenerate the daily, weekly and yearly horoscopes across the twelve sign catalog, each sign with its own page. The heaviest recurring publishing job on the site runs without an editor, which is the whole reason a small team can hold this much indexed surface.
The content desks build depth
A blog carrying per-post reader analytics, a news feed, CMS pages on a slug catch-all route, website FAQs and a help-centre tree with chat handoff. Practitioners publish stories and blogs under their own name, which feeds the discovery grid and gives the portal topical range the engines cannot produce.
The first paid step is small
The same chart the reader already generated, offered as a downloadable PDF across three price tiers. It needs no practitioner on the other side, which is why it is the shortest distance between free traffic and first revenue, and usually the first transaction anyone on the portal ever makes.
AI answers at any hour
Ten wallet-metered verticals behind one provider switch: counsellor personas, a master chatbot, tarot on a 78 card deck, numerology across Chaldean and Pythagorean systems, a vastu compass, vision reading, transit analysis, paid ask-a-question, the remedy engine and downloadable AI remedy reports. Each is priced independently.
Diagnosis finds a destination
The remedy engine maps weak planets and doshas to remedies and the AstroMall sells them with GST-aware checkout, cart, coupons and a seven day return window. If and when practitioner supply exists, per-minute chat, call and live streaming switch on behind the same wallet.
Every step after the second is behind a section flag. A portal can launch on the free engine set alone and price nothing until the traffic justifies it.
Every Feature Earns Its Place
Each row is here because a content-led portal stops working without it, not because a competitor lists it.
| Module | Why it is in the base build |
|---|---|
| Scheduled horoscope generation | Twelve signs across three cadences is a publishing job no small team can sustain by hand. Generating it is the difference between a portal that survives and one that quietly stops updating. |
| Chart work computed, not stored | An anonymous free-tool visitor who generates a chart and leaves should not add a row you pay to keep. Bounded cost is what makes a large unmonetized surface affordable. |
| Three paid PDF tiers | The reader has already generated the chart and already trusts the output. Selling that same chart back as a report is the shortest priced step available, and it needs no supply side. |
| Per-post reader analytics | On an organic portal you cannot improve what you cannot see. Knowing which posts hold readers is what turns a content desk into an acquisition function. |
| Slug catch-all CMS | Landing pages, campaign pages and evergreen explainers need to live at arbitrary URLs without a developer. A catch-all route is what makes the operator self-sufficient. |
| Section flags on every surface | Where free ends and paid begins is the single most important number on this platform, and it should be a field you move after watching behaviour rather than a decision frozen at launch. |
| Ten independently priced AI verticals | A portal has far more readers than practitioners. AI is how anybody gets answered at all, and pricing each vertical separately is what lets you find which ones readers actually pay for. |
| Help-centre tree with chat handoff | Free tools generate support questions at the same volume they generate traffic. Answering them in a tree rather than an inbox is what keeps that volume from consuming the team. |
Underneath sit 8 scheduled tasks and 6 queue classes keeping regeneration, reminders and notification dispatch off the request path entirely.
The Technology Behind the Features
Deliberately unexotic, because a small team has to hold a large organic surface.
The framework is the least interesting decision here, deliberately. What is worth looking at is the scheduler and the flag store: one renews the twelve-sign surface without an editor, the other holds the free and paid boundary as a form field.
What Is Not Included in the Base Package
Named here rather than discovered after the invoice.
Birth data is personal data
This point matters more on a content-led portal than on a marketplace: the free tools collect birth date, birth time and birth place from anonymous visitors at scale, and that is personal data whether or not anybody pays. The pre-launch hardening pass is what stands between a public form and a public incident.
There is no audit trail
No authentication-event log and no admin-action log exists, so who edited a price or opened a reader record cannot be reconstructed later. On a platform where an operator can move the free and paid boundary, that is worth closing early, and it is named here rather than left for a review to find.
The chart API is yours
The engines compute against an astrology chart API on demand rather than shipping their own ephemeris. That is what keeps the free surface cheap and bounded, but it means the account, the key and the ongoing cost are yours, and the engines are only as available as that provider is.
Payment verification covers three gateways
Twenty gateway configurations ship, and server-side payment verification is implemented today on Tap, Sadad and PhonePe. Those three are the template the rest are built against. We would rather write that than let a count of configurations imply the same count of verified integrations.
The CRM is five of twenty-five modules
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.
What is built is real
Seven-section kundali in two chart styles, guna milan, geolocated panchang, muhurta across six purposes, twelve sign pages on a scheduler, three paid PDF tiers, ten metered AI verticals, the blog, news, CMS and help-centre desks, an append-only wallet ledger, role-based access across all 89 admin pages, and both Android builds.
The remaining outside accounts are MSG91 for OTP, OpenAI or OpenRouter for the AI layer, Google Maps for geocoding the panchang, FCM and OneSignal for push, an RTC provider if you switch consultations on, and a merchant account per gateway. The full pre-launch list sits on the Development Company page.
See how Miracuves compares to agencies and freelancers
The deployment process, a modelled reference deployment for a free-tool portal, the pre-launch hardening list, and the nine questions worth asking before you hire anyone - on the Development Company page.
Frequently Asked Questions
Which parts are actually free, and which are paid?
Where does the horoscope content come from?
Do I need astrologers to launch this?
How is this different from your Astrotalk Clone?
What do the ten AI features actually do?
Do I get the source code and both mobile apps?
Run the funnel demo, not the feature reel
Generate a free kundali without paying anything, then look at what the platform offers you next, and see the same reader appear in the operator console with their chart history against them.
Explore the AstroSage Clone
The free tools are the marketing budget, not the product
A reader portal, a practitioner 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 is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by AstroSage.
“AstroSage Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to AstroSage, and how clients search for it.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from the AstroSage website or applications.
AstroSage 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.
