Balai Litbang Kesehatan Magelang's tech stack
What does Balai Litbang Kesehatan Magelang use?
Balai Litbang Kesehatan Magelang (kemkes.go.id) uses at least 8 tools we can see from public records, including Google Analytics for analytics, Cloudflare for content delivery, SendGrid for email delivery and GlobalSign for security. Last checked .
- Size
- 1–10 employees
- Based in
- Borobudur, Indonesia
- Company page
- Tools found
- 8
- Categories
- 6
- Layers
- 5 of 5
- Last checked
- Oct 2026
Balai Litbang Kesehatan Magelang'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
1 tool, where the bytes are served from
CDN & Edge
Application
2 tools, what the product is built with
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
3 tools, what the team runs on day to day
Email Delivery
Security & Compliance
Balai Litbang Kesehatan Magelang tech stack FAQ
What tools does Balai Litbang Kesehatan Magelang use?
We've found 8 tools at Balai Litbang Kesehatan Magelang (kemkes.go.id). Edge & Hosting: Cloudflare. Application: YouTube and Font Awesome. Data & Observability: Google Analytics. Company Ops: SendGrid, GlobalSign and UserWay. Last checked October 1, 2026.
What analytics tools does Balai Litbang Kesehatan Magelang use?
Balai Litbang Kesehatan Magelang uses Google Analytics for analytics. We found Google Analytics through website code.
Does Balai Litbang Kesehatan Magelang use Cloudflare?
Yes. We found Cloudflare at Balai Litbang Kesehatan Magelang through DNS records, email records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Balai Litbang Kesehatan Magelang uses?
We read public traces only: Balai Litbang Kesehatan Magelang's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website 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.