runsonwhat

Music Story's tech stack

What does Music Story use?

Music Story (music-story.com) uses at least 10 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, Better Stack for monitoring and Bunny.net for content delivery. Last checked .

“Customized music metadata to create immersive, differentiated customer experiences.”

Industry
Music
Size
11–50 employees
Based in
Lille, France
Founded
2008
LinkedIn
Company page
Tools found
10
Categories
9
Layers
5 of 5
Last checked
Oct 2026

Music Story'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

Application

2 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Company Ops

3 tools, what the team runs on day to day

Email Delivery

Security & Compliance

Music Story tech stack FAQ

What tools does Music Story use?

We've found 10 tools at Music Story (music-story.com). Edge & Hosting: Gandi and Bunny.net. Application: Anthropic. Data & Observability: Google Analytics and Better Stack. Company Ops: Google Workspace, Mailjet and NordPass. Last checked October 2, 2026.

What email provider does Music Story use?

Music Story uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does Music Story use?

Music Story uses Google Analytics for analytics. We found Google Analytics through website code.

Does Music Story use Google Workspace?

Yes. We found Google Workspace at Music Story through email records. Google Workspace is used by 126,364 companies we track.

How does runsonwhat know what Music Story uses?

We read public traces only: Music Story'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.