Astrology Platform with Smart Alerts
Budget: ₹12,500 – ₹37,500 INR
I’m building a full-featured astrology site that does more than generate charts—it will actively guide astrologer through the ups and downs of planetary transits, mahadasha and antardasha phases. So that Astrologer can notify their client on good and bad transits, good and bad mahadasha, antardasha insights also provide insight into challenging and favorable time and then rely on an intelligent alert engine to tip them off before key moments arrive.
Core scope
• Planetary transit insights presented in an easy timeline view, calculated from a reliable ephemeris (Swiss-Ephemeris or equivalent) and my preferred ayanamsa.
. KP method should also be applied to predicts good timing
• Detailed mahadasha / antardasha breakdowns accurate to the second, with plain-language interpretations pulled from my own text library.
• Fully customizable alerts: user can choose the planets, houses, dasha levels, and orb thresholds that matter to them, plus decide whether reminders land in their email inbox or via SMS. (We might add push notifications later, so please structure the code to keep that door open.)
• A scheduler that checks each profile nightly and queues messages through SendGrid (for email) and Twilio (for SMS) without breaching rate limits.
• Admin dashboard where I can edit interpretation text, adjust default settings, and monitor delivery logs.
Deliverables
1. Responsive front-end (React or Vue preferred) with sign-up, profile, and dashboard pages.
2. Back-end API (Node, Python or PHP—your choice) that performs astronomical calculations, stores preferences in a SQL or NoSQL database, and triggers the alert cron jobs.
3. Integrated email and SMS pipelines, tested end-to-end with sample users.
4. Deployment scripts (Docker or similar) so I can move the stack to AWS Lightsail without drama.
5. Brief hand-over video or document walking me through the codebase and the alert rule builder.
Acceptance criteria
• Transit and dasha timings match Jagannatha Hora output for five test charts within ±2 seconds.
• Good and Bad Nadi transits should be considered i.e. 3rd house, 11the house, 5th house, 7th house and 9th house” receives an email and an SMS at least 1 months before each event.
. When transit planet becomes stationary and its aspects any natal planet proper alert should be sent to the Astrologer/User.
• No duplicate or missed alerts across a month-long simulation with 100 dummy users.
If this sounds like your wheelhouse—especially if you’ve worked with astrology calculations, Swiss-Ephemeris, or Twilio before—let’s talk timelines and milestones.
Core scope
• Planetary transit insights presented in an easy timeline view, calculated from a reliable ephemeris (Swiss-Ephemeris or equivalent) and my preferred ayanamsa.
. KP method should also be applied to predicts good timing
• Detailed mahadasha / antardasha breakdowns accurate to the second, with plain-language interpretations pulled from my own text library.
• Fully customizable alerts: user can choose the planets, houses, dasha levels, and orb thresholds that matter to them, plus decide whether reminders land in their email inbox or via SMS. (We might add push notifications later, so please structure the code to keep that door open.)
• A scheduler that checks each profile nightly and queues messages through SendGrid (for email) and Twilio (for SMS) without breaching rate limits.
• Admin dashboard where I can edit interpretation text, adjust default settings, and monitor delivery logs.
Deliverables
1. Responsive front-end (React or Vue preferred) with sign-up, profile, and dashboard pages.
2. Back-end API (Node, Python or PHP—your choice) that performs astronomical calculations, stores preferences in a SQL or NoSQL database, and triggers the alert cron jobs.
3. Integrated email and SMS pipelines, tested end-to-end with sample users.
4. Deployment scripts (Docker or similar) so I can move the stack to AWS Lightsail without drama.
5. Brief hand-over video or document walking me through the codebase and the alert rule builder.
Acceptance criteria
• Transit and dasha timings match Jagannatha Hora output for five test charts within ±2 seconds.
• Good and Bad Nadi transits should be considered i.e. 3rd house, 11the house, 5th house, 7th house and 9th house” receives an email and an SMS at least 1 months before each event.
. When transit planet becomes stationary and its aspects any natal planet proper alert should be sent to the Astrologer/User.
• No duplicate or missed alerts across a month-long simulation with 100 dummy users.
If this sounds like your wheelhouse—especially if you’ve worked with astrology calculations, Swiss-Ephemeris, or Twilio before—let’s talk timelines and milestones.
Related categories:
PHP
JavaScript
Python
Mobile App Development
Android
SQL
Node.js
Vue.js
NoSQL
Twilio