Why local-first matters for AI assistants
When your AI assistant knows everything about your work, where that data lives matters enormously. Here's why Noet is designed local-first and what that means in practice.
Sources and product references
"Local-first" can describe several architectures, so the useful question is which operations and data stay on the device. Noet stores indexed data in a local SQLite database on the Mac. Retrieval starts locally, while selected context may be sent to configured AI providers for synthesis.
That distinction matters. Local storage can reduce the amount of indexed work data held in a separate cloud search database, but it does not mean every feature is offline. OAuth providers, optional sync and AI requests still have their own data paths. The Security and Privacy pages describe the current boundaries and subprocessors.
Before connecting a work account, review the requested provider scopes and your organisation's policy. Check which feature initiates an external request, which data is selected and whether the action requires confirmation. Local storage is one control, not a substitute for access control, encryption or clear retention rules.
Noet's public security documentation is the source of truth for the product's current design. This article does not claim that local-first architecture alone satisfies a regulated organisation's legal or compliance obligations.
Noet connects your tools into one queryable context layer for macOS.
Join waitlist