User and tenant context
The active user, assigned tenant, and permitted workspace establish the context for the requested work.
Security & trust
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
The active user, assigned tenant, and permitted workspace establish the context for the requested work.
The system routes work to an appropriate enabled capability and checks the relevant execution conditions.
Configured approval points allow an authorized reviewer to assess consequential actions before they proceed.
Outputs can retain source references, version context, progress, and execution records so the result can be reviewed.
Deployment responsibilities
Decide where data, models, and execution operate. Optional external services require their own configuration and authorization.
Define account ownership, tenant access, roles, connected providers, and administrative responsibilities.
Confirm backup, restoration, version retention, and deletion policies for the environment and data involved.
Review encryption configuration, key custody, network boundaries, monitoring, maintenance, and incident response.
Product descriptions do not imply third-party certification or suitability for a regulated use. Confirm the requirements of your intended workflow and deployment in writing.
Contact and disclosure
Review what the public site collects and how optional provider connections are described in the privacy notice →.
Use the security contact route or the published security.txt →. Include a general description and a safe way to follow up.
Start with the work your team needs to finish. We’ll help define the right capabilities, deployment, and next step.