ODIGO's tech stack
What does ODIGO use?
ODIGO (odigo-dm.com) uses at least 11 tools we can see from public records, including Kinsta for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .
- Industry
- Printing
- Based in
- Belgium
- Founded
- 1955
- Company page
- Tools found
- 11
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
ODIGO'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
Hosting & Cloud
CDN & Edge
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
3 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
ODIGO tech stack FAQ
What tools does ODIGO use?
We've found 11 tools at ODIGO (odigo-dm.com). Edge & Hosting: Cloudflare and Kinsta. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics. Go-to-market: WordPress and Yoast SEO. Company Ops: Microsoft 365 and reCAPTCHA. Last checked October 4, 2026.
What cloud does ODIGO run on?
ODIGO uses Kinsta for hosting. We found Kinsta through website code.
What email provider does ODIGO use?
ODIGO uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does ODIGO use?
ODIGO uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does ODIGO use?
ODIGO uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does ODIGO use Microsoft 365?
Yes. We found Microsoft 365 at ODIGO through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what ODIGO uses?
We read public traces only: ODIGO'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.