If you have ever opened a plane-mode laptop to a spinning Notion logo, you already know the problem. This guide explains why cloud-first tools struggle offline, what a local-first alternative does differently, and what Bedrock does and does not support today.

Why cloud-first tools break offline

Notion renders pages in your browser but stores every block on its servers. Open a page offline and the app has nothing to render until it reaches the network. Some content is cached, but the cache is a best-effort browser store, not a database you can rely on — edits made offline are limited and sync conflicts are common.

What local-first means in practice

• The database lives on your disk. Bedrock stores your workspace in a local SQLite file. Opening a page is a disk read, not a network round-trip.
• Every action works offline. Documents, tasks, databases, calendar, chat — all of it runs against the local store with no connectivity.
• Encryption is local. Workspace data is AES-256 encrypted at rest on your machine; no account exists to leak.

How to evaluate any offline claim

1. Turn off Wi-Fi before opening the tool. If the app is unusable, the data is not really local.
2. Create a task offline, then reconnect. Watch whether it syncs or duplicates.
3. Ask where the encryption key lives. If the vendor holds it, "encrypted" means encrypted for them too.

Trying Bedrock offline in five minutes

Download the installer, create a workspace, then disconnect. Create a document, add a task with a due date, and open a database view. Everything works because every read and write hits the local SQLite file. Reconnect and nothing changes — the network was never in the path.

For the feature-by-feature version of this argument, see the Bedrock vs Notion vs Obsidian vs Craft comparison.