Cloudflare Website Development and Hosting

Cloudflare Pages has a free tier that covers unlimited requests and unlimited bandwidth for static sites, with a monthly cap on builds. Most of the websites LGTCS delivers run inside that free tier indefinitely. Costs only appear when you add R2 storage, D1 database usage, or build volume beyond the free allowance, and those are metered at Cloudflare's published rates on your own account, so there is no markup from LGTCS and nothing is resold through us. If you want a number before you commit, tell LGTCS roughly how much traffic and media you expect and we will estimate the monthly running cost for you.

LGTCS deploys to Cloudflare Pages today. Cloudflare has said that new development is now focused on Workers, which can serve static assets and handle dynamic routes in a single deployment, and that Pages remains fully supported. For a statically exported site the two are functionally equivalent right now, and because our builds are plain static files the move to Workers is a deployment configuration change rather than a rewrite. We will make that move when there is a reason to, not because of a headline.

R2 is Cloudflare's object storage, built for large files such as images, PDFs, and video. Databases are built for structured records and become slow and expensive when used as file cabinets. LGTCS keeps media in R2 and keeps only the records about that media in the database, which keeps pages fast and, because R2 charges nothing for data transferred out, keeps your bill flat as the library grows. If you are carrying a large media archive today, ask LGTCS to review it and we will tell you what moving it to R2 would cost to run.

D1 is a real SQL database, generally available since 2024, and it runs at the edge so queries happen close to the visitor rather than in one distant data centre. It is sized for organisational websites, portals, and applications rather than enterprise analytics workloads. For the scale of site LGTCS builds, it is the right tool. If your project genuinely needs something larger, LGTCS will say so and integrate a different database instead of forcing the fit. Describe what your data has to do and we will tell you which one your project actually needs.

Yes, the Cloudflare account is yours. LGTCS creates it under your organisation with your own billing details and is added as a collaborator, rather than holding the account ourselves and billing you through it. You can remove LGTCS access at any point and the site keeps running, because nothing about the setup depends on us being in the account. Ask LGTCS to walk you through the account before handover and you will see exactly what is in it.

Your site would be affected, and LGTCS would rather say that plainly than pretend otherwise. Putting hosting, storage, database, and form protection with one provider concentrates the risk with that provider. What limits the damage is that the site is a folder of static files in your own GitHub repository, so it can be redeployed to another host in minutes if it ever came to that. That is a large part of why LGTCS builds this way rather than into a platform you could not leave. If continuity is a board-level concern for you, ask LGTCS to document the failover route as part of your handover.

Usually yes, and migrating existing websites onto Cloudflare is one of the things LGTCS specialises in. What it involves depends on what your site is built on. A static or Next.js site moves across straightforwardly, often with no visible change other than the speed. A WordPress site has two sensible paths: put it behind Cloudflare for speed and protection while leaving it where it is, or rebuild it properly as a static site so the hosting cost and the security exposure both largely disappear. Send LGTCS your current web address and we will tell you which of the two makes sense for your site, what it would cost, and what you would save each month afterwards. We will also help you figure out the domain and DNS side, which is the part most people expect to be difficult.