Product
What ORVION is made of.
ORVION is a Business Operating System. It holds the structure of your business, puts specialist work behind each part of it, keeps the context that work depends on, and stops at the point where a decision belongs to you.
Where your business lives
The business workspace.
Everything ORVION knows and does for a business sits inside that business’s own workspace.
Business workspace
Each business you run has its own workspace, its own stored records and its own context. One business does not read another’s data. If you run more than one, you switch between them; what ORVION knows about each stays with that business.
Set up once
You describe the business during setup — what it does and how it is organized. That description becomes the context every later piece of work reads from, rather than something you re-explain each time.
How work is organized
Departments and AI specialists.
Work belongs to a department, and specialists do defined work inside one.
Departments
ORVION organizes work into departments rather than a flat task list — Executive Leadership, Finance & Accounting, Human Resources, Sales, Marketing, Operations, Customer Service, Information Technology, and Facilities & Support where the operation calls for it. Which departments a business receives is determined during setup and bounded by the plan.
Teams and roles
Inside a department, work is grouped into teams or functions, and performed by roles with defined authority — a Supply Chain Manager inside Supply Chain & Logistics, a Digital Marketing Specialist inside Marketing. See the organization.
AI specialists
A specialist is scoped to one department. It reads your business context, produces work of a defined kind, and returns it for review. It does not roam across your business on its own initiative.
Workflows
Repeatable sequences of work, so a thing you need regularly is run the same way each time and produces a comparable result.
What ORVION remembers
Business memory and goals.
Business memory
The context ORVION keeps about your business between sessions, held per business. It is what lets work start from what your company actually is rather than from a blank prompt.
Goals
What the business is trying to achieve, recorded so that work can be related to it rather than treated as a series of disconnected requests.
The boundary
Approvals and execution.
This is the distinction ORVION is built around: proposing an action and performing it are separate events.
Approvals
Consequential work is filed for a decision instead of being carried out. It arrives with the reasoning attached, so you are approving something you can actually read. Starting work and approving its result are deliberately separate acts and can be held by different people.
Execution
Routine, low-risk steps may complete under policy. Anything beyond that stops and waits. Where your package includes Automation, ORVION can carry out approved work itself rather than only analysing and recommending it.
Receipts
Work that executes leaves a receipt describing what ran and what it produced, so there is a record of the action and not only of the intention.
What comes back
Reports and records.
Reports
What the work produced, in writing, rather than a result you have to reconstruct from a chat log.
Audit trail
Actions are recorded as they happen and attributed to the business they belong to, so the history stays readable later.
What ORVION connects to
Integrations and the AI provider gateway.
Integrations
Connections to services you already use. ORVION distinguishes integrations that only read information from those that can act on an outside system for you — the second kind is gated separately, and where it is not included those integrations are unavailable entirely.
AI provider gateway
Reasoning is routed through one governed gateway rather than wiring a model directly into your business. Claude (Anthropic), ChatGPT (OpenAI) and Gemini (Google) are supported through it. Which are usable depends on the credentials and permissions set for the installation.
Configured is not the same as available
ORVION distinguishes a provider that is configured from one that has actually answered, and reports an unavailable provider as unavailable rather than quietly using a different one.