User and tenant context
The active user, tenant, and allowed workspace establish the initial boundary.
Trust center / architecture
Know the
boundary.
NbotaiOS makes owner scope, tenant placement, execution routes, review gates, and resulting receipts visible. Infrastructure controls still depend on the deployment you choose and operate.
System route
Intent enters.
Bounded work leaves.
This is the product architecture at a functional level. Exact network, identity, encryption, backup, and retention settings are deployment responsibilities and should be reviewed for each environment.
Capability selection
The Orchestrator selects an appropriate work lane and verifies availability before execution.
Approval when required
Consequential actions can pause for a visible human decision.
Result and evidence
Finished work can retain source references, progress, and execution evidence.
Claims and responsibilities
Specific, not inflated.
What the product is designed to expose
Owner scope, tenant-aware workspaces, capability routing, reviewable progress, human approval surfaces, and durable work receipts.
What must be confirmed per installation
Identity provider, network segmentation, encryption configuration, key custody, backup policy, retention, monitoring, incident response, and regulatory mapping.
No certification is implied here
This page does not claim SOC 2, ISO 27001, FedRAMP, HIPAA, or another third-party certification.
Responsible disclosure path
Security reports can be submitted through the contact route or the published security.txt instructions.
Open security.txt