What's new in v1.8.0
This release completes the Enterprise & Team and Developer Ecosystem roadmap phases, plus crash-safe recovery that no longer takes a VM offline when Blackout Kit dies:
- Enterprise & Team — role-based access control (viewer / operator / admin), a distributable and optionally HMAC-signed access policy, a multi-device registry with an online/offline dashboard, and GDPR / HIPAA / SOC 2 control checklists scored from your effective settings.
- Developer ecosystem — a Python SDK (
from blackoutkit.sdk import Blackout), a plugin system for custom rules/analyzers/exporters, a community marketplace with SHA-256-verified installs, and a read-only REST API v2 with webhooks and a WebSocket event stream. - Self-heal & VM safety —
blackout tools vmcheckreports VM detection and leftover state, the daemon heals its own leftovers at startup, and the Go core recovers from panics instead of killing the host process.
See the changelog for the full list.
Enterprise & Team
RBAC, signed access policy, multi-device dashboard, and compliance scoring from effective settings — all local-first, nothing uploaded.
Developer SDK
from blackoutkit.sdk import Blackout is a thin facade over the CLI internals, so the SDK and CLI can never disagree. Typed errors derive from BlackoutError.
Plugins & marketplace
Drop-in analyzers, exporters, and rules — gated behind plugins_enabled (default off) — installed from a SHA-256-verified community catalog.
REST API v2
Read-only, loopback-only endpoints for events, webhooks, plugins, devices, and compliance, plus a /ws/events WebSocket stream.
What it is
Blackout Kit coordinates local bypass engines, saved proxy or VPN configurations, local readiness checks, targeted recovery, and user-facing CLI/GUI workflows.
It is not a hosted VPN service and does not operate the upstream servers users trust for tunneled traffic.
Windows
Broad engine catalog, GUI, system-proxy workflows, split-tunnel proxy bypass patterns, and native DLL-backed runtime paths.
Linux
Supported paths are currently xray, tun, hysteria2, and tuic through the managed blackout-engine runtime.
Safety model
Readiness and route ranking are local-only. A green local check does not prove remote reachability or bypass success.
Guides
- README for the high-level project overview
- User Guide for operators and end users
- Contributing Guide for maintainers and contributors
- Security Policy for threat model and trust boundaries
Important boundaries
- Blackout Kit does not guarantee anonymity.
- Country profiles are guidance, not proof.
- The supported kill switch is Linux-only.
- Default recovery is intentionally targeted, not a full system reset.