Self-hosted web protection

Protect your site.
Share the cost of access.

Sibuna asks clients to solve a puzzle before granting access. Creating the proof takes more computation than checking it. This helps preserve your app's resources for admitted traffic.

Open source · LGPL 3.0 · v1.0.0-beta.3

Follow a request

Work before access.

Sibuna checks requests before they reach your application Requests pass from a client through an HTTPS ingress to Sibuna. Sibuna may admit, challenge or refuse them. A client creates a proof; Sibuna verifies it and issues a session. Requests with sessions still pass applicable checks. ClientHTTPS ingress SibunaYour app Challenge, then client work, then proof verification
  1. Client
  2. HTTPS ingress
  3. Sibuna
  4. Your app

Admit, challenge or refuse. A session avoids another puzzle here; applicable rules and rate limits still apply.

CLIENT WORK · CHECK THE PROOF AT SIBUNA
STEP 1 / 8 Static illustration

A request arrives

The browser sends a request through your HTTPS ingress.

Scripted illustration, not live traffic or measured timing. Proof time varies by device and settings. This shows the reverse-proxy path; with forward-auth, your ingress forwards admitted requests. Deployment guide

01 / Govern admission

Ask bots to do the work.

Browser challenges add a cost to automated access. Signed sessions let admitted visitors return without a new puzzle on every request. Hardware and difficulty affect the cost.

02 / Protect applications

Keep requests flowing.

Use Sibuna as a reverse proxy or an admission service for your existing ingress. Rules can match the JA4 TLS fingerprint that a trusted ingress forwards. Shield checks requests for SQL injection, XSS, path traversal and command injection.

03 / Operate with evidence

See the decisions.

The optional console shows traffic, recorded incidents and policy changes. Coverage and sampling labels help explain what each view can tell you.

Try v1.0.0-beta.3

Download.
Verify. Configure.

Download binaries for Linux, macOS and Windows; Debian, RPM and Arch packages; or CLI packages for FreeBSD 15.1 and OpenBSD 7.9 x86-64. Releases also include a Helm chart and a container image. Verify checksums before installation.

All downloads
TERMINAL · LINUX x86-64
curl -fLO https://github.com/insanai/sibuna/releases/download/v1.0.0-beta.3/sibuna-linux-amd64.tar.gz
curl -fLO https://github.com/insanai/sibuna/releases/download/v1.0.0-beta.3/SHA256SUMS
sha256sum --ignore-missing -c SHA256SUMS
tar -xzf sibuna-linux-amd64.tar.gz
./sibuna --help

# Configure a trusted HTTPS ingress before deployment.

Find your way through the system

Learn it. Use it. Question it.

Know the deployment boundary

Application protection.
Explicit limits.

Terminate public HTTPS at a trusted ingress and keep Sibuna's listener private. Linux requires kernel 5.10 or later; macOS requires 12 or later; Windows requires Windows 10 or Server 2016 or later.

CLI and protocol reference

The built-in inspector checks the first 8 KiB of supported bodies. WebSocket messages are relayed without inspection. Forward-auth sees the metadata supplied by the ingress.

Your ingress handles public TLS and HTTP/2. Rate limits are local to each node. Sibuna does not provide volumetric network mitigation. A challenge adds work; it does not establish that a visitor is human.

The console is opt-in. Its strict performance isolation target has not formally passed. Published measurements identify the code revision and uncertainty.

Console contract · Architecture whitepaper · Book PDF · Whitepaper PDF