Roadmap
Where InnovaEdge is going.
This is sequence, not schedule. Dates live in our internal tracker, not on a public page that would go stale the moment a phase slips — what you get here is the order things happen in and what has to be true before we call a phase done.
Six phases with status · what is in development now · what is planned next
01 — Six phases, in order
From product foundation to an open ecosystem.
Each phase has an outcome and an exit gate — the condition that has to hold before we consider it done and move to the next one. Phases one to three are substantially delivered: the machine interface is shipped and in use, not future work. Where a phase and a capability disagree, the badged sections further down this page are the authoritative record.
Substantially delivered
1. Product foundation
Outcome: the platform is a durable product, not a disposable demonstration — its own users, organizations and identity, its own storage ownership, real services instead of route handlers, and a clear separation of desired state, reported state, and evidence.
Exit gate: an organization can onboard infrastructure and devices, deploy state, verify its effect, and recover from failure without developer intervention or demo-only assumptions.
In progress
2. First-customer readiness
Outcome: guided onboarding, production-grade installation and enrollment, provider-neutral recipes with a visible support grade, and broader hardware bench coverage.
Exit gate: initial customers can onboard and operate supported integrations under documented service, security, recovery and provider-dependency boundaries.
Delivered
3. The machine interface
Outcome: an organization-scoped MCP server, starting with read-only resources and adding structured tools for drafting, validation, dry runs, deployment, reconciliation and recovery.
Exit gate: supported MCP clients can inspect and execute controlled workflows without bypassing product policy, leaking tenant data, or producing false completion claims.
In progress
4. The embedded agent
Outcome: an in-product agent that helps customers understand and operate InnovaEdge through the machine interface, with proposed actions rendered as native preview cards and a combined conversation and action audit trail.
Exit gate: the agent improves onboarding, integration authoring, diagnosis and recovery without becoming an unreviewable privileged control path.
In progress
5. Developer & runtime ecosystem
Outcome: a stabilized, documented UDI schema and lifecycle, SDKs, validators, a local simulator, and a published device-family adapter contract so third parties can build their own runtime adapters.
Exit gate: a developer can author and validate an integration without private platform knowledge, then deploy it through InnovaEdge to more than one compatible device family.
Not started
6. Licensing & standardization
Outcome: proven product adoption used to establish broader runtime compatibility — certification levels defined, and manufacturer embedding, licensing and co-selling opportunities evaluated.
Exit gate: measured integration-time, deployment-reliability and support-cost improvements, with source-availability or public standardization considered only once governance and incentives are clear.
02 — In development now
Being built against the phases above, right now.
Pulled straight from the capability registry across every cluster, so this list is exactly what the capability pages already say is in development — nothing more, nothing less.
Twin-driven observability In development
Attach geofences and thresholds to a location or equipment type rather than to a device, and let the platform fan them out to every device that resolves to it. Author once, watch the whole class.
Native approval cards & deep links In development
Proposed actions rendered as native preview cards with links to the product object they act on, and long-running workflow milestones shown in the conversation.
03 — Planned
Next in line, not yet started.
Same registry, same rule: an item here carries no claim about timing, only that it has not started.
OPC UA client ingest Planned
Read from existing OPC UA servers, closing the loop on plant-floor sources that are not MQTT devices.
Enterprise SSO & passkeys Planned
SCIM-style membership administration, enterprise SSO connectors and passkey authentication.
Custom domains & login branding Planned
A branded login page on your own domain, mapped to your organization.
Where to go next
Changelog
Real releases, with the version running in production marked.
What the platform does
Fleet, twins, OTA, automations and the agent surface, end to end.
Pricing
Four tiers, the metered device floor, and what is included in each.
Want to know what has actually shipped?
This page is where things are headed. The changelog is the record of what is already running in production.