The gateway between zones
Each network port gets a role: internet uplink, internal network, DMZ, management or unused, with VLANs on any port. Traffic between these zones, and to the gateway itself, follows your policy.
How it works
VYREON runs as the gateway between the internet and your internal networks. It filters and inspects the traffic that crosses that boundary, enforces your firewall policy, terminates your VPNs, and is managed from a web console in the browser.
Screenshots show the console with demonstration data.
Each network port gets a role: internet uplink, internal network, DMZ, management or unused, with VLANs on any port. Traffic between these zones, and to the gateway itself, follows your policy.
Intrusion prevention inspects traffic inline between interface pairs and blocks attacks. Detection-only mode can also watch a switch mirror (SPAN) port or a network TAP and only raise alerts.
Run a single gateway, or two as an active/standby pair: the standby takes over the gateway addresses when the active node fails.
Addresses on your blocklists and on downloaded threat-intelligence feeds, countries you block and floods that exceed your limits are dropped before they cost resources. The last good feed data stays in force if a download fails.
Traffic is inspected for known attacks with maintained rule sets plus your own rules, and applications are identified so your policy and events can name them. Repeat attackers can be blocked automatically for a set time. IDS or IPS?
Rules decide what may pass between zones and to the gateway: addresses, ports, applications, VPN user groups, NAT and port forwarding. Every rule shows how often it was hit.
VYREON never decrypts your traffic. Inspection uses what is visible on the wire: headers, plain-text protocols and TLS metadata such as the server name.
Edits are collected in a draft. You see exactly what is waiting, apply it when you are ready or schedule it for a maintenance window, and the gateway confirms it before the console calls it done.

Accounts with roles and optional two-factor sign-in, every setting in one place and an audit log of every change, on desktop and mobile.
A change runs on a confirmation timer and is shown as applied only after the gateway confirms it. If you do not confirm in time, for example because the change cut off your access, the gateway rolls back on its own.
Installing VYREON changes nothing on the network by itself. After installation, a guided setup describes your uplink, internal networks and public servers, then applies the network and the firewall policy in a safe order, each step with a confirmation timer.

Install the .deb on your own server; VYREON runs as a system service.
A ready VYREON appliance image for virtual machines or dedicated hardware.
Two gateways as an active/standby pair with failover and configuration sync. How a pair works.
VYREON starts with a 30-day trial that includes every feature. A licence is a small signed file bound to the node fingerprint shown in the console (or unbound for appliance images). You install it under Settings, Licence; VYREON verifies the signature locally, so it works without internet access.
When the gateway has internet access, it asks VYREON's licence service once a day whether the licence is still valid and receives renewals automatically. A failed check never changes anything, and no licence state ever reduces protection.
Software updates are published as signed packages. VYREON checks for them (notify only by default), verifies the signature and checksum, and installs only what an administrator approves or what falls into a configured maintenance window. Your update entitlement is part of your licence.