Google PageSpeed Insights - 100% on ibstechnology.com

And in 2026, we discovered Cloudflare. We’d always known it as the best DNS manager with built-in proxy-cache services, but what we really didn’t know about was Cloudflare’s edge infrastructure—that is, operating at the closest point to where the user makes the request.

We started running tests and trying out some very specific tools, like a private dashboard for data visualization (amazing), but all that time we hadn’t dared to set up a website. And we said… why don’t we set up our first website on Cloudflare with our own corporate site? And that’s exactly what we did!!!

THE DEVELOPMENT

One thing we were certain of was that if we made the change, we wanted a website that wasn’t just fast—but hyper-fast—to load, with a modern, appealing design suited to today’s standards, available in two languages, and featuring clear, simple navigation.

We also knew that our team had to consist of code agents to handle the heavy lifting of programming and real people—software architects—to review the entire architecture, content, and design.

We launched Opencode as a platform to work with the code agents; we started with GLM 5.3, but it didn’t run very smoothly and would sometimes “go haywire.” We were able to switch to Claude Code in time, despite the expected increase in cost that this would entail, but we saw that they’d just added Meta’s Muse Spark 1.3, so we jumped right in to program with this new tool—and we have to tell you, it’s performing very, very well.

As a human, I took on the project all by myself—there was no need for more people. I knew exactly what I wanted, how I wanted it, and in what way, so I started pushing my senior programmer hard, making him work to his absolute limit, even outside of regular working hours.

In three afternoons, the website was fully live, but here’s the thing with these projects: when something is for yourself—and you’re the one building it—your standards are sky-high, and you’re never satisfied; you always find something to improve or add.

THE RESULT Spectacular, incredible, amazing... the website loads incredibly fast from anywhere; we've run tests using VPNs from the Americas, Europe, Africa, and Asia, and the website loads incredibly fast from anywhere in the world.

I also think the design is excellent; the developer immediately grasped the design direction I wanted for the site and stayed true to it on every page.

The content is a whole other story—some people will get it, and others won’t. We’ve done a complete 180 and now offer what we know and enjoy doing: developing and orchestrating, with developers, any type of application with infinite scalability and growth.

The result isn’t just empty talk—the ultimate proof is to visit the Google Speed test page and try it out for yourselves....all with a score of 100 and 3/3 in AI Agent compatibility—isn’t that amazing?

What was the cost?

Well, in the end, the ibstechnology.com website is an Edge CMS—an ultra-fast, secure content generator that costs nothing. You heard that right:

• Development cost: ZERO—we used the free tier of Opencode. My time would have been the only cost, but we allocated it as internal work.
• Infrastructure cost: ZERO—we used Cloudflare’s free tier, which is virtually impossible to max out for this kind of project. Even if you did max it out, the next tier costs a mere 5 euros/month to scale up to limits that would cost hundreds or thousands of euros on Amazon AWS or Azure.

HOW DID WE SET IT UP?

Well, by using only and exclusively Cloudflare’s services, we didn’t have to rely on any external services:

• 2 Workers for setting up the DEV and PROD versions. These little guys have no monthly cost; they’re idle, “asleep,” and only wake up when they receive a request. They consume CPU and handle requests—that’s it. I’ll say it again: it’s very hard to use up the free tier of workers because it renews daily, and to exceed it, you’d need a considerable amount of traffic and workload. In other words, for any corporate website—whether for a small business or a large company—Cloudflare’s free tier is sufficient.
• D1 SQL Database: We have 4 tables—no more—and they’re very well optimized. D1 isn’t Oracle or SQL Server, but why would you need anything more than that?
• R2: As a storage source for images, documents, etc. It’s like Amazon S3, with the advantage that it charges very little when you upload a resource and nothing when you retrieve it (GET), unlike S3, which charges for everything.
• 1 KV Worker: These are small units with key-value storage capacity; we use them to handle all page caching.
• Secrets Store: Secure storage for secrets; we store SMTP credentials and a few other pieces of data.
• Turnstile: A security system to protect forms from spam bots—similar to a CAPTCHA—it’s a native Cloudflare tool already used on many sites.
• Security: For now, we’re keeping it set to low; gradually, we’ll increase the settings and block requests from suspicious countries that don’t generate meaningful traffic or business for us.
• Analytics: We’re skipping Google Analytics because Cloudflare provides its own built-in analytics tool.
• AI LLMs: We use agents to generate weekly news; we use OpenAI’s gpt-oss-120b for content generation and flux-1-schnell for image generation. Again, we’d never even come close to exhausting its free tier.

We have an admin panel that lets us manage news and updates, clear the cache, regenerate sitemap.xml, robots.txt, and llms.txt, and view traffic statistics. For now, we don’t need anything else; we’ll gradually add new features while always staying true to our core principle: it’s an ultra-lightweight CMS in terms of components and ultra-fast in execution and loading.

NEXT STEPS

The next step we’re clear on is to gradually reduce our reliance on WordPress and migrate projects from this CMS to our own. This way, we’ll lower the cost of our VPS servers and reduce the constant risk of hacking we face.

We’ll start by tackling one of our other websites and then draw up a tentative migration plan to present to our clients.

CLOUDFLARE'S FREE TIER

Below, to wrap things up, is a detailed summary of the free tier and its limits:

Workers (Serverless Execution)

• Requests: 100,000 requests/day (resets daily at 00:00 UTC).
• CPU time: Up to 30 ms per request.
• Wall-clock time: Unlimited (while the Worker is waiting for I/O responses or fetching data from APIs or databases, it does not consume CPU).
• Script size: Maximum 1 MB (after compilation/minification).
• Number of scripts: Up to 100 Workers per account.
• Memory: 128 MB per execution.
• Subrequests (external fetches): Maximum of 50 outbound fetch calls per incoming request.

Storage and Associated Resources

Workers KV (Key-Value):

- 100,000 reads per day.
- 1,000 writes, deletes, and lists per day.
- 1 GB of total storage.
- Up to 1,000 namespaces per account.

Cloudflare D1 (Serverless SQL Database):

- 5,000,000 rows read per day.
- 100,000 rows written per day.
- 500 MB of total storage on the free tier per database; on the paid tier, this increases to 5 GB.
- Up to 10 databases per account.

Cloudflare R2 (Object Storage / S3-Compatible):

- 10 GB of total storage.
- 1,000,000 Class A operations (writes and updates) per month.
- 10,000,000 Class B operations (reads) per month.
- Bandwidth / Egress: Completely free (€0 per egress transfer).
- Up to 1,000,000 buckets per account (Cloudflare does not impose an artificial bucket limit in the free tier; the product’s overall limit applies equally to both Free and Paid plans).

Vectorize (Vector Database for AI / Embeddings)

- 5,000,000 dimensions queried per month.
- 10,000 stored dimensions.
- Up to 100 indexes per account on the free tier (on the Paid tier, this increases to 50,000 indexes).

At IBS_technology, we continue to work and specialize in the entire Cloudflare infrastructure to offer our clients the best option when it comes to choosing high security and low costs.

David Espí CEO - Business Development