Skip to content
infolio infolio
Sync setup guide 6 min read Updated 2026-07-15

How to Use Cloudflare R2 to Sync an infolio Knowledge Base

Prepare Cloudflare R2 as an infolio custom sync source: bucket, S3 API endpoint, Access Key, Secret Access Key, region auto, permissions, and recovery checks.

Quick answer

Cloudflare R2 fits users who already use Cloudflare or want S3-compatible object storage for knowledge-base sync. The key fields are bucket, Account ID, S3 API endpoint, Access Key, Secret Access Key, and region auto.

Steps

1

Create a dedicated R2 bucket

Create a separate R2 bucket for infolio instead of mixing sync data with website assets, archives, or other apps. A dedicated bucket makes permissions, billing, and troubleshooting clearer.

  • Use a bucket name that identifies the purpose without exposing private data.
  • Do not mix several apps in the same prefix.
  • Record the Cloudflare Account ID and bucket name.
2

Prepare S3 API connection fields

R2 supports an S3-compatible API. A sync configuration usually needs endpoint, bucket, Access Key ID, Secret Access Key, and region. Cloudflare documents the S3 region for R2 as auto; empty value or us-east-1 can alias to auto for tools that do not allow auto.

  • Copy the endpoint from the Cloudflare R2 dashboard.
  • Use auto for region unless the product asks differently.
  • Do not store R2 credentials in ordinary notes or public screenshots.
3

Create a least-necessary R2 token

Generate a dedicated R2 API token or S3-compatible access key for infolio. Avoid reusing broad Cloudflare account credentials, and scope access to the infolio bucket where possible.

  • Save the Access Key ID and Secret Access Key securely.
  • Add a note for purpose and creation date.
  • Disable this dedicated credential if you stop using the sync source.
4

Configure the custom sync source in infolio

Enter the R2 endpoint, bucket, region, and credentials in infolio custom sync settings. Recheck bucket and endpoint before saving so data is not written to the wrong account or bucket.

  • Confirm the network can reach the R2 endpoint.
  • Test with a small non-critical knowledge base first.
  • If you see 403 errors, check token permissions and bucket scope.
5

Verify recovery on a second device

A successful first sync does not prove recovery. Connect another device to the same R2 sync source and confirm documents, workspaces, whiteboards, and vaults recover as expected.

  • Confirm normal documents and whiteboards recover.
  • Confirm vault access and device authentication work.
  • Review R2 usage and unusual requests periodically.

Related pages

Cloudflare R2 sync source See when R2 makes sense for infolio sync. S3 and R2 sync topic Understand object storage sync tradeoffs. Choose sync strategy Compare official cloud, iCloud, OSS, S3, and R2.

FAQ

What region should I use for Cloudflare R2?

Cloudflare documents the R2 S3 API region as auto. Empty value or us-east-1 can alias to auto for some tools, but follow the product prompt when configuring infolio.

Does R2 sync mean infolio is self-hosted?

No. R2 is a custom sync storage layer. infolio remains a local-first app, not a self-hosted web service.