runsonwhat

FEDSYNC's tech stack

What does FEDSYNC use?

FEDSYNC (fedsync.net) uses at least 15 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
IT Services
Size
51–200 employees
Based in
Alexandria, United States
Founded
2007
LinkedIn
Company page
Tools found
15
Categories
11
Layers
5 of 5
Last checked
Oct 2026

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

5 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

FEDSYNC tech stack FAQ

What tools does FEDSYNC use?

We've found 15 tools at FEDSYNC (fedsync.net). Edge & Hosting: Cloudflare, Google Cloud and Fastly. Application: jQuery, Google Fonts and GSAP. Data & Observability: Google Analytics and Sentry. Go-to-market: Wix. Company Ops: Microsoft 365 and N-able Mail Assure. Last checked October 5, 2026.

What cloud does FEDSYNC run on?

FEDSYNC uses Google Cloud and HostGator for hosting. We found Google Cloud through website code.

What email provider does FEDSYNC use?

FEDSYNC uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.

What analytics tools does FEDSYNC use?

FEDSYNC uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does FEDSYNC use?

FEDSYNC uses Wix for its website. We found Wix through custom domain and website code.

Does FEDSYNC use Microsoft 365?

Yes. We found Microsoft 365 at FEDSYNC through email records. Microsoft 365 is used by 513,206 companies we track.

How does runsonwhat know what FEDSYNC uses?

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