Local-first does not mean “no cloud”
How DraPub Universal Client separates workspace storage, online sync, and agent execution into independent choices.
“Local-first” is often reduced to offline software or self-hosting. What shapes trust is whether a system clearly answers three different questions: where data is stored, where the interface runs, and where an agent executes.
Workspace chooses data location
Online workspaces live in DraPub Cloud and support Web, teams, and multi-device sync. Local workspaces stay in Universal Client SQLite, start without a network, and do not upload because a user signed in.
Agent execution is another choice
A local workspace can use a device runtime. An online workspace can send work to local Codex, Claude Code, or Qoder. With explicit authorization, a local workspace may use cloud model capability. Storage and execution do not need to be coupled.
Phones and desktops have different capabilities
Tauri lets one product interface run across platforms. It does not mean every platform can run the same sidecar. Desktops can host a local runtime; initial mobile clients use cloud agents while preserving local app data and explicit sync boundaries.
Local-first is not anti-cloud. It makes every cross-device and cross-boundary data movement visible, explainable, and optional.
