Astrotalk Clone Development Company: What to Check Before You Hire
On a metered marketplace the questions that matter are about money rather than features. How a minute is billed, how a commission resolves, what happens when the balance runs out mid-call, and whether anyone can reconstruct an operator action afterwards. Below is how we work, the pre-launch list we publish rather than bury, and the nine questions we would want answered if we were the ones buying.
Talk to Our Team →See PricingAgency vs Freelancer vs Miracuves
Three routes to the same platform, and where each tends to fail once real money moves through it.
| What matters | Freelance team | Miracuves ready-made |
|---|---|---|
| Time to live | Four to nine months, if the scope holds | Six working days |
| The wallet | A balance column, incremented | Dual-currency, append-only ledger, rate snapshot per row |
| Commission | One percentage, edited in code | Boost override, then per-astrologer rate, then default |
| Tax on payouts | Worked out in a spreadsheet each quarter | Withheld at settlement, PAN captured, CSV and PDF |
| Changing a price | A release, and a developer | One of 298 typed flags in 47 groups |
| Overnight demand | Nothing answers | Ten wallet-metered AI verticals |
| A second market | Reopen the payments layer | Twenty gateway configurations, currency per gateway |
| Stated limitations | Rarely offered at all | Published before purchase, the awkward ones included |
| Price behaviour | Hourly, and it moves | $2,499 fixed, quoted before work starts |
Good agencies exist and will build you a competent platform. What the table measures is elapsed months, price certainty, and whether the billing layer was designed in from the start or added after the first payout run went wrong.
Questions Worth Asking Any Provider
Put all nine to us and to whoever else is bidding. What a provider says about the ledger tells you more than any portfolio.
All nine get answered on the first call, the uncomfortable ones included. The Platform Trust section below puts the same answers in writing.
The Six-Step Development Process
What we do, in the order we do it.
Set the commercial numbers
Commission default, per-minute rates, the feature price for each AI vertical, the referral reward and cap, the withdrawal minimum and the tax percentage. On a metered marketplace those flags are the business model rather than settings around it, so they come before anything visual.
Branding, vocabulary and locales
Name, logo and colour scheme across both portals, the back office and both Android builds, one of the five app design sets chosen with dark mode configured, the profession vocabulary token set if you are launching as something other than astrology, and your language packs activated from the 143 seeded.
Deploy and connect your accounts
The application and its MySQL go onto infrastructure you control. Gateway keys, MSG91 for OTP, your RTC provider for calls and live, the AI provider key, Exotel if you want the PSTN fallback, Firebase for push and admin support chat, and your storage provider are connected with credentials you hold.
Hardening and the supply side
The pre-production security pass runs against the named list: test OTP bypass and test contact hooks removed, live keys moved out of the audited configuration, and the rest closed. Alongside it, operator accounts are created against team roles and the astrologer KYC queue is configured with its gating rules.
Walkthrough and handover
We run the money loop end to end in front of your team: recharge a wallet through your live gateway, run a metered chat and watch the deduction land in the ledger, open the session in the console to see the commission split and the tax withheld, then approve a withdrawal. Source, schema and documentation transfer.
The support window
Sixty days of launch guidance, six months of priority bug fixes and twelve months of updates. Additional verified gateways, the audit-logging build and store publishing for both apps usually run inside this window on their own scoped schedule.
Day zero carries more weight here than on most products. A commission default or a per-minute rate set casually is awkward to revisit once practitioners have signed up against it and customers have recharged behind it.
Red Flags That Mean Walk Away
Five answers that should end the conversation
"We bill after the session." Then you have built a collections business rather than a marketplace. Advice already delivered is the hardest thing in the world to invoice for, and the customer has no reason left to pay.
"The wallet is a balance on the user." A number that gets incremented and decremented cannot tell you where value came from, cannot support a refund cleanly, and cannot reconcile a month. You need rows, not a field.
"Commission is a setting in the config file." That is one rate for everyone forever, or a deployment every time you negotiate with a practitioner. Neither survives a real supply side.
"We support twenty payment gateways." Ask how many are verified server-side. Supported and verified are different claims, and the gap between them is where fraudulent recharges live. Ours is three of twenty and we say so.
An estimate with no named exclusions. Software has edges, and marketplace software has provider accounts on top of them. A number presented without either was never costed properly.
We are on the uncomfortable side of our own fourth flag, which is exactly why it is written here in the same words we would use on a call rather than left for you to discover in the codebase.
What a Metered Marketplace Has to Get Right
The parts that are cheap to design in and expensive to retrofit.
All six ship in the base build. Ask on the call and we will open each one in the demo with data behind it, including running a metered session and reading the resulting ledger row.
What We Have Not Done Yet
Six items, stated before a purchase rather than after one.
There is no audit trail
The security review rates audit logging weak: no authentication-event log and no admin-action log, so operator actions are not reconstructable after the fact. On a platform where an operator can change a commission rate or issue a wallet bonus, this is the item we would schedule first, and it leads this list for that reason.
Three of twenty gateways are verified
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 plainly than let a count of configurations imply the same count of verified integrations.
Test hooks ship in the audited code
The codebase as audited carries a test OTP bypass and test contact hooks. They are removed during the pre-production hardening pass we run with you before your domain is exposed, but they are in the code you would be reading, so you should hear it from us rather than find it.
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, sales pipelines, tasks and campaigns have no tables, models or routes yet.
Every provider account is 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 per gateway. The switches are built; the relationships are yours.
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 giving near-zero classic injection surface, an append-only wallet ledger with conversion-rate snapshots, and role-based access across all 89 admin pages.
The VAPT posture document frames its findings as a pre-production gate rather than a clean bill of health. Every item on the hardening list is a configuration change or a code removal measured in developer-hours rather than an architectural rework, and we complete that pass with you.
Modelled Reference Deployment
An authored scenario showing how the shipped platform is configured for an operator converting free-tool traffic into prepaid balance. It is not a client engagement, and every figure in it is a property of the platform rather than a reported outcome.
Metered Astrology Consultation Marketplace
How the shipped platform is configured for an operator converting free-tool traffic into prepaid wallet balance, then metering it across consultations, AI verticals, remedies and rituals.
What the situation makes hard: free astrology tools drawing traffic that never converts into a paid session; practitioner payouts reconciled by hand against commission, tax and refunds; and consultation demand arriving at three in the morning with no human supply available to answer it.
What the configuration addresses: metering every minute against a prepaid wallet rather than billing after the fact; settling practitioner earnings through one commission waterfall with withholding applied at settlement; and covering the overnight hours with wallet-metered AI instead of idle capacity.
What ships in the base build: per-minute metering across chat, call and live with mid-session top-up; a commission waterfall of boost override, then per-astrologer rate, then system default; twenty gateway configurations with a conversion-rate snapshot per transaction; and ten wallet-metered AI verticals answering when no practitioner is online.
Named client deployments are published separately. See the Miracuves portfolio for real engagements with their own reported figures, and hold this page to what it says it is.
Frequently Asked Questions
Is the platform secure, and what needs doing before launch?
Why publish your own gaps?
What exactly do I own at the end?
Will you build the audit logging for us?
Have you deployed this for a live operator?
Can we relaunch this as something other than astrology?
Ask us the hard questions first
Come with the nine questions above. You will get straight answers, the absent audit trail included, well before a contract enters the conversation.
Explore the Astrotalk Clone
Hire on the answers, not the deck
Six working days to a branded metered consultation marketplace on your own infrastructure, the Laravel source in your repository, and a pre-launch list you read before signing rather than after.
Talk to Us →Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by Astrotalk.
“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.
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.
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.
