ONE NAME.
EVERY PROCESS.
ANNIHILATED.

Mass-scale process termination infrastructure for teams that move fast and break things on purpose.

Start Purging Free
0 Processes terminated per day
0 Signal delivery rate
0 Teams shipping with PURGE
0 Avg. time to full annihilation

THE ARSENAL

Every flag. Every signal. Every process. Handled.

🎯

Name-Based Targeting

Specify a name. PURGE finds every process running under that name and delivers SIGTERM simultaneously. No PIDs. No guesswork. Just names.

🔬

Exact Match Engine™

Long process names get truncated at 15 characters by the kernel. Our -e flag skips anything that can't be fully verified. Zero false positives. Enterprise-grade precision.

🧲

Case-Blind Targeting

With -I, PURGE ignores case boundaries entirely. Whether it's nginx, Nginx, or NGINX — nothing hides from a case-insensitive sweep.

👥

Group Sweep™

The -g flag targets the entire process group at once. One signal per group, no duplicates, no wasted resources. Surgical group-level elimination.

🔮

Regex Targeting

Full POSIX extended regular expressions via -r. Pattern-match your way through process lists. Wildcards are amateur hour — PURGE speaks regex natively.

Custom Signal Delivery

SIGTERM is just the default. Send any signal you want with -s. SIGHUP, SIGKILL, SIGUSR1 — your call. List every available signal with -l.

👤

User-Scoped Purging

The -u flag constrains all operations to a single user. Multi-tenant infrastructure? Scope your purge to one user's processes without collateral damage.

Time-Based Filtering

Target only processes older than a threshold with -o, or younger with -y. Specify durations in seconds, minutes, hours, days, weeks, months, or years.

HOW IT WORKS

From name to termination in four steps.

01

Name The Target

Provide the process name. PURGE scans the entire process table and identifies every matching instance across all users and namespaces.

02

Apply Filters

Narrow your scope with user filters, regex patterns, age thresholds, case rules, or security contexts. Zero ambiguity before you pull the trigger.

03

Deliver The Signal

PURGE sends your chosen signal to every matched process simultaneously. One sweep. No stragglers. No manual PID hunting.

04

Confirm The Kill

With -w, PURGE monitors every second until all targeted processes have stopped. Guaranteed completion. Verified annihilation.

SEE IT IN ACTION

Real output. Real power. No simulations.

PURGE Terminal
$ purge -v nginx
Killed nginx(12847) with signal 15
Killed nginx(12848) with signal 15
Killed nginx(12849) with signal 15
$ purge -i -u deploy python3
Kill python3(20441) ? (y/N) y
Kill python3(20512) ? (y/N) y
$ purge -w -s SIGKILL node
Killed node(8891) with signal 9
Killed node(8904) with signal 9
$ purge -o 2h -v java
Killed java(4401) with signal 15
$ purge -r "worker_[0-9]+" -q
$

WHY NOT SINGLE-TARGET?

Stop hunting PIDs one at a time. Scale your termination strategy.

Feature Single-Process Tools Manual Scripts PURGE
Kill by name ❌ PID-only ⚠️ Shell loops ✅ Native
Regex matching ⚠️ Fragile grep chains ✅ POSIX extended
User-scoped ⚠️ Requires parsing ✅ Built-in -u
Age-based filtering ⚠️ Complex logic -o / -y
Group termination ⚠️ Race conditions ✅ Single signal per group
Wait for completion ❌ Fire and forget ⚠️ Polling scripts -w built-in
Interactive confirm ⚠️ DIY prompts -i per-process

LIVE FEED

Real-time purge events from our global network.

CHOOSE YOUR TIER

One signal type for free. Pay to unlock the full arsenal.

Starter

$0/mo
  • SIGTERM only
  • 50 purges / month
  • Single user scope
  • No regex targeting
  • No age-based filtering
  • No -w wait mode
Get Started

Team

$59/seat/mo
  • Everything in Pro
  • User-scoped purging -u
  • Group sweep -g
  • Interactive confirm -i
  • Case-blind targeting -I
  • SSO & audit logs
Start Trial

Enterprise

Custom
  • Everything in Team
  • Exact match engine -e
  • SELinux context filtering -Z
  • Namespace isolation -n
  • Dedicated SLA
  • Custom integrations
Contact Sales

WHAT THEY SAY

"We were running bash loops piped through grep to kill rogue processes. Took 14 seconds and broke on edge cases. PURGE replaced all of it with one call. Changed the game."

David Strom
David Strom VP of Platform, ScaleForge

"The regex targeting alone was worth the upgrade. We went from manually hunting PIDs to pattern-matching our way through 400+ worker processes. This is the 10x tool I've been waiting for."

Caleb Walsh
Caleb Walsh Solo Developer & Indie Hacker

"User-scoped purging in a multi-tenant environment was a compliance nightmare before PURGE. Now it's one flag. Our auditors stopped losing sleep."

Rina Nakamura
Rina Nakamura CTO, InfraGrid

"I shipped PURGE into our CI pipeline to kill stale test runners older than 2 hours. The -o flag is unbelievably underrated. This should be embedded in every deployment."

Derek Moss
Derek Moss Staff SRE, Vortex Systems

WHAT'S NEW

v3.2.0

Namespace Isolation

Match against PID namespace of any given process via -n. Default behavior matches across all namespaces — opt in to surgical namespace targeting.

v3.1.0

SELinux Context Filtering

Full -Z support for security-context-aware purging. Extended regex patterns against process security labels. Lock-step with your zero-trust posture.

v3.0.0

PURGE Core Rewrite

Complete overhaul of the matching engine. Regex targeting, age-based filters, and guaranteed wait-for-completion — all shipping as first-class primitives.

FAQ

By default, PURGE reports a non-zero exit code. Enable quiet mode with -q to suppress the warning if you prefer silent no-ops in automated pipelines.

No. PURGE has built-in self-preservation — a PURGE process never terminates itself, though it can terminate other PURGE instances running concurrently.

Use the -i flag for interactive mode. PURGE prompts you with a y/N confirmation before sending a signal to each matched process. Full control, zero surprises.

The -w flag checks once per second until all targeted processes are gone. If a process ignores the signal or enters zombie state, wait mode will persist indefinitely. Pair with SIGKILL for guaranteed results.

PURGE operates at the signal layer. It doesn't read, store, or transmit process data. With -Z SELinux context filtering, you can enforce security policies at the targeting level. Enterprise tier includes SOC 2 compliance.

Backed by mandō