CodeHawkeYour files stay in your bucket. Not ours.
On the Business plan, connect your Cloudflare R2 or AWS S3 bucket. CodeHawke handles buyer entitlement checking and signed delivery, and your files stay in your infrastructure. No re-uploading if you ever change platforms.
Platform-hosted files create dependency risk.
When your product files live on a platform’s servers, you can’t move without re-uploading everything, and storage limits and pricing changes are outside your control. BYOB means your asset infrastructure is portable — CodeHawke just controls the access layer.
Connect your bucket
Link a Cloudflare R2 or AWS S3 bucket. Files stay in your infrastructure, not on CodeHawke servers.
Signed delivery URLs
CodeHawke generates time-limited, buyer-specific signed URLs at fulfillment time. The bucket itself stays private.
Access control from purchase
Only buyers with valid orders get delivery URLs. Refunded orders stop generating new signed links.
Downloads on the order
Each order counts its downloads, so support can see whether the buyer got the file.
Upload from the dashboard
Upload a product file as usual. With your bucket connected, it goes straight into your bucket under the prefix you choose.
No vendor lock-in
Your files stay on your infrastructure. Switching platforms or storage providers does not require re-uploading assets.
Connect once. Signed delivery for every buyer.
The storage connection is configured once per account. After that you upload product files as usual, and they land in your bucket. Buyers never interact with your bucket directly.
Your infrastructure. Our access layer.
Keep files in your R2 or S3 bucket. Let CodeHawke handle buyer entitlement checking and signed URLs.
Try CodeHawke