NetClamp pre-release

Build status

What's shipped, what's pending, and the rough ETA to first installer. Updated by hand — expect a few-day lag from what's actually on master.

Pre-release

Shipped

  • Kernel driver. WFP callouts for block, allow, rate-limit. Survives BFE bounces; graceful unload. Test-signed today; production attestation pending.
  • Service. Windows SCM service, REST on :9845, gRPC on :9846, SQLite rule + quota + history store. Phase F/G/G+ recovery: BFE bounce mid-rule-create auto-heals via reconcile.
  • Tray app. System-tray icon with live up/down indicators, flyout with per-app rates, one-click "throttle to N KB/s" preset, WebView2-embedded SPA.
  • CLI tool. Full rule / quota / diag surface; same auth as the REST API.
  • SPA dashboard. React + Vite. Rules, quotas, history, license / credit management. Bundled into the service binary via rust-embed.
  • Credit-based licensing. Free baseline of 10 managed entities + $10 packs of +10. Hwid-bound Ed25519 tokens, phone-tunneled activation design.
  • Billing-server skeleton. Routes, schema, signer. Live at billing.netclamp.com behind a Cloudflare Tunnel. Endpoints currently return 501 with a structured "pending integration" hint.
  • This site. Cloudflare Pages at netclamp.com.

Pending

  • Microsoft Hardware Dev Center attestation. The kernel driver runs under test-signing today; production deployment needs an EV cert + WHQL submission. Estimated 1–3 weeks once the EV cert lands.
  • Authenticode code-signing. User-mode binaries (service, tray, CLI, installer) need a code-signing cert so SmartScreen doesn't warn on first install.
  • Stripe wiring. The billing server's /checkout, /webhook/stripe, /bind, and /release routes are stubbed. Live integration needs a Stripe account + the webhook secret in the service env.
  • Phone-tunnel UX. The activation QR → phone → pay flow has a design but no implemented UI yet on the phone side.
  • Documentation site. User guide, REST reference, troubleshooting. Currently lives in .planning/ in the repo — needs a public docs site.
  • Installer signing pipeline. CI step that signs the Inno Setup output with the production cert.

Where we're at

Day-to-day development happens on gitlab.com/netclamp/NetClamp against the master branch. If you want to build from source and try the current state, the repo's CLAUDE.md has a five-minute orient.

For everyone else: drop your email on the home page and we'll ping you when the installer is ready. No newsletter, no drip, one message.