DocsApplicationsWorkflows
Loading documentation, please wait.
NEMORIONDocsWorkflows is Sovereign's application for automating processes across systems and APIs. It began with the goal of automating business management; the same idea applies wherever a repeatable process connects services and performs work.
Its purpose is to make those processes repeatable, visible, and manageable on infrastructure you control.
A business process often crosses several systems. Someone receives a request, looks up information, checks a rule, obtains approval, and updates records. Each manual handoff takes time and creates an opportunity for something to be missed.
Workflows makes that sequence explicit. Steps perform defined operations, conditions select the next path, and data passes between the systems involved. The process follows the rules you specify.
APIs make it possible to automate work across applications. Integrations provide the operations a process needs: retrieve a record, create an item, update a status, or send a notification.
Reusable integrations and process components let teams build on work they have already defined. Connection details, credentials, and permission to use an operation remain administrative concerns rather than something every person running the process needs to handle.
Consider an equipment request:
The process defines which decisions follow rules, where a person must approve, and which operations may proceed afterward. This example illustrates the automation model; the available integrations determine which systems a particular installation can connect.
An API can be unavailable, an approval can be declined, or a record can change while work is in progress. Failure handling belongs in the process definition.
The Workflows design includes explicit error paths and retry behavior so operators can understand where a run stopped and what should happen next. Repeating an operation must account for its effects: retrying a lookup and retrying a payment are different decisions.
Deterministic orchestration means following defined rules. It does not mean external systems never fail or that changing inputs always produce the same result.
Permission to run a process, edit its definition, and configure its credentials are different responsibilities. A person may be authorized to invoke an approved operation without receiving the privileges or credentials used to carry it out.
For example, an administrator can configure a particular node to use a service identity and authorize eligible people to invoke the workflow with that configured authority. The workflow constrains the operation they can perform.
The design distinguishes this explicit delegation from acting on behalf of a user, where the user's permissions remain part of the access decision.
Understand delegated authority
Self-hosting matters when processes need to reach internal systems or operate under your organization's infrastructure policies.
Connected services still determine where particular data is sent. Keeping the workflow engine inside your environment does not automatically keep an external service's processing there.
Execution history helps operators follow a process through its steps and investigate failures. Audit records provide accountability for the actions performed, including who initiated the work and which identity carried it out.
Workflows builds on Sovereign's shared authorization, auditing, and observability foundations so those concerns remain part of how automation operates.
AI can be added to selected steps for tasks such as summarization or interpreting unstructured information. It is an optional capability; process automation is the purpose of Workflows and does not require a model.
See the evaluation options for application availability and the manuals overview for setup documentation.