Your organization. Connected. Informed. Thinking.
Questions & answersReceived an AIOSnode invitation?Click here
AIOSnode / Ownership

Purchased property model

The delivered Node becomes your operating property.

You purchase the organization-specific AIOSnode implementation and receive it for continued operation. AIOSnode retains the reusable platform, Factory, generic components and future platform technology.

Customer property

What travels with the Node

Organization-specific configuration and content
Customer data, records and generated operating assets
Knowledge collections, source inventory and customer policy bindings
Forms, workflows, apps and organization-specific automation configuration
Evidence, receipts and historical AS-OPERATED records
Backup/export material and operating documentation
Delivered browser extension version and granted use rights when included
AIOSnode retained IP

What we keep

Reusable AIOSnode platform architecture
Property Factory and generic build machinery
Reusable templates, generic modules and component libraries
AIOSnode trademarks and product identity
Future versions, new platform capabilities and future generic improvements

The owner-control rules

No rent on the property you purchased.

Optional services can add capability later, but they must not become a kill switch for the delivered property.

Portable

Customer-specific configuration, records, evidence and operating assets can travel with the property.

Self-hostable

Customer-controlled, hybrid and external AI deployment are valid choices. Managed external AI is not the only path.

Owner credentials

Operational credentials after handoff belong under the owner's control, not ours.

No accessory kill switch

Stopping AppInHere, FormAIOS, KBAIOS or another accessory service must not make the purchased Node unusable.

Delivered extension rights

When an extension is part of the delivered property, the delivered version carries permanent use plus organization install/copy rights, with no required subscription heartbeat or remote-disable dependency.

History stays history

Current rules may change. Historical AS-OPERATED evidence remains tied to the exact sources, versions and decisions that governed the action at the time.

Closing package

Think of the transfer like receiving the keys and records for a property.

The final handoff is evidence-bearing, not merely a username and password.

Node/core version and Property Package identity
Customer configuration and source/data inventory
Integration inventory and operational dependencies
Authority and governance settings
Evidence package and accessibility target record
Backup/restore and export material
Operating manual and administrator transfer
Delivered artifact rights
Acceptance record and transfer receipt

Your Node. Your Data. Your AI. Your Infrastructure.

Ownership includes the freedom to choose where the intelligence runs and to continue operating the delivered property without AIOSnode remaining in the middle.