anonym.legal
Terug naar BlogTechnisch

Gratis PII-detectie kost €13.000 per jaar

Zelf-hosten van Presidio vereist 40–80 uur initiële setup en 5–10 uur/maand doorlopend onderhoud. Tegen €100/uur engineeringskosten is dat €13.200+ per jaar.

June 12, 20267 min lezen
Presidio TCOopen-source costmanaged SaaSPII infrastructureDevOps cost

De werkelijke kosten van 'gratis' PII-detectie

"Het is gratis" is geen kostenanalyse. Het is een licentieprijsopgave — één factor van vele.

Microsoft Presidio kost €0 om te downloaden. De software is open source. Maar het uitvoeren ervan bij een verzekeringsmaatschappij kost meer dan €13.000 in het eerste jaar. Dat verschil is engineeringtijd.

Wat een productie-implementatie vereist

De tool gereedmaken voor productie kost 40–80 uur. Dit omvat:

  • Docker-omgeving opzetten of Python 3.9+ configureren
  • spaCy-modellen installeren (1–2 GB per taal)
  • Presidio Analyzer en Anonymizer configureren
  • Aangepaste entiteiten aanmaken voor organisatiespecifieke ID's
  • Integreren in de bestaande datapijplijn
  • Tests schrijven om detectienauwkeurigheid te valideren
  • Eerste productietest uitvoeren, fouten debuggen

Bij €100/uur: 40–80 uur × €100 = €4.000–€8.000 initiële setup.

Doorlopende onderhoudskosten

Na productieimplementatie:

  • Modelupdates: spaCy geeft regelmatig nieuwe modellen uit. Elke update vereist testen of detectienauwkeurigheid consistent blijft. 2–4 uur per update.
  • Afhankelijkheidsbeheer: Python-pakketafhankelijkheden veranderen. Upgrade-conflicten vereisen debug-sessies. Gemiddeld 2–3 uur per maand.
  • Nieuwe entiteitsvereisten: elke keer dat beleid verandert (bijv. een nieuw nationaal ID moet worden gedetecteerd), is er engineeringtijd nodig om de aangepaste entiteit toe te voegen en te valideren.

Totaal doorlopend onderhoud: 5–10 uur per maand. Bij €100/uur: €500–€1.000 per maand = €6.000–€12.000 per jaar.

De volledige jaarlijkse kostenberekening

PostLage schattingHoge schatting
Initiële setup€4.000€8.000
Doorlopend onderhoud€6.000€12.000
Hosting (server)€1.200€3.600
Totaal jaar 1€11.200€23.600

Het €13.200-cijfer is een conservatieve schatting op basis van typische overhead bij kleine tot middelgrote teams.

Break-even met beheerde SaaS

Anonym.legal's gebruik-gebaseerde prijs begint aanzienlijk onder de €11.200-grens voor de meeste organisaties. Break-even met zelf-hosten treedt pas op bij volumes die de meeste mkb-organisaties nooit bereiken.

Limitations / When this doesn't apply

The hour ranges are estimates that swing on team and context. The 40–80 setup hours and 60–120 annual maintenance hours assume a team without prior Presidio experience and without an existing platform team; a team already running containerized NLP services absorbs much of this as marginal cost. The headline 70x year-one gap depends on the high end of the self-hosted estimate and the low end of usage, so run the numbers with your own rates and infrastructure rather than adopting the multiple as given.

A lower cost says nothing about detection quality. The comparison is about who maintains the stack, not whether either path correctly finds your PII — a managed service that deploys in twelve minutes can still miss a custom or legacy identifier format, and a missed entity is a compliance gap regardless of how cheaply you reached it. Validate that the chosen tool detects your entity types on held-out documents before treating the cost decision as settled. And sending data to a managed service relocates rather than removes obligations: hosted processing adds a processor relationship, a data-transfer assessment, and vendor due diligence that the TCO hour-count omits but that are real cost (and where the offline Desktop App may fit instead).

Gerelateerde Artikelen

Technisch

Presidio: 3-Week Setup vs Managed PII

Microsoft Presidio has thousands of GitHub stars and hundreds of open issues. Setup complexity, PySpark integration overhead, and Python dependency.

Technisch

6 Weeks to 3 Days: Managed PII Setup

Healthcare SaaS teams spend 6 weeks on self-hosted Presidio production deployment before switching to managed API. The managed API replaces the deployment.

Technisch

Presidio 22.7% Precision Problem

A 2024 benchmark found Presidio's person name recognizer achieves 22.7% precision in business documents — meaning 77.3% of detections are false positives.

Klaar om uw gegevens te beschermen?

Begin met het anonimiseren van PII met 267+ entiteitstypen in 48 talen.

Start Gratis ProefperiodeBekijk Kenmerken

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

Related reading

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022, held by our hosting provider.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our company HQ is in Saarbrücken, Germany. Our servers run in Hetzner's Falkenstein datacenter.

Hetzner holds ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

Automated checks run on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We test detection against sample documents before each release.

A failing unit or integration run stops the release.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

Paid plans can buy top-up credits.

Credits reset at the end of each cycle.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.