I will deploy debug and cache your site on cloudflare workers and pages


About this gig
Built your site? Get it live, fast and correctly cached. I deploy, debug and speed up sites on Cloudflare Workers and Pages - no stale files, no broken builds.
WHAT I DO
- Deploy React, Next.js, Astro, Vite or static sites to Cloudflare Pages
- Custom domains with automatic SSL
- Caching done right: rules, TTLs, headers, purge-on-deploy
- Debug build and deployment failures from logs
- Write and fix Workers: redirects, auth, rate limiting, geo routing
- Continuous deployment from GitHub or GitLab
HOW IT WORKS
1. Share your repo or build output and what is failing.
2. I deploy to a preview URL first - your live site never goes down.
3. You approve, I flip it live and hand over a runbook.
WHAT YOU GET
- A live URL on your domain with HTTPS, plus preview links
- Cache that invalidates correctly on every deploy
- Clear explanations and logs for everything debugged
- A documented setup so your team can deploy solo
NOT INCLUDED
- Writing your application code, DNS changes outside Cloudflare
FAIR USE
Each package defines the number of deployments, issues and Workers. Need more? We agree before I start.
Message me your build error or repo link - I will tell you what it takes.
Respect third-party rights
Please be aware that it is against Fiverr's policies for sellers to include themes, templates, or any other elements that infringe third-party rights or applicable laws in the delivered work. Read more about in our Guide to Responsible Digital Creation.
Get to know Uttkarsh T.
React Nextjs Astro Developer Drupal Expert AI Automation
- FromIndia
- Member sinceJul 2020
Languages
English
Other Website Maintenance Services I Offer
FAQ
Do I need my own Cloudflare account?
Yes, and the free plan covers Pages, Workers and cache configuration. I can guide you through the setup, or you can add me as a member of the account - you keep full ownership and billing control at all times.
Will my site have downtime during the deployment?
No. I always deploy to a preview URL first, you review it, and only then do I flip it live. DNS changes are batched, tested and cut over with your approval.
Why does my updated site still show old content?
In almost every case it is stale cache. I set up cache rules plus purge-on-deploy so every release appears instantly and predictably - and I can show you how to trigger a purge yourself.
Do you also write the Worker code?
Yes - redirects, rewrites, auth checks, rate limiting and similar utilities are included in the Production Setup package. Larger custom Workers can be quoted as a follow-up order.
