What is PhEye?
PhEye is the service that hosts the AI and NLP models that find PII and PHI in unstructured text. POST text to its
/find endpoint and it returns the detected entities with confidence scores. It's designed to plug directly into
Phileas and
Philter, or to call from any application that needs entity detection over HTTP.
How is PhEye different from using an LLM?
PhEye serves NLP models trained specifically for PII and PHI entity recognition, not a general-purpose LLM. For this task that means faster inference and a tiny fraction of the compute cost, and it runs entirely in your own environment with no model-provider account.
What is a lens?
A lens is a swappable model for a particular kind of text. The Philterd lenses detect people's names in English in four sizes, and community lenses cover French text and healthcare entities. Each PhEye Docker image has one lens built in, chosen by the image tag. See the
available lenses.
Is a lens the same as a policy?
No. A lens decides what is detected and where it is in the text. A
policy decides what to do with each detection: mask, redact, encrypt, abbreviate, or pass it through. You need both. Lenses are models served by PhEye, and policies are JSON files loaded by Phileas or Philter.
Can a lens replace a regex?
For names, the lens is the better tool. A trained model finds names in context that a regex can't reliably match, like "Dr. Smith" or a name buried in a clinical narrative. For structured identifiers (SSNs, credit card and account numbers, national IDs, phone numbers), a validated pattern is faster and more reliable than a model, and that is what Phileas's pattern layer does. Production deployments use both.
Can I combine lenses?
Yes. Run one PhEye container per lens and list each endpoint in your Phileas policy. A team processing English and French tickets runs both, and the detections from each are applied to the same document. Switching lenses is a change to the image tag and the policy, not to the calling application.
Does running multiple lenses slow things down?
Each lens adds its own inference time per document, and larger lenses take longer than smaller ones. Measure on your own hardware and document mix, and use
Philter Scope to check whether a larger lens actually improves recall on your data before paying for it.
Are the lenses open source?
Licensing varies per lens. Each lens's detail page, linked from the table above, lists its license alongside the language and version, and community models carry the license their authors chose. Custom-trained lenses are deliverables of a paid engagement and are owned per the engagement terms.
Does PhEye send my text anywhere?
No. Deploy PhEye alongside your data and sensitive text never leaves your infrastructure: no third-party API, no model-provider account, and no outbound dependency.
Do I need a GPU?
No. The standard Docker images run inference on CPU with no special hardware required. GPU-accelerated images, built on PyTorch with CUDA, are available for workloads that need higher throughput or handle high request volume.
How does PhEye relate to Phileas and Philter?
PhEye is the default model server for both
Phileas and
Philter: they call its
/find endpoint to get the machine-learning detections that complement their regex, dictionary, and validation rules. Wire it in through configuration, or call its HTTP API directly from anything that speaks JSON.