A set of cooperating components — not one monolith.
lixwi is modular. Only a small core is always present; refinement, workspaces and automation are optional layers added per deployment. A deployment runs just the parts it needs, and what's present works without what's absent.
The always-present spine.
Where knowledge lives, how change travels, how AI work runs, and how people reach it all.
Knowledge graph store
The single, connected source of knowledge. Holds items and their typed relationships, keeps everything navigable and searchable, enforces who-sees-what on every read, and announces every change.
Event backbone
Every meaningful change becomes an event on a durable, ordered, replayable stream. A new document can set work in motion; a finished task can advance a process. Components stay decoupled and recover cleanly.
Execution engine
Launches and supervises short-lived AI workers, holds their durable state, recovers them after failure, and tracks usage and limits so automated work never runs away.
Model routing & definitions
Translates a 'kind of model' into a concrete connected one at run time, keeps model choice swappable per deployment, and holds the governed, reusable definitions that shape agent behavior.
Gateway
One secure front door. Verifies identity and access, routes each request inward, streams live updates back out, and exposes the platform to external AI through a standard MCP interface.
Frontend
The configurable human face — a full workspace, a pared-down role view, or an embedded app — that stays live as the data behind it changes.
Add capability as you're ready.
Keeps knowledge findable and self-describing. Semantic index & search make content searchable by meaning and surface related items; the summarizer keeps a current summary on every item and explains why any two are linked — all automatically.
A real, isolated environment where an agent can work with files and run commands — writing code, processing document batches, running data jobs. Scratch by design, running on the company's own compute; durable results leave to the knowledge store or a repository.
Runs repeatable processes end-to-end on their own. Pluggable process definitions lay out steps and decision points; the engine handles the wiring while judgment is delegated to an agent or a person. Every run stays bounded and visible.
The always-there plumbing that keeps it secure and installable.
Secrets vault
All sensitive credentials live in one guarded, encrypted place. Everywhere else holds only a reference — never the secret itself — kept out of logs, records and exports, and rotated on their own schedule.
Access & deployment
Each company's data is a hard partition, with no path between companies. Within a company, visibility is graded and checked on every read. The same system ships as a managed cloud service or a self-contained on-premise install.
See lixwi mapped to your operation
Tell us how your company runs today. We'll show you where a shared brain removes the most friction, starting with a focused, measurable pilot.