The NbotaiOS idea
A plain-language narrative connects fragmented software, owner-controlled deployment, specialized Suites, durable outputs, and continuing work.
Public release record
What changed.
What is live.
This log covers the public marketing website. Product deployment releases and private tenant changes have separate owner records.
July 28, 2026 / Homepage literature revision
The complete NbotaiOS story.
In the open.
The homepage now includes a long-form explanation of why NbotaiOS exists, what an AI operating system means, how local-first ownership works, and how work continues from intent to an accountable result. A twelve-part capability library describes the practical work NbotaiOS can support, and a new category section explains the exact combination behind “There is only one NbotaiOS.”
Twelve capability areas
Research, content, files, projects, automation, AEC, construction, collaboration, media, production, system control, and governance are made specific.
A category of its own
The page explains why NbotaiOS is more than any one chat, model, cloud service, automation tool, app collection, or answer.
July 28, 2026
Clear product language.
More useful detail.
The homepage now explains what NbotaiOS is, what work it supports, who it serves, how local-first deployment works, and where human approval fits. Every indexable public page also has a distinct customer-facing title, description, sharing summary, canonical URL, and structured product description.
Direct product definition
NbotaiOS is described as a local-first AI platform for knowledge, documents, workflows, projects, AEC, construction, and operations.
Customer search language
Suite pages use the terms people use for AI research, document management, workflow automation, construction AI, AEC AI, and private collaboration.
Grounded boundaries
Local deployment, optional connected services, tenant routing, human approval, and public-safe proof remain explicit without invented claims.
July 18, 2026
Public decision
and support layer.
The release adds the guided demo, filterable solutions, trust architecture, public-safe proof, package estimator, documentation map, grounded public assistant, validated contact flow, status endpoint, support route, and legal/accessibility pages. It also defines one canonical www origin for public marketing pages.
Demo, solutions, proof
Visitors can inspect a synthetic workflow and match work to connected Suite routes.
Trust and pricing
Product boundaries, deployment responsibilities, packages, and quote factors are explicit.
Docs, support, status
Public guidance, issue preparation, health, disclosure, and policy paths are linked.
July 14, 2026
Suite-led public site.
The homepage and seven Suite pages established the public visual system, local-first product narrative, Suite detail routes, search metadata, sitemap, security headers, and release-boundary validation.