Ordnary

Docs Ordnary Web Services Ordnary Netway

What Ordnary Netway is

Protection in front of your own server: how traffic flows, what is stopped, what your server sees, and what it costs.

3 min readBeginner
flowchart LR
  V[Visitors] -->|your hostname| E[Netway edge]
  E -->|DDoS, WAF, rate limits| E
  E -->|HTTPS to your origin| O[Your server]
Traffic reaches your server only after it passed Netway.

What it does

DDoS protection

Volumetric attacks on layers 3, 4 and 7 are absorbed by the edge network automatically.

Managed firewall

Managed rules against the common web attacks, plus rules per security profile: rate limits, challenges and blocking of known-bad clients.

TLS for your hostname

A certificate for your hostname is issued and renewed for you. Visitors always connect over HTTPS.

What it is for

Websites and APIs served over HTTP(S) from a server you run: a VPS, a dedicated machine, a cluster behind a load balancer. The server has to serve HTTPS on port 443 and be reachable from the internet. Netway does not protect non-HTTP services such as game servers or mail.

What your server sees

Requests arrive from the edge over HTTPS, with the original hostname and the visitor's address in the X-Forwarded-For header. Your application does not need to change; configure it to read the visitor's address from that header for logging and rate limiting of its own.

What it costs

Netway launches without usage pricing. Activating it is free and records your acceptance of the terms; there is nothing to pay for protection at the moment. If that changes, the rates appear on the activation page and under Billing before they apply.

Was this page helpful?
Updated 25 October 2026 Suggest an edit

Choose which cookies Ordnary may use. You can change this at any time via Cookie settings at the bottom of every page.