Inside Crux: How Local-First Keeps Your Data Yours
A look at the architecture that lets Crux work across your apps while keeping your chats, files, and context on your own machine.
Local-first is not just a tagline for Crux. It is an architectural decision that shapes how the whole product works. Here is what that means in practice.
Where your data lives
Your chats, files, and the context Crux builds about your work stay on your machine by default. There is no central pool of user data, and your history is not used to train shared models.
How Crux still does real work
Acting across your apps does require talking to services like Gmail or Notion. The difference is in what crosses the network and what does not:
- Your accumulated context and history stay local.
- Only the specific request needed for a task touches an external service.
- You stay in control of which integrations are connected.
The trade-off we refuse to make
Many tools treat privacy and capability as opposites. We designed Crux so you do not have to choose. You get an assistant that genuinely helps, without handing your life to the cloud.
Want the deeper story? Read why local-first matters.