How an engagement starts
No big-bang decision anywhere. Every step is small enough to say yes to, pays for itself, and earns the next one. Or it tells you honestly that ROSA isn't your answer.
The path
Step 01
45 minutes on your situation: where firmware hurts, what ROSA can and can't do about it. No sales deck, no commitment.
FreeStep 02
A fixed-price working session on-site: a Prioritisation Workshop on your whole firmware estate, or a CRA readiness check. You keep a written findings document with a prioritised picture, useful whether or not we ever meet again.
€5,000 fixed · fully credited against a later ROSA licenceStep 03
Whatever the plan prioritised, running where you work: the quality stack wired into your CI and benches, CRA evidence flowing from your builds, or ROSA on your own SoC. Success criteria agreed in writing before we start.
Days to weeks, capped priceFrom there it grows on its own merits, from team scope to organisation to group. The engagement models are below. When two days is not enough, a portfolio-wide assessment embedded with your teams over several weeks also exists. It's usually what a workshop recommends, not where an engagement starts.
Fit
You don't have to replace anything to get started. Where ROSA fits depends on what you already have:
Option A
Your platform and your application logic stay in place. Your team brings in the parts of ROSA that help: managed Zephyr and Linux, kept current and secure by us, hardware abstraction modules for new silicon, the quality stack wired into your existing CI. Everything lands in your repos as code you own.
Best for:
Teams with a working platform that want to reduce the maintenance burden or reach new hardware without a rewrite.
Option B
Starting a new product, or moving off bare metal? Your team describes the product in ROSA's explicit product model and picks modules for the undifferentiated work: updates, provisioning, connectivity. ROSA generates the rest deterministically, into your repos, as readable code you own. Your team builds the application logic that makes the product yours.
Best for:
Teams starting fresh or transitioning from bare metal.
Either way, you get the same core guarantee: fixed cost, we carry the risk in everything we maintain, and a clear path to adding more as your product grows.
Your starting point
Three ways into ROSA, depending on where your product is today.
Engagement Model
There are three engagement levels based on how many products and hardware platforms you need to support. All tiers include the same core guarantee.
Tier 1
One product, one hardware platform. The right starting point for teams evaluating ROSA or launching their first ROSA-based product.
Tier 2
Multiple products on a single hardware platform. For teams building a product family that needs to scale without fragmentation.
Tier 3
Multiple product families across multiple hardware platforms. For organisations managing a broad embedded portfolio.
Pricing
We don't publish a fixed price list because the embedded industry varies too much: different sectors, different hardware complexity, different compliance requirements.
What we do: estimate what your internal development would cost, and target roughly 25% of that number. The upfront licence covers the product. The annual fee covers maintenance, long-term support, and the risk in everything we maintain.
If something unexpected comes up (the compliance evidence takes more work than expected, or a hardware bring-up runs long), that's our problem, not yours. The price doesn't change.
~25%
of estimated internal development cost, upfront licence
20%
of licence fee per year, covering maintenance, LTS, and risk
Fixed
No surprise overruns. If anything we maintain causes a problem, we solve it.
45 minutes on your situation. No commitment, no sales deck, just an honest discussion of what ROSA can do for your specific firmware challenge.