Local-first, not local-only
Use the browser and the user's device when they are capable. Connect to remote services when the task genuinely needs them.
Lwati is designed around a simple idea: not every piece of intelligence, computation or source code should have to travel to a remote server before a person can get useful work done.
Use the browser and the user's device when they are capable. Connect to remote services when the task genuinely needs them.
Search, calculation, SQL, tests and scientific runtimes should solve deterministic problems directly. AI is reserved for reasoning and creation.
Source code, research artifacts and assessments should remain exportable and inspectable.
A weak GPU should not make the editor, SQL engine or research workspace useless. Different device classes should get different capability paths.
Local runtimes, cached assets and ordinary deployment targets matter anywhere — and they matter even more where connectivity, hardware and cloud budgets are constrained.
When AI helps create deterministic workflows, those workflows can run later as normal code. More users do not automatically need to mean more model calls.