OperatorHub's tech stack
What does OperatorHub use?
OperatorHub (operatorhub.tech) uses at least 12 tools we can see from public records, including Microsoft 365 for email and documents, Help Scout for customer support, Wix for its website and Brevo for marketing. Last checked .
- Industry
- Software
- Size
- 11–50 employees
- Based in
- Queenstown, New Zealand
- Founded
- 2008
- Company page
- Tools found
- 12
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
OperatorHub'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
Application
1 tool, what the product is built with
Data & Observability
1 tool, what they measure and store
Monitoring
Go-to-market
7 tools, how they find and keep customers
Website & CMS
Ads & Pixels
Support & Docs
Company Ops
1 tool, what the team runs on day to day
Workspace
OperatorHub tech stack FAQ
What tools does OperatorHub use?
We've found 12 tools at OperatorHub (operatorhub.tech). Edge & Hosting: Cloudflare and Fastly. Data & Observability: Sentry. Go-to-market: Meta Pixel, LinkedIn Insight Tag and Brevo. Company Ops: Microsoft 365. Last checked October 6, 2026.
What email provider does OperatorHub use?
OperatorHub uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What does OperatorHub use for customer support?
OperatorHub uses Help Scout for customer support. We found Help Scout through website code.
What CMS does OperatorHub use?
OperatorHub uses Wix for its website. We found Wix through custom domain, email records and website code.
What marketing software does OperatorHub use?
OperatorHub uses Brevo and POWR for marketing. We found Brevo through DNS verification records.
Does OperatorHub use Microsoft 365?
Yes. We found Microsoft 365 at OperatorHub through DNS verification records and email records. Microsoft 365 is used by 685,134 companies we track.
How does runsonwhat know what OperatorHub uses?
We read public traces only: OperatorHub'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.