OMA's tech stack
What does OMA use?
OMA (oma.aero) uses at least 16 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and SendGrid for email delivery. Last checked .
- Industry
- Aviation
- Based in
- Mexico
- Founded
- 1998
- Company page
- Tools found
- 16
- Categories
- 12
- Layers
- 5 of 5
- Last checked
- Oct 2026
OMA'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
DNS
Application
4 tools, what the product is built with
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
5 tools, what the team runs on day to day
Email Delivery
Workspace
Dev Tools
Finance & Legal
OMA tech stack FAQ
What tools does OMA use?
We've found 16 tools at OMA (oma.aero). Edge & Hosting: Gandi. Application: jQuery, Google Fonts and React. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Google Ads and Meta Pixel. Company Ops: Microsoft 365, SendGrid and Atlassian. Last checked October 3, 2026.
What email provider does OMA use?
OMA uses Microsoft 365 for email and documents. We found Microsoft 365 through custom domain, DNS verification records, email records and website code.
What analytics tools does OMA use?
OMA uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does OMA use?
OMA uses WordPress for its website. We found WordPress through website code.
Does OMA use Microsoft 365?
Yes. We found Microsoft 365 at OMA through custom domain, DNS verification records, email records and website code. Microsoft 365 is used by 319,377 companies we track.
How does runsonwhat know what OMA uses?
We read public traces only: OMA'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.