SFTP and FTP for Cloudflare R2

No. R2 speaks the S3 API and HTTP, and Cloudflare has no managed SFTP or FTP product — the usual workarounds are a third-party gateway or a VM running sshd that you maintain yourself. DocEvent is the endpoint instead, and files land straight in your own R2 bucket.

Not to Cloudflare - R2 has no egress charge, so a download costs you R2's Class B operation rate and nothing per gigabyte. On the DocEvent side the transfer counts against the data allowance included in your plan; beyond it, additional data is US$10 per 10GB a month (see the pricing page). With S3 the same download is also billed per gigabyte out by AWS, and removing that second bill is the main reason to put SFTP in front of R2 rather than S3.

Object read and write on the bucket you point the service at. Create it under R2 in the Cloudflare dashboard; you get an access key ID and secret to pair with your account's S3 endpoint. Scope it to a single bucket and the endpoint can never see the rest of the account, and revoke or roll it whenever you like.

Yes. DocEvent writes standard R2 objects, so R2 event notifications fire on every upload exactly as if the file had arrived over the S3 API - wire them to a queue and a Worker consumer and each SFTP delivery is processed the moment it lands. No copy step, no polling, and nothing about the pipeline knows or cares that the file came in over SFTP.

Yes. Where an R2 bucket physically lives is a Cloudflare-side setting, and DocEvent connects to whichever endpoint you supply — so jurisdiction restrictions and location hints keep applying exactly as configured.