--- title: "We run the platforms. We are not the platforms." description: "Configuration is going self-serve. Judgment is not." canonical_url: https://optimi.com/en/news/we-run-the-platforms-we-are-not-the-platforms md_url: https://optimi.com/en/news/we-run-the-platforms-we-are-not-the-platforms.md last_updated: 2026-09-29 --- # We run the platforms. We are not the platforms. Configuration is going self-serve. Judgment is not. --- This autumn a CTO will ask, without heat: “Why still a managed partner, now that bot management, WAF tuning, and AI controls live directly in the console?” The question is fair. Edge providers really did make some things easier. We concede that. Then we say what did not get easier. --- ## What the consoles just made simpler Over the past year, major edge and infrastructure providers (such as Cloudflare and Fastly, among others) have shipped dozens of sophisticated classification knobs. Enterprise bot management, AI gateways in front of models, granular bot preference sync aligning `robots.txt` with active enforcement, and post-cache WAF rules are now standard capabilities in modern web consoles. Writing an allow, a challenge, or a block in a single modern console is simpler than it was three years ago. For a team with time, skill, and a single provider, self-serve configuration is real. We do not dispute that. We have no network to protect. --- ## Configuration is going self-serve. Judgment is not. A richer enterprise plan adds features. It does not add the people who operate them. Provider features reward engineering investment, including custom VCL, complex edge rules, and false-positive mitigation. But every console still requires someone to decide when to allow, challenge, or block when SEO, product, and security disagree. Someone needs to be there when a rule that looked clean in staging meets peak traffic. Someone who is still there in five years, when vendors have shipped three more control layers. That is the layer nobody owns. Toggles do not close it; they widen it. Self-serve fails at a precise point: policy crosses consoles. A bot score in one dashboard, a WAF signal in another, a rate limit, a `robots.txt` file, a sitemap, an SEO analytics console. DIY means six separate owners. Or a single DevOps generalist on a Friday evening. --- ## We have no CDN to push No house network, no exclusive WAF, no partnership that dictates our recommendations. Providers are supply. Neutrality is the job, not a slide slogan. We do not dunk on edge providers. Whether you rely on Cloudflare, Fastly, or a hybrid multi-provider architecture among others, a vendor comparison matrix is the opposite of what we sell. You keep your providers. We run them. --- ## Partners, not rivals When platforms (whether Cloudflare, Fastly, or others) extend their capabilities into AI security and model gateways, we operate them: managing keys, routing policies, edge rules, and un-sampled logs, rather than leaving a lean engineering team to staff yet another console. We do not build a proprietary model gateway. We trap no one in a closed CDN fabric. The durable job is not basic configuration, which providers are rapidly industrializing. It is judgment, multi-vendor neutrality, and operational accountability. "We are an operational partner, not a software SKU" is the direct answer to "We'll buy enterprise consoles and run them ourselves." You can buy enterprise licences and run them yourselves. Some teams do. Others write custom VCL and WAF rules in-house. The question is not the licence. It is whether you will hold bot, WAF, crawler, and agent policy ownership without a dedicated owner, especially this autumn, when budgets are voted and peak season approaches. --- ## What we are asking Not to switch providers for sport. To review who owns bot and WAF policy *today*: which console, which rule, which engineer at 2 a.m., which exception after an SEO false positive. If the answer fits a clean architecture diagram, keep it. If it fits three tickets that never meet, a non-human traffic audit is the right first move, evaluating the stack you already pay for (Cloudflare, Fastly, or any combination), without adding new software SKUs. **We run the platforms, whether Cloudflare, Fastly, or any of your chosen providers. We are not the platforms. The rest of the autumn is that sentence, applied to bots, then crawlers, then agents.** --- **Review bot / WAF ownership, not the provider** A non-human traffic read to see who decides allow, challenge, or block on the infrastructure you already have. [Request an operational read](/en/contact) *Operating at the Edge since 2014 as a partner in your performance and digital resilience. Faster, safer, more visible.*