runsonwhat

MetaMorph's tech stack

What does MetaMorph use?

MetaMorph (metamorphsoftware.com) uses at least 10 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Google Analytics for analytics and Squarespace for its website. Last checked .

Based in
United States
Founded
2013
Tools found
10
Categories
8
Layers
5 of 5
Last checked
Oct 2026

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

3 tools, where the bytes are served from

Application

2 tools, what the product is built with

Data & Observability

1 tool, 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

MetaMorph tech stack FAQ

What tools does MetaMorph use?

We've found 10 tools at MetaMorph (metamorphsoftware.com). Edge & Hosting: Amazon Web Services, Amazon Route 53 and GitHub Pages. Application: jQuery and Adobe Fonts. Data & Observability: Google Analytics. Go-to-market: Squarespace. Company Ops: Google Workspace. Last checked October 3, 2026.

What cloud does MetaMorph run on?

MetaMorph uses Amazon Web Services and GitHub Pages for hosting. We found Amazon Web Services through website code.

What email provider does MetaMorph use?

MetaMorph uses Google Workspace for email and documents. We found Google Workspace through email records and website code.

What analytics tools does MetaMorph use?

MetaMorph uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does MetaMorph use?

MetaMorph uses Squarespace for its website. We found Squarespace through custom domain, DNS records and website code.

Does MetaMorph use jQuery?

Yes. We found jQuery at MetaMorph through website code. jQuery is used by 363,483 companies we track.

How does runsonwhat know what MetaMorph uses?

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