AstroSage Clone Features: The Full Content-Led Portal Scope
This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product or a fixed bundle.
Six people touch a content-led portal - two kinds of reader, an editor, a practitioner, a pricing desk and an operator. Every capability below is proposed scope for one of them, confirmed in writing before work starts.
Feature Set by Role
Every capability below is proposed scope, grouped by the person who uses it.
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 - the surface that turns a calculator into a destination people return to.
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 free and paid is a section flag - a decision you revisit against real behaviour.
The operator
Proposed: 89 admin menu pages 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.
The Proposed Build vs a Generic Script
Most routes to an astrology portal hold up until somebody has to publish tomorrow's horoscopes. The middle column is proposed scope, agreed in writing per project; the right column is the check worth making on any alternative.
| What decides it | Omnistu proposed build | What to check on other routes |
|---|---|---|
| Daily horoscope content | Generated across twelve signs on a scheduler | Ask who writes tomorrow's horoscopes, and what that costs every month |
| The free tool set | Kundali, matching, panchang, muhurta, transit | Ask which tools exist beyond a birth chart, and which are roadmap |
| First revenue | Paid PDF tiers, with no practitioner needed | Ask what the first priced step is and whether it needs supply you do not have |
| The free and paid boundary | A section flag you move against real behaviour | Ask whether moving that boundary is a form field or a release |
| Content surface | Blog with reader analytics, news, CMS, help centre | Ask what publishing surface exists beyond a blog plugin |
| Answering at volume | Ten metered AI verticals, priced independently | Ask what answers a reader when no practitioner is online |
| Source code | Full ownership, no runtime licence, no per-seat fee - as proposed terms | Ask whether any file is encrypted or licence-checked |
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 proposed build against the alternatives, 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. Each step below is proposed flow.
1 - 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 keeps an unmonetized acquisition surface cheap to run at volume: cost scales with use rather than with stored history.
2 - 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.
3 - 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 running without an editor.
4 - 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, feeding the discovery grid and giving the portal topical range the engines cannot produce.
5 - 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.
6 - AI answers at any hour
Ten wallet-metered verticals behind one provider switch between OpenAI and OpenRouter, with vendor, model and key held as system flags: 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.
7 - Diagnosis finds a destination
The remedy engine maps weak planets and doshas to remedies, and the storefront sells them with tax-aware checkout, cart and coupons. If and when practitioner supply exists, per-minute chat, call and live streaming switch on behind the same wallet.
Every step is a flag
Every step after the second sits 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 proposed base |
|---|---|
| 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. |
Proposed underneath: eight scheduled tasks and six queue classes keeping regeneration, reminders and notification dispatch off the request path entirely.
The Technology Behind the Proposed Scope
Deliberately unexotic, because a small team has to hold a large organic surface. Every element is the proposed architecture - counts from the specification inventory, confirmed per project.
Astrology engines
A seven-section kundali in north and south chart styles from the same data, guna milan matching with full match reports, panchang resolved against reader geolocation, a muhurta finder across six purposes, and transit analysis feeding the remedy engine.
Scheduled generation
Eight scheduled tasks spanning the content and reminder domains regenerate the twelve-sign catalog daily, weekly and yearly, with six queue classes keeping dispatch off the request path. No editor is required for the recurring publishing job.
Application core
Laravel 10 on PHP with MySQL 8, Blade templating and a Vite build: 170 tables reached through incremental migrations, 179 controllers against 133 models, roughly 191 reader routes and 552 admin routes, with bound parameters across every raw query fragment.
AI layer
One provider interface with vendor, model and key all held as system flags, so all ten verticals share a single switch between providers. The balance is checked and debited ahead of each call, and reading history is retained and exportable as PDF.
Configuration and storage
298 typed flags spread over 47 groups, the profession wording replaced across more than forty routes, 143 languages seeded with ten live app-side and five on web per the specification inventory, five app design sets with dark mode, and a storage backend chosen per deployment.
What is worth looking at
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.
Named Here Rather Than Discovered Later
These items are additive scope or external accounts beyond the proposed base, quoted in writing per project. Nothing here is implemented or verified by this preview.
Birth data is personal data
This matters more on a content-led portal than on a marketplace: the proposed free tools would collect birth date, time and place from anonymous visitors at scale, and that is personal data whether or not anybody pays. That collection requires privacy and security controls scoped and tested per project; no single hardening pass prevents an incident, and this preview does not implement or verify any of it.
Reported gap: no audit trail
Stated plainly: the supplied specification records no authentication-event log and no admin-action log, 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. This preview does not implement or verify the logging; the build work is scoped, tested and quoted with you - 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 keeps the free surface cheap and bounded, but the account, the key and the ongoing cost are yours, and the engines are only as available as that provider is.
Reported inventory: three of twenty gateways verified
Stated plainly: the supplied specification records twenty gateway configurations with server-side payment verification on three - Tap, Sadad and PhonePe; this preview does not implement or verify any of them. 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.
Reported inventory: five of twenty-five CRM modules
Stated plainly: the supplied specification records five functional implementations - a customer timeline, computed behavioural tags, health metrics covering lifetime value, retention and churn, a recommendation engine and a centralized notification engine - with lead management, pipelines, tasks and campaigns not yet built. This preview does not implement or verify any of them; each is scoped individually.
Proposed base scope
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 the admin pages, and both Android builds - all as proposed scope confirmed in writing.
Remaining outside accounts recorded in the supplied specification: MSG91 for OTP, OpenAI or OpenRouter for the AI layer, Google Maps for geocoding the panchang, FCM and OneSignal for push, a calling provider if you switch consultations on, and a merchant account per gateway - proposed external dependencies, not verified integrations.
Frequently Asked Questions
Which parts are free, and which are paid?
Free by default in the proposed configuration: kundali generation with its seven report sections, north and south chart styles, guna milan matching, geolocated panchang, the muhurta finder, 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 and the consultation layer. Every one of those boundaries is a section flag you can move.
Where does the horoscope content come from?
The platform generates it. Eight scheduler tasks produce the daily, weekly and yearly horoscopes across the twelve-sign catalog, each sign with its own page, so the largest recurring publishing job runs without an editor. Alongside that sit the desks an operator does write in: a blog with per-post reader analytics, a news feed, CMS pages, website FAQs and a help-centre tree with chat handoff.
Do I need astrologers to launch this?
No - 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, so the portal can earn before you have recruited anybody. The consultation layer sits behind section flags and switches on when your audience justifies it.
How is this different from the Astrotalk Clone?
They are the same underlying software, 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, tax withholding and practitioner payouts. This page is built for an operator whose question is how to make existing free-tool traffic pay: the engine set, the content surface, the paid report tiers and the AI verticals, with consultation switched on later.
What do the ten AI features actually do?
They are how a portal with far more readers than practitioners answers anybody at all: 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 Chaldean and Pythagorean systems returning gemstones and mantras, a vastu compass reading eight directions, vision reading from an uploaded photograph, transit analysis, paid ask-a-question, the remedy engine and downloadable AI remedy reports.
Do I get the source code and both mobile apps?
That is the proposed handover: the Laravel application, the reader portal, the practitioner portal, the JSON API, the back office, the 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 - on this configuration the ones buyers reach for first are usually the schema reference and the VAPT posture.
Independence and third-party names
Omnistu is an independent software development project. 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 similar functionality, and how buyers search for it. 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.
Discuss your scope by message
Tell us which surfaces you would switch on at launch - free tools, paid reports, AI verticals - and which markets you are launching in. We reply by email with a scoped proposal - no calls required, no phone numbers collected.
