Platform · Data connections
Your ERP, CRM and internal apps connect to aitnus over MCP (Model Context Protocol). Each person sees only what they're allowed to see in that system.
Companies that run their AI on aitnus
Define a system once. Every assistant and every team then uses it under the same rules.
Company systems
Used by
Grant access by group. Sales can reach the CRM, Legal can't.
| Documents | CRM | ERP | HR | Contracts | |
|---|---|---|---|---|---|
| Sales | Allowed | Allowed | Allowed | Not allowed | Allowed |
| HR | Allowed | Not allowed | Not allowed | Allowed | Not allowed |
| Legal | Allowed | Not allowed | Not allowed | Not allowed | Allowed |
Each user connects to the system with their own account
Illustrative data
Add a policy, a price list or a handbook to an assistant or a project. Every answer shows the document behind it.
Sources
Illustrative data
For systems without a ready connection, our engineers connect them with your team and take the first use cases live.
Processes and data sources
ERP, CRM and document stores
First assistants and workflows
Groups, permissions and budgets
Training and usage tracking
aitnus engineersYour teamtogether at every step
Define the MCP server, or let us set it up.
Choose which teams can use which systems.
The assistant goes to the right system and brings the result back with its source.
Any system that offers an MCP server or an API, such as ERP, CRM, Jira, Confluence or Slack. For internal apps without one, our engineers can connect them with your team when needed.
No. The employee connects to the system with their own account, and the assistant returns only what they can see. You also decide which teams can reach which systems.
Encrypted. Each user connects with OAuth or their own key.
Yes. Access changes and system calls are logged. The MCP usage report shows call counts, success rates and the most used tools.
