Fail-open is a feature.
A protection layer that can take the proxy down is a second outage. Leviathan keeps the gate running when the license plane blinks, and keeps every block inside the JVM.
The gate should not become the hostage.
Remote authority is useful for entitlement. It is a bad reason to let a proxy die. Leviathan separates the two: Premium features fail open, while the core anti-bot engine stays in the connection path.
- No exit
- A rejected or unreachable license logs a warning; it does not call
System.exit. - No host takeover
- No sudo, iptables, ipset, nftables, package installs, or host firewall changes.
- No residual state
- Stop the proxy and the in-process blocks are gone. Nothing survives on the host.
- Bounded I/O
- Reputation and webhook calls are asynchronous and HTTPS-only; a slow API does not stall the Netty event loop.
The inherited pattern, changed.
Leviathan is in the XCord / Travertine lineage. The safety differences are deliberate: a proxy should protect a network without claiming the machine.
| Concern | The risky pattern | Leviathan |
|---|---|---|
| Edition handling | Remote check coupled to startup | Free Trial is independent of the private Premium validator |
| Validation failure | Exit on an invalid result | Fail-open; warn and keep protecting |
| Host firewall | sudo iptables / ipset | Never touches the host; mitigation is in-proxy |
| OS packages | Silent installs on first run | Installs nothing |
| Reputation keys | Plain HTTP | HTTPS only |
| Persistence | Java-serialized manager object | Small versioned binary of primitives |
| Privileges | root / sudo | Normal, non-root user |
Comparison is limited to the listed runtime behaviors. It is not a performance claim.
Where the claim stops.
Honesty is part of the security model. Leviathan filters application-layer connections; it is not a scrubbing center, a host firewall, or an audited appliance.
- Not DDoS-proof
- It targets join floods and pre-play traffic inside the proxy. Volumetric L3/L4 attacks need upstream capacity.
- No external audit
- No external pentest or live security qualification is claimed. AbyssLink explicitly records what is not yet demonstrated.
- No perfect detection
- Fingerprints and reputation can produce false positives. Tune the windows and use the whitelist.
- No hosted service
- You run the jar. The studio issues a license; it does not operate your proxy.