user
Usuario / rol
sso · canal
Kodex
Technology solutions
We design augmented workstations: the assistant understands your domain, cites sources, and acts on real systems — with identity, guardrails, and ISO 27001.
What it is and why it matters
A bare LLM answers. A Kodex assistant collaborates: memory (RAG), tools (MCP), identity policies, and UX designed for adoption — from the floor to the C-suite.
What the assistant must do, for whom, with which permissions, and which adoption KPIs.
RAG with citations and abstention when there is no evidence — less hallucination, more trust.
MCP and guardrails: it can query and execute only what is allowed, with an auditable trail.
Generic chatbot
Kodex assistant
Live flow
Two lanes: the augmented-seat interface and the runtime with memory, tools, and guardrails.
Flujo del asistente: usuario, modelo, guardrails, RAG, MCP y respuesta con evidencia
01 · Interfaz del puesto
user
Usuario / rol
sso · canal
assistant
Asistente
llm · sesión
guardrails
Guardrails
policy · PII
02 · Runtime con evidencia
memory
RAG
corpus · citas
tools
MCP tools
read · write
policy
HITL / scopes
allow · approve
output
Respuesta
cita · acción · audit
Depth
Three depths. Start with an evidence-backed copilot and grow to multi-role with governed execution.
01
Nivel 01
Answers well — and says from where
Ideal for support, legal, or internal technical teams: RAG, mandatory citations, and abstention policy.
Qué incluye
Ideal para · Teams that need truth before autonomy.
Resultado · Fewer repetitive tickets · more trust in the answer.
02
Nivel 02
Reads, writes, and escalates to a human
The assistant uses MCP tools (CRM, helpdesk, ERP) with scopes and HITL on critical actions.
Qué incluye
Ideal para · Ops and CX that want to close the loop in the same thread.
Resultado · Fewer clicks · more cases resolved with context.
03
Nivel 03
RecomendadoMulti-role · multi-model · perimeter
Multiple profiles (legal, procurement, plant), cloud or on-prem, observability, and ISO governance.
Qué incluye
Ideal para · Product and IT industrializing AI in day-to-day work.
Resultado · A system of assistants — not N orphaned pilots.
The model is the engine; RAG, MCP, and guardrails are the chassis. Without them, you only have a chat.
Corporate assistant
From user message to action: identity, model, memory, tools, and policy. Business sees adoption; engineering sees a governed runtime.
What the client gains
We do not sell ‘a chatbot’: we sell operational capacity with control.
01
The assistant resolves the repeatable and escalates the critical with full context.
02
Citations, abstention, and logs: useful for legal, quality, and ISO.
03
Updates CRM, opens tickets, or queries ERP — via MCP, not copy/paste.
04
UX and usage KPIs: if no one opens it, there is no ROI — we design so they do.
Dual reading
Same interface, two languages.
Negocio
It speaks like our team
Ingeniería
System prompts · glossary · sector few-shots
Negocio
It does not invent when it does not know
Ingeniería
RAG + citations · refusal policy · grounded evals
Negocio
It can do what is allowed
Ingeniería
MCP tools · scopes · HITL on writes
Negocio
We know what happened
Ingeniería
Traces · feedback loops · quality per case
From forgotten pilot to adopted seat
Illustration: how value redistributes when the assistant stops being a demo and becomes real work.
Casos de uso
01
Business: you choose sovereignty. Technical: OpenAI, Anthropic, Llama — same product contract.
02
Business: one system, several seats. Technical: profiles, prompts, and tools per role.
03
Business: reports, CRM, alerts. Technical: MCP + guardrails + audit trail.
A chat without memory or tools is noise. An augmented seat with governance is scalable capacity.
Business
The team focuses on exceptions; the assistant closes the recurring work with evidence.
Engineering
Model, RAG, MCP, evals, and UX: a versionable system — not a prompt in a wiki.
Illustration · Operational trust
+38 pts
illustrative trust vs generic chatbot without RAG or guardrails
↓ 55 % vs unanchored LLM
↑ 38 pts vs unanchored LLM
Answer confidence index (0–100)
Illustrative example: trust rises when moving from a bare LLM to an assistant with RAG, citations, and tools.
Each lever brings the assistant closer to real work — with less risk and more adoption.
Anchored answers in seconds, not searching across 4 systems.
Citations and abstention when the corpus does not cover the case.
MCP tools with scopes and HITL on writes.
Clear UX and roles: the assistant enters the workflow.
Cycle in days
20d → 6d
illustrative time from pilot to first seat in production
Antes
Con Kodex
Antes
Con Kodex
Antes
Con Kodex
Antes
Con Kodex
Illustrative values. In project we measure your case backlog and the post-assistant delta.
How we deliver
From the business role to the assistant in production — with clear deliverables for product and engineering.
Fase 1
Who, what, and with which permission
We define roles, channels, adoption KPIs, and the human/assistant boundary.
Fase 2
Data, hallucination, and PII
We assess corpus, guardrails, hallucination risk, and identity integration.
Fase 3
LLM + RAG + MCP + UX
We deploy the runtime, connect memory and tools, and tune the adoption interface.
Fase 4
The assistant learns from real use
Evals, prompts, corpus coverage, and new roles based on adoption.
Trust perimeter
The assistant inherits your security policy — it is not an anonymous widget on the intranet.
Identity
Every session knows who the user is and what they can request or execute.
IAM
Risk
PII filters, abstention, and human approval on critical actions.
Policy
Evidence
Where the answer came from and which tool was invoked — retained and auditable.
Audit trail
No. It amplifies capacity: it resolves the recurring work and escalates the critical to humans with full context.
With RAG, mandatory citations, abstention policies, and groundedness evals in the pipeline.
Yes, via MCP and governed connectors — the assistant operates on your real stack, not only PDFs.
You choose sovereignty: cloud for elasticity or on-prem / VPC for sensitive data — same product design.
Filtro de oro
Design, deployment, and operation of the assistant with RAG, MCP, and guardrails.
Book assistant designReview guides and resources to inform the stack decision.
View resourcesProcesos
Automatizaciones orquestadas
Menos horas y errores para negocio; eventos, MCP y logs para ingeniería — no triggers aislados.
Ver →RAG
Sistemas RAG
Base vectorial + citas: menos alucinaciones, más casos cerrados y conocimiento que mueve CRM/tickets.
Ver →MCP
Integraciones & MCP
Puerto MCP: la IA lee y actúa sobre ERP/CRM con scopes y auditoría — sin conectores punto a punto.
Ver →Kodex assistants: LLM with memory, tools, and governance — so your team does more with less risk.