Partner Marketing

EmbeddedOS runs on hardware, and hardware is made by silicon vendors and integrators. When a vendor ships EmbeddedOS in their products — on their boards, in their SDKs, in their reference designs — that is an event worth announcing. It tells engineers the stack is production-serious, and it tells the vendor's customers that the software is open and auditable. The Partner Marketing programme exists to make those moments visible: joint announcements and co-authored material with the silicon vendors and integrators shipping EmbeddedOS in their products.

Co-authorship matters. An announcement written by one side reads like advertising; a joint announcement and co-authored technical material — porting notes, performance results, integration guides — reads like engineering. The programme will favour material that teaches over material that merely announces.

That standard protects both sides. The vendor gets an announcement engineers actually read instead of scroll past, and the Foundation keeps its pages free of marketing fluff. If a proposed joint piece would not survive review as a technical article, it does not get published as one.

The programme will produce joint announcements with partners shipping EmbeddedOS: coordinated launch posts, co-authored blog articles on the integration work, and shared appearances at events. The Foundation will bring the community and the platform; the partner brings the hardware and the production context.

It will also build a standing library of partner material: board bring-up notes, porting guides, and verified configurations that any engineer can follow. Marketing that leaves behind documentation is marketing that keeps paying. As with member marketing, partnership confers recognition, not technical authority — the roadmap stays in the public governance process.

For silicon vendors and integrators shipping, or planning to ship, EmbeddedOS in their products: chip companies with boards to support, module makers, and system integrators building products on the stack.

For engineers evaluating hardware: the programme's output gives them real evidence — porting notes, performance data, joint documentation — about what EmbeddedOS looks like on specific hardware, written by the people who did the work.

For the broader ecosystem: each partnership announcement is also a signal to other vendors that the stack is viable on commercial hardware, which is how an open platform builds the hardware support it needs to be taken seriously.

That signal compounds. The first vendor to ship creates the reference that the second vendor's engineers point to internally; the programme's job is to make each partnership's technical output good enough to be that reference.

The Partner Marketing programme is planned and has not started. There are no partner announcements in the queue today. Silicon vendors and integrators interested in partnering can email partners@embeddedos.org to start the conversation about technical collaboration and joint announcements.

Community members who work at hardware companies and want to champion an EmbeddedOS partnership internally can use contact@embeddedos.org for background material and an introduction. The News page will carry the first joint announcements when the programme launches.

A note on how partnerships begin: they start with technical work, not with a logo swap. A vendor becomes a partner by shipping the stack and documenting the integration — the announcement follows the engineering, because an announcement without engineering behind it is the kind of marketing this programme will not do.