First Community Bank's tech stack
What does First Community Bank use?
First Community Bank (fcbot.com) uses at least 12 tools we can see from public records, including Microsoft 365 for email and documents, Mixpanel for analytics, Cloudflare for content delivery and SendGrid for email delivery. Last checked .
- Industry
- Banking
- Size
- 51–200 employees
- Based in
- Corpus Christi, United States
- Founded
- 1983
- Company page
- Tools found
- 12
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
First Community Bank'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
CDN & Edge
DNS
Application
3 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
5 tools, what the team runs on day to day
Email Delivery
Workspace
Security & Compliance
First Community Bank tech stack FAQ
What tools does First Community Bank use?
We've found 12 tools at First Community Bank (fcbot.com). Edge & Hosting: Cloudflare and Namecheap. Application: Google Fonts, Font Awesome and Adobe Fonts. Data & Observability: Mixpanel. Company Ops: Microsoft 365, SendGrid and Mailgun. Last checked October 7, 2026.
What email provider does First Community Bank use?
First Community Bank uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does First Community Bank use?
First Community Bank uses Mixpanel for analytics. We found Mixpanel through website code.
Does First Community Bank use Microsoft 365?
Yes. We found Microsoft 365 at First Community Bank through DNS verification records and email records. Microsoft 365 is used by 685,402 companies we track.
How does runsonwhat know what First Community Bank uses?
We read public traces only: First Community Bank'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.