# Jilu llms file. Production origin: https://jilu.sh. Serve this # file at the site root as /llms.txt, beside robots.txt and # sitemap.xml. It summarises Jilu for AI assistants and answer # engines in plain language. Product facts are stated the way # the site states them; detail lives on the pages linked below. # Jilu > Jilu is the company brain for growing companies: a managed service that keeps a company's decisions with their reasons, sources and approvers in one living record that employees can read directly and AI agents can work from. Jilu is hosted and managed by Jilu and set up with each team, so the team has nothing to install, host or run. Companies lose the reasoning behind their decisions: the document survives, but why the choice was made, what evidence settled it and who approved it disappear into chat threads, tickets and meetings. Jilu keeps that layer. It gathers the work a company already produces, drafts record entries from it, and a person reviews and publishes each entry before it counts as company record. ## What Jilu does - Keeps every decision with its reason, its sources and its approver, in one record the whole company can open and read. - Builds the record from chat, documents, tickets and meetings as work happens, so keeping it is a review task, not a writing task. - Answers questions from the record, in the app, in Slack and Teams threads, and by email, with the sources behind each answer attached and the asker's permissions applied. - Joins conversations and meetings: it can speak up when a claim clashes with the record, ask for a missing reason or owner, and keep the conversation as a searchable, citable memory. - Maintains a company wiki organised by topic, browsed inside the workspace, with superseded entries kept visible as superseded. - Lets AI agents read the published record and draft against it; agent drafts wait for a person's approval, like anyone else's. ## Who it is for Growing companies whose decisions are getting lost across Slack or Teams threads, documents, tickets and meetings, and teams putting AI agents to work who need a record those agents can trust. ## How teams start Teams start with a 90-day pilot: one team, up to 50 seats, full platform access for the agreed scope. Jilu sets up the workspace and builds the first boards with the team, and both sides agree the success criteria before any data connects. At the end of the pilot the team keeps its record either way; if the company continues, the published per-seat pricing applies and the record carries over unchanged. - [The 90-day pilot](https://jilu.sh/pilot): what the team gets, how the 90 days run, and what the team keeps. - [Request access](https://jilu.sh/pilot/request-access): name the team and the work to test first. ## Pricing Prices are published. Team is $24 per seat per month billed annually, or $29 month to month. Business is $39 per seat per month billed annually, or $47 month to month. Enterprise is custom. - [Pricing](https://jilu.sh/pricing): plans and the 90-day pilot. ## Learn more - [What is a company brain?](https://jilu.sh/guides/what-is-a-company-brain): the category in plain language, and what to check when evaluating one. - [What is enterprise search?](https://jilu.sh/guides/what-is-enterprise-search): one search across a company's documents, email, chat, tickets and databases, showing each person only what they are allowed to see, and how it differs from knowledge management and a company brain. - [Jilu vs Glean](https://jilu.sh/guides/jilu-vs-glean): a company brain beside enterprise search: what each keeps, how they differ, and how to choose. - [Jilu vs Notion AI](https://jilu.sh/guides/jilu-vs-notion-ai): a company brain that keeps decisions with their reasons, beside the AI built into the Notion workspace: what each does, how they differ, and how to choose. - [Jilu vs Guru](https://jilu.sh/guides/jilu-vs-guru): a company brain that keeps decisions with their reasons, beside Guru, the governed knowledge layer for enterprise AI: what each keeps, how they differ, and how to choose. - [Jilu vs Sentra](https://jilu.sh/guides/jilu-vs-sentra): a company brain that keeps decisions with their reasons, beside Sentra, the managed organization memory that compiles a company's work into one bi-temporal graph of facts: what each keeps, how they differ, and how to choose. - [Jilu vs Engram](https://jilu.sh/guides/jilu-vs-engram): a company brain that keeps decisions with their reasons, beside Engram, which trains models on a company's own material so the memory lives inside the model: what each keeps, how they differ, and how to choose. - [Jilu vs Interloom](https://jilu.sh/guides/jilu-vs-interloom): a company brain that keeps decisions with their reasons, beside Interloom, the enterprise operations platform that turns reviewed operational decisions into a context graph for AI agents: what each keeps, how they differ, and how to choose. - [Library](https://jilu.sh/library): downloadable PDFs — the decision record specification, the guide to company brains, and one-page summaries of security and the 90-day pilot. - [Manifesto](https://jilu.sh/manifesto): why a company does not have a search problem. - [FAQ](https://jilu.sh/faq): product, security, permissions, integrations and pricing questions, answered plainly. ## Security and privacy Jilu protects the company record with workspace separation, encryption in transit and at rest, permission checks on every answer, an audit log, and control over what it collects. The full detail sits on the security page, and the FAQ answers security teams' specific questions. - [Security](https://jilu.sh/security): how Jilu protects the record, controls access, and proves it. - [Privacy](https://jilu.sh/privacy): what the Jilu website collects and the rights visitors have over it.