Using the company Cloudflare account for internal workflows
The goal is to use the company's Cloudflare account to support internal workflows. The first focus is uploading and previewing/reviewing evidence; we expand only if there is a need.
1Goals & scope
- Use resources already available on the company Cloudflare account: R2, Pages, Workers.
- Provide one place to store, share and preview evidence: automation test reports, screenshots, logs, documents, HTML reports.
- Cut setup time for internal tooling, and stop requesting access to client resources for needs that don't really require it.
- Pilot with a few developers and one project first, not company-wide.
2Planned resources
R2 — Storage
- Test reports, screenshots, videos, artifacts
- Documents, logs, review files
- Files larger than the 25 MiB Pages limit
Object storage with a free tier and free egress.
Pages — Hosting & preview
- Playwright HTML reports
- Automation test result dashboard
- Evidence index by project/build/run
Cloudflare Access — Security
- Sits in front of Pages; only people signed in with the company Google Workspace can view
- Zero Trust Free: up to 50 users
Workers — API (optional)
- Upload/list API, signed URLs, permission checks
- CI/CD integration to upload artifacts automatically
Probably not needed in the first phase.
3Rollout plan
Phase 1 — POC (~1 week)
- Only 1–2 people need dashboard access; no Admin role by default. CI uses an R2 API token scoped to a single bucket.
- Create one R2 bucket for internal evidence and one Pages project for report previews.
- Enable Cloudflare Access on Pages; no public bucket.
- Try uploading manually or from one automation pipeline.
- Test the full flow: upload → store → preview/review → delete.
Deliverable: a working POC on one project, with a usage guide and the actual cost.
Phase 2 — Workflow integration (1–2 weeks, depending on scope)
- CI/CD uploads reports automatically after each automation run.
- Shareable evidence links for team members.
- Add Workers if upload handling, metadata or access control needs it.
- Retention policy: delete old evidence automatically after 7–30 days.
- Track storage, request volume and cost.
Phase 3 — Review & expand
After 2–4 weeks of real use, review usefulness, time saved, storage and traffic, actual cost, and whether to expand to other workflows.
4Expected cost
Start on the Free plan, with no paid plan commitment.
- R2: free 10 GB-month, 1M Class A and 10M Class B requests per month. Beyond that: $0.015/GB-month, Class A $4.50/million, Class B $0.36/million. Egress is free.
- Pages: Free, $0. Limits: 500 builds/month, 25 MiB per file.
- Access: Zero Trust Free, $0, up to 50 users.
- Workers: Free tier 100,000 requests/day, 10 ms CPU/request. Workers Paid starts at $5/month per account.
| Average R2 storage | Storage cost/month |
|---|---|
| 5 GB | $0 |
| 10 GB | $0 |
| 50 GB | ≈ $0.60 |
| 100 GB | ≈ $1.35 |
Storage only, assuming requests stay within the free tier.
5Pros
- Uses existing infrastructure, so less setup time.
- Low starting cost; we can try it without buying anything.
- Easy to integrate with CI/CD and automation testing.
- The team can share, preview and review evidence on its own.
- Reusable across projects and internal workflows.
6Cons & risks
- Initial time needed for setup, permissions and integration.
- Storage, retention and usage must be managed to avoid unexpected cost.
- No public buckets or reports containing sensitive data.
- No client data, credentials or tokens uploaded without approval under the relevant policy.
- The account is shared, so access, ownership and handover must be clearly defined.
7Compared with Cloudflare Tunnel
Cloudflare Tunnel (already used to serve reports to the team) is quick and free, but needs a machine running all the time and keeps no history. R2 + Pages keeps evidence per run and doesn't depend on anyone's machine. Both can be used side by side depending on the need.