Cloud Sync

This page explains the tradeoffs between self-hosted and cloud productivity tools inside OpenNapse. It stays intentionally truthful about what is already live, what is staged, and where local-first workflows fit today.

How it works

OpenNapse uses Supabase as its cloud backend foundation. The adapter and bootstrap flow are in place, while full production sync remains staged behind ongoing rollout work.

Cloud Free

OpenNapse Cloud's Free tier currently gives you managed hosting, 10 AI credits per day, and BYOK support. Cross-device sync is still being hardened before general availability.

Self-hosted Supabase

Bring your own Supabase project for full control. Set VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY in your .env and run the migration on startup:

# In your .env VITE_SUPABASE_URL=https://your-project.supabase.co VITE_SUPABASE_ANON_KEY=your-anon-key

Local-only mode

Without Supabase, everything runs in IndexedDB in the browser. Data never leaves your machine. You can export and import your workspace at any time from the Settings panel.

Data portability

Export your entire workspace as JSON from Settings → Data. Import it back into any OpenNapse instance — local, self-hosted, or cloud. There is no vendor lock-in.