VeloDNS
Authoritative DNS with DNSSEC and health-aware steering
Sovereign Edge & Traffic Platform
Your edge. Your DNS. Your traffic. Under your control.
Operate a global traffic entry layer with authoritative DNS, distributed edge, intelligent steering, reverse proxy, load balancing, TLS, WAF, and failover — on infrastructure you control with centralized governance.
Adopt it progressively or run the full stack: centralized control plane, distributed data plane, and last-known-good continuity.
Multi-edge
Distributed nodes and clusters on infrastructure you control
LKG
Keep the edge serving through control-plane failures
BYOS
Bring Your Own Servers without single-provider edge lock-in
Centralized control. Distributed execution. Isolated failures.
VeloFlux separates control from the critical traffic path so policy, telemetry, and automation can evolve without making the control plane a mandatory dependency for every request.
Control Plane · API + Dashboard
- Projects, domains, DNS zones, routes, upstreams, clusters, and edge nodes
- Traffic, security, health, TLS, and dynamic configuration policies
- Operational visibility through metrics, logs, audit, and telemetry
- Change orchestration, draining, rollouts, and multi-tenant governance
- Snapshot distribution for resilient data-plane operation
Data Plane · Edge + DNS + Routing
- L7 reverse proxy with multiple origins, retries, circuit breaker, and health checks
- Authoritative VeloDNS with DNSSEC, failover, and health/performance-aware edge selection
- Independent edge nodes with dynamic config and last-known-good state
- WAF, rate limiting, origin protection, and local mitigation enforcement
- Routing plane for multi-edge, Anycast, and evolving multi-provider topologies
One platform, six infrastructure pillars
From the DNS decision that selects an edge to the proxy hop that delivers a request to the origin.
01 · Global Traffic
Authoritative VeloDNS, DNSSEC, health-aware DNS, failover, and adaptive steering to select healthy edges without assuming the geographically closest POP is always the fastest.
02 · Edge Network
Clusters and multiple edge nodes, public IP and heartbeat, BYOS, draining, and routing/Anycast components for distributing traffic entry across regions and providers.
03 · Application Delivery
L7 reverse proxy, multiple origins, round robin, least_conn, least_time, ip_hash, and weighted balancing plus retries, circuit breaker, and runtime configuration.
04 · Security
Automatic TLS, WAF, rate limiting, origin protection, security policies, and a mitigation agent for abuse reduction and local enforcement close to traffic.
05 · Reliability
Independent health checks, automatic reconciliation, origin/edge failover, last-known-good snapshots, and a design built to keep serving when central dependencies fail.
06 · Observability & Control
Multi-tenant dashboard and API, metrics, logs, telemetry, audit, feature flags, and rollouts for safer infrastructure operations.
Load balancing for different workloads
Select a strategy based on application behavior and combine health, capacity, and observed performance.
| Strategy | When to use |
|---|---|
| round_robin | Stateless services with equivalent capacity. |
| least_conn | Long-lived connections, streaming, and variable-duration workloads. |
| least_time | Adaptive preference based on observed upstream latency. |
| ip_hash | Client session affinity without external state. |
| weighted | Backends with different capacity or priority. |
Built to reduce complexity and dependency
Adopt only the layers you need today and grow into a complete edge mesh as operations scale.
SaaS custom domains
Centralize traffic entry, TLS, routes, and origins for large hostname fleets without making every app an infrastructure project.
Multi-region high availability
Distribute edge and origins across regions with health checks and automatic failover.
Cloud and provider independence
Reduce lock-in by operating your own nodes and separating DNS, edge, and origins from a single provider.
Critical application protection
Keep origins away from direct exposure and enforce controls at the traffic entry layer.
BYOS and private infrastructure
Run the data plane on your servers, VPSs, or providers while maintaining centralized governance.
Platform teams and internal products
Standardize delivery, routing, health, TLS, and observability across products and teams.
Security and resilience on the critical path
Application and operational controls designed to limit blast radius and keep traffic behavior predictable.
- L7 WAF and edge rate limiting
- Automatic TLS with issuance governance
- Origin protection and reduced direct exposure
- Circuit breaker, retries, and controlled timeouts
- Health checks with configurable path, timeout, and thresholds
- Mitigation agent and local enforcement
- DNSSEC on authoritative VeloDNS
- Last-known-good isolation from control-plane failures
- Node draining and operational failover
- HttpOnly sessions, CORS, security headers, and payload limits
- Audit, metrics, logs, and operational telemetry
- CI gates, security tests, and E2E smoke coverage
Technical and commercial FAQ
The questions teams usually ask before putting VeloFlux on a production traffic path.
Is VeloFlux just a reverse proxy?
No. Reverse proxy is one part of the data plane. The platform also covers authoritative DNS, DNSSEC, steering, distributed edge, health, failover, security, routing, and observability.
Can I run VeloFlux on my own infrastructure?
Yes. The BYOS model lets you operate edge nodes on infrastructure you control while managing policy through the VeloFlux control plane.
Can I connect multiple servers and regions to one service?
Yes. Routes can use multiple origins and distributed edge nodes with balancing, health, and failover policies.
Is SSL automated?
Yes. Edge supports automatic certificate issuance with domain approval policy and shared certificate storage.
Is DNS part of the platform?
Yes. VeloDNS provides authoritative DNS and integrates health, DNSSEC, and steering decisions with the edge topology.
Does the edge keep working if the control plane is unavailable?
The architecture is designed to preserve the last valid configuration and keep serving with last-known-good state instead of making a central outage automatically take down the data plane.
Does VeloFlux eliminate all downtime risk?
No infrastructure is infallible. VeloFlux reduces single points of failure and provides redundancy and failover mechanisms, but final availability also depends on networks, providers, servers, and origin architecture.
Build an edge layer your operation can own.
Start with the reverse proxy, DNS, or edge capability you need today and evolve toward a global traffic platform without redesigning your application for every new region.