Cloudflare R2v1.0.9

Engineering teams use Cloudflare R2 as a zero-egress-fee origin for static websites, SPAs, and media assets. The skill creates buckets per environment, applies CORS policies for frontend domains, and lists bucket contents during deployments. This replaces S3 in cost-sensitive architectures where egress fees dominate.

IT operations scripts use the skill to provision R2 buckets for database dumps, log archives, and cold storage with jurisdiction and storage-class settings. Buckets are created, updated, and eventually deleted programmatically via the oo CLI. This provides durable, low-cost offsite retention without managing raw Cloudflare tokens.

A SaaS platform uses the skill to spin up a dedicated R2 bucket per customer or workspace during onboarding, set per-bucket CORS rules for browser uploads, and tear them down on cancellation. The OOMOL connector handles credential injection so tenant isolation doesn't require embedding Cloudflare API keys in application code.

Media and e-commerce teams manage R2 buckets that back Cloudflare CDN delivery for images and video. The skill lists buckets across accounts, updates default storage class for cost optimization, and configures CORS so web players can fetch assets. Workflows can audit bucket configuration before each release.

Data and ML engineers store training datasets, model checkpoints, and inference artifacts in R2 buckets provisioned through the skill. Buckets with appropriate jurisdiction settings are created per project and CORS policies configured for notebook environments. This keeps artifact storage costs predictable while avoiding direct API token management.

Cloudflare R2 charges for storage and operations but waives egress fees, differentiating it from AWS S3. Customers pay per GB stored and per class of operation, making it attractive for read-heavy workloads. The skill enables automated provisioning and lifecycle management of buckets that generate these usage-based charges.

OOMOL bundles the R2 connector into its automation platform, charging users a subscription or token/credit fee for running actions. The underlying Cloudflare R2 usage is paid separately by the customer's Cloudflare account. Value comes from credential injection, schema discovery, and CLI-driven workflow automation.

Agencies and internal platform teams build deployment, backup, and provisioning pipelines around the skill, selling automation deliverables or charging internal cost-recovery. The R2 buckets themselves generate Cloudflare usage revenue, while the automation layer adds labor or licensing revenue. CORS and bucket policies are codified as reusable infrastructure templates.