React Roadmap Timeline
Publishing a roadmap builds confidence in a young vendor — but only if it is hedged properly. Shipped items are commitments kept; anything further out is an intention, and saying so plainly is what keeps a roadmap from becoming a liability.
Product roadmap
Q2 2026 — shipped
Q3 2026 — current
- ML-DSA signature accelerationSiliconIn progressFIPS 204 hardware path, currently in silicon validation.
- Fleet attestation dashboardCloudIn progressContinuous device attestation with historical evidence.
- Common Criteria EAL4+ re-certificationComplianceIn progress
Q4 2026
- KLV-3000 industrial temperature gradeSiliconPlanned−40 °C to +105 °C variant of the entry part.
- Zephyr in-tree driverSoftwarePlannedUpstream the driver rather than shipping it as a module.
2027 and beyond
- KLV-9000 architectureSiliconExploringNext-generation core. Design partners are being onboarded now.
- Confidential computing attestation bridgeCloudExploringInvestigating interoperability with cloud TEE attestation.
Forward-looking and subject to change. Nothing here is a contractual commitment, and dates beyond the current quarter are intentions rather than promises.
Request a featureInstallation
Props
| Prop | Type | Description |
|---|---|---|
| periods | RoadmapPeriod[] | { label, items } |
| title | string | Heading |
| disclaimer | string | Forward-looking-statement note (has a sensible default) |
| feedbackHref | string | Where users request or vote on features |
Four statuses, and the one that is honest
shipped, in-progress, planned, and exploring. That last one earns its place: most roadmaps collapse "we are seriously building this" and "we are thinking about it" into a single "planned" bucket, and customers reasonably read everything as a commitment. Separating them lets you publish early thinking without implying a delivery date.
The disclaimer ships with a default rather than being optional, for the same reason year is required on the Awards Strip: the version you might forget is the one that causes a problem. A public roadmap is routinely read as a promise by procurement, and in some jurisdictions statements about future product capability can matter contractually. Keep the note.
Periods are plain labels, not dates — "Q3 2026 — current", "2027 and beyond". That keeps the component free of timezone-dependent formatting and lets you be deliberately vague further out, which is more honest than a false precision of specific dates twelve months ahead.
New components every week
Get the week's new Kelvin UI components and templates in one short email. No spam, unsubscribe anytime.