AegisGate Rampart — Local AI Security Proxy & IDE Plugin

⚡ AegisGate Rampart v0.7.1 is LIVE — Local proxy, IDE plugins for VS Code/Cursor and JetBrains, real-time detection. Download from GitHub (free, open source, Apache 2.0).

What is Rampart?

Rampart is a local security tool for developers who use AI coding assistants like GitHub Copilot, Cursor, or local LLMs (Ollama, LM Studio). It sits between your editor and the AI model, scanning everything you send — and everything the AI sends back — for sensitive data and security risks.

Think of it as a firewall for AI coding tools. It catches the moment you’re about to send a database password to Copilot, or when the AI generates code that contains an API key, and stops it before it’s too late.

Do I need Rampart?

If you use AI chat in a browser (ChatGPT, Claude, etc.): You need Lens — it’s a free browser extension that protects you in the browser. Rampart is not for this use case.

If you use AI coding tools (Copilot, Cursor, local LLMs, API calls): You need Rampart. It protects the places Lens can’t reach — your IDE, your terminal, your API calls.

See Rampart in Action

What does it catch?

Architecture Overview

Detection Flow

Is it private?

Yes. Everything runs on your machine. Nothing is sent to any server — not your prompts, not your code, not your detection results.

Open source (Apache 2.0): github.com/aegisgatesecurity/aegisgate-rampart

Quick Start

Option 1: Install the IDE plugin (recommended)

VS Code / Cursor:

1. Open the Extensions panel (Ctrl+Shift+X / Cmd+Shift+X)
2. Search for “AegisGate Rampart”
3. Click Install, then Reload
4. Detection runs automatically as you type — results appear as inline warnings

JetBrains (IntelliJ, PyCharm, WebStorm, etc.):

1. Open Settings → Plugins → Marketplace
2. Search for “AegisGate Rampart”
3. Click Install, then Restart
4. Detection results appear in the Problems tool window

Neovim / any LSP editor:

# Download the Rampart LSP binary
curl -L https://github.com/aegisgatesecurity/aegisgate-rampart/releases/latest/download/rampart-lsp-linux-amd64 -o /usr/local/bin/rampart-lsp
chmod +x /usr/local/bin/rampart-lsp

# Add to your LSP config (Neovim example)
# lspconfig.rampart_lsp.setup({})

Option 2: Run as a local proxy

# Download for your platform
curl -L https://github.com/aegisgatesecurity/aegisgate-rampart/releases/latest/download/aegisgate-rampart-linux-amd64 -o aegisgate-rampart
chmod +x aegisgate-rampart

# Start the proxy
./aegisgate-rampart --port=8443 --upstream=https://api.openai.com

# Point your AI tool at the proxy
# Instead of: https://api.openai.com/v1/chat/completions
# Use:        http://localhost:8443/v1/chat/completions

Option 3: Docker

docker run -d \
  -p 8443:8443 \
  -p 9090:9090 \
  ghcr.io/aegisgatesecurity/aegisgate-rampart:v0.7.1

How it works

Rampart runs in two modes — you can use either or both:

1. IDE Plugin Mode

Rampart runs inside your editor as a Language Server (LSP). As you type prompts or code that will be sent to an AI tool, Rampart checks for sensitive data and security risks in real-time. Warnings appear inline, just like lint errors.

The LSP server uses JSON-RPC 2.0 over stdio — it works with any editor that supports LSP.

2. Local Proxy Mode

Rampart runs as a transparent proxy on your machine. Any AI tool that makes HTTP requests — Copilot, Cursor, local LLMs, API calls — gets intercepted and scanned.

Your AI tool (Copilot/Cursor/API) → Rampart proxy (localhost:8443) → AI model (OpenAI/Anthropic/local)

• Rampart generates a local CA certificate and configures your system to trust it
• All HTTPS traffic to AI services flows through the proxy
• Requests and responses are scanned in real-time
• Malicious content is blocked before it reaches the model (or before the response reaches you)
• CA keys are encrypted at rest with a passphrase — no plaintext keys on disk

Rampart vs Lens vs Platform

For Organizations

Typical team setups

• Individual developer: Lens (browser) + Rampart (IDE) → full local protection, zero cost
• Developer team (2-10): Rampart (IDE) for each dev + Platform (server) for centralized policy, audit logs, and compliance reporting
• Enterprise: Platform (server) + Lens (browser) for non-technical staff + Rampart (IDE) for developers + SIEM/SOAR integration + 31 compliance frameworks

Privacy & Security (for compliance teams)

1. Zero data collection — no telemetry, no analytics, no phone-home
2. All detection is local — patterns and ML model run on your machine
3. CA keys encrypted at rest — passphrase-protected, never plaintext
4. Audit log redaction — PII and secrets stripped from logs before writing to disk
5. No network egress — Rampart never sends your data anywhere
6. Open source — Apache 2.0, auditable, no hidden behavior

Download

Release Assets (v0.7.1)

All 13 assets on GitHub → Source code →

IDE Integration Details

For detailed setup instructions for each editor, see our IDE Integration Guide.

{
  "rampart.detection.severity": "warning",
  "rampart.detection.categories": ["pii", "secrets", "xss", "compliance", "ml"]
}

-- Neovim (init.lua with nvim-lspconfig)
require'lspconfig'.rampart_lsp.setup{
  cmd = {"/path/to/rampart-lsp"},
  filetypes = {"*"}, -- scan all file types
  settings = {
    detection = {
      categories = {"pii", "secrets", "xss", "compliance", "ml"},
      severity = "warning"
    }
  }
}

Architecture

Frequently Asked Questions