LFPC's tech stack
What does LFPC use?
LFPC (lfpc.net) uses at least 11 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Wix for its website. Last checked .
- Industry
- Healthcare
- Size
- 51–200 employees
- Based in
- Litchfield, United States
- Founded
- 1978
- Company page
- Tools found
- 11
- Categories
- 11
- Layers
- 5 of 5
- Last checked
- Oct 2026
LFPC'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
Monitoring
Analytics
Go-to-market
3 tools, how they find and keep customers
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
LFPC tech stack FAQ
What tools does LFPC use?
We've found 11 tools at LFPC (lfpc.net). Edge & Hosting: Google Cloud and Fastly. Application: React. Data & Observability: Google Analytics and Sentry. Go-to-market: Google Ads and Wix. Company Ops: Microsoft 365 and AppRiver. Last checked October 7, 2026.
What cloud does LFPC run on?
LFPC uses Google Cloud for hosting. We found Google Cloud through website code.
What email provider does LFPC use?
LFPC uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does LFPC use?
LFPC uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does LFPC use?
LFPC uses Wix for its website. We found Wix through custom domain and website code.
Does LFPC use Microsoft 365?
Yes. We found Microsoft 365 at LFPC through DNS verification records and email records. Microsoft 365 is used by 685,462 companies we track.
How does runsonwhat know what LFPC uses?
We read public traces only: LFPC'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.