Omega Dev.'s tech stack
What does Omega Dev. use?
Omega Dev. (omegalab.dev) uses at least 7 tools we can see from public records, including Google Workspace for email and documents, HubSpot for sales, Google Analytics for analytics and Ahrefs for marketing. Last checked .
- Industry
- Software
- Size
- 51–200 employees
- Based in
- Amsterdam, Netherlands
- Founded
- 2013
- Company page
- Tools found
- 7
- Categories
- 6
- Layers
- 5 of 5
- Last checked
- Oct 2026
Omega Dev.'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
CDN & Edge
Application
1 tool, what the product is built with
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
3 tools, how they find and keep customers
Sales & CRM
Company Ops
1 tool, what the team runs on day to day
Workspace
Omega Dev. tech stack FAQ
What tools does Omega Dev. use?
We've found 7 tools at Omega Dev. (omegalab.dev). Edge & Hosting: Cloudflare. Application: Google Fonts. Data & Observability: Google Analytics. Go-to-market: HubSpot and Ahrefs. Company Ops: Google Workspace. Last checked October 6, 2026.
What CRM does Omega Dev. use?
Omega Dev. uses HubSpot for sales and CRM. We found HubSpot through website code.
What email provider does Omega Dev. use?
Omega Dev. uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Omega Dev. use?
Omega Dev. uses Google Analytics for analytics. We found Google Analytics through website code.
What marketing software does Omega Dev. use?
Omega Dev. uses Ahrefs for marketing. We found Ahrefs through website code.
Does Omega Dev. use Cloudflare?
Yes. We found Cloudflare at Omega Dev. through DNS records. Cloudflare is used by 569,699 companies we track.
How does runsonwhat know what Omega Dev. uses?
We read public traces only: Omega Dev.'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.