Security & trust

Keep ownership
part of the architecture.

NbotaiOS is designed around local-first operation, tenant-aware context, permissioned capabilities, and reviewable work. The deployment determines how those principles are put into practice.

How work is bounded

A clear chain from request to result.

User and tenant context

The active user, assigned tenant, and permitted workspace establish the context for the requested work.

Capability selection

The system routes work to an appropriate enabled capability and checks the relevant execution conditions.

Review where it matters

Configured approval points allow an authorized reviewer to assess consequential actions before they proceed.

Results with supporting evidence

Outputs can retain source references, version context, progress, and execution records so the result can be reviewed.

Deployment responsibilities

Make the deployment decisions explicit.

Infrastructure and models

Decide where data, models, and execution operate. Optional external services require their own configuration and authorization.

Identity and permissions

Define account ownership, tenant access, roles, connected providers, and administrative responsibilities.

Retention and recovery

Confirm backup, restoration, version retention, and deletion policies for the environment and data involved.

Network and operations

Review encryption configuration, key custody, network boundaries, monitoring, maintenance, and incident response.

Contact and disclosure

A direct path for questions.

Privacy and connected data

Review what the public site collects and how optional provider connections are described in the privacy notice →.

Report a security concern

Use the security contact route or the published security.txt →. Include a general description and a safe way to follow up.

Bring your next workflow.

Start with the work your team needs to finish. We’ll help define the right capabilities, deployment, and next step.