Lesson 3 4 min
Local mode, cloud mode and where your data lives
You start in a local workspace with no account, and everything stays in this browser. Here is what changes when you sign in, and what never leaves your device.
The local workspace
After installing, you’re in a local workspace: no account, no login wall, and every workflow, run and credential is saved in this browser, on this device. The sidebar shows Local workspace · Saved on this device. It’s all you need for the whole Foundations track.
When to sign in
Sign in when you want your workflows in the cloud on several devices, or to install and publish workflows on the Marketplace. Installing from the Marketplace needs an account.
When you’re signed in, each workflow and credential can be saved in the cloud or locally. Cloud is the default for new items (Settings › Preferences › Default storage location), and you can still choose each time. The first time you sign in with local work, AWFlow offers to move it to your account; anything you don’t move stays on this device and keeps working.
Where each thing is kept
| What | Where |
|---|---|
| Workflows and their runs | This browser, or your account if you save them to the cloud |
| Credentials | This browser (encrypted), or your account if you save them to the cloud |
| Chats, agents, memory, knowledge bases | This browser only |
| AI providers and their API keys | This browser only |
These always stay on the device, whichever mode you use, even when you’re signed in.
Key takeaways
- The local workspace needs no account and keeps everything in this browser.
- Signing in adds cloud workflows on several devices, and installing and publishing on the Marketplace.
- AI providers, chats, memory and knowledge bases always stay on your device.