runsonwhat

Marco Technology Inc.'s tech stack

What does Marco Technology Inc. use?

Marco Technology Inc. (marcoapp.io) uses at least 10 tools we can see from public records, including Railway for hosting, Google Workspace for email and documents, Intercom for customer support and Better Stack for monitoring. Last checked .

LinkedIn
Company page
Tools found
10
Categories
8
Layers
5 of 5
Last checked
Oct 2026

Marco Technology Inc.'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

1 tool, what the product is built with

Media & UI

Data & Observability

1 tool, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

4 tools, what the team runs on day to day

Marco Technology Inc. tech stack FAQ

What tools does Marco Technology Inc. use?

We've found 10 tools at Marco Technology Inc. (marcoapp.io). Edge & Hosting: Cloudflare and Railway. Application: Three.js. Data & Observability: Better Stack. Go-to-market: Intercom. Company Ops: Google Workspace, SendGrid and Amazon SES. Last checked October 2, 2026.

What cloud does Marco Technology Inc. run on?

Marco Technology Inc. uses Railway for hosting. We found Railway through custom domain.

What email provider does Marco Technology Inc. use?

Marco Technology Inc. uses Google Workspace for email and documents. We found Google Workspace through email records.

What does Marco Technology Inc. use for customer support?

Marco Technology Inc. uses Intercom for customer support. We found Intercom through custom domain.

Does Marco Technology Inc. use Cloudflare?

Yes. We found Cloudflare at Marco Technology Inc. through DNS records, email records and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Marco Technology Inc. uses?

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