Roadmap
What we are building now, next, and later.
Themes, not feature dates. Customer input shapes the order. We update this page monthly and stamp the date so you can tell when the picture last moved.
Last updated: August 31, 2026
SHIPPED · RUNNING TODAY
Already built and in the product
Production-grade ERP adapters
SAP, Oracle and Microsoft Dynamics are production-ready, not scaffolded. Bi-directional work orders, parts reservations and cost rollups, with the audit chain behind every write.
- SAP S/4HANA adapter with bi-directional work orders
- Oracle EBS adapter for parts and inventory
- Microsoft Dynamics 365 adapter for cost rollups
Multi-region hosting
US region today, with additional regions selectable per tenant at provisioning as they come online. Data residency that satisfies the procurement teams who already ruled out vendors without it.
- US region live, selectable per tenant at provisioning
- Additional US availability zones
- Further regions added as they come online
NOW · ACTIVELY IN BUILD
Expect within this quarter
Native team-app integrations
Slack and Microsoft Teams as more than webhook destinations. Slash commands, threaded work-order discussions, and acknowledge-from-Teams without leaving the channel.
- Slack app with slash commands and threaded work-order updates
- Teams app with the same surface
- Acknowledge and snooze alerts from inside the channel
Operator-floor mobile
The line operator should not need a laptop to log a downtime. Two-tap reason codes, voice-to-text comments, and an offline buffer for the moments the shop-floor Wi-Fi blips.
- Operator-grade web app for tablets and phones
- Two-tap reason-code entry
- Voice-to-text comments with on-device fallback
- Offline buffer that syncs on reconnect
NEXT · COMMITTED
Expect within the next one or two quarters
Wider protocol coverage
For customers whose stacks do not expose OPC UA. MQTT, native Siemens S7, and EtherNet/IP let the same edge agent talk to controllers it cannot reach today.
- MQTT broker as a first-class input
- Native Siemens S7 reader without the OPC UA round trip
- EtherNet/IP via CIP for Rockwell-heavy plants
Audit and compliance certification
The control framework is in place; the third-party attestations follow. SOC 2 Type II observation begins Q1 2027, ISO 27001 pre-audit gap analysis in Q2 2027, and Cyber Resilience Act readiness in parallel.
- SOC 2 Type II observation period from Q1 2027, report expected Q3 2027
- ISO 27001 pre-audit gap analysis Q2 2027
- Cyber Resilience Act coordinated vulnerability disclosure policy live by Q1 2027
LATER · DIRECTIONAL
Where we are heading, no timeline
Advanced deterministic analytics
TEEP, the six big losses, anomaly clustering, predictive lead times. All deterministic, all explainable, all derived from the same canonical event stream. The black box stays closed.
- TEEP alongside the existing OEE rollup
- Six big losses categorisation per ISO 22400
- Anomaly clustering by reason code and shift
- Predictive lead-time bands from historical work-order data
Customer-controllable pipelines
User-defined alert-rule expressions, custom report templates, and tag transforms that survive an upgrade. The customer should be able to tune the platform without filing a support ticket.
- Expression language for alert rules with AND/OR and time windows
- Custom report templates in the admin console
- User-defined tag transforms that version with the tenant
Tenant-grade extensibility
A plugin SDK and outbound webhook contracts that customers and partners can build against. Strictly opt-in, signed, sandboxed at the application boundary.
- Plugin SDK with a sandboxed runtime and capability scopes
- Outbound webhook contracts versioned per tenant
- Partner marketplace for community detectors and report templates
WHAT WE ARE NOT BUILDING
Where we deliberately stay out of scope
A roadmap that lists everything is a wish list. Here is what we have decided against, so you know what to expect from us and what to keep your existing vendors for.
SCADA or DCS replacement
We complement your SCADA and DCS, we do not replace them. Control-loop responsibility stays where it belongs.
Safety-instrumented system
We are explicitly out of IEC 61511 scope. Safety functions live in a separate, certified system.
Black-box ML predictions
Our explainability is the wedge. We are not abandoning deterministic detectors for opaque models, however good the marketing slide.
Consumer-facing app
We are B2B industrial only. The shop-floor operator is the consumer end of our world; the family living room is not.
HOW THIS WORKS
We move themes when the customer case is strong
The roadmap is a snapshot of intent, not a contract. If a pilot uncovers a sharper need than the themes above, we re-order and say so. The audit-chain principle applies here too: changes are public, dated, and never silently rewritten.
COMMON QUESTIONS
Questions about what comes next
When does Haltless become generally available?
General availability is scheduled for Q1 2027. Haltless is pre-launch until then, which is why this page describes themes and horizons rather than a release calendar with dates against each line.
Are the items on this roadmap commitments?
Now and Next are, in the sense that they are actively in build or committed to a horizon. Later is directional and carries no timeline on purpose. The roadmap is a snapshot of intent rather than a contract, and when it changes we say so instead of quietly re-ordering it.
What is Haltless deliberately not building?
A SCADA or DCS replacement, a safety-instrumented system, black-box machine-learning predictions, and a consumer-facing app. The first two are scope we stay out of, IEC 61511 included. The third is the product argument, not an omission.
Can a customer move something up the roadmap?
Themes move when the case is strong, and a pilot that uncovers a sharper need than what is listed is exactly the kind of case that moves one. Ask during an evaluation rather than after signing, when the answer costs nothing to give.
