runsonwhat

FPL's tech stack

What does FPL use?

FPL (fpl.com) uses at least 38 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Adobe Analytics for analytics and Adobe Experience Manager for its website. Last checked .

Industry
Electricity Supply Company
Size
5,001–10,000 employees
Based in
Juno Beach, United States
Founded
1925
LinkedIn
Company page
Tools found
38
Categories
17
Layers
5 of 5
Last checked
Oct 2026

FPL'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

4 tools, where the bytes are served from

Application

7 tools, what the product is built with

Company Ops

15 tools, what the team runs on day to day

FPL tech stack FAQ

What tools does FPL use?

We've found 38 tools at FPL (fpl.com). Edge & Hosting: Amazon Web Services, Amazon Route 53 and Amazon CloudFront. Application: jQuery, Font Awesome and GSAP. Data & Observability: Adobe Experience Platform Tags, Adobe Analytics and Adobe Experience Platform. Go-to-market: Meta Pixel, Microsoft Xandr and Adobe Audience Manager. Company Ops: Microsoft 365, SendGrid and Atlassian. Last checked October 2, 2026.

What cloud does FPL run on?

FPL uses Amazon Web Services for hosting. We found Amazon Web Services through website code.

What email provider does FPL use?

FPL uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does FPL use?

FPL uses Adobe Analytics, Adobe Experience Platform and Qualtrics for analytics, among 5 tools in this category. We found Adobe Analytics through custom domain and website code.

What CMS does FPL use?

FPL uses Adobe Experience Manager for its website. We found Adobe Experience Manager through website code.

Does FPL use Microsoft 365?

Yes. We found Microsoft 365 at FPL through DNS verification records and email records. Microsoft 365 is used by 685,700 companies we track.

How does runsonwhat know what FPL uses?

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