What Octy is

Octy™ answers questions from the organisation’s own knowledge: product documentation, policies, support content or sector regulation. Each answer cites the passages it was written from. Octy runs inside the organisation’s deployment, on the organisation’s models, and the cost of every model call is recorded in LightHouse™.

Octy is one agent, with the same code, character and rules in every deployment. Each use is defined by an Octy profile: the knowledge it may read, who may ask it, the channels they use, the limits it runs under and where it runs. Client administrators create and manage Octy profiles in LightHouse. See Octy profiles and Manage Octy profiles.

What it does

• Answers from the organisation’s knowledge. Octy searches only the knowledge its profile names, within the access of the person asking, and answers from the passages it finds. Every answer cites its sources. When the knowledge does not cover a question, the answer states this. See Knowledge and boundaries.
• Shows its evidence. The sources behind an answer are shown with it, and each answer is checked against them before it is sent. Each answer carries a signed receipt that any party can verify. See Evidence and question insights.
• Does not act. Octy answers, explains and routes. It holds no tool that approves, pays, changes access or changes a limit. Work goes to an agent, through an approval card that a person approves in LightHouse. See Octy and agents.

Cost

Octy answers at the lowest cost that meets the profile’s quality bar.

1. Retrieval first. The knowledge base is searched inside the deployment, with no call to a model provider. A question the knowledge does not cover receives a “not covered” answer before an answering model is called. Answers composed of the retrieved passages, quoted with their sources, call no model.
2. The cheapest model that meets the bar. When an answer needs an explanation, a small model writes it from the retrieved passages, through the organisation’s gateway. Every such answer goes through the profile’s router, which selects the cheapest model that meets the profile’s quality bar and escalates only when an answer misses it. See The router for every profile. An explained answer typically costs a fraction of a cent, estimated. Sending every question to a large model costs many times more, estimated.
3. A cap on every profile. Each profile has a monthly spend cap, enforced before a model is called. See Controls.

One question to Octy

1. A question arrives from the profile's audience, on one of its channels.
2. Controls: who may ask, from where, how often, and within the spend cap. A question refused here costs nothing.
3. Retrieval searches the profile's knowledge only, within the caller's access scope.
4. Not covered: if nothing is relevant enough, Octy says so, and no answering model is called.
5. Retrieval answer (Coming): the passages themselves, quoted with their sources, and no model is called.
6. Explained answer: a small model writes the answer from the passages, through your gateway. The router choosing the cheapest model that meets the quality bar for each answer is Coming.
7. Evidence: every source is cited with the answer. A signed receipt is Coming.
8. Measurement: counts, timings and the cost of each answer go to LightHouse. No content does.

Most of the work is retrieval, which runs in your deployment at almost no cost. A model is called only when an answer needs explaining, and then a small one. Dashed stages are Coming.

Cost analysis describes how cost is measured for each profile. Every figure is labelled estimated.

Where it runs

An Octy profile runs where its knowledge is held. A profile over the organisation’s own knowledge runs in the organisation’s deployment: in its AWS, Azure or Google Cloud account, on its own servers, or air-gapped on local models, under any deployment profile. The profile uses the organisation’s models through its gateway, and the organisation pays its own provider. The knowledge remains in the organisation’s account and is read in place. Atlantic hosts the profiles that answer from Atlantic’s public material and from the tenant’s LightHouse data. See Where Octy runs.

Status

Capability	Status
Octy in a client deployment: answers from the organisation’s documents with citations, for people signed in through its identity provider	Built
Octy in the LightHouse portal, answering from the tenant’s data under the person’s role	Built
Channels: a web widget for the organisation’s website or intranet, Microsoft Teams, Slack, MCP for other agents	Built
Controls: a monthly spend cap, rate limits per person, allowed origins	Built
“Not covered” before any model is called; refusal of any request to act	Built
Octy on these docs: answers from this documentation, with a monthly cap and rate limits	Built
Retrieval answers with no model call, for every profile	Built
The evidence panel and signed receipts	Built
The Octy profiles page in LightHouse: create, test, publish, pause and delete a profile, with its knowledge, channels, controls and router, and the audit of every change	Built
Profiles applied to a client deployment by signed command, or by command file when it is air-gapped	Built
Rate limits per visitor, per session and overall; address allow and deny lists; allowed pages; the bot check for public profiles	Built
The router for every profile, with each decision and escalation recorded	Built
The website widget for any profile, the web panel, and the MCP and API channels per profile	Built
Cost analysis and question insights for each profile	Built
Octy profiles consulting each other	Coming

In this section

• Octy profiles: what a profile holds, its states and revisions, and the rules every profile keeps.
• Manage Octy profiles: the LightHouse page, from draft to live profile, and how a change reaches a deployment.
• Knowledge and boundaries: the knowledge Octy answers from, and how the boundary is enforced.
• Controls: who can ask, from where, how often and at what cost, in order of enforcement.
• The router for every profile: the cheapest model that meets the profile’s quality bar.
• Cost analysis: model cost per answer, and the cost figures for each profile.
• Evidence and question insights: citations, the evidence panel, verifiable receipts, and the questions each profile receives.
• Where Octy runs: Atlantic-hosted, each cloud, the organisation’s own servers, air-gapped, and each deployment profile.
• Channels: the web panel, the widget, the portal, Teams, Slack, MCP and the API.
• The website widget: the script tag, its content security policy, and the checks the service enforces.
• Octy and agents: how Octy differs from agents, and how it hands work to them.