Philter
Open-source, self-hosted PII and PHI redaction API built on the Phileas engine.
About
Philter is an API-based application from Philterd that identifies and manipulates sensitive information in text: redacting, anonymizing, encrypting, or replacing PII, PHI, and other sensitive data. It sits on top of Phileas, Philterd's open-source redaction engine, and adds a REST API plus a policy engine for managing filtering policies. For each entity type you choose how it is handled: mask it, encrypt it (including format-preserving encryption), replace it with a synthetic value, drop it, or pass it through. The policy engine also supports conditional redaction, such as only certain names or only credit cards that pass Luhn validation, plus custom entity types via dictionaries and identifier patterns.
Philter was released as open source under Apache 2.0 in July 2024 (version 2.6.0), though the project dates back to 2019, and it remains actively maintained with commits days old. It runs as a Java 17+ application via Docker, ships a web UI for policy management, and is also available as turnkey images on the AWS, Google Cloud, and Azure marketplaces. The Philterd toolkit around it includes Phileas libraries in Java, Python, .NET, and Go, a Philter AI Proxy that strips PII from prompts before they reach LLM providers, Phinder for discovery scanning, and Philter Scope for benchmarking redaction policies. Philter Desktop is a separate Windows app for redacting documents locally; its source is open under Apache 2.0 while the signed build is a commercial $100/user/year subscription. It is a solid pick for teams that need redaction inside their own VPC with full source access, though at 60 GitHub stars it is a niche project rather than a mainstream standard.
What it can do
- REST API for PII/PHI redaction, anonymization, and encryption
- Policy engine with per-entity handling: mask, encrypt, synthetic replacement, drop, pass-through
- Custom entity types via dictionaries and identifier patterns
- Philter AI Proxy: strips PII from prompts before LLM providers
- Phinder discovery scanner and Philter Scope policy benchmarking
- Turnkey images on AWS, GCP, and Azure marketplaces
Setup
- Clone https://github.com/philterd/philter (requires Java 17+ and Maven) or pull the Docker image.
- Build with
mvn clean install, then run withdocker compose up. - Send text to the API:
curl -k https://localhost:8080/api/filter --data "..." -H "Content-type: text/plain". - Open the UI at http://localhost:9000 to author and manage redaction policies.
Prerequisites
Java 17+ and Docker for the self-hosted API; nothing to install for the cloud marketplace images.
Use cases
Works with
Trust score — 7/10
Scored 7/10 (verified tier, metrics-v1). Evidence: 60 GitHub stars, pushed 2026-10-14, not archived, Apache-2.0 (GitHub API); open-sourced Jul 2024 v2.6.0, project dates to 2019 (GitHub README); philterd.ai and docs verified live; AWS/GCP/Azure marketplace listings documented. Strengths: fully self-hosted with full source, mature policy engine, active maintenance, honest commercial/open split. Docked for: (1) small community (60 stars) and niche visibility; (2) Java/Docker stack is heavier than a pip-installable library. License: Apache-2.0.
★ 60 GitHub stars
How the trust score is built
Full methodology →- Adoption · stars/downloads, log-scaled vs peers
- 4.0/10
- Maintenance · recency, releases, issue load
- 8.0/10
- Openness · license + docs
- 10.0/10
- Manual review · sanity read + red-flag check
- 6.0/10
- · 60 GitHub stars, pushed 2026-10-14, not archived, Apache-2.0 (GitHub API)
- · Open-sourced Jul 2024 (v2.6.0), project dates to 2019; built on Phileas engine
- · Policy engine: mask/encrypt/synthetic/drop per entity type; Philter AI Proxy for LLM prompts
- · Turnkey images on AWS/GCP/Azure marketplaces; philterd.ai verified live
- · Small niche community; Java/Docker stack heavier than a library
Sources
Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.