runsonwhat

Vin Di Bona's tech stack

What does Vin Di Bona use?

Vin Di Bona (fbwmedia.com) uses at least 9 tools we can see from public records, including Microsoft 365 for email and documents and WordPress for its website. Last checked .

Industry
Production Company
Based in
United States
Founded
2010
Re-check liveVisit fbwmedia.com
Tools found
9
Categories
6
Layers
3 of 5
Last checked
Oct 2026

Vin Di Bona'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.

Application

3 tools, what the product is built with

Frontend

Media & UI

Go-to-market

3 tools, how they find and keep customers

Website & CMS

Marketing

Company Ops

3 tools, what the team runs on day to day

Workspace

Dev Tools

Companies like Vin Di Bona also use

Tools common among companies with a similar stack that we haven't found at Vin Di Bona.

Companies with a stack like Vin Di Bona's

Ranked by shared tools, with rare tools counting more.

More Production Company companies

Other Production Company companies we've checked.

Vin Di Bona tech stack FAQ

What tools does Vin Di Bona use?

We've found 9 tools at Vin Di Bona (fbwmedia.com). Application: jQuery, Vimeo and YouTube. Go-to-market: WordPress and Yoast SEO. Company Ops: Microsoft 365, Google Workspace and BugHerd. Last checked October 3, 2026.

What email provider does Vin Di Bona use?

Vin Di Bona uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records and email records.

What CMS does Vin Di Bona use?

Vin Di Bona uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does Vin Di Bona use Microsoft 365?

Yes. We found Microsoft 365 at Vin Di Bona through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Vin Di Bona uses?

We read public traces only: Vin Di Bona'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.