# Ainomos

Ainomos develops NomOS. Teams and connected AI agents use company knowledge, current policies and reviewed decisions in their work. Employees use web chat; agents connect through MCP. Reviewed results remain available for further tasks with their sources, rationale and scope.

Technical action controls apply to appropriately integrated execution paths. An MCP connection alone does not control arbitrary local actions. Reuse can reduce repeated research and model work; actual savings must be measured.

NomOS provides web chat and MCP capabilities. NomGate is planned as a local Windows/macOS control service, and NomApp for mobile knowledge access, notifications and approvals. NomStore remains an announced knowledge exchange platform. The operating model, data processing and capabilities are agreed for each deployment.

## Further reading

- [Product](https://ainomos.ch/en/how-it-works/)
- [Agent integrations](https://ainomos.ch/en/mcp-governance/)
- [Pilot and operation](https://ainomos.ch/en/offering/)
- [Evaluate value](https://ainomos.ch/en/value/)
- [Security](https://ainomos.ch/en/security/)
- [Questions and answers](https://ainomos.ch/en/faq/)
- [Company](https://ainomos.ch/en/company/)

## MCP and platform outlook

Through MCP, agents can retrieve knowledge, read decisions, submit knowledge and decision proposals, request action assessments and track their proposals. People approve new content and decisions. validate_action returns an assessment; it does not itself stop external execution. MCP capabilities do not require NomGate. NomGate is planned as a Windows/macOS control service. NomApp is planned for mobile knowledge access, notifications and approvals.

[Platform outlook](https://ainomos.ch/en/platform/)