# The organization becomes the context for work.

NelliaOS gives people and AI agents a shared operating foundation. Each task carries its business context, its authorized scope and the evidence of what happened.

## Bring the relevant parts of the business together.

Work crosses applications. NelliaOS keeps its meaning and ownership intact as it moves.

### A shared business context

Customer records, operating knowledge and company goals inform the work. Source ownership, freshness and permissions determine what a person or agent can use.

### Tasks, applications and knowledge

Team workspaces connect shared queues and purpose-built applications. A task links to its conversation, documents and decision history, with a responsible person and a next action.

### Conversations across channels

A multichannel inbox brings supported messaging accounts and email into the same operating context. Account identity, assignments and channel capabilities stay explicit in the conversation.

## Turn context into controlled action.

The same operating rules apply whether work starts with an employee, a business event or an AI agent.

### People and agents with defined authority

Every identity has a scoped role. Agents prepare work and use approved tools within a delegated boundary. Sensitive actions pass through the required human approval.

### Guidance that follows the job

Welcome flows help each role reach its first useful task. Contextual next actions respond to current work, support pause and resume, and record completion separately from a click.

### A complete customer lifecycle

Adoption signals inform retention tasks and relevant expansion opportunities. Journeys connect the customer record to approved outreach, offers and verified commercial outcomes.


# Choose where the system runs. Define who operates it.

NelliaOS runs in a dedicated managed environment, your cloud or a hybrid operating model. The deployment scope defines data location, control ownership and service responsibilities.

## Match the deployment to the organization.

Infrastructure choice belongs alongside the workflow and governance decisions.

### Managed dedicated

Nellia operates a dedicated environment with an agreed service boundary. The deployment specifies the region, integration access and recovery responsibilities, with your team retaining business and access policy.

### Customer cloud

Run the system inside your infrastructure account. Your organization owns the infrastructure boundary and grants Nellia the access required for the agreed implementation and operating responsibilities.

### Hybrid

Keep selected data and services within internal boundaries while approved workloads run elsewhere. Each connection defines its permitted data flow, identity and responsible owner.

## Keep the system maintainable as requirements change.

Documented interfaces and deployment artifacts make ownership and change practical.

### A portable operating foundation

Versioned application artifacts, explicit dependencies and defined infrastructure boundaries support relocation and handover. Operating documentation travels with the deployed system.

### Models that fit the workload

Select hosted or privately served models according to the task, data policy and operating budget. Routing and evaluation criteria remain visible to the platform owner.

### Responsibility in writing

Assign ownership for updates, credentials, monitoring and recovery before rollout. Change procedures specify the approval path and the evidence required for release.


## Managed dedicated

A dedicated environment operated by Nellia within an agreed service scope.

**Where it runs:** An agreed hosting region

**Data location:** Dedicated stores and documented integration flows

**Operating responsibility:** Nellia, with named customer decision owners

**Control boundary:** Your business policy; agreed infrastructure and service responsibility

## Customer cloud

NelliaOS inside your infrastructure, with explicit delivery and operating access.

**Where it runs:** Your cloud or private infrastructure

**Data location:** Your selected region and storage boundary

**Operating responsibility:** Your platform team and Nellia within defined responsibilities

**Control boundary:** Customer-controlled infrastructure, keys and granted service access

## Hybrid

An operating model that connects internal services to approved external workloads.

**Where it runs:** Internal and approved external environments

**Data location:** A defined location and permitted flow for each workload

**Operating responsibility:** Named owners for each service and connection

**Control boundary:** Explicit interfaces, delegated access and data movement policy

Nellia
https://nellia.co/en/