Start with one useful workflow
Identify the outcome, people, input files, and acceptance criteria. Choose the relevant Suites, then confirm the deployment and access requirements.
Continue →Guides & FAQs
Practical starting points for understanding the platform, choosing Suites, connecting services, and planning a deployment.
Getting started
6 guides shown
Identify the outcome, people, input files, and acceptance criteria. Choose the relevant Suites, then confirm the deployment and access requirements.
Continue →Use cd.nbotaios.com/login. Your account opens the tenant workspace assigned to you. Contact your workspace administrator if the expected environment is missing.
Continue →Research and knowledge use SearchEngine; deliverables use Office; design and construction have dedicated Suites. Production, OSC, and NbotSync support execution, operations, and continuity.
Continue →Check source relevance, assumptions, versions, and unresolved questions. Technical and professional deliverables need the appropriate responsible review before release.
Continue →Gmail, Outlook, Procore, and ConstructConnect are separately authorized where available. Confirm provider accounts, permissions, supported actions, and license requirements.
Continue →Define infrastructure, models, user roles, backups, retention, integrations, and support expectations before expanding the environment.
Continue →Frequently asked questions
A local-first AI operating system connecting research, documents, projects, workflow automation, architecture, engineering, construction, collaboration, and system operations in an owner-controlled workspace.
The platform supports work across business and technical teams. Design AE and Construction are specialized Suites alongside research, office, workflow, collaboration, and operational capabilities.
No. Enabled models and working data can operate on owner-managed infrastructure, while web research, connected providers, and optional external services require network access and configuration.
Where enabled, you can separately authorize the provider connection. Signing in does not automatically connect a mailbox. The privacy notice explains the published purposes and data-use boundaries.
Availability depends on enabled programs, model configuration, infrastructure, licenses, provider connections, and permissions. Confirm the requirements for your workflow during deployment planning.
Start with a scoped deployment conversation. Users, Suites, compute, integrations, migration, training, and operating support contribute to the written proposal.
Yes. The demo is an illustrative walkthrough with sample content. It does not run a private tenant or perform actions in a real project.
Use the support contact route and describe the issue without including passwords or private content. Your workspace administrator can also help with tenant assignments and roles.
Start with the work your team needs to finish. We’ll help define the right capabilities, deployment, and next step.