Blinx株式会社's tech stack
What does Blinx株式会社 use?
Blinx株式会社 (blinx.jp) uses at least 11 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Google Analytics for analytics and Cloudflare for content delivery. Last checked .
“ループエンジニアリング、リッチコンテンツ、パーソナライズマーケティングを組み合わせ、システム開発・Webサイト構築・動画制作・LINEの個別チャットを支援する会社。”
- Industry
- Gotomarket Engineering
- Based in
- 品川区, Japan
- Founded
- 2025
- Tools found
- 11
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Blinx株式会社'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
2 tools, where the bytes are served from
Hosting & Cloud
CDN & Edge
Application
2 tools, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
3 tools, what the team runs on day to day
Blinx株式会社 tech stack FAQ
What tools does Blinx株式会社 use?
We've found 11 tools at Blinx株式会社 (blinx.jp). Edge & Hosting: Cloudflare and Vercel. Application: Next.js. Data & Observability: Google Analytics and Microsoft Clarity. Go-to-market: Google Ads. Company Ops: Google Workspace, Resend and Lark. Last checked October 4, 2026.
What cloud does Blinx株式会社 run on?
Blinx株式会社 uses Vercel for hosting. We found Vercel through DNS records and website code.
What email provider does Blinx株式会社 use?
Blinx株式会社 uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Blinx株式会社 use?
Blinx株式会社 uses Google Analytics and Microsoft Clarity for analytics. We found Google Analytics through website code.
Does Blinx株式会社 use Cloudflare?
Yes. We found Cloudflare at Blinx株式会社 through DNS records. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Blinx株式会社 uses?
We read public traces only: Blinx株式会社'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.