Replace hacked WordPress with editable static HTML.
Keep the website and its design. Remove the fragile public CMS backend.
Website · Live demo · Downloads · Install
SiteBrush imports an existing website, preserves its pages and design, and replaces the risky public-facing CMS with fast static files.
Visitors receive ordinary HTML, CSS, JavaScript, and images. The site owner can still edit text, pictures, buttons, menus, and page blocks directly in the browser.
SiteBrush is not a WordPress clone. It is a WordPress retirement tool.
- Preserve the existing design instead of rebuilding the website.
- Remove WordPress, public login forms, plugins, themes, PHP, and the database from the visitor-facing side.
- Reduce the attack surface and ongoing maintenance burden.
- Edit content directly on the page with a right-click or long-press.
- Freeze the public version while preparing changes, then publish safely.
- Run the server as one standalone binary without a separate dependency stack.
- Import existing WordPress, Joomla, Wix, Readymag, and custom websites.
Nothing is completely invulnerable, but a static public website exposes far fewer moving parts than a traditional WordPress installation.
- Import — SiteBrush copies pages, media, styles, scripts, and other website files.
- Edit — open the site and use right-click on desktop or long-press on mobile.
- Publish safely — visitors keep seeing the stable version until your changes are ready.
Try SiteBrush with your own website without changing the live site, or open the demo.
The server version is recommended for a public website. Desktop builds are useful for local work with a graphical interface.
| Platform | Desktop application | Server binary |
|---|---|---|
| amd64 GTK 4.1 · GTK 4.0 arm64 GTK 4.1 · GTK 4.0 |
amd64 · arm64 | |
| Universal DMG | Intel amd64 · Apple Silicon arm64 | |
| amd64 ZIP · arm64 ZIP | amd64 EXE · arm64 EXE | |
| — | amd64 · arm64 | |
| — | amd64 · arm64 | |
| — | amd64 · arm64 |
Linux desktop builds use GTK 4.1 for newer distributions and GTK 4.0 for older LTS distributions.
Server checksums · Desktop checksums · All latest builds
Each block below is ready to copy and paste. It automatically selects amd64 or arm64, downloads SiteBrush, makes it executable, and installs the system service.
Linux — copy and paste into the terminal
(
set -eu
case "$(uname -m)" in
x86_64|amd64) ARCH="amd64" ;;
aarch64|arm64) ARCH="arm64" ;;
*) echo "Unsupported CPU architecture: $(uname -m)" >&2; exit 1 ;;
esac
sudo mkdir -p /usr/local/bin
sudo curl -fL \
"https://sitebrush.com/download/latest/server-app/sitebrush_linux_${ARCH}" \
-o /usr/local/bin/sitebrush
sudo chmod +x /usr/local/bin/sitebrush
sudo /usr/local/bin/sitebrush -install
)The installer detects the available Linux service manager and configures automatic startup.
macOS — Intel and Apple Silicon
(
set -eu
case "$(uname -m)" in
x86_64|amd64) ARCH="amd64" ;;
arm64|aarch64) ARCH="arm64" ;;
*) echo "Unsupported CPU architecture: $(uname -m)" >&2; exit 1 ;;
esac
sudo mkdir -p /usr/local/bin
sudo curl -fL \
"https://sitebrush.com/download/latest/server-app/sitebrush_darwin_${ARCH}" \
-o /usr/local/bin/sitebrush
sudo chmod +x /usr/local/bin/sitebrush
sudo /usr/local/bin/sitebrush -install
)The installer configures SiteBrush as a launchd service.
Windows — PowerShell as Administrator
Open PowerShell as Administrator, then paste:
$ErrorActionPreference = "Stop"
$Arch = if ($env:PROCESSOR_ARCHITECTURE -eq "AMD64") {
"amd64"
} elseif ($env:PROCESSOR_ARCHITECTURE -eq "ARM64") {
"arm64"
} else {
throw "Unsupported CPU architecture: $env:PROCESSOR_ARCHITECTURE"
}
$Dir = Join-Path $env:ProgramFiles "sitebrush"
$Exe = Join-Path $Dir "sitebrush.exe"
New-Item -ItemType Directory -Force -Path $Dir | Out-Null
Invoke-WebRequest `
-Uri "https://sitebrush.com/download/latest/server-app/sitebrush_windows_${Arch}.exe" `
-OutFile $Exe
& $Exe -installThe installer creates and verifies the Windows service and enables automatic startup.
FreeBSD — amd64 and arm64
(
set -eu
case "$(uname -m)" in
x86_64|amd64) ARCH="amd64" ;;
aarch64|arm64) ARCH="arm64" ;;
*) echo "Unsupported CPU architecture: $(uname -m)" >&2; exit 1 ;;
esac
sudo mkdir -p /usr/local/bin
sudo fetch \
-o /usr/local/bin/sitebrush \
"https://sitebrush.com/download/latest/server-app/sitebrush_freebsd_${ARCH}"
sudo chmod +x /usr/local/bin/sitebrush
sudo /usr/local/bin/sitebrush -install
)
OpenBSD — amd64 and arm64
(
set -eu
case "$(uname -m)" in
x86_64|amd64) ARCH="amd64" ;;
aarch64|arm64) ARCH="arm64" ;;
*) echo "Unsupported CPU architecture: $(uname -m)" >&2; exit 1 ;;
esac
doas mkdir -p /usr/local/bin
doas ftp \
-o /usr/local/bin/sitebrush \
"https://sitebrush.com/download/latest/server-app/sitebrush_openbsd_${ARCH}"
doas chmod +x /usr/local/bin/sitebrush
doas /usr/local/bin/sitebrush -install
)Run the commands as root when doas is not configured.
NetBSD — amd64 and arm64
(
set -eu
case "$(uname -m)" in
x86_64|amd64) ARCH="amd64" ;;
aarch64|arm64) ARCH="arm64" ;;
*) echo "Unsupported CPU architecture: $(uname -m)" >&2; exit 1 ;;
esac
sudo mkdir -p /usr/local/bin
sudo ftp \
-o /usr/local/bin/sitebrush \
"https://sitebrush.com/download/latest/server-app/sitebrush_netbsd_${ARCH}"
sudo chmod +x /usr/local/bin/sitebrush
sudo /usr/local/bin/sitebrush -install
)The -uninstall command removes the configured system service.
Linux, macOS, FreeBSD, and NetBSD
sudo /usr/local/bin/sitebrush -uninstallOpenBSD
doas /usr/local/bin/sitebrush -uninstallWindows — PowerShell as Administrator
& "$env:ProgramFiles\sitebrush\sitebrush.exe" -uninstallAfter installation:
- Point the website domain to the server.
- Open the domain in a browser.
- Use right-click on a computer or long-press on a phone.
- Edit the content and save it.
https://your-domain.example
- Business websites and landing pages
- Portfolios and agency websites
- Documentation and knowledge bases
- Old WordPress websites that keep breaking
- Mostly static websites that still need easy browser editing
Keep a traditional dynamic CMS when the project requires complex e-commerce, memberships, extensive server-side workflows, or custom plugin logic.
Keep the website. Keep the design. Keep simple browser editing.
Leave the database, plugin stack, public admin backend, and constant maintenance behind.