Community
Philterd is open source software for PII and PHI redaction. The toolkit, the issues, the conversations all happen in public. Here’s how to participate.
An open source toolkit is shaped by the people who use it. The earlier you show up, the more your voice carries.
The features we prioritize, the entity detectors we add next, the deployment patterns we document: all of it follows what the community asks for. File an issue, open a discussion, or join a roadmap thread, and the answer doesn’t have to wait for a vendor product committee.
No support tier triage. When you file an issue or ask in Slack, you reach the engineers who wrote the line of code in question. Questions get answered, bugs get root-caused, and architecture trade-offs get debated by the people who built them.
Need an entity type we don’t have? A custom policy strategy? A new SDK language? Apache 2.0 means the door is open: submit a pull request, fork freely, or just pick up the source and run with it. Many of today’s features started as a contributor’s “I wish this worked differently” ticket.
All projects under github.com/philterd. Read the code, file issues, contribute pull requests.
Turnkey, self-hosted PII redaction with a clean API. Drops into any pipeline that needs sensitive data removed from text, and runs entirely inside your cloud.
Star 58The core redaction, anonymization, masking, and replacement library underneath Philter. Available in Java, Python, and .NET, with checksum-validated identifiers for national and financial IDs.
Star 108Offline Windows desktop app that redacts PII from PDF, Microsoft Word, Excel, text, and email files entirely on your own machine, using the same policy engine as Philter.
Star 2OpenSearch plugin that redacts PII and PHI from search results at query time, built on Phileas. Runs inside your cluster so sensitive fields are redacted before results reach the user.
Star 2Elasticsearch plugin that redacts PII and PHI from search results at query time, built on Phileas. The Elasticsearch build of the same query-time redaction, for clusters running Elasticsearch.
Star 1The trained AI and NLP models that find PII and PHI in text, plus the service that hosts them. Designed to plug directly into Phileas and Philter.
Star 1High-speed discovery scanner that crawls files and storage to map where sensitive information actually lives across your environment.
Star 2Intelligent monitoring that tracks PII flow across the organization and alerts on suspicious activity or unusual trends.
Star 3Drop-in proxy that redacts PII and PHI before prompts reach LLM providers like OpenAI and Anthropic Claude.
Star 5MCP server that exposes Philter's PII and PHI redaction as tools for Claude Desktop, Claude Code, Cursor, and other MCP-aware clients. Redact inside the agent's tool loop, with no integration code.
Star 1Standalone audit tool that scores redaction policies on precision and recall, so policy changes can be measured rather than guessed at.
Star 1Human-in-the-loop PII redaction. Search, review, and override automated detection decisions with structured exemption codes. Built for AI training-data prep and regulated everyday workflows.
Star 1Privacy-first analytics that applies differential privacy to PII counts, preserving statistical utility without exposing individuals.
Star 1Web console that lets non-technical users build and deploy redaction rules through a visual, no-code interface.
Star 1Declarative query language for PII operations. Write readable redaction policies as code that compile to the standard Phileas JSON schema.
Star 1The routing front door for Philter. Selects the redaction policy and engine for each file from its content type, filename, directory, and an optional local-LLM classification, with a mandatory default so no file is routed around redaction.
Star 1Most questions are answered in the docs. Every product ships a user guide, and the site collects how-tos and reference material in the guides. Start there before filing an issue.
Found a bug? File it in the relevant repo’s issue tracker; we triage weekly. For security-sensitive reports, see SECURITY.md in any repo.
Need an SLA, a custom evaluation on your data, or hands-on engineering? Get in touch. We work directly with healthcare, finance, legal, and government teams.
Pull requests welcome: bug fixes, new entity detectors, language support, docs improvements. Each repo has its own CONTRIBUTING.md.
The Philterd Slack is where contributors work things out quickly: talking through an approach before a pull request, getting unstuck on a build, or asking which repo a change belongs in. A few ground rules:
Issues labeled good first issue across the philterd org.
Philterd is built and maintained by Jeff Zemerick, PMC Chair of Apache OpenNLP and primary developer behind the entire toolkit. The contact form below reaches Jeff directly.
