Roadmap
What does not exist yet — said plainly.
Nothing on this page is included in what you buy today. Either the feature exists and is sold, or it is here.
External execution API
An outside system — the ERP, a customer portal, another orchestrator — triggers a process and checks its status over an API, authenticated by a token issued in NexaOrch and scoped per process. It is the missing path for NexaOrch to be called, rather than only calling.
Parallel branches within a process
Today the steps of a process run in sequence (and several processes run in parallel). Splitting one process into simultaneous branches, with a join point, is a large change: it touches the execution engine, the editor, the diagram and the semantics of failure when one branch breaks and another does not.
LDAP / Active Directory / OIDC
Authentication today is local. Integration with an identity provider is a recurring request.
Active-active portal
Today portal continuity is handled by the infrastructure (the cluster restarts the container on another node) — and runs do not even stop when it goes down. What is not yet a tested, documented topology is running two portal instances at the same time.
Multi-tenant in a single installation
Today each customer is one installation. Real isolation within a single one does not exist yet.
AI alerts and insights
Marked as “coming soon” inside the product itself. Do not count on them in a purchase decision.
Native Windows executor
Today the executor runs in a Linux container — including on Windows Server with virtualization. The native service, to reach what lives on the internal network without a Linux VM in between, is being built and is not yet available for purchase.
No dates. We would rather publish no deadline than one we do not meet. If any of these is decisive for you, say so in the conversation — it weighs on prioritization.