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.
Use company knowledge in service and sales.
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.
What the platform handles
For each agent, you configure the model, instructions, knowledge sources and available tools. LIVOI coordinates their execution.
Knowledge and files
Documents are prepared for knowledge retrieval. Retrieval-augmented generation (RAG) gives the agent relevant content and sources from the available knowledge base.
Tools, custom APIs and MCP
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.
Example applications
Three examples from practice. The tasks an agent takes on depend on your sources, tools and access permissions.
Fault diagnosis in service
Service technicians work with fault trees and repair guides in chat. We prepare the sources and test the diagnostic workflows with your team.
View exampleTalk to Odoo
Query project status, quotes and invoices or create sales opportunities in chat. We connect the Odoo functions you need with appropriate access permissions.
View exampleFind the right kit
From 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 exampleSetup and integration with P-CATION
Together 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.
Data security and storage locations
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 locationsHow we protect data
Encryption protects data in transit and sensitive credentials. Permissions determine who can use which content. These safeguards work together at different levels.
Encrypted connections
Data between your browser and LIVOI is encrypted in transit. This protects messages and login data against interception on the network.
Technical details
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.
Credentials encrypted with AES-256
Sensitive credentials for connected services are encrypted in designated database fields. These include model API keys, OAuth tokens and MCP credentials.
Technical details
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.
Tenants and permissions
A tenant is a separate workspace for an organization. Within it, roles and groups define who may read or edit data and configure agents.
Technical details
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.
Time-limited file access
For certain file operations, LIVOI creates signed links with an expiry time. Authorized workflows can retrieve files without requiring a permanently valid download link.
Technical details
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.
API keys and signature verification
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.
Technical details
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.
Where data is sent
Storage in Germany does not mean all processing takes place there. Depending on the feature, content is sent to configured services.
- AI and embedding services
- Model requests may include messages, context and attachments. For knowledge preparation, the embedding service receives text sections or supported file and media content.
- Custom tools and MCP
- Custom APIs receive the configured request data. MCP sends the tool name and arguments to the MCP server, which may contact further systems. Results return to the agent.
- Connected channels
- With channels such as WhatsApp, the channel provider also processes messages and attachments. External service locations and terms depend on the selected integration.
Manage access with tenants, roles and groups
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.
Legal documents
Privacy policy
Read privacy policyTerms and conditions
On requestData processing agreement (DPA)
On requestYou can read the privacy policy directly. Terms and the DPA are provided on request.
Frequently asked questions
What is an agent harness?
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.
How can we connect our own systems?
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.
How is data encrypted in LIVOI?
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.
Does all data stay in Germany?
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.
Which rules apply to external AI services?
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.