Attacks stop at our edge.
Players do not.
Your players connect to a protected Argus IP. Volumetric and protocol attacks are filtered upstream and at our edge; clean traffic reaches your origin over a private tunnel, with the player IP intact.
Edge nodes are being deployed across three locations. We onboard services by request while the rollout finishes.
Events today
1,240
Threats blocked
86
Agents online
3
Plan
Fortress
// THE PROBLEM
An attack does not have to break your server.
It only has to fill the pipe.
Once the traffic reaches your origin the damage is done: the uplink saturates, the host drops packets, and your provider null-routes the IP to protect everyone else. Argus moves the front line off your origin.
// HOW IT WORKS
Four layers between the attack and your origin.
You point players at a protected IP and give us a tunnel endpoint. What arrives at your origin is traffic we have already filtered.
Protected IPs, upstream filtering
Players connect to an Argus IP, never to your origin. Volumetric floods are filtered by the upstream network before they reach our nodes.
Scrubbing and filtering at the edge
Spoofed and malformed packets are dropped, per-source connection and rate limits hold the line, and the ruleset is tuned for your protocol.
Admission before the origin
Sources that do not pass admission get no path to your game ports. We are rolling this out edge-side, so nothing has to run inside your game loop.
Private transport to your origin
Clean traffic arrives over a GRE tunnel with the player source IP preserved, so your own bans, logs and analytics keep working.
Metin2 is our first tested profile; other TCP and UDP services get a profile of their own. Keeping player IPs correct on Metin2 needs proxy-IP support in your server source, and we check that with you before onboarding.
// COMPARE
Built for game traffic, not for websites.
Generic protection speaks HTTP. Your players speak your own TCP and UDP protocol, and that is the traffic we filter and tune for.
| Capability | Origin only | Host / generic edge | Argus |
|---|---|---|---|
| Absorbs volumetric floods (L3/L4) | Varies | Yes - upstream + our edge | |
| Tuned for game TCP/UDP protocols | Partial | Yes - per-service profile | |
| Attack traffic stops before your origin | Partial | Yes | |
| Player source IP kept at the origin | Yes | Often lost | Yes - GRE + proxy IP |
| Live events and per-service visibility | Basic | Yes | |
| Access rules pushed to the origin firewall | Yes | ||
| One console for every service | Partial | Yes |
Argus does not replace the limits inside your game server. Per-account rules stay where the accounts are.
// CONTROL PLANE
See everything. Control everything.
Not a black box - a live window into every service, every decision, every change. The origin agent reports telemetry and applies what you set here.
One console, every service
Register a service, then run your whole fleet - state, agents, health - from one cloud control plane.
Live event feed
Admission and mitigation decisions stream into the dashboard as your agent reports them. Filter it, watch it move.
Server-health rollup
Online state, last report, events per hour, threats per day and active IP rules - at a glance, per server.
Access rules that push live
Trust or blacklist an IP in the dashboard and the agent applies it in the origin firewall within about 30 seconds. No SSH, no reloads.
Protection you tune live
Detection thresholds, Strict mode, Panic mode and maintenance - changed in the dashboard, applied on the next agent poll.
Incidents and analytics
Attack episodes detected from event density, with a timeline and a per-server breakdown.
Alerts and webhooks
Rules that post to Discord, Telegram or any webhook when bans or incidents cross the threshold you set.
Host and firewall telemetry
Host health, firewall table sizes and listening ports, reported by the agent every 30 seconds.
Pay per protected service.
Two plans, billed monthly per service. Pricing and self-serve checkout land with the edge rollout; until then we onboard by request and quote your setup directly.
Guard
A protected IP, edge filtering and the full control plane for one service.
Request accessFortress
Everything in Guard, on anycast, with incident detection and alerting.
Request accessTell us what you run. We do the rest.
Send us the service, its ports and where the origin lives. We assign a protected IP, build the profile, set up the tunnel and bring you up.