runsonwhat

DEVBOT's tech stack

What does DEVBOT use?

DEVBOT (devbot.com) uses at least 7 tools we can see from public records, including Cloudflare Pages for hosting, Microsoft 365 for email and documents, Cloudflare for content delivery and Resend for email delivery. Last checked .

“Enterprise software development with secure, local AI workflows embedded in the real development process. Teams in Austin, TX and Monterrey, MX.”

Based in
Austin, United States
LinkedIn
Company page
Re-check liveVisit devbot.com
Tools found
7
Categories
7
Layers
4 of 5
Last checked
Oct 2026

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

Go-to-market

1 tool, how they find and keep customers

Marketing

Company Ops

3 tools, what the team runs on day to day

Email Delivery

Workspace

Security & Compliance

Companies like DEVBOT also use

Tools common among companies with a similar stack that we haven't found at DEVBOT.

Companies with a stack like DEVBOT's

Ranked by shared tools, with rare tools counting more.

DEVBOT tech stack FAQ

What tools does DEVBOT use?

We've found 7 tools at DEVBOT (devbot.com). Edge & Hosting: Cloudflare and Cloudflare Pages. Application: GSAP. Company Ops: Microsoft 365, Resend and Sophos. Last checked October 6, 2026.

What cloud does DEVBOT run on?

DEVBOT uses Cloudflare Pages for hosting. We found Cloudflare Pages through custom domain.

What email provider does DEVBOT use?

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

Does DEVBOT use Microsoft 365?

Yes. We found Microsoft 365 at DEVBOT through email records. Microsoft 365 is used by 505,480 companies we track.

How does runsonwhat know what DEVBOT uses?

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