runsonwhat

Openembedded's tech stack

What does Openembedded use?

Openembedded (openembedded.org) uses at least 8 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Cloudflare for content delivery and Amazon SES for email delivery. Last checked .

Industry
Software
Size
51–200 employees
Based in
San Jose, United States
Founded
2003
LinkedIn
Company page
Re-check liveVisit openembedded.org
Tools found
8
Categories
6
Layers
3 of 5
Last checked
Oct 2026

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

Hosting & Cloud

CDN & Edge

DNS

Application

1 tool, what the product is built with

Frontend

Company Ops

4 tools, what the team runs on day to day

Email Delivery

Workspace

Companies like Openembedded also use

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

Companies with a stack like Openembedded's

Ranked by shared tools, with rare tools counting more.

More Software companies

Other Software companies we've checked.

Openembedded tech stack FAQ

What tools does Openembedded use?

We've found 8 tools at Openembedded (openembedded.org). Edge & Hosting: Cloudflare, Amazon Web Services and DNSimple. Application: jQuery. Company Ops: Google Workspace, Amazon SES and Mailgun. Last checked October 7, 2026.

What cloud does Openembedded run on?

Openembedded uses Amazon Web Services for hosting. We found Amazon Web Services through website code.

What email provider does Openembedded use?

Openembedded uses Google Workspace for email and documents. We found Google Workspace through email records.

Does Openembedded use jQuery?

Yes. We found jQuery at Openembedded through website code. jQuery is used by 600,560 companies we track.

How does runsonwhat know what Openembedded uses?

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