Models and context
Instructions, conversation history and attachments provide context for the selected model. The platform brings model requests and tool results together in the conversation.
LIVOI connects documents, business systems and conversations.
With LIVOI, employees, dealers and customers access documents and business systems in a conversation. P-CATION works with your team to understand the process and set up the right agents, knowledge sources and integrations.
For each agent, you configure the model, instructions, knowledge sources and available tools. LIVOI coordinates their execution.
Instructions, conversation history and attachments provide context for the selected model. The platform brings model requests and tool results together in the conversation.
Documents are prepared for knowledge retrieval. Retrieval-augmented generation (RAG) gives the agent relevant content and sources from the available knowledge base.
LIVOI tools provide capabilities such as knowledge retrieval. Custom tools call your own HTTP APIs. MCP clients connect agents to tools offered by configured MCP servers.
The agent queries Odoo and your documents. Every tool call stays visible in the conversation, and every answer cites its sources.
Requests from WhatsApp, Teams and email arrive in one place. The agent replies where the question was asked.
The dashboard also works in a mobile browser.
Three examples from practice. The tasks an agent takes on depend on your sources, tools and access permissions.
Service technicians work with fault trees and repair guides in chat. We prepare the sources and test the diagnostic workflows with your team.
View exampleFrom a photo of the registration document to an evidenced parts list with price and fitting time. We connect product data to chat and check the mappings with your domain experts.
View exampleEngineering designs with sliders, live charts and a PDF report right in the conversation. We bring your domain logic into the chat as an MCP App and check the results with your experts.
View exampleTogether with your team, we clarify the process, the required sources and permissions. We configure agents and integrations, test them on real cases and support the rollout. After each step, you decide whether and how to continue.
The LIVOI application, background processing and central data stores run in a German data center. Stored data includes original files, chat attachments, conversation history, prepared text, metadata and embeddings.
View data flows and locationsEncryption protects data in transit and sensitive credentials. Permissions determine who can use which content. These safeguards work together at different levels.
Data between your browser and LIVOI is encrypted in transit. This protects messages and login data against interception on the network.
The dashboard and API are available over HTTPS and support TLS 1.2 and TLS 1.3. TLS encrypts the connection and verifies the server identity using a certificate. To handle a request, LIVOI processes its content in plaintext; configured AI services receive the content sent to them for their task.
Sensitive credentials for connected services are encrypted in designated database fields. These include model API keys, OAuth tokens and MCP credentials.
LIVOI uses PostgreSQL pgcrypto with AES-256 for these fields. Encryption and decryption happen at field level. The required key is supplied through the operating environment. The application decrypts values when it needs them for an authorized integration. This additional field encryption applies to the designated credential fields.
A tenant is a separate workspace for an organization. Within it, roles and groups define who may read or edit data and configure agents.
LIVOI combines role-based access control (RBAC) with row-level security (RLS) in PostgreSQL. Application database access is restricted according to the tenant, user and permission context. Resource grants allow targeted access to individual items.
For certain file operations, LIVOI creates signed links with an expiry time. Authorized workflows can retrieve files without requiring a permanently valid download link.
Presigned URLs sign a specific file operation and limit its validity. The lifetime depends on the individual request. Anyone holding the link can use it while it is valid. Expiration does not delete content that has already been downloaded.
LIVOI checks its own API keys against a stored verification value. For connected WhatsApp webhooks, it also checks that the message carries a valid signature.
To verify its own API keys, LIVOI stores an HMAC-SHA-256 value calculated with an individual salt. WhatsApp webhook signature verification also uses HMAC-SHA-256. Hashes and signatures verify secrets or message authenticity and integrity; they do not encrypt message content.
Details of additional storage layers, backups, retention and organizational safeguards are established for the specific operating environment. Technical and organizational measures (TOMs) and contractual documents are available on request.
Storage in Germany does not mean all processing takes place there. Depending on the feature, content is sent to configured services.
Permissions are evaluated within each tenant. Roles bundle permitted actions; groups help assign them to multiple users. Depending on the resource, access can be limited to owned, shared or tenant-wide content.
You define who can configure agents, maintain knowledge and use resources. Permissions in external APIs and MCP servers are also governed by the respective integration.
You can read the privacy policy directly. Terms and the DPA are provided on request.
Knowledge management covers everything a company does so that existing knowledge (manuals, experience, processes, customer knowledge) is captured and reaches the right person at the right moment. Software helps store and retrieve that knowledge. LIVOI adds AI agents that answer questions directly.
You do not have to start from scratch. Existing documents such as PDFs, Word and Excel files are uploaded to LIVOI and prepared for knowledge search automatically. Current data from ERP or CRM is connected rather than copied. Which sources make sense and who may access what is something we clarify together in the first step.
That depends on what you need. If your team mainly wants to store documents and search them itself, classic knowledge management tools such as a wiki or intranet are often enough. If employees, dealers or customers need fast answers with sources, on the go and from several systems, an AI solution like LIVOI is the better fit. In the first conversation we tell you honestly what suits you.
The market ranges from wiki and intranet solutions to document management systems and AI platforms. LIVOI comes from P-CATION in Arnsberg: developed and operated in Germany, with a personal rollout and integration with the systems you already use.
No. P-CATION sets up agents, knowledge sources and integrations and supports the rollout. Your team then works in familiar channels such as chat, WhatsApp or Teams.
LIVOI is model-agnostic. Each agent uses the model that fits the task, for example from OpenAI, Azure or Anthropic, including your own endpoints. Switching does not require rebuilding knowledge or tools.
The price depends on your use case, the integrations and the number of agents. We quote it after a short conversation, on request and without sales pressure.
LIVOI is designed for GDPR-compliant use: the application and central data stores run in a German data center, every company has its own tenant, roles control access, and the data paths to AI services and connected systems are disclosed. Customer data is not used to train our own models. The data processing agreement is available on request.
An AI model only generates text. The agent harness turns it into an agent: it tells the model which tools are available, detects tool calls in the response, executes them and returns the results to the model until an answer is ready. In LIVOI, the platform does this: it assembles the context, provides tools such as knowledge search, custom tools and MCP, and validates inputs against the schema before running them. Model, instructions, knowledge and tools are configured per agent. Conversations, channels and permissions are handled separately by the LIVOI platform.
Custom tools call configured HTTP APIs. MCP clients expose tools from connected MCP servers. The LIVOI API also lets you embed agents into your applications. P-CATION helps implement the appropriate integration.
The dashboard and API use HTTPS with TLS, supporting TLS 1.2 and TLS 1.3. Sensitive credentials such as model API keys, OAuth tokens and MCP credentials are encrypted in designated database fields using AES-256 through PostgreSQL pgcrypto. Further storage and backup details depend on the operating environment and are addressed in its technical and organizational measures.
The central data stores of the LIVOI environment are in a German data center. AI requests, knowledge preparation, tool calls and external communication channels may send content to other services. Their processing locations must be considered separately.
Processing region, retention and possible provider use of content depend on the selected service, its configuration and agreed terms. These points are established for the specific integration.