You are handing us the manuals, wiring diagrams, and service history that run your fleet. We treat that like the operational record it is — separated per account, scoped to your team, and used only to answer your own questions.
Per-account isolation · retrieval scoped to your data · every answer cites its source.
Washer throws E-23 mid-cycle and stops draining. What should I check first?
E-23 E-23 is a drain-timeout fault. Answered only from documents in your account:
J4 against spec.No marketing abstractions — concrete properties of how the platform is built and run. Where a control is a roadmap item, we say so plainly.
Every account is a separate tenant. Documents, machines, service calls, and chat history carry an account boundary on every record, and isolation is enforced in the application layer on every query — not left to a shared filter someone could forget.
account boundary · enforced per requestAnswers are retrieved from your account’s ingested documents and service history — and nothing else. Never the open web, never another customer’s manuals, never a shared model trained on your content.
scope: this account onlyEvery answer links the exact manual page or past service call it drew from, so a supervisor can verify a fix instead of trusting a black box. The citation trail is built to support your compliance program — audit-ready by design.
answer → source, every timeGranular role-based access decides who can read, edit, and delete each kind of record. Scoped resources support an “all” vs “own” distinction — a technician sees the service calls and tickets assigned to them; a manager sees the whole account.
roles · scopes: all / ownThe platform runs on AWS in an EU region. Data is encrypted in transit and at rest, and infrastructure access is restricted to the operating team. We host your knowledge — we don’t resell it.
AWS · EU region · encryptedAccounts are invite-based: people join your workspace only when an administrator invites them, and access is removed the moment they’re off-boarded. The sign-in layer is built to support single sign-on as your team standardizes on it.
invite-based · SSO-readyTrust on a B2B platform isn’t a badge — it’s how the system behaves when a technician asks it something under pressure. These are the rules the product holds to.
We’d rather be precise than impressive. Here’s the line between what the platform does today and what it doesn’t.
A 30-minute walkthrough on your own equipment and documents. We map your manuals and service history, then show your team asking the questions they hit every week.
A 30-minute walkthrough on your own equipment and documents · no credit card