Competitor watch

Living tracker. Updated by the research function. Each competitor has: official positioning, what they do well, where they overlap with ROSA, where 4Rooks should differentiate, public pricing, and recent moves.

Foundries (FoundriesFactory)

• Positioning: Linux device lifecycle platform — Yocto/Linux microPlatform, GitOps, CI, OTA, fleet, secure boot, TUF updates
• Strength: Linux DevSecOps, managed PKI, manufacturing workflow, production fleet ops
• Overlap with ROSA: buyers may compare as "faster way to standardise Linux device software"
• Differentiation for 4Rooks: cross-product firmware architecture reuse, MCU/RTOS-adjacent needs, standards migration economics — not just Linux lifecycle tooling
• Public pricing: Community free · Startup $500/mo · Pro $1,500/mo · Production $2,500/mo · Enterprise $15,000/mo
• Recent moves: to be filled by research function

Mender

• Positioning: Secure software update + lifecycle management with troubleshoot, config, monitoring add-ons
• Strength: OTA, rollback, gateway support, phased rollouts, data localisation, remote troubleshoot
• Overlap: when buyers diagnose their pain as "updates in the field"
• Differentiation: ROSA reduces the amount of bespoke firmware that needs updating in the first place — integrate with Mender where useful, don't compete
• Public pricing: Free OSS · Basic $34/mo · Pro $291/mo · Enterprise custom
• Recent moves: to be filled

Torizon

• Positioning: Open-source embedded Linux platform — secure boot, SBOM/CVE, remote access, OTA, monitoring, CRA-oriented
• Strength: Linux teams needing compliance acceleration + supported hardware paths
• Overlap: "security compliance" + "faster development" language
• Differentiation: avoid head-on Linux fights; emphasise reuse across variants and non-differentiating firmware layers, especially for buyers not solved by Linux tooling alone
• Public pricing: Maker free · Developer $249/mo or $2,500/yr · custom
• Recent moves: to be filled

Zephyr Project

• Positioning: Modular RTOS for resource-constrained / embedded systems
• Strength: technical base for many constrained devices, broad architecture support
• Overlap: indirect — through the internal "we'll build on Zephyr ourselves" option
• Differentiation: sell the cost of team-specific assembly, architecture drift, repeated integration on top of Zephyr
• Pricing: open source

Yocto Project

• Positioning: Tools/templates/methods for custom Linux systems
• Strength: bespoke Linux distributions, deep control
• Overlap: indirect — internal DIY baseline
• Differentiation: integration and maintenance tax of doing everything in-house
• Pricing: open source

Eclipse hawkBit

• Positioning: Domain-independent backend for rolling out updates to constrained devices and gateways
• Strength: mature OSS rollout backend, deployment groups, REST APIs
• Overlap: only at update orchestration layer
• Differentiation: ROSA above hawkBit — architecture and reuse, not just rollout
• Pricing: open source

Internal stack ("we build it ourselves")

The real default competitor. Differentiation: executive cost of duplicated platform work, hiring concentration, delayed reuse across families. Sell the opportunity cost, not the technical limitation.

New entrants to monitor

Populated by research function. Likely candidates: composable firmware startups, AI-assisted embedded code-gen tooling, vertical-specialist platforms (e.g., building-automation-specific firmware shops).

Comparison framework (use in customer conversations)

This table is a sales tool — keep it accurate as competitors move.