veilx brings "acceleration" and "security" together on one platform. Understanding a few core concepts helps you read every setting in the console faster and know what problem each one solves.
Edge nodes and caching
Edge nodes are servers distributed around the world, closer to your visitors. A visitor's request first reaches the nearest edge node; if the node already has the requested content cached, it returns it directly without going back to your origin. That's a "cache hit", and it's the core of acceleration — the closer content is to the user, the faster the response and the lighter the load on your origin.
Origin and origin fetch
The origin is your own server, holding the site's original content. When an edge node has no cache hit, it requests data from the origin — this is called "origin fetch". The origin configuration (address, port, protocol, origin Host) determines how the node correctly retrieves content from your origin.
WAF and CC protection
The Web Application Firewall (WAF) inspects every request at the edge node and blocks malicious traffic such as injection and bots by rule; CC protection targets bursts of high-frequency requests, identifying and dampening attacks. Both take effect before requests reach your origin, so no changes to your application code are needed.
Port and streaming forwarding
Not all traffic is web. Port forwarding carries non-HTTP services at Layer 4 (TCP/UDP), while streaming relay targets audio and video traffic. They let veilx accelerate these connections too, and hide your origin's real address.
Plans and quotas
Your plan determines quotas such as available sites, monthly traffic, bandwidth cap and number of forwards. The console home page shows your current usage; when growth reaches a limit, you can upgrade your plan at any time.