Efficient on-device inference
How do we preserve useful task performance while operating within the memory, compute, thermal, and energy limits of real business devices?
We research how useful AI can run locally, work without continuous internet, speak the user's language, and remain under the organisation's control.
Our research starts with operational constraints, not ideal laboratory conditions. Devices may be modest. Connectivity may disappear. Business knowledge may be sensitive. Interfaces must work for people who prefer speech over software menus.
How do we preserve useful task performance while operating within the memory, compute, thermal, and energy limits of real business devices?
How can an organisation build durable, searchable intelligence from its records without surrendering that memory to a remote platform?
Which business tasks can be completed end-to-end without a cloud round-trip, and where should the system deliberately ask for human review?
How should a local agent understand code-switched speech, regional vocabulary, and spoken intent while turning it into structured, reviewable work?
These are active research tracks, not published performance claims. Each study moves from question to method to reproducible evidence.
What level of useful business intelligence can different device classes sustain locally?
Can workers finish meaningful operational tasks with connectivity removed?
Can the agent answer from approved business documents without inventing unsupported instructions?
Can spoken, code-switched requests become accurate business actions on-device?
SwaPilot is designed around a short, inspectable path from human intent to a saved business outcome. Connectivity sits outside the core loop.
Updates, encrypted backup, collaboration, and integrations may connect when the user chooses. Core AI and workflows do not depend on that path.
We evaluate the whole workflow, not only model output. A smaller local model is useful only when people can complete real work accurately, safely, and within device limits.
Did the user complete the intended business outcome?
How quickly did useful feedback appear on the device?
Could the workflow run within the target hardware limit?
What did useful intelligence cost the device battery?
Which steps finished without any network dependency?
Was every factual answer supported by approved local knowledge?
A system idea that still needs testing.
A repeatable result from the current prototype environment.
A documented result from a reproducible evaluation.
We will publish concise technical notes as methods and results become reproducible. Until then, every item is clearly labelled by its current stage.
System boundaries, local-first action patterns, and where optional connectivity adds value without becoming a dependency.
A practical model for local retrieval, permissions, provenance, export, deletion, and encrypted synchronization.
From code-switched speech to a structured, reviewable business action on low-cost devices.
We welcome device and chipset partners, research institutions, field programmes, and businesses willing to help define realistic evaluation environments.
Propose a collaboration ↗