runsonwhat

Bedu AI's tech stack

What does Bedu AI use?

Bedu AI (bedu.io) uses at least 6 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Cloudflare for content delivery and Amazon SES for email delivery. Last checked .

Industry
Internet
Size
51–200 employees
Based in
United Arab Emirates
Founded
2021
LinkedIn
Company page
Tools found
6
Categories
6
Layers
4 of 5
Last checked
Oct 2026

Bedu 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

2 tools, where the bytes are served from

Hosting & Cloud

CDN & Edge

Application

1 tool, what the product is built with

Go-to-market

1 tool, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Bedu AI tech stack FAQ

What tools does Bedu AI use?

As of October 2026, runsonwhat has found 6 tools at Bedu AI (bedu.io) in public records. Edge & Hosting: Cloudflare and Vercel. Application: Google Fonts. Company Ops: Google Workspace and Amazon SES. Last checked October 23, 2026.

What cloud does Bedu AI run on?

Bedu AI uses Vercel for hosting and cloud infrastructure, according to runsonwhat (October 2026). runsonwhat found Vercel through a subdomain that points at Vercel and a DNS verification record. Vercel is used by 47,901 companies runsonwhat tracks.

What email provider does Bedu AI use?

Bedu AI uses Google Workspace for email and office software, according to runsonwhat (October 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace. Google Workspace is used by 401,493 companies runsonwhat tracks.

Does Bedu AI use Google Fonts?

Yes. runsonwhat found Google Fonts at Bedu AI through Google Fonts code on bedu.io. Google Fonts is a Media & UI tool used by 806,480 companies runsonwhat tracks.

How does runsonwhat know what Bedu AI uses?

runsonwhat reads public records only. Of the 6 tools at Bedu AI, 2 were found through DNS records, 2 through email records, 1 through code on bedu.io and 1 through subdomains that point at the vendor. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and bedu.io about 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.