Enterprise DNAEnterprise DNA

Open Source

PrivAiTe

Self-hosted PII redaction proxy for LLM APIs and agent CLIs.

Our verdict

Not reviewed yet

We have not reviewed PrivAiTe yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About PrivAiTe

Self-hosted PII redaction proxy for LLM APIs and agent CLIs. Scrubs names, emails and secrets from Claude Code, Codex and any OpenAI-compatible app before requests leave your machine, tool-call arguments included, then restores them in the reply. Local detection, zero telemetry.

Best for

Python developers who want local PII redaction for LLM and agent workflows without sending data to third-party services

Use cases

  • Redact PII from LLM API requests before they leave the machine
  • Protect agent CLI tool-call arguments for Claude Code and Codex
  • Restore redacted entities in responses from OpenAI-compatible apps

Notes

47 stars on GitHub. Last updated 2026-10-05. Licensed BSD-3-Clause.

Pros

  • Local detection with zero telemetry keeps data on your machine
  • Restores redacted values in replies, so downstream workflows keep working
  • Works across standard OpenAI-compatible APIs and popular agent CLIs

Cons

  • Requires self-hosting and a local proxy setup to intercept traffic
  • Small community with 47 GitHub stars and limited ecosystem traction
  • Only covers OpenAI-compatible APIs and the specifically listed agent CLIs

Key facts

What we have checked

Days since the last commit
2
Checked GitHub
GitHub forks
3
Checked GitHub
GitHub stars
62
Checked GitHub
Open issues
1
Checked GitHub
Releases in the last 90 days
11
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

Stars and usage

How PrivAiTe is growing

GitHub stars

47 to 62

stars. 5 Oct 2026 to 6 Nov 2026, 3 readings.

Source: GitHub. Checked .

Health and security

Is PrivAiTe looked after, and what do its setup files show

Health score

75 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity30 of 30Last push 2 days ago
Releases15 of 1511 releases in 90 days
Issue repliesNot countedThe latest check has no issue response reading (fewer than 3 measured issues, or issues switched off)
Maintainer0 of 15Owned by a single user
Official sourceNot countedMCP servers only

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.