Signature Healthcare's tech stack
What does Signature Healthcare use?
Signature Healthcare (signature-healthcare.org) uses at least 13 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics and Barracuda for security. Last checked .
- Industry
- Healthcare
- Size
- 1,001–5,000 employees
- Based in
- Brockton, United States
- Founded
- 1896
- Company page
- Tools found
- 13
- Categories
- 8
- Layers
- 4 of 5
- Last checked
- Oct 2026
Signature Healthcare'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
4 tools, what the product is built with
Data & Observability
2 tools, what they measure and store
Go-to-market
3 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
4 tools, what the team runs on day to day
Workspace
Security & Compliance
Signature Healthcare tech stack FAQ
What tools does Signature Healthcare use?
We've found 13 tools at Signature Healthcare (signature-healthcare.org). Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel and Google Ads. Company Ops: Microsoft 365, Apple Business and Barracuda. Last checked October 3, 2026.
What email provider does Signature Healthcare use?
Signature Healthcare uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does Signature Healthcare use?
Signature Healthcare uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does Signature Healthcare use Microsoft 365?
Yes. We found Microsoft 365 at Signature Healthcare through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Signature Healthcare uses?
We read public traces only: Signature Healthcare'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.