NetPulse pushes country rules and curated blocklists down to every server you run. Every block executes locally, in your kernel firewall — your traffic and logs never leave your machine.
RDP, RDWeb and SSH stay online around the clock — permanently enumerable, permanently scanned by bots across the planet.
Rotating residential-proxy farms make single-IP blacklists always one step behind. Ban one address, a thousand more rotate in.
Thousands of background-noise events a day bury the real attack. Nobody can watch a wall of noise forever.
Country-level rules cut the noise in one stroke; curated Spamhaus DROP intel pre-bans known hostile ranges before they connect; your own failure rules cover the rest.
Bans live in your kernel firewall: enforcement continues through console or network outages, filters are restored automatically after reboot, and whitelist guardrails make self-lockout impossible.
A single dependency-free binary. One command to enroll a server. GeoIP databases and threat feeds sync in the background. Many servers, one console.
The cloud holds your configuration — never your traffic.
The GeoIP database ships with each agent; country lookups run offline with zero external calls.
Bans live in your kernel firewall. The console is a management plane — losing it does not lower your protection.
No traffic capture, no raw log uploads — and event reporting is configurable per server: full, metadata only, or completely off.
The console is one open-source binary with an embedded database — run the entire pipeline inside your own datacenter.
The platform subscribes to Spamhaus DROP once, cleans and canonicalizes it, merges it with your private lists, filters it through whitelist guardrails, and delivers it as a versioned delta. Nothing is ever uploaded from you to a crowd — there is no crowd to feed.
One click in the console. Keys are single-use and expirable.
Paste it on the server — Windows or Linux. The agent installs itself as a service and registers.
[Net.ServicePointManager]::SecurityProtocol='Tls12' first if you hit an SSL/TLS erroriex(irm "https://app.netpulsecloud.com/i?k=KEY")curl -fsSL https://app.netpulsecloud.com/install-client.sh | sh -s -- https://app.netpulsecloud.com KEYGeoIP databases, curated feeds and your country policy sync automatically from then on.
Every plan includes local enforcement, IPv6 and the curated feed. Upgrading only changes quotas.
Built by operators who were tired of watching RDP logs fill with hits from rotating residential-proxy farms.
GeoIP attribution runs entirely on each server — no external lookups. Per server you choose how much to report: full events, metadata only, or nothing at all. Raw traffic and raw logs are never uploaded in any mode, and enforcement keeps working even when reporting is off.
Nothing at the enforcement layer. Rules and feeds already delivered live in your kernel firewall and keep blocking through console downtime, network failures and reboots.
Yes. The console is a single open-source Go binary with an embedded SQLite database — the whole management plane can run inside your own network.
Windows Server (WFP) and Linux (ipset / iptables / nftables), with full IPv4 and IPv6 on both.