waja bazar's tech stack
What does waja bazar use?
waja bazar (waja.co.jp) uses at least 13 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Google Analytics for analytics and Cloudflare for content delivery. Last checked .
- Based in
- Japan
- Founded
- 2003
- Tools found
- 13
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
waja bazar'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
Application
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
3 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
3 tools, what the team runs on day to day
Email Delivery
Workspace
waja bazar tech stack FAQ
What tools does waja bazar use?
We've found 13 tools at waja bazar (waja.co.jp). Edge & Hosting: Cloudflare, Amazon Web Services and Amazon Route 53. Application: jQuery and Google Fonts. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads and Criteo. Company Ops: Google Workspace, Amazon SES and Mailgun. Last checked October 3, 2026.
What cloud does waja bazar run on?
waja bazar uses Amazon Web Services for hosting. We found Amazon Web Services through website code.
What email provider does waja bazar use?
waja bazar uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does waja bazar use?
waja bazar uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does waja bazar use Cloudflare?
Yes. We found Cloudflare at waja bazar through website code. Cloudflare is used by 303,836 companies we track.
How does runsonwhat know what waja bazar uses?
We read public traces only: waja bazar'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.