DocsDiscover SovereignMeet Sovereign
Loading documentation, please wait.
NEMORIONDocsNEMORIONDocsSovereign is for organizations that need to keep their work on infrastructure they control, with clear boundaries around who can see information and who can act on it.
The goal is straightforward: make ongoing and upcoming work easy to manage, make repeatable processes reliable, and make both accessible to AI when you choose. AI is optional. Security and accountability are part of the foundation.
Where work lives can be a requirement, not a preference. Your team may need to connect private systems, control its operating environment, or share sensitive work with a precisely defined audience.
Self-hosting addresses where the application runs. Sovereign's authorization model addresses what happens inside it: who can administer a workspace, read a document, contribute to a task, or use a particular capability.
Explore security and compartmentalization
Orbit brings planning, work items, discussions, and documentation together. Teams can organize projects and timelines while controlling access to the individual pieces of work.
A person assigned a task does not automatically need access to the larger initiative. A person responsible for administration does not automatically need to read the content they administer. Those distinctions matter when collaboration has to respect information boundaries.
Orbit's purpose is useful, accessible work management. Quickly see the exact state of everything. Plan, execute, and track work seamlessly.
Workflows is the automation application. Its purpose is to turn repeatable processes into explicit steps across systems and APIs, with defined authority and an accountable execution history.
Connect systems, validate requests, route approvals, and update records according to the process you define. The Workflows design brings those operations together with reusable integrations, explicit failure handling, and control over who may run or change the process.
AI is an optional feature for steps that benefit from interpretation. The automation itself does not require it.
When you ask an AI assistant to search your documents, your permissions should determine what it can retrieve. Connecting an assistant should not open information you could not read yourself.
Some processes need a different arrangement, however. An employee might be allowed to run an approved banking workflow without being given the banking credentials or permission to perform other transactions. An authorized administrator grants the workflow the access it needs and decides who may run it.
The Workflows design supports that distinction. Act within a person's permissions, or use authority explicitly assigned to an approved operation. In either case, the audit trail should show who requested the work, what performed it, and whose authority it used. Including when AI acted on someone's behalf.
Understand delegated authority
The managed alpha is the initial path for exploring Orbit before operating an installation yourself. The self-hosted setup guide is coming soon; dedicated application manuals will cover installation, administration, and troubleshooting.