runsonwhat

Metaveo's tech stack

What does Metaveo use?

Metaveo (mwttech.com) uses at least 10 tools we can see from public records, including Railway for hosting, Microsoft 365 for email and documents and Google Analytics for analytics. Last checked .

“Metaveo combines strategy, design, software engineering, AI automation, and production capabilities for education and growth-focused organizations.”

Industry
Software
Size
51–200 employees
Based in
Kochi, India
Founded
2011
LinkedIn
Company page
Tools found
10
Categories
8
Layers
5 of 5
Last checked
Oct 2026

Metaveo'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

Application

2 tools, what the product is built with

Media & UI

Data & Observability

2 tools, what they measure and store

Go-to-market

3 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Metaveo tech stack FAQ

What tools does Metaveo use?

We've found 10 tools at Metaveo (mwttech.com). Edge & Hosting: Amazon Route 53 and Railway. Application: GSAP and Next.js. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads and Meta Pixel. Company Ops: Microsoft 365. Last checked October 6, 2026.

What cloud does Metaveo run on?

Metaveo uses Railway for hosting. We found Railway through website code.

What email provider does Metaveo use?

Metaveo uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.

What analytics tools does Metaveo use?

Metaveo uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

Does Metaveo use Microsoft 365?

Yes. We found Microsoft 365 at Metaveo through email records. Microsoft 365 is used by 685,126 companies we track.

How does runsonwhat know what Metaveo uses?

We read public traces only: Metaveo'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.