Indexed Corpus
Your manuals, SOPs, and institutional data — indexed, sovereign, and searchable as the single source of truth.
Innaris turns your indexed corpus and everyday work into a living knowledge base — every answer gated and verified against sources, every job captured as experience, so lessons learned are never repeated and patterns surface on their own.
Your manuals, SOPs, and institutional data — indexed, sovereign, and searchable as the single source of truth.
Every response is grounded in cited sources and passes a verification gate — no ungrounded claims reach the field.
Interactions become experiences — what worked, what didn't, caveats, and senior tacit knowledge, referenced on the next job.
Dashboards reveal common problems, solutions, and emerging themes — signalling which documents, SOPs, and training to update.
A knowledge graph of your own corpus, a retrieval pipeline that must demonstrate relevance, and a delivery gate that verifies every answer before it reaches the screen.
PDF manuals, SOPs, work orders, spreadsheets, photos. Figures inside documents are OCR'd and stored with their caption and surrounding text, so nameplates and diagrams are searchable and citable.
Filename similarity, exact keyword grep, embedding similarity and knowledge‑graph relations — a passage only enters an answer when its own content meets the question's threshold.
The model drafts from the retrieved evidence only. An NLI verifier checks each claim against the cited passages; the answer is delivered, marked inferred, or withheld.
Technicians file what actually fixed it. Submissions are signed on the device, verified by an admin, and become citable memory with who, seniority, when and validation attached.
Every answer carries the evidence behind it and an honest number for how much to trust it.
The percentage is computed from the verifier verdict, per‑claim entailment coverage, retrieval tier, evidence count and validated experience — and the tooltip lists every factor.
No evidence in your corpus? The answer is delivered blurred as general knowledge, capped at low confidence, and revealed only on your say‑so. Alert‑linked diagnoses stay withheld until acknowledged.
Experience submissions are Ed25519‑signed and chained; the store carries a Merkle manifest. The hub refuses submissions whose signature doesn't verify.
Documents live on the device or your own Central Hub. Online mode sends only the question plus the sanitized retrieved context to the model — never your library.
Every install is a node. Nodes work offline and sync to your Central Hub when online, so every technician's verified experience keeps building the same institutional brain.
A technician's experience stays on their device and in the local review queue. It's pushed to the hub inbox as pending and joins the master graph only after an admin verifies it.
Nodes pull the master corpus, figures and every verified experience — with provenance — into their local store, even after weeks offline.
Admins issue a client key per user and device, revoke it any time, and see last‑seen and sync state for the whole fleet.
The same key authorises online model calls through the hub — Amazon Bedrock, Anthropic, OpenAI and more — metered per organization with a spend cap. The picker shows exactly the models your account can use.
Choose Personal (a few nodes for one person) or Enterprise (many nodes across your teams) at any tier. Pricing is per active node plus the hub, scaled to the tier's capability — request access and we'll confirm a quote with your keys.
Personal or Enterprise · pricing on request
Your Central Hub, master corpus and knowledge graph hosted on Innaris cloud infrastructure, isolated per organization. Cloud models (Amazon Bedrock and more) through your hub, metered to your account.
Enterprise · pricing on request
Everything in Cloud Hub, on infrastructure you own: a company-controlled Central Hub and data store (your premises or VPC), with an optional air-gapped server running large models behind a private, protected API.
Enterprise · pricing on request
Everything in Protected, fully offline. Nodes run locally and the Central Hub can be offline too; nodes sync with each other over near-field / proximity links and relay changes hop by hop until they reach the hub.
Tell us who you are and what you need. When an Innaris administrator approves the request you'll receive a one-time secure link that reveals your organization's admin key and setup steps. From there you install the app, connect it to your Central Hub, and issue keys to your own team or devices.
Desktop installs run the local model on your hardware; phones and tablets install the web app and talk to your node or Central Hub.
Runs the local model on Metal. Install as an app from Safari (File → Add to Dock) or Chrome (install icon).
git clone the repository, then `bash start_mac.sh` (creates the venv, installs requirements, starts on http://localhost:3131)CUDA offload when an NVIDIA GPU is present; CPU otherwise. Install as an app from Edge or Chrome (install icon).
git clone the repository, then `powershell -ExecutionPolicy Bypass -File start_windows.ps1`CUDA/ROCm or CPU. Install as an app from Chrome/Chromium (install icon).
git clone the repository, then `bash start_linux.sh`Open your Innaris node or Central Hub address in Safari, tap Share → Add to Home Screen. Runs full-screen with offline shell; answers come from your node/hub.
Open your Innaris address in Chrome and tap Install (or ⋮ → Install app). Works as a standalone app.
Use the address-bar install icon to pin Innaris as an app.
.env as INNARIS_HUB_URL and INNARIS_HUB_CLIENT_KEY.