BYOC Configuration

BYOC (Bring Your Own Cloud) lets you store sync data in your own cloud infrastructure for stronger control over data residency and compliance.

Supported options

Option	Typical implementation	Best for
WebDAV	Self-hosted WebDAV or third-party WebDAV service	Fast onboarding with lower ops complexity
S3-compatible storage	S3, MinIO, or object storage services	Scalable setups with fine-grained IAM

Core fields

Field	Type	Required	Description
`provider`	`string`	Yes	Backend type, such as `webdav` or `s3`
`endpoint`	`string`	Yes	Service endpoint URL
`bucket`	`string`	No	Target bucket/container (S3 flows)
`username`	`string`	No	Account or access key identifier
`password`	`string`	No	Password or secret key
`pathPrefix`	`string`	No	Namespace prefix for sync objects

Setup flow

Prepare credentials and permissions

Confirm endpoint reachability and read/write policy readiness.

Fill BYOC fields in app settings

Enter required parameters based on your provider.

Run connection test

Verify test object read/write before enabling production sync.

Example

byoc.config.jsonjson

{  "provider": "s3",  "endpoint": "https://s3.example.com",  "bucket": "octoclip-sync",  "pathPrefix": "prod/user-a/",  "username": "ACCESS_KEY",  "password": "SECRET_KEY"}

WARNING

Never commit credential-bearing config files to public repositories. Prefer environment variables or secret managers.

Common issues

Cloud Sync

Understand where BYOC fits in the sync pipeline.

Privacy and Security

Apply stronger handling for secrets and sensitive clips.

Was this page helpful?