What WEDOS Users Actually Say, and What We'd Do Differently

Back to Blog

We sell Flowtriq, a per-node DDoS detection platform for ISPs, hosting providers, and infrastructure operators. WEDOS is a Czech hosting provider that includes DDoS protection as part of its hosting services. This post is less of a direct competitor comparison and more of an analysis of what users say about WEDOS's protection model and how infrastructure-level detection differs from provider-bundled protection.

Understanding the market difference

WEDOS is primarily a webhosting company serving customers in the Czech Republic and Slovakia. They build and operate their own DDoS protection infrastructure for their hosted customers. Flowtriq sells DDoS detection tools to ISPs and hosting providers who operate their own infrastructure.

These are fundamentally different markets. WEDOS is a hosting provider that includes protection. Flowtriq is a detection platform that hosting providers deploy. The comparison is useful for operators evaluating whether to rely on their hosting provider's bundled protection or run independent detection on their own infrastructure.

Support and response times

Support quality is the most common complaint WEDOS users raise across review platforms.

"Support is slow. Tickets take days to get a response. When you're having an issue with your site being down, waiting 48 hours for a reply is not acceptable."

"[This provider's] support has gotten worse over time. It used to be responsive, but now it feels like tickets go into a queue that nobody watches."

"Downtimes happen and the communication about them is poor. You find out your site is down from your own monitoring, not from [the provider]."

When your DDoS protection is bundled with your hosting provider, the quality of that protection is tied to the provider's support capacity. If the provider is slow to respond, your DDoS protection is slow to respond. With independent detection like Flowtriq, mitigation triggers automatically regardless of any provider's support queue. The system does not wait for a human to acknowledge a ticket before taking action.

Blocking legitimate traffic

Several users report that WEDOS's protection is overly aggressive, blocking traffic that should be allowed through.

"[This provider's] DDoS protection blocks legitimate traffic. Customers from certain countries cannot access our site because the filtering is too aggressive. We lost real business because of false positives."

"The protection seems to use geo-based filtering. If your audience is international, you will have visitors getting blocked for no reason."

Aggressive filtering that blocks legitimate traffic is a common trade-off in provider-bundled DDoS protection. The provider optimizes for their entire customer base, not for any individual customer's traffic profile. A geo-blocking rule that makes sense for most Czech-focused websites hurts customers with international audiences.

Flowtriq uses per-server dynamic baselines that learn each server's specific traffic patterns. A server that legitimately receives traffic from Southeast Asia has different thresholds than a server that only serves European customers. The baselines adapt to each server individually, which reduces the false positive problem that comes from one-size-fits-all filtering rules.

WordPress plugin issues

"[This provider's] WordPress plugin broke my admin panel. After installing it, I could not access wp-admin. It took me hours to figure out the plugin was the cause."

"The WordPress security plugin they recommend is poorly maintained. It conflicts with other plugins and has not been updated in months."

Flowtriq operates at the infrastructure level, not the application level. There are no WordPress plugins, no CMS integrations, and no application-layer components that can conflict with your site's software. The agent runs at the kernel level on the server, completely independent of whatever application stack you are running.

Manual emergency response

"During a serious attack, [this provider] told us to use Grafana to monitor the situation. That requires knowing how to use Grafana, setting it up, and watching dashboards manually. That is not DDoS protection, that is DIY monitoring."

Telling customers to monitor Grafana dashboards during an active attack puts the response burden on the customer rather than on the detection system. Effective DDoS protection should respond automatically, not require the customer to learn a monitoring tool during an emergency.

Flowtriq's detection and mitigation pipeline is fully automated. When an attack is detected, mitigation actions fire, alerts go out to the channels you configured, and incident documentation is generated. The dashboard exists for review and investigation, not as a tool customers need to learn under pressure during their first attack.

Geographic and market limitations

"[This provider] is great if you are in the Czech Republic. If you need hosting with DDoS protection for an international audience, the infrastructure is not designed for global reach."

"Support is Czech-first. English support exists but is clearly secondary. If you are not a Czech customer, you feel like an afterthought."

WEDOS built their business serving the Czech and Slovak market. That focus is not a weakness; it is a business choice. They serve their local market well. But operators outside Central Europe who need DDoS protection for globally distributed infrastructure need a platform designed for that use case.

Flowtriq agents deploy on servers anywhere in the world. The dashboard, alerting, and support are English-first and not tied to any geographic market. Whether your servers are in Frankfurt, Dallas, Singapore, or Sao Paulo, the detection and mitigation capabilities are identical.

Provider-bundled vs. independent detection

The broader question behind WEDOS's approach is whether relying on your hosting provider for DDoS protection is sufficient. Provider-bundled protection has trade-offs that apply to any provider, not just WEDOS.

• No portability: If you switch hosting providers, your DDoS protection does not come with you. With independent detection, your monitoring stays the same regardless of where your servers are hosted.
• No per-server visibility: Provider-bundled protection typically operates at the network edge, not at the server level. You do not get per-server baselines, per-server PCAP, or per-server attack classification.
• No control over mitigation policies: The provider decides what gets blocked and what gets through. You cannot customize thresholds, whitelist specific traffic patterns, or configure mitigation escalation.
• Single point of dependency: If the provider has a bad day, both your hosting and your DDoS protection are affected simultaneously.

Independent detection platforms like Flowtriq give operators control over their own DDoS defense. You set the thresholds, you configure the mitigation, you own the forensic data. The trade-off is that you are responsible for deploying and managing the detection platform, rather than having it bundled into your hosting fee.

When provider-bundled protection works (and when it does not)

When it works: If you are hosting a Czech-language website on WEDOS's shared or VPS hosting, their bundled DDoS protection covers your basic needs without additional cost or configuration. You do not need to think about detection, mitigation, or BGP. The provider handles it.

When it does not: If you operate your own infrastructure across multiple providers, need per-server visibility, require PCAP forensics for compliance or upstream reporting, or serve an international audience, provider-bundled protection creates gaps. Independent detection gives you consistent coverage regardless of where your servers live.

The bottom line

WEDOS serves the CZ/SK webhosting market with bundled DDoS protection included in their hosting packages. For their target market, this is a reasonable approach. The complaints from users reflect the trade-offs of provider-bundled protection: limited control, aggressive filtering, support capacity constraints, and geographic focus.

Flowtriq targets a different market entirely: ISPs, hosting providers, and infrastructure operators who need to deploy their own DDoS detection across their own infrastructure. The comparison is less about which product is better and more about which model fits your situation. If you run your own servers, Flowtriq gives you detection you control. If you host on someone else's platform and want them to handle DDoS, a provider with bundled protection may be the simpler path.