DivineAPI's tech stack
What does DivineAPI use?
DivineAPI (divineapi.com) uses at least 23 tools we can see from public records, including Amazon Web Services for hosting, Zoho for sales, Google Analytics for analytics and Stripe for payments. Last checked .
“The Most Complete Astrology API Platform. 300+ endpoints across 8 spiritual domains - the widest coverage of any astrology API.”
- Industry
- Internet
- Size
- 11–50 employees
- Based in
- New Delhi, India
- Founded
- 2021
- Company page
- Tools found
- 23
- Categories
- 12
- Layers
- 5 of 5
- Last checked
- Oct 2026
DivineAPI's stack, layer by layer
Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.
Edge & Hosting
3 tools, where the bytes are served from
Hosting & Cloud
Application
8 tools, what the product is built with
Frontend
Payments & Billing
Media & UI
Data & Observability
4 tools, what they measure and store
Monitoring
Go-to-market
6 tools, how they find and keep customers
Sales & CRM
Company Ops
2 tools, what the team runs on day to day
Dev Tools
Security & Compliance
DivineAPI tech stack FAQ
What tools does DivineAPI use?
As of October 2026, runsonwhat has found 23 tools at DivineAPI (divineapi.com) in public records. Edge & Hosting: Amazon Web Services, Hostinger and DigitalOcean. Application: jQuery, Google Fonts and Anthropic. Data & Observability: Google Analytics, Google Tag Manager and Sentry. Go-to-market: Google Ads, Meta Pixel and Mailchimp. Company Ops: reCAPTCHA and Postman. Last checked October 22, 2026.
What cloud does DivineAPI run on?
DivineAPI uses Amazon Web Services for hosting and cloud infrastructure, alongside Hostinger and DigitalOcean, according to runsonwhat (October 2026). runsonwhat found Amazon Web Services through Amazon Web Services on divineapi.com's subprocessor list. Amazon Web Services is used by 146,187 companies runsonwhat tracks.
What CRM does DivineAPI use?
DivineAPI uses Zoho for its CRM, according to runsonwhat (October 2026). runsonwhat found Zoho through Zoho code on divineapi.com and its subprocessor list. Zoho is used by 63,247 companies runsonwhat tracks.
What payment provider does DivineAPI use?
DivineAPI uses Stripe for payments and billing, according to runsonwhat (October 2026). runsonwhat found Stripe through Stripe on divineapi.com's subprocessor list. Stripe is used by 30,224 companies runsonwhat tracks.
What analytics tools does DivineAPI use?
DivineAPI uses Google Analytics for analytics, alongside Google Tag Manager and Inspectlet, according to runsonwhat (October 2026). runsonwhat found Google Analytics through Google Analytics code on divineapi.com. Google Analytics is used by 896,747 companies runsonwhat tracks.
What marketing software does DivineAPI use?
DivineAPI uses Mailchimp for marketing, according to runsonwhat (October 2026). runsonwhat found Mailchimp through Mailchimp on divineapi.com's subprocessor list. Mailchimp is used by 117,126 companies runsonwhat tracks.
Does DivineAPI use jQuery?
Yes. runsonwhat found jQuery at DivineAPI through jQuery code on divineapi.com. jQuery is a Frontend tool used by 924,619 companies runsonwhat tracks.
Does DivineAPI use AI tools?
Yes. runsonwhat has found Anthropic, OpenAI, MCP Registry and Google Gemini at DivineAPI; Anthropic, for example, through Anthropic on divineapi.com's subprocessor list. AI services called only from servers leave no public trace, so DivineAPI may use more AI tools than these.
Which companies have a tech stack similar to DivineAPI's?
The companies with the stacks most like DivineAPI's are Jsmon, Trunk, OneSchema and Morningscore, according to runsonwhat (October 2026). Each shares 9 to 15 tools with DivineAPI, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.
How does runsonwhat know what DivineAPI uses?
runsonwhat reads public records only. Of the 23 tools at DivineAPI, 10 were found through code on divineapi.com, 8 through its own subprocessor list, 3 through DNS records, 1 through website configuration files and 1 through email records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and divineapi.com about monthly.
We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.