Skip to content
Blazle Vanguard · Developer machines: IDE, local proxy, pre-commit

Vanguard. Stopped on the laptop, not in production.

Vanguard protects the machines where coding agents run: the editor, the terminal and every commit.

The problem

  • Coding agents run shell commands with the developer's rights
  • Secrets get committed before any server-side scan sees them
  • Each developer's tools are a blind spot for security

How it works

Vanguard. Stopped on the laptop, not in production.

  1. 01

    Install once

    A local proxy, a VS Code extension and a git pre-commit hook.

  2. 02

    Check before it runs

    Prompts, commands and staged changes are checked on the way out.

  3. 03

    Same policy everywhere

    The rules you set in Command apply on every seat.

Vanguard · Event LedgerExample data
EventResult
Vanguardgit commit · AKIA••••••••••••dev-laptop-07Blocked
Vanguardcurl … | shClaude CodeBlocked
Vanguardnpm testCursorAllowed

Controls

  • Dangerous command blocking

    Wipes, pipes to shell and credential theft are stopped.

  • Secret blocking at commit

    Known key formats never reach the repository.

  • Works with your agents

    VS Code, Cursor, Claude Code and Antigravity.

  • Per-seat identity

    Every block shows which developer machine it came from.

Plans and price

  • 1 developer seat included on Hacker.
  • Extra seats: $15 per seat per month ($150 per year), on every plan.
Plans and price ›
Read the docs