No signal. No cloud. No exceptions.
Niobe Edge is Niobe with the cord cut. It listens, reads your documents, reasons, and answers — entirely on the device in your hand. Your data never leaves, because there is nowhere for it to go.
Same brain. Same voice. Works in a basement, on a plane, offshore, or anywhere the bars run out.
One capability. Three levels of consequence.
Running offline means something different depending on what happens when you can't. Same engine every time — only the stakes change.
Nothing you say gets uploaded anywhere.
The reason most assistants can answer you is that they ship your words to somebody's server. Niobe Edge doesn't have that option, which means the promise isn't a policy you have to trust — it's a fact about how it's built. It also means it still works on a plane, in a parking garage, out past the last tower.
Some information is not allowed to leave the building.
Client files, patient records, case notes, drawings, payroll. Plenty of small businesses can't use cloud AI at all, not because they don't want the help but because handing that material to a third party is the one thing they can't do. An assistant that reads your documents on your own machine is a different product from one that promises to be careful with them. It's also the answer for crews working where coverage doesn't reach — job sites, basements, vessels, remote installations.
The network is denied, and being wrong is dangerous.
Emergency response, maritime operations, industrial and defense work. Here the connection isn't slow, it's gone, and a confidently wrong answer causes harm. This is the version we engineered against first — hands-free because the operator is gloved, grounded in real manuals because guessing is unacceptable, and honest about stale data instead of drawing it as though it were live.
Two paths. One display. The picture never stops.
Thinking takes seconds. Watching has to be instant. Most assistants make you wait for both, because they run one loop. Niobe Edge runs two at once, and they share only the screen.
The obvious build is one loop. We built that first and threw it away: it freezes everything on screen for as long as an answer takes. You can wait for an answer. What you're looking at can't wait for anything.
We built the hard version first.
The fastest way to know an offline assistant actually holds up is to test it where failure is expensive. So the first three workflows we built end to end were the demanding ones — naval maintenance, emergency response, and navigation with no visibility. Each runs as a repeatable test that declares the answer it expects and reports pass or fail.
Support that doesn't hang up
An engineer works an equipment failure while the link back to head office degrades and then drops. The device keeps answering. Every field technician who has lost signal mid-repair knows this one.
Guidance with both hands full
A fire develops while the operator is masked and gloved, with readings changing by the second. No touchscreen is available at any price, and the display cannot pause to think.
Knowing what's stale
Moving through a tight channel as visibility closes. A reading eight seconds old, drawn as though it were current, is worse than no reading — so it's withheld and labelled instead.
Running today, on a machine with no internet.
| Capability | Status | Where it stands |
|---|---|---|
| Fully offline operation | Built | Refuses to start if it finds a route out. Enforced by the software, not promised in a policy. |
| Hands-free voice | Built | Wake word, push-to-talk, and always-on. Push-to-talk is the low-power mode for loud places. |
| Answers grounded in your documents | Built | If your documents don't cover it, it says so instead of guessing, and cites the source when they do. |
| Instant display refresh | Built | Measured every run and reported. Comfortably inside target on development hardware. |
| Tamper-evident activity log | Built | Records that something happened without recording what was said. Refuses to run if the log has been altered. |
| Encryption at rest | Built | AES-256-GCM over the activity log and the document store, with no key written to disk. |
| Formal security certification | In progress | Required for regulated and government work. Underway, not finished. |
| Ruggedised hardware | Next | Temperature, water and dust resistance, all-day battery. Currently runs on commercial hardware. |
| Consumer glasses release | Next | The display side works today. Packaging it for everyday wear is the next build. |
What we're not claiming
Everyone in this space overstates. Here's the subtraction, so you know what the rest of the page is worth.
- —It only knows what's on the device. No documents loaded, no answers — and it will tell you that rather than invent something.
- —It advises. It doesn't take actions on your behalf or operate equipment.
- —Security certification is in progress, not complete. If you're in a regulated environment, ask us where it actually stands before you buy.
- —The cryptography uses correct, standard algorithms, but the build is not a formally validated module.
- —Demonstration content is synthetic and labelled. Your real documents stay yours and are loaded on your own machine.
- —Hardware is commercial today. Ruggedised units are a later build, not something you can order now.
Built for one operator first.
Niobe ran its founder's own business for months before it was offered to anyone else. That's still the whole idea: an intelligence that knows how you decide, working for you, on hardware you own.
Niobe Edge is that same architecture with the consequences raised. When the requirement stops being we'd rather not send your data anywhere and becomes this cannot leave the device, almost nothing about the design has to change. That's not luck. It's what you get from building local-first from the beginning instead of bolting privacy on afterwards.
local speech recognition
local language model
local document search
activity log & safeguards
no telemetry, any tier
Everyday, professional, and critical use run the same core.
Tell us where your signal drops.
Field crews, regulated offices, response teams, and operators working past the edge of coverage — we want the specifics of your environment.
Start with Niobe