runsonwhat

OR Auto & Home Insurance Agent Brian Halcom - State Farm®'s tech stack

What does OR Auto & Home Insurance Agent Brian Halcom - State Farm® use?

OR Auto & Home Insurance Agent Brian Halcom - State Farm® (brianhalcom.com) uses at least 7 tools we can see from public records, including Google Cloud for hosting and Postmark for email delivery. Last checked .

Industry
Insurance
Size
11–50 employees
Based in
Ontario, United States
LinkedIn
Company page
Tools found
7
Categories
6
Layers
4 of 5
Last checked
Oct 2026

OR Auto & Home Insurance Agent Brian Halcom - State Farm®'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

1 tool, where the bytes are served from

Hosting & Cloud

Application

3 tools, what the product is built with

Go-to-market

2 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Email Delivery

OR Auto & Home Insurance Agent Brian Halcom - State Farm® tech stack FAQ

What tools does OR Auto & Home Insurance Agent Brian Halcom - State Farm® use?

We've found 7 tools at OR Auto & Home Insurance Agent Brian Halcom - State Farm® (brianhalcom.com). Edge & Hosting: Google Cloud. Application: Font Awesome, YouTube and Tailwind CSS. Go-to-market: Meta Pixel. Company Ops: Postmark. Last checked October 6, 2026.

What cloud does OR Auto & Home Insurance Agent Brian Halcom - State Farm® run on?

OR Auto & Home Insurance Agent Brian Halcom - State Farm® uses Google Cloud for hosting. We found Google Cloud through DNS records.

Does OR Auto & Home Insurance Agent Brian Halcom - State Farm® use Meta Pixel?

Yes. We found Meta Pixel at OR Auto & Home Insurance Agent Brian Halcom - State Farm® through website code. Meta Pixel is used by 342,812 companies we track.

How does runsonwhat know what OR Auto & Home Insurance Agent Brian Halcom - State Farm® uses?

We read public traces only: OR Auto & Home Insurance Agent Brian Halcom - State Farm®'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.