How to Choose an infolio Sync Source: Official Cloud, iCloud, or Object Storage
Use a clear decision framework to choose infolio official cloud, iCloud, OSS, S3, R2, COS, GCS, Azure Blob, or TOS for your personal knowledge base.
Quick answer
A sync source is not a checkbox. It is a choice about data boundaries, maintenance work, and cross-device experience. Decide whether simplicity or control matters more first.
Want the least setup? Start with official cloud
If the goal is simply to continue work across devices as soon as possible, official cloud is the most direct choice. It avoids bucket, region, credential, and policy configuration, which is useful when you want to focus on content rather than infrastructure.
That does not make the knowledge hub cloud-first. infolio still works locally; sync connects changes between devices.
Mostly Apple devices? Consider iCloud
If macOS, iPhone, and iPad are your main devices and you already use iCloud Drive, iCloud can be a low-maintenance custom sync route. Confirm every device uses the same Apple Account and has enough system cloud storage before starting.
iCloud is best for personal cross-device flow, not complex permissions or real-time team collaboration.
Already manage cloud resources? Match your object storage
OSS, S3, R2, COS, GCS, Azure Blob, and TOS make sense for people already comfortable with object storage. They keep the sync layer in a familiar cloud account, region, and policy model, while asking you to maintain buckets, credentials, billing, and recovery details.
For any object store, prefer a dedicated bucket or prefix, scoped credentials, and a clear record of recovery steps. Keep sensitive keys in an appropriate encrypted location.
FAQ
Does a custom source make infolio cloud-only?
No. infolio still reads and writes locally first. The source only transports and stores sync data between devices.
Does sync replace backup?
Not completely. Sync connects device state; retain recovery information and an independent backup approach that matches your risk tolerance.