New: Philter One, a redaction box for your office, is coming soon. Learn more →

Contact Us

Tell us about your stack and the privacy problems you're trying to solve. We typically respond within one business day.

Prefer email? support@philterd.ai

Please do not enter PII or PHI in this form. If you need to share an example, use a sanitized one.

← All comparisons

Comparison

Philter and Phileas vs Microsoft Presidio

Presidio is a Python toolkit you assemble and run yourself. Philterd’s open source engine comes two ways. Phileas is a library for Java, Python, and .NET, and Philter is a redaction service you deploy in your own cloud. This page compares both with Presidio, from the team that builds them.

Philter, Phileas, or Presidio?

Two of these are Philterd and one is the alternative. They are not really rivals so much as three different shapes. The quick way to choose:

Philter

A turnkey, self-hosted redaction API other systems call over HTTP, shipping with NLP models, cloud-marketplace deploys, and a commercial-support path.

Choose when: you want a running service to point pipelines at, not a library to build into one.

Phileas

The open source library underneath Philter. Embed it in a Java, Python, or .NET application and redact in-process, governed by a versioned policy and PhiSQL.

Choose when: you want redaction inside your own process with no extra service to run. This is the closest like-for-like with Presidio.

Microsoft Presidio

Microsoft's open source, Python-first PII toolkit. You assemble the analyzer and anonymizer yourself, with spaCy or transformer recognizers.

Choose when: your stack is Python-only and you are happy to operate it yourself, or you need its image, DICOM, or structured-data coverage.

Side by side

PhileasPhilterMicrosoft Presidio
What it isA library you embed in your applicationA self-hosted redaction API, built on PhileasA Python library, with Docker images for a REST service you run yourself
LicenseApache 2.0Apache 2.0MIT
LanguagesNative Java, Python, and .NET on one policy schemaAny language, over HTTPPython, or any language through its REST service
Policy modelPhiSQL, a declarative language that compiles to a versioned JSON policy you can reviewThe same policies, managed through Philter’s APIRecognizers and operators configured in code or YAML, with no compiled policy artifact
DetectionPatterns, dictionaries, and PhEye models trained to find namesThe same, with a name model loaded by defaultPatterns plus general-purpose spaCy, Stanza, or transformer NER
Conditional redactionBuilt in. Redact based on zip code population, age thresholds, confidence, or patternsSame as PhileasLeft to your own code
Redaction strategiesMask, redact, hash, AES-GCM encryption, FF3 format-preserving encryption, date shift, consistent pseudonymization, synthetic replacementSame as Phileas, plus audited re-identification of encrypted valuesReplace, redact, mask, hash, AES encryption, and custom operators. No format-preserving encryption or date shift
PDFBuilt in, rasterized so no text is recoverable under a redactionSame as PhileasThrough the image redactor
Image, OCR, DICOMNot a focusNot a focusYes, presidio-image-redactor
Structured dataFree text focusFree text focusYes, presidio-structured
DeploymentInside your own processAWS, Azure, and Google Cloud marketplaces, a container, on premises, or air-gappedYou build and operate the service
CostFreeFree to self-host, or from $0.49 an hour on a cloud marketplaceFree
SupportCommunity, with commercial support from PhilterdCommunity, with commercial support and consulting from PhilterdCommunity only
Surrounding toolkitPhilter Scope (precision and recall), Philter Workspace (review), Phinder (discovery), Phield (monitoring), Philter AI Proxy and Philter MCP (LLM traffic)Standalone

Service vs library

Two diagrams. On the left, a web app, a data pipeline, and a batch job call Philter over HTTPS inside your cloud or data center, and Philter runs the Phileas engine with its policies, API keys, and audit log. On the right, your Java, Python, or .NET code calls the Phileas library directly inside one application process, with no network hop.
Philter is a service that other systems call over HTTPS. Phileas is the same engine as a library, running inside your own application.

Where Phileas and Philter differ from Presidio

Presidio and Phileas are both good detectors, and Presidio is ahead on images and structured data. The difference shows up in the policy model and in what happens to a value once it is found. That is where teams moving a Presidio prototype into a governed production pipeline tend to hit walls.

A policy you can review

Policies are versioned JSON, written directly or in PhiSQL, and kept in version control. Presidio is configured in code or YAML.

Conditional redaction

Redact only zip codes below a population threshold, or only ages over a cutoff. In Presidio, that logic is yours to write.

Consistent and reversible replacement

The same person gets the same stand-in throughout a document. Values can be encrypted, including format-preserving, or date-shifted.

Java, Python, and .NET

Phileas runs natively on all three with one policy schema. Presidio is Python, or a service you call.

Models trained for PII

Name detection runs on PhEye models trained for PII. Presidio uses general-purpose NER models.

When you want a service instead of a library

Many teams start with Presidio in a notebook, then wrap it in their own API so other systems can call it. At that point they are building and running a redaction service, with its scaling, monitoring, and upgrades.

Philter is that service, already built. It is Phileas behind a REST API with API keys, audit logging, and policy management. You can launch it from the AWS, Azure, or Google Cloud marketplace and pay for it on your cloud bill, which is often faster than a new vendor contract. It also runs as a container on premises or air-gapped. The code stays Apache 2.0, and commercial support and consulting are available from the people who wrote it.

Moving from Presidio

The migrate from Presidio guide maps Presidio recognizers to Phileas filters and anonymizer operators to Phileas strategies and PhiSQL, with Presidio code next to its Phileas equivalent.

Where Presidio is strong

Presidio’s strengths are real, and in a few areas it is ahead of Phileas and Philter today.

  • A large community and a familiar name. It is Microsoft-backed and MIT-licensed. You run pip install presidio-analyzer and have a wide set of recognizers out of the box.
  • Image, OCR, and DICOM de-identification. The presidio-image-redactor package redacts PII burned into images and supports DICOM medical imaging. Phileas and Philter work on text and PDF.
  • Structured and semi-structured data. presidio-structured targets tabular and JSON data. Phileas and Philter are built around free text.
  • Easy Python extensibility. A custom recognizer is a small Python class, and there is a clear path to plug in transformer or LLM recognizers alongside spaCy or Stanza.

If your problem is image or DICOM de-identification, tabular data, or a Python prototype you want running this afternoon, Presidio is a good choice. All three tools share the property that matters most. They are open source, you can read the code that touches your data, and none of them sends that data to a vendor.

We want this comparison to be accurate and fair. Open source projects move fast, so this reflects publicly documented behavior at the time of writing and may have changed since. Check the current Presidio documentation before deciding, and if you spot anything inaccurate, please let us know and we will correct it.

Further reading

Try it on the text you test Presidio with

Add Phileas to your Java, Python, or .NET code, or deploy Philter from your cloud marketplace when you want a service instead of a library.