runsonwhat

Feedloop AI's tech stack

What does Feedloop AI use?

Feedloop AI (feedloop.ai) uses at least 9 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, GitBook for customer support and Brevo for marketing. Last checked .

Industry
IT Services
Size
51–200 employees
Based in
Jakarta, Indonesia
Founded
2019
LinkedIn
Company page
Tools found
9
Categories
7
Layers
4 of 5
Last checked
Oct 2026

Feedloop AI'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

4 tools, where the bytes are served from

Application

1 tool, what the product is built with

Go-to-market

3 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Feedloop AI tech stack FAQ

What tools does Feedloop AI use?

We've found 9 tools at Feedloop AI (feedloop.ai). Edge & Hosting: Cloudflare, Google Cloud and Vercel. Application: Google Fonts. Go-to-market: Brevo and GitBook. Company Ops: Google Workspace. Last checked October 7, 2026.

What cloud does Feedloop AI run on?

Feedloop AI uses Google Cloud and Vercel for hosting. We found Google Cloud through website code.

What email provider does Feedloop AI use?

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

What does Feedloop AI use for customer support?

Feedloop AI uses GitBook for customer support. We found GitBook through custom domain.

What marketing software does Feedloop AI use?

Feedloop AI uses Brevo for marketing. We found Brevo through DNS verification records.

Does Feedloop AI use Cloudflare?

Yes. We found Cloudflare at Feedloop AI through email records, DNS records and website code. Cloudflare is used by 571,316 companies we track.

How does runsonwhat know what Feedloop AI uses?

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