When we were setting up Digital Creative Alliances, one of the first real decisions we had to make was which platform to specialise in. Not which one we liked best, but which one we were willing to bet the whole agency on. Because that is essentially what the choice is.
It would shape how every client site is built, maintained, and handed over. It would affect our workload, our reliability, and whether clients could actually manage their own content without calling us every week. And yes, it would determine the environmental footprint of every site we launch.
We chose OPTe. Here is the honest version of why.
The WordPress Problem Nobody Talks About
We like WordPress. It runs 43.5% of the web, which tells you something about how useful it is. But traditional WordPress hosting has problems that most agencies quietly absorb as part of the job.
Security updates land every few weeks. Miss one and you are vulnerable. Plugins conflict with each other and break things without warning. Sites slow down as they grow. And clients become afraid to touch anything, which means they end up calling you for changes they should be able to make themselves.
There is also something less obvious. Every traditional WordPress site runs as a separate installation on its own server resources. Separate copies of the same core files, same themes, same plugins, all running independently across millions of sites globally. That is a lot of redundant computation and storage that nobody really needs.
What We Looked at Before Deciding
We evaluated the main options properly before committing.
Webflow has a genuinely good editing experience. But your content lives inside their ecosystem, and if they change their pricing or shut down a feature, you have limited options. That felt like too much risk to pass to clients.
Wix and Squarespace work fine for simple sites. They stop working fine the moment a client needs something custom.
Headless CMS setups like Contentful or Strapi are technically interesting but client-hostile in practice. Basic content edits require ongoing technical support. That is not a relationship model we want to build.
Standard WordPress was the devil we knew. Powerful, flexible, and carrying all the maintenance overhead described above.
None of them balanced what we were actually looking for: clients who can manage their own sites, infrastructure that does not create constant maintenance work, and a build process that does not generate waste by default.
What OPTe Actually Is
OPTe runs WordPress as a centralised multisite application. Instead of thousands of separate installations, sites share a single optimised WordPress core, consolidated plugin and theme libraries, a unified security and maintenance layer, and centralised media management with automatic optimisation.
In practical terms this means a few things for our clients.
Editing without fear. The visual builder works the way Elementor or Bricks Builder should work. Clients can update content without breaking layouts and without needing to understand WordPress internals.
Security without babysitting. Updates and patches happen at the platform level. Clients do not need to worry about plugin vulnerabilities and we do not need to run security checks manually every week.
Actual ownership. Clients can manage their own content without technical knowledge. We are there when they need us, not because the platform requires us to be.
Speed by default. Cloudflare CDN integration, automatic image optimisation, and built-in caching are part of the infrastructure, not add-ons we configure per project.
The Environmental Side
This is where it gets interesting, and where I want to be careful not to overstate things.
The architectural efficiency of OPTe is real. One shared WordPress core instead of millions of separate copies does mean less redundant storage, less duplicate computation, and lower energy requirements per site. That is not a marketing claim, it is just how the maths works when you consolidate.
OPTe partners with AWS, Microsoft Azure, and Cloudflare for infrastructure. AWS has committed to 100% renewable energy. Azure has committed to carbon negative by 2030, with a stated goal to remove all historical emissions by 2050. Cloudflare has run carbon-neutral since 2018. These are public commitments with third-party verification. They are also commitments, not outcomes, which is worth keeping in mind.
We are not claiming that building your website with us saves the planet. We are saying the infrastructure choices we make have a measurably lower footprint than the default, and we think that is worth choosing when the technical case is equally strong. Which it is.
Who This is For
DCA makes sense if you want a website that actually drives business results, you want to manage your own content without needing a developer for routine updates, and you care at least a little about how your digital infrastructure is built.
It probably does not make sense if you need the cheapest option in the market, you need something live in a week, or you just want a vendor to hand a brief to. We would rather work with fewer clients and do better work than scale quickly by cutting corners on both.
Being Transparent About Where We Are
We launched in 2025. We do not have years of proof behind these decisions yet. What we have is a clear rationale, a platform we believe in technically, and a commitment to report back honestly on what actually worked.
We are documenting the first six months publicly. Month three: first client case studies with measurable outcomes. Month six: a full transparency report covering how many clients we served, what the environmental data looked like, what we got wrong, and what we would change.
If you are building in Cambodia or Southeast Asia and this approach sounds right for your project, get in touch. We are happy to talk through it.
Digital Creative Alliances is a web design agency based in Siem Reap, Cambodia, and Cambodia’s first OPTe-certified partner. See our work or read our transparent pricing.
Table of Contents
Request a Free Proposal
Request a call to discuss your business & project details!
