coreX vs Cloudflare, Akamai, F5, and HAProxy: Which WAAP Belongs on Your Infrastructure?
coreX Platform is a self-hosted control plane, data plane, and web GUI for HAProxy — WAF, security rules, caching, API security, and AI agent governance in one stack you run yourself. Cloudflare, Akamai, Imperva, AWS, and Azure sell a different product: a global edge network. F5 and HAProxy Enterprise sell the same shape of product as coreX — software you operate — with different engines, pricing, and feature depth.
This comparison is written for operators who are shortlisting a self-hosted WAAP (web application and API protection) and want an honest map of where coreX wins, where the clouds still win, and which incumbent it actually replaces.
Product facts for coreX come from the platform itself. Competitor capabilities reflect public documentation as of September 2026. Tiers and pricing change; verify before a purchase decision.
Jump to: The trust-model difference · Feature matrix · F5 and HAProxy Enterprise · MCP / AI agents · Pricing · Verdict · FAQ
What is coreX Platform?
coreX Platform is software you deploy with Docker Compose, Docker Swarm, or Kubernetes/Helm — on-prem, in your cloud VMs, or air-gapped.
It combines:
- A data plane built on HAProxy 3.4, Coraza WAF, Varnish, Valkey, and custom Rust/Lua modules
- A control plane (FastAPI + web GUI) with preview, apply, snapshots, and rollback
- First-class modules for WAF, security rules, API Armor, Page Protect, response transforms, and an MCP Gateway for AI agent traffic
It is not a CDN. It does not give you 300 anycast points of presence. That single fact explains most of the comparison below.
If you want the feature tour first, start at coreX features and the quick start.
The real difference is the trust model
Every other row in a feature matrix is downstream of this table.
| Platform | What it is | Where traffic and config live |
|---|---|---|
| coreX Platform | Self-hosted control plane + data plane (HAProxy + Coraza + Varnish + Valkey) | Your hosts. Docker Compose, Swarm, or Kubernetes. On-prem, cloud VM, or air-gapped. |
| Cloudflare | Global anycast edge + WAAP | SaaS. Traffic proxies through Cloudflare’s 300+ PoPs. |
| Akamai | Global edge + WAAP | SaaS. ~4,000+ PoPs, enterprise-managed. |
| Imperva Cloud WAF | Cloud WAAP + optional on-prem WAF Gateway | Hybrid. Cloud PoPs or a self-managed appliance. |
| AWS CloudFront + AWS WAF | CDN + attachable WAF | AWS edge, ALB, API Gateway, AppSync. |
| Azure WAF / Front Door | Managed rules on Front Door or Application Gateway | Azure edge or regional gateway. |
| F5 Advanced WAF / NGINX App Protect | ADC + WAF appliance or NGINX Plus module | Self-hosted hardware/VE or per-instance software. |
| HAProxy Enterprise + Fusion | Commercial HAProxy + security modules + fleet control plane | Self-hosted instances. Air-gap capable. Optional HAProxy Edge network. |
coreX trades a vendor edge network and vendor-curated threat intel for data sovereignty, no per-request tax, and enterprise-tier features that cloud WAFs usually lock behind the top SKU.
That is the buying question. Not “who has more PoPs?” — you already know the answer — but “do we need those PoPs in the same product that inspects our APIs and agent tools?”
Who this comparison is for
coreX is a fit when you:
- Must keep request bodies, TLS keys, WAF logs, and agent tool payloads on infrastructure you control
- Already run HAProxy (or would, if it had a modern control plane)
- Need Cloudflare-style expression rules, API schema validation, or client-side script inventory without an Enterprise contract
- Want a governed MCP path for AI agents on the same box as the HTTP proxy
- Are tired of per-million-request WAF line items
coreX is the wrong sole product when you:
- Need geo-distributed caching and last-mile latency reduction
- Need unmetered L3/L4 volumetric DDoS absorption
- Want a vendor SOC tuning managed rules against internet-scale telemetry
- Need zero-ops SaaS and will not run a control plane
A common production pattern: Cloudflare or CloudFront in front for absorption and caching, coreX behind it for app-layer depth — WAF, fingerprinting, API Armor, response transforms, and MCP governance.
Feature matrix: coreX vs cloud WAF / CDN platforms
The five cloud platforms below compete on edge. F5 and HAProxy Enterprise compete on deployment model and get their own section.
Core delivery and traffic management
| Capability | coreX | Cloudflare | Akamai | Imperva | AWS CF+WAF | Azure |
|---|---|---|---|---|---|---|
| L7 load balancing | Yes — roundrobin, leastconn, source, uri, static-rr | Add-on (geo-steering) | Yes (GTM / site failover) | Yes | Origin failover | Front Door routing |
| L4 / TCP proxying | Yes | Spectrum (paid) | Yes | Limited | HTTP-only | HTTP-only |
| Global anycast PoPs | No | Yes | Yes | Yes | Yes | Yes |
| Sticky sessions | Yes | No (cookie-less LB) | Yes | Yes | No | Yes (App Gateway) |
| Health checks | Yes | Yes (LB add-on) | Yes | Yes | Origin failover | Yes |
| Origin mTLS | Yes | Yes | Yes | Yes | Yes | Yes |
| FastCGI backends | Yes | No | No | No | No | No |
| QUIC / HTTP/2 / HTTP/3 | Yes | Yes | Yes | Yes | Yes | Yes |
| HA / failover | Keepalived VRRP, stick-table peers, Swarm/K8s, Valkey Sentinel | Inherent to the network | Inherent | Inherent | Inherent | Inherent |
| Authoritative DNS | No | Yes | Yes | Partnership | Route 53 (separate) | Azure DNS |
Takeaway. coreX is a full traffic-management data plane — closer to F5 or HAProxy Enterprise than to Cloudflare. It does work cloud products deliberately skip (L4, sticky sessions, FastCGI). It cannot geo-steer or hide origin latency on its own.
Caching and content optimization
| Capability | coreX | Cloudflare | Akamai | Imperva | AWS CloudFront | Azure Front Door |
|---|---|---|---|---|---|---|
| CDN edge caching | No — origin-side only | Yes | Yes | Yes | Yes | Yes |
| Two-tier cache (memory + disk) | Yes — HAProxy + Varnish | N/A (edge) | N/A | N/A | Origin Shield (partial) | N/A |
| Cache purging | Per-backend + global, BAN-based | API / dashboard | CP Code / APIs | Yes | Invalidations | Purge |
| Brotli / zstd / gzip | Yes — per-backend algorithm | Brotli / gzip at edge | Yes | Yes | Brotli / gzip | Yes |
| On-the-fly image → WebP | Yes — Accept-negotiated, cache-aware | Polish (paid tiers) | Image & Video Manager | No | Lambda@Edge | No |
| Response body transforms / PII | Yes — regex, PII mask + tokenize (Valkey / AES-256-GCM) | Workers (custom code) | EdgeWorkers | No | Lambda@Edge | No |
Takeaway. coreX will not replace a CDN. Origin-side two-tier cache, WebP conversion, and PII tokenization are differentiated — most competitors require custom edge code for the same transforms.
TLS and certificates
| Capability | coreX | Cloudflare | Akamai | Imperva | AWS | Azure |
|---|---|---|---|---|---|---|
| ACME automation | Yes — HTTP-01 + DNS-01, 6+ CAs | Universal SSL | CPS | Auto certs | ACM | Managed certs + Key Vault |
| Custom cert upload | Yes | Business+ | Yes | Yes | Yes | Yes |
| Cipher baselines | FIPS, FedRAMP, PCI, Modern, custom + HSTS | Min TLS version | Yes | Yes | Security policies | TLS policy presets |
| SSL Labs scan integration | Yes (built-in) | No | No | No | No | No |
WAF and application security
| Capability | coreX | Cloudflare | Akamai | Imperva | AWS WAF | Azure WAF |
|---|---|---|---|---|---|---|
| Managed ruleset | OWASP CRS (Coraza) + remote / custom sets + versioned CRS with rollback | Cloudflare Managed + OWASP subset | Kona / Adaptive | Proprietary, low-FP focus | Managed groups (CRS-based) | DRS (CRS-based) + bot ruleset |
| Custom rule language | Cloudflare-parity expressions (visual builder + free text) | Wirefilter | Match criteria UI | Custom rules | JSON rules | Simple match conditions |
| Actions | block, allow, redirect, custom response, CAPTCHA, skip, tarpit / silent-drop | block, challenge, JS challenge, log, skip, redirect | deny, alert, custom | block, challenge | block, allow, count, captcha, challenge | block, allow, log, redirect, JS challenge |
| WAF exceptions | Conditional (ctl:ruleRemoveById / target) | Exclusions / skips | Exceptions | Exceptions | Action overrides | Exclusions |
| Per-rule snapshots / restore | Yes | No (IaC only) | Versioned configs | Policy versions | IaC | No |
| TLS fingerprinting | JA4 lists + req_fp in any rule | JA3/JA4 internal (Bot Mgmt, Enterprise) | Internal | Client classification | JA3 + JA4 match keys | No |
| Rate limiting | Stick-table sliding window, tarpit, per-endpoint, multi-key | Rate limiting rules | Yes | Yes | Rate-based rules | Rate-limit custom rules |
| CAPTCHA | Cap (self-hosted PoW), reCAPTCHA, Turnstile — client-bound tokens | Turnstile / managed challenge | Bot Manager | Yes | CAPTCHA ($/1K) | JS challenge |
| Risk / bot scoring | Expression rules → signed points → risk.score | Bot Management (Enterprise, ML) | Bot Manager Premier | Advanced Bot Protection | Bot / Fraud Control (add-ons) | Basic bot ruleset |
| IP / ASN / Geo / JA4 lists | Named lists + dynamic feeds | IP lists + ASN/geo | Yes | Yes | IP sets, geo, regex sets | IP/geo in custom rules |
Takeaway. The coreX security-rules engine is modeled on Cloudflare’s expression language and ships JA4 and scoring features Cloudflare gates at Enterprise. The gap is ruleset quality: Coraza + CRS is community-maintained. Akamai, Imperva, and Cloudflare tune managed rules against telemetry from millions of sites. Remote rule-set download and CRS snapshots shrink the operational gap. They do not recreate a vendor research team.
API security
| Capability | coreX (API Armor) | Cloudflare (API Shield) | Akamai | Imperva | AWS | Azure |
|---|---|---|---|---|---|---|
| OpenAPI schema validation | Yes — at the proxy | Enterprise only | Yes | Yes | API Gateway (separate) | APIM (separate) |
| GraphQL analysis | Yes — depth, complexity, field / alias / fragment counts | Enterprise only | Yes | Yes | No | No |
| Learned schema inference | Yes — from live traffic | Schema learning (Enterprise) | Yes | Yes | No | No |
| JWT / API-key at the edge | Yes | mTLS + tokens (Enterprise) | Yes | Yes | API Gateway | APIM / Entra |
| Behavioral profiling | Yes — 7-dimensional per-endpoint baselines | API discovery / anomaly (Enterprise) | Yes | Yes | No | No |
| Per-endpoint rate limits | Yes | Yes | Yes | Yes | Per-resource rules | Via APIM |
Takeaway. API Armor is one of coreX’s strongest cards: schema validation, GraphQL analysis, learned schemas, and profiling without an Enterprise SKU or a second product.
Client-side / supply-chain security
| Capability | coreX (Page Protect) | Cloudflare (Page Shield) | Akamai | Imperva | AWS | Azure |
|---|---|---|---|---|---|---|
| CSP monitoring / reporting | Yes | Enterprise only | Client-Side Protection | Client-Side Protection | No | No |
| Script inventory | Yes | Yes | Yes | Yes | No | No |
| Script change detection | Yes — SHA-256 | Yes | Yes | Yes | No | No |
| JS beacon injection | Yes | Yes | Yes | Yes | No | No |
Takeaway. Page Protect lands in the same PCI DSS 4.0 conversation as Page Shield — self-hosted and ungated.
DDoS protection
| Capability | coreX | Cloudflare | Akamai | Imperva | AWS | Azure |
|---|---|---|---|---|---|---|
| L7 DDoS | Rate limits + tarpit + security rules | Unmetered, all plans | Yes | Yes | Rate-based rules | Rate rules |
| L3/L4 volumetric | No — bounded by host bandwidth | Unmetered anycast | Prolexic | Yes | Shield Standard / Advanced | DDoS Basic / Network |
| Anycast absorption | No | Yes | Yes | Yes | Yes | Yes |
Takeaway. This is the structural gap. No self-hosted proxy absorbs a multi-hundred-Gbps flood. Put a scrubbing edge in front if that is a real threat model.
Observability and operations
| Capability | coreX | Cloudflare | Akamai | Imperva | AWS | Azure |
|---|---|---|---|---|---|---|
| Live request logs | Structured JSON + GeoIP, JA4, req_fp, actions | Logpush / Logpull (paid) | DataStream | Yes | Kinesis / WAF logs | Monitor |
| Metrics | HAProxy, WAF, cache, time ranges | Analytics | Control Center | Attack Analytics | CloudWatch | Monitor / Sentinel |
| Log shipping | Vector → S3, Elasticsearch, Datadog, Splunk, New Relic, Azure, HTTP | Logpush | SIEM | SIEM | Kinesis / CloudWatch | Event Hub |
| Config lifecycle | Diff, preview, apply, revert, rollback snapshots | Terraform / API | Property Manager | Policy management | CloudFormation / Terraform | IaC |
| Audit log | Pending-vs-applied tracking | Enterprise | Yes | Yes | CloudTrail | Activity Log |
| Terraform | Export → terraform-provider-corex | Mature provider | Provider | Provider | aws | azurerm |
| RBAC | admin / operator / viewer + JWT + TOTP | Members / roles | Yes | Yes | IAM | Entra ID |
| AI / agent integration | MCP server (~339 tools) + multi-tenant MCP gateway | MCP Portals + AI Gateway | Firewall for AI (model path) | None for agents | Bedrock AgentCore | APIM / Foundry |
Config preview → apply → snapshot → rollback is a control-plane advantage most cloud consoles do not try to match. They expect you to live in Terraform. coreX speaks both.
The real shortlist: F5 and HAProxy Enterprise
Cloudflare is the product people compare in conversation. F5 Advanced WAF / NGINX App Protect and HAProxy Enterprise + Fusion are the products a serious buyer puts on the same RFP, because they share coreX’s deployment model: no mandatory cloud edge, no per-request fee.
coreX vs F5 Advanced WAF / NGINX App Protect
F5’s self-hosted line is two products: BIG-IP Advanced WAF (the legacy market-leading appliance WAF on LTM) and NGINX App Protect (the same signature engine as a module on NGINX Plus). F5 Distributed Cloud is a different class — closer to Cloudflare.
| Dimension | coreX | F5 (AWAF / NGINX App Protect) |
|---|---|---|
| Data plane | HAProxy — L4 TCP + L7 HTTP, 5 algorithms, sticky sessions, FastCGI | BIG-IP LTM (full ADC) or NGINX Plus (L7 + Ingress) |
| WAF engine | Coraza + OWASP CRS + custom / remote sets | Proprietary signatures, positive and negative models, threat campaigns |
| Custom rules | Cloudflare-parity expressions | AWAF policy builder / NAP declarative JSON |
| Programmability | Shipped Rust/Lua filters (compression, WebP, transforms, API Armor) | iRules (TCL) — more general, DIY |
| Fingerprinting | JA4 + req_fp in user rules | Device fingerprinting (internal) |
| API security | API Armor: schema, GraphQL depth/complexity, learned schemas, profiling | OpenAPI enforcement — no GraphQL complexity analysis or behavioral profiling |
| Client-side protection | Page Protect | Client-Side Defense is on Distributed Cloud, not self-hosted AWAF/NAP |
| PII masking | Response transforms — detect, tokenize, encrypt | BIG-IP Data Guard; NAP: no |
| Bot defense | Risk scoring via expressions | AWAF Bot Defense / NAP DoS + signatures (Shape pedigree) |
| Control plane | One GUI + REST + snapshots | TMUI + BIG-IQ; NGINX Instance Manager / NGINX One |
| IaC | Terraform export + provider | AS3 + Terraform |
| AI / agents | MCP server + MCP gateway | F5 AI Gateway (LLM-facing); no MCP tool governance |
| Pricing | Self-host; Apache 2.0 + Commons Clause | Perpetual or subscription + support — among the priciest lines in the market |
F5 wins on detection-engine maturity, hardware / FIPS options, iRules, and a professional-services ecosystem.
coreX wins on a modern integrated control plane, an expression language, exposed fingerprinting, API Armor and Page Protect breadth, the MCP gateway, and cost.
NGINX App Protect in particular is a WAF module plus fleet ops. coreX is a security product surface around a comparable self-hosted proxy.
coreX vs HAProxy Enterprise + Fusion
This is the sharpest comparison in the market. Same engine family.
HAProxy Enterprise (HAPEE) is the commercial HAProxy build plus vendor modules. Fusion is the self-hosted fleet-management control plane. Together with optional HAProxy Edge they form HAProxy One.
| Dimension | coreX | HAProxy Enterprise + Fusion |
|---|---|---|
| Data plane | HAProxy 3.4 + custom Rust/Lua (GeoIP, compression, WebP, transforms, fingerprinting, API Armor) | Same core engine + vendor modules (UDP LB, SAML/OIDC agent) |
| WAF | Coraza SPOA + OWASP CRS — open, auditable | Intelligent WAF Engine — proprietary, Edge-fed intel |
| Bot detection | User-authored risk scoring | Threat Detection Engine — behavioral + reputational, local processing |
| Rate limiting | Stick-tables, tarpit, per-endpoint, multi-key | Global Rate Limiting |
| Control plane | Deep single-platform control of one data plane (plus 2-node HA) | Fleet orchestration across many clusters and teams |
| Rule expressiveness | Full expression language on request / TLS / fingerprint / API fields | Security Profiles + Threat-Response Matrix — curated, less freeform |
| Security surface | Expressions, JA4/network/ASN/geo lists, API Armor, Page Protect, PII masking, CAPTCHA, MCP | WAF + bot module + rate limiting + mTLS — narrower, vendor-supported |
| Edge network | None | Optional HAProxy Edge |
| Air-gap | Yes | Yes |
| Support | Self-supported / community | 24/7 vendor support, certified builds |
| AI / agents | MCP server + MCP gateway | None announced |
coreX wins on integrated feature breadth and price.
HAProxy Enterprise wins on engine quality (threat-intel-fed WAF, real behavioral bot classification), fleet scale, UDP load balancing, an optional global edge, and a support contract.
If you already standardized on HAPEE across fifty clusters, Fusion is the control plane that matches that topology. If you want one rich platform around a single (or HA) data plane — expressions, API Armor, Page Protect, PII, MCP — coreX is the broader product.
AI agent integration: where coreX is most different
Most “AI” slides in this category protect models (prompt injection on the LLM path) or expose a vendor’s own API as tools. coreX ships two components that sit on the agent → tool path, on your network.
1. coreX MCP Server
The coreX MCP Server turns the platform into agent-manageable infrastructure:
- ~339 MCP tools generated from the OpenAPI spec — listeners, backends, WAF, security rules, certs, cache purge, metrics, snapshots, apply / rollback
- Read-only resources (
corex://config/preview, snapshots, HAProxy stats, audit, health) - Workflow prompts: diagnose traffic, security review, add backend, WAF investigation, apply-and-verify
- MCP spec 2025-11-25 over Streamable HTTP, OAuth 2.0 resource metadata, optional bearer auth
- Self-registers into the MCP gateway on startup
An agent can review a WAF hit, propose a conditional exception, preview config, and apply — against the same control plane a human uses in the GUI.
2. coreX MCP Gateway
The gateway is not “our API as MCP.” It is a multi-tenant governance plane for arbitrary upstream MCP servers.
| Area | What it does |
|---|---|
| Multi-tenancy | Teams and membership. Servers, identities, policies, DLP, guardrails, and skills are team-scoped. |
| Upstreams | streamable_http and stdio (local npx / uvx / python servers). TLS verify, timeouts, max body. |
| Upstream auth | None, bearer, custom header, or full OAuth 2.0 client flow with encrypted token storage. |
| Resilience | Circuit breaker, health probes, catalog freshness, replica sets load-balanced through HAProxy. |
| Identities | PAT and JWT, expiry, revocation, last-used, Auth0 sync. |
| Policies | Ordered expressions on method, server, tool, resource, prompt, identity, args, JWT claims, source IP. |
| DLP | Bidirectional scanning of tool payloads: email, phone, SSN, PAN, IP, AWS keys, private keys, GitHub / Slack tokens, custom regex. Actions: block, redact, tokenize. |
| Guardrails | Prompt-injection packs (jailbreak_v1, instruction_override, obfuscation) plus custom regex. |
| Skills registry | Versioned SKILL.md with draft / publish / rollback and enable_when expressions. |
| Marketplace | npm + PyPI search, one-click install as stdio servers. |
| Ops | Session inventory and kill, SSRF checks on upstream URLs, encrypted hot-reloaded config, Vector event log. |
The gateway reuses the HTTP data plane: the same expression language as Security Rules, the same tokenize/redact path as response transforms, the same Valkey store. Agent traffic inherits TLS termination, rate limits, and observability.
What the others ship
| Vendor | Agent-facing product | Covers | Missing vs coreX |
|---|---|---|---|
| Cloudflare | MCP Server Portals (Cloudflare One) + AI Gateway | Aggregated MCP endpoint, Access auth, tool-level least privilege, LLM-provider gateway | No stdio hosting / marketplace, no skills registry, DLP is generic HTTP not MCP-aware tokenize, not self-hosted |
| AWS | Bedrock AgentCore Gateway | MCP aggregation + REST/Lambda/OpenAPI/Smithy → MCP translation, semantic tool search, IAM / 3LO | No MCP-aware DLP or tool-payload guardrails; Bedrock-coupled; per-usage pricing |
| Azure | APIM “AI gateway” patterns + AI Foundry | Front MCP with API policies; Content Safety for prompts | No purpose-built multi-tenant MCP gateway |
| Akamai | Firewall for AI | Prompt injection, DLP, toxicity, hallucination on LLM traffic | Guards the model, not tools/call. No MCP gateway. |
| Imperva | None for agent traffic | WAF explainability, AI-bot classification | No MCP server, no agent gateway |
| F5 | F5 AI Gateway + NGINX One assistant | LLM-facing injection / leakage / cache; ops copilot | No MCP tool governance |
| HAProxy Enterprise | None announced | — | No MCP server, no agent gateway |
coreX leads on self-hosted agent governance, MCP-aware DLP and guardrails, stdio + marketplace + skills, and one control plane for HTTP and agents.
Competitors lead on API→MCP translation and semantic tool search (AgentCore), IdP / MFA / device posture for agent identity (Cloudflare Access), and LLM-provider gateways (Cloudflare AI Gateway, Akamai Firewall for AI). coreX does not inspect model traffic. It inspects tool traffic.
Per-competitor summary
coreX vs Cloudflare — closest product analog
coreX mirrors Cloudflare’s architecture more than anyone else’s: expression language, first-match rules, lists, risk scoring, Page Protect ≈ Page Shield, API Armor ≈ API Shield, MCP gateway ≈ MCP Server Portals.
- coreX: self-hosting, no Enterprise gating on JA4 / schema validation / client-side protection / MCP, L4 + FastCGI, config snapshots, PII tokenization, MCP depth (stdio, skills, tokenize, guardrails).
- Cloudflare: anycast CDN, unmetered L3–L7 DDoS, authoritative DNS, internet-scale ML bot scores, Workers, Zero Trust / SASE, AI Gateway for LLM traffic, a $0 entry price.
Cloudflare is the right edge. coreX is the right origin-side control plane if you refuse to put every rule and every tool payload on someone else’s network.
coreX vs Akamai — premium enterprise edge
Akamai is the heavyweight: PoP count, Kona research-tuned rules, Bot Manager Premier, PCI client-side compliance, API discovery, Prolexic, GTM, Firewall for AI.
- coreX: cost, self-service speed, on-prem without appliances, open CRS, MCP governance (Akamai has none).
- Akamai: delivery, absorption, managed-rule quality, managed operations, LLM-content inspection.
Buy Akamai when the RFP is “global media company, seven-figure security + delivery contract.” Buy coreX when the RFP is “we will run this.”
coreX vs Imperva — closest on hybrid deployment
Imperva is the only cloud WAAP with a serious on-prem WAF Gateway beside Cloud WAF.
- coreX: fully self-hosted platform (not only a WAF appliance), traffic-engineering depth, exposed fingerprinting, config lifecycle, MCP gateway, price.
- Imperva: SOC-tuned proprietary rules, near-zero-FP positioning, Advanced Bot Protection, Attack Analytics, global PoPs + DDoS, hybrid optionality.
coreX vs AWS CloudFront + AWS WAF — composable cloud primitives
Two services you glue together. CloudFront is an excellent CDN. AWS WAF added JA3 (2023) and JA4 match / aggregation keys (2025).
- coreX: one pane, expression language vs JSON rules, API Armor and Page Protect (no AWS edge equivalents), snapshot UX, on-prem MCP governance.
- AWS: pay-as-you-go, Shield, ALB / API Gateway attachment, IAM / CloudTrail / Kinesis, AgentCore’s API→MCP translation and semantic search, CDN↔origin integration.
If the rest of the estate is already AWS-native and you do not care about on-prem, compose CloudFront + WAF. If you want schema validation and agent DLP at the proxy you run, that composition still does not get you there.
coreX vs Azure WAF — thinnest of the five clouds
Azure WAF on Front Door or Application Gateway is CRS-based managed rules, coarse custom matches, rate limits, a JS challenge, and a basic bot ruleset.
- coreX is ahead on rule expressiveness, fingerprinting, API security, client-side protection, and agent governance.
- Azure wins when Entra / Monitor / Sentinel / Key Vault gravity matters more than WAF depth.
coreX vs F5 Advanced WAF — the incumbent appliance
See the table above. Short version: F5’s engine and ecosystem vs coreX’s product breadth and price.
coreX vs HAProxy Enterprise + Fusion — same engine, different product
See the table above. Short version: vendor engines and fleet scale vs integrated feature surface and a self-hosted MCP plane.
Pricing and TCO
| Platform | Commercial model | Entry | At scale |
|---|---|---|---|
| coreX | Apache 2.0 + Commons Clause. Self-host free. You may not sell it as a hosted service without a separate license. | Infra (one VM) | Infra only. No per-request fee. |
| Cloudflare | Free / Pro ~$20 / Business ~$200 / Enterprise custom | $0 | Enterprise security features are custom |
| Akamai | Enterprise contract | $$$$ | Bundled delivery + security |
| Imperva | Subscription per site / bandwidth | Mid | Mid–high |
| AWS | CloudFront per GB/req; WAF $5/ACL + $1/rule + $0.60/1M req + bot add-ons; AgentCore usage | Cheap to start | Linear with traffic |
| Azure | Front Door base + per-GB/req; WAF per policy/rule/million; DDoS Network ~$2.9K/mo | Moderate | Traffic + DDoS sticker shock |
| F5 AWAF / NAP | Per-instance / throughput license + support | High | Very high |
| HAProxy Enterprise | Per-instance subscription (Enterprise + modules + Fusion) | Moderate–high | Scales with instances, not requests |
At sustained high traffic, a flat infra bill is the economic argument. At hobby traffic, Cloudflare Free is unbeatable. coreX is priced like software you run, not like a tax on every GET.
Honest verdict
Where coreX genuinely wins
- Self-hosting, sovereignty, air-gap. None of the five clouds are this product. Imperva’s WAF Gateway is the closest hybrid, and it is not the full platform.
- Ungated enterprise-tier features. JA4 /
req_fp, API schema + GraphQL validation, Page Protect, client-bound CAPTCHA, MCP gateway — included. - Full L4–L7 data plane. TCP proxying, FastCGI, five LB algorithms, sticky sessions, two-tier cache, body transforms and PII tokenization.
- Config lifecycle. Diff, preview, apply, snapshot, rollback.
- AI agent governance. The only self-hosted multi-tenant MCP gateway in this set, with MCP-aware DLP, guardrails, skills, and a marketplace.
- Flat cost at any request volume.
Where it cannot compete (structural)
- No global edge — no geo-latency win, no edge cache, no volumetric DDoS absorption.
- Community WAF rules — Coraza + CRS, not a research team’s managed set.
- No internet-scale ML bot classifier.
- No LLM-traffic product equivalent to Cloudflare AI Gateway or Akamai Firewall for AI.
- No API→MCP translation or semantic tool search (AgentCore).
- You harden the box. The platform holds TLS keys and admin credentials.
How to position it
coreX is not a Cloudflare replacement. It is a self-hosted WAAP and data-plane platform in the gap between “HAProxy plus scripts” and “enterprise WAF appliance.”
The honest shortlist is F5 Advanced WAF / NGINX App Protect and HAProxy Enterprise + Fusion. Against those, coreX competes on integrated breadth, a richer security surface, and price. They compete on detection-engine maturity, fleet orchestration, and a support contract.
Against the clouds, feature-for-feature it reaches much of Cloudflare’s Enterprise tier on the app-layer side — and it is the only product here that treats AI agent traffic as a first-class governed data plane on infrastructure you own.
Suggested architecture: edge CDN / scrubbing tier in front, coreX on the origin side for everything the edge will not do — or cannot do without reading the bodies you do not want to send it.
FAQ: coreX vs Cloudflare and other WAAPs
Is coreX a Cloudflare alternative?
For WAF rules, API security, client-side script inventory, and expression-driven policy: yes, especially if those features are locked behind Cloudflare Enterprise. For CDN, authoritative DNS, and volumetric DDoS: no. Many teams run both.
Is coreX open source?
The project is licensed Apache 2.0 with the Commons Clause. You can use, modify, and self-host it. You cannot sell it — including as a paid hosted service — without a separate license. See the coreX repository.
Does coreX replace a CDN?
No. Caching in coreX is origin-side (HAProxy memory + Varnish disk). Use Cloudflare, CloudFront, Akamai, or Fastly in front when users are global.
How does coreX compare to HAProxy Enterprise?
Same data-plane family. HAProxy Enterprise adds vendor WAF / bot engines, Fusion fleet management, optional Edge, and paid support. coreX adds a deeper single-platform security surface (expressions, API Armor, Page Protect, PII transforms, MCP gateway) and snapshot-based config workflow around one data plane.
How does coreX compare to F5 Advanced WAF?
F5 still leads on proprietary detection and the ADC ecosystem. coreX leads on a modern control plane, Cloudflare-style expressions, API and client-side modules, MCP governance, and cost. NGINX App Protect is a strong WAF module; it is not a full WAAP control plane of the same scope.
Can coreX stop a volumetric DDoS attack?
Not beyond the bandwidth of the hosts it runs on. Rate limits, tarpit, and security rules handle application-layer abuse. For L3/L4 floods, put Cloudflare, AWS Shield, Akamai Prolexic, or an equivalent scrubbing service in front.
What is the coreX MCP Gateway?
A self-hosted, multi-tenant proxy in front of MCP servers. It adds team-scoped policy, DLP, prompt-injection guardrails, identities, rate limits, a skills registry, and a package marketplace — and it reuses the same expression language and tokenize path as the HTTP data plane. Details live in the coreX docs.
Does coreX work air-gapped?
Yes. Deploy with Docker Compose, Swarm, or Helm. ACME DNS-01 and remote rule feeds need connectivity if you use them; the data plane does not require a vendor cloud.
Where should I start?
Install from the quick start, skim features, then turn on WAF + one security-rules list on a non-production listener. Add API Armor and the MCP gateway after the first snapshot you trust.
Sources and methodology
- coreX: verified against the platform codebase github.com/ne4u/corex_manager.
- Competitors: public product documentation as of September 2026, including Cloudflare MCP Server Portals and AI Gateway, AWS Bedrock AgentCore Gateway, AWS WAF JA3/JA4 announcements, Akamai Firewall for AI, Imperva Cloud WAF, Azure Front Door WAF, F5 ADSP / AI Gateway and NGINX App Protect, and HAProxy Enterprise / Fusion.
coreX Platform — Correct What Matters. One proxy. Multiple directions. Zero blind spots.