A true layer-7 firewall,
professional and fully configurable
Korthveil decides by application, website, user and device, not only by address and port. Everything a commercial next-generation firewall does is here, configurable down to the last option, and explained in plain words.
It knows what the traffic is, and who it belongs to
A port-based firewall sees "TCP 443 to some address". Korthveil sees "Maria's laptop opening YouTube", "a phone asking a botnet server for orders", or "the accounting group uploading to an unapproved cloud drive". You write rules in those terms, and every decision can be explained.
- Rules that match applications, URL categories, users and groups, host names and devices
- Application identification from TLS and QUIC server names, HTTP hosts, DNS answers and packet content, with per-application usage
- Intrusion prevention, web filtering, TLS inspection, anti-virus and sandboxing on the traffic you allow
- Every block explained: which rule or module decided, and why
Port-based firewall vs Korthveil
| Question | Ports only | Korthveil (L7) |
|---|---|---|
| Block YouTube for the TVs at night | Guess the addresses | One rule: kind TV β YouTube, schedule 23:00β05:00 |
| Allow the sales group, not guests | By IP ranges | By directory group |
| Stop a phone talking to a botnet | Not seen | IPS and threat feeds drop it, and name the device |
| Block gambling and malware sites | Not possible | URL categories, block page |
| See which app uses the bandwidth | Port numbers | Applications, users, rules |
| Why was this blocked? | Search the logs | "Blocked by your rule #6": the rule, devices and owner |
| Does my new rule work? | Wait for complaints | The flow chart shows the attempts it stops, live |
| Does this device really use the VPN? | Traceroute and guess | Every conversation shows the tunnel or line it leaves through |
| Keep uploads of card numbers in | Not possible | Data loss prevention on decrypted uploads |
Application identification
Classifies connections into applications, including QUIC (HTTP/3) and by packet content: SSH, BitTorrent, RDP, SMB, VPN protocols, WebRTC and SIP. Rules allow or block an application by name.
Web filtering
URL and domain categories per zone, user and group: block, warn or allow, custom categories, safe search, and a branded HTTPS block page.
User and group rules
Maps addresses to users from Active Directory, LDAP, RADIUS, VPN and portal sign-ins, so rules follow people, not IP addresses.
TLS inspection
Transparent inspection of outbound HTTPS with its own certificate authority, privacy exemptions (banking, health) and strict origin checks.
Data loss prevention
Checks decrypted uploads for card numbers, social security numbers, IBANs, private keys, cloud and API keys and your own keywords; logs or blocks, and never stores the data itself.
Cloud app security (CASB)
Discovers shadow IT and controls each SaaS application: block, allow for chosen groups, or monitor. Blocks are enforced in DNS and in TLS inspection, with a block page.
Host names in rules
Use youtube.com or an object of host names in any rule; the firewall keeps their addresses up to date.
Rules by device kind
Write "all TVs" or "all cameras" in a rule; the firewall recognises each device's kind and keeps the rule current as devices come and go.
DNS tunnel and call-home detection
Finds data hidden in DNS queries and devices that keep calling unknown servers on a timer, and names the device.
Traffic flow chart
Each conversation drawn from device to rule to the tunnel or line it leaves through, with the attempts your rules block shown live.
Zero-trust app access
Identity-aware access to internal web apps with OpenID Connect (Entra ID, Okta, Keycloak, Google, or an on-premises provider on your own CA) and per-app policies.
Endpoint integration
Reads device posture from Defender for Endpoint, CrowdStrike or SentinelOne, and quarantines at-risk devices automatically.
Rules you can see, test and trust
A stateful firewall on the Linux kernel's nftables, with IPv4 and IPv6 handled the same way in every feature.
Stops attacks, malware and scanners
Every kind of address translation
Multiple lines, tunnels and routing domains
Connect sites, people and phones
Who connects, with what, and when
Private, filtered name resolution
See everything, live
Every conversation, in and out, and where it leaves
The flow chart draws your traffic as bands from device, to rule, to the way it leaves, to the destination. It is built for the moment you write or test a rule: you see at once what it lets through and what it stops.
- How traffic leaves: each conversation shows the VPN tunnel, internet line, phone backup or local network it goes through, with totals per way out; click one to see only its traffic
- What your rules block: blocked attempts over the last 1, 5, 15 or 60 minutes as dashed red bands through the rule that stopped them, with the number of tries
- Direction: outbound to the internet, inbound from it, or between your own networks
- Devices by name, kind and maker, not only addresses
- Search by device, rule, application or way out, colour by any column, and step back through the history
Typical questions it answers
- Is the TV really going through the VPN, or straight out?
- My new deny rule: how often does it fire, and from which devices?
- What is coming in from the internet, and through which rule?
- Which device uses the bandwidth right now, and on which line?
Built to stay up
Configurable everywhere, simple anywhere
Your hardware, your firewall
Any 64-bit computer or virtual machine that Debian 13 supports, with two network interfaces. Korthveil runs on Debian 13 with its own Linux 6.18 kernel and the nftables data plane.
Core firewall
2 cores, 4 GB RAM, 32 GB disk.
With IPS, WAF or the Full Suite
4 or more cores, 8 GB RAM, 64 GB disk.
Virtual machines
KVM, Proxmox, XCP-ng and VMware, with two virtual network cards.
Ready to see it on your network?
Start with the Core firewall and add exactly the modules you need, or take the Full Suite.
Build your license Read the guides