runsonwhat

FreshBooks's tech stack

What does FreshBooks use?

FreshBooks (freshbooks.com) uses at least 55 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents, Qualified for sales and Zendesk for customer support. Last checked .

Industry
Software
Size
201–1,000 employees
Based in
Toronto, Canada
Founded
2003
LinkedIn
Company page
Tools found
55
Categories
20
Layers
5 of 5
Last checked
Oct 2026

FreshBooks'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.

FreshBooks tech stack FAQ

What tools does FreshBooks use?

We've found 55 tools at FreshBooks (freshbooks.com). Edge & Hosting: Google Cloud. Application: YouTube, Anthropic and OpenAI. Data & Observability: Google Analytics, Google Tag Manager and Atlassian Statuspage. Go-to-market: Meta Pixel, Google Ads and Mailchimp. Company Ops: Microsoft 365, Google Workspace and SendGrid. Last checked October 4, 2026.

What cloud does FreshBooks run on?

FreshBooks uses Google Cloud for hosting. We found Google Cloud through DNS records.

What CRM does FreshBooks use?

FreshBooks uses Qualified for sales and CRM. We found Qualified through website code.

What email provider does FreshBooks use?

FreshBooks uses Microsoft 365, Google Workspace and Apple Business for email and documents. We found Microsoft 365 through email records and DNS verification records.

What does FreshBooks use for customer support?

FreshBooks uses Zendesk, Drift and Discourse for customer support. We found Zendesk through email records.

What payment provider does FreshBooks use?

FreshBooks uses Stripe for payments. We found Stripe through DNS verification records.

Does FreshBooks use Microsoft 365?

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

How does runsonwhat know what FreshBooks uses?

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