hfiguera
Hi everyone,
I’ve released Obscura 0.1.1, an Elixir library for detecting and anonymizing personally identifiable information before it reaches logs, external APIs, analytics systems, or LLM providers.
The dependency-light core recognizes structured identifiers such as email addresses, phone numbers, credit cards, SSNs, IBANs, IP addresses, URLs, and domains. Optional local Nx/Bumblebee profiles add person, location, and organization recognition without requiring a hosted recognition service.
A basic redaction looks like this:
{:ok, result} =
Obscura.redact(
"Contact jane@example.com or call 202-555-0188",
profile: :fast,
entities: [:email, :phone]
)
result.text
#=> "Contact [EMAIL] or call [PHONE]"
Obscura also supports nested Elixir data:
input = %{
customer: %{email: "jane@example.com"},
password: "secret"
}
{:ok, result} =
Obscura.redact(input,
entities: [:email],
field_policies: %{password: :drop}
)
result.data
#=> %{customer: %{email: "[EMAIL]"}}
The available operators are replacement, redaction, masking, hashing, pseudonymization, and application-defined callbacks. Pseudonymization can use an ETS-backed vault when an application needs to restore selected values after an LLM or external-service round trip.
The three stable profiles serve different use cases:
:fastuses dependency-light deterministic and parser-backed recognition.:balancedadds one local model for general person, location, and organization recognition.:accurateuses a two-model cascade for the highest measured general accuracy.
Model-backed profiles require explicit preparation and reusable runtime resources. Normal analysis never downloads a model implicitly.
One important asset note: :balanced and :accurate currently use an OntoNotes-trained TNER checkpoint. Obscura does not bundle or license that checkpoint, and LDC confirmed that commercial use requires LDC for-profit membership. The dependency-light :fast profile is unaffected. The complete review is documented in the model-asset licensing guide.
Links:
- Hex: obscura | Hex
- Documentation: obscura v0.1.1 — Documentation
- Example workbench: GitHub - hfiguera/obscura_examples: Phoenix LiveView workbench demonstrating Obscura's public PII detection and anonymization APIs · GitHub
- Practical guide: Protecting PII in Elixir Before It Reaches Logs, APIs, and LLMs · Obscura
- Model licensing: Third-Party Dependency And Model Asset Review — obscura v0.1.1
This is the first public release, and I’d particularly appreciate feedback about the API, entity coverage, structured-data behavior, model preparation, deployment, performance, and use cases that the current profiles do not handle well.
Trending in Announcing
Other Trending Topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #ai
- #graphql
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
hfiguera
I wrote a follow-up engineering case study about validating Obscura’s model-backed profiles on Linux with an NVIDIA Tesla T4 and EXLA.
The article covers the complete path from a CPU environment to real CUDA inference, including an NVSHMEM ABI failure that initially prevented EXLA from loading.
Rather than treating CUDA discovery as sufficient proof, I verified four independent signals:
nvidia-smiusing GPU memory.I then prepared the
:balancedand:accurateprofiles and ran real Obscura inference. This is a compatibility report on one Tesla T4, not a production throughput benchmark.thiagomajesk
Thanks for sharing @hfiguera, this is extremely useful!
alvinkatojr
Woah, this is neat! Thanks for sharing!
hfiguera
I published a third Obscura engineering article: A Model Card Is Not a License: What We Learned Shipping Local NER in Obscura.
While reviewing the
:balancedand:accurateprofiles, I found that the MIT license of the base RoBERTa model did not answer whether the fine-tuned OntoNotes checkpoint was authorized for commercial use.I traced the model’s provenance and contacted LDC directly. They confirmed that commercial use of this specific checkpoint requires an LDC for-profit membership. That conclusion is checkpoint-specific and does not apply to TNER models generally.
The article documents the investigation and the resulting Obscura changes, including machine-readable licensing metadata and notices before model downloads:
fairwaydm
Very Cool - Excited about checking this out!
hfiguera
I published a new engineering article about privacy-safe request logging in Phoenix.
The problem is subtle:
Obscura.Phoenix.Plugcan create a redacted assign while leavingconn.paramsunchanged for controllers, but Phoenix’s default telemetry logger still reads the original parameters.The article explains the opt-in
Obscura.Phoenix.Loggerintegration, why the default Phoenix logger must be disabled, how route templates and sanitized parameters are logged, and how failures are handled without falling back to raw request data.The integration is available in Obscura 0.1.3. Feedback from people operating Phoenix applications would be especially useful.