How to Choose a Local-First Sync Strategy for infolio
Choose between infolio official cloud, iCloud, OSS, AWS S3, Cloudflare R2, and other sync sources based on devices, privacy boundaries, maintenance effort, and recovery.
Quick answer
There is no universally best sync source. Official cloud is simpler; custom sync fits users with object storage experience and clearer data-boundary needs.
Steps
Identify the devices that need sync
List the devices you will actually use: phone for capture, desktop for organization, tablet for reading, or just one computer. More devices increase the need for reliable sync and recovery.
- List primary and backup devices.
- Separate read-only devices from editing devices.
- Confirm whether you need cross-platform use.
Decide whether you want to maintain cloud resources
The official cloud reduces setup work. Custom sync requires you to manage access keys, buckets, permissions, and billing. Do not choose a path you cannot maintain.
- Choose official cloud if you do not want to manage keys and buckets.
- Consider custom sync if you already know object storage.
- Store credentials safely instead of scattering them in ordinary notes.
Pick a sync source that matches your ecosystem
Apple users can evaluate iCloud. Users with domestic cloud accounts can consider OSS, COS, or TOS. Developers and international-cloud users can evaluate S3, Cloudflare R2, Google Cloud Storage, or Azure Blob.
- Prefer a cloud provider you already trust and expect to keep using.
- Use a dedicated bucket or directory for infolio.
- Avoid reusing high-permission root credentials.
Put sensitive records in vaults before syncing
The sync source should move data, not become plaintext private-record storage. Passwords, IDs, API keys, and private documents should go into infolio encrypted vaults before sync.
- Move sensitive records out of ordinary documents.
- Confirm device authentication is available.
- Do not keep sync credentials in ordinary pages.
Verify recovery on another device
Sync matters because recovery matters. After configuration, use another device to sign in and recover the knowledge base. Confirm documents, workspaces, whiteboards, and vaults behave as expected.
- Record the sync source type and credential location.
- Confirm that a new device can recover core data.
- Check sync errors and storage usage periodically.
Related pages
FAQ
Can I sync without understanding object storage?
Yes. The official cloud is the simpler option. S3, R2, OSS, and other custom sources are advanced options.
Is a custom sync source automatically safer?
No. It gives more control, but safety still depends on credentials, permissions, devices, and backups. Sensitive content should still live in encrypted vaults.