Product · In development
Erasix
Erasure, export, consent, retention and the audit record, as a service you host — with a self-service portal for your users and a NuGet package for your ASP.NET Core app. Personal data is classified where it is declared, not discovered afterwards.
The ticket says “implement GDPR data subject rights.” Nobody can tell you what done looks like. You start reading, discover it is eight distinct rights rather than one, and realise the endpoints are not the work. The work is knowing which columns across forty tables hold personal data, and keeping that knowledge true as the schema changes.
So you write a deletion routine. Six months later someone adds a table and nobody updates it. You now have a compliance mechanism that is silently wrong, with no way to detect that it is wrong.
Classification lives in the code
[PersonalData("user.contact.email")]
public string Email { get; set; }
The key is a fideslang term — an openly licensed privacy taxonomy maintained by others, not a vocabulary invented here. Because classification is declared at the field, the map of personal data cannot drift without the code changing. Discovery becomes a build-time property instead of a scanning problem.
erasix.capabilities
erasure
Deletion and anonymisation across declared personal data.
portability
Structured export in a machine-readable format.
consent
Checked against a fideslang dataUse key rather than an arbitrary string, so "was this processing permitted" has a typed answer.
audit
Append-only record of every access and deletion, each event carrying its data categories and data use.
retention
Storage limits enforced on a schedule rather than promised in a policy document.
breach
Tooling for the 72-hour clock — who was affected, what categories, and when you knew.
portal
A branded, multi-language self-service portal your users reach directly, with magic-link sign-in — so a request does not have to become a support ticket.
Erasix is built for ASP.NET Core: one container, one NuGet package, one
sovereignty.yaml, feature flags for what you do not need. It runs standalone beside any
deployment, or as the data-subject rights component of SOVRAK. An earlier design
split this across seven services, which is operationally absurd for a single-server
deployment. It was wrong and it got fixed.
Honest scope
This covers personal data your application controls. It does not reach into your CRM, your mail platform, or your warehouse, and it will not pretend to. If your estate is large and fragmented, this is a component of your answer, not all of it.
Nor does it make you compliant. Compliance is a property of your organisation’s practices, not of a dependency. What this provides is the technical mechanism; your policies, records of processing, and legal basis remain yours. Any vendor claiming otherwise is selling something that cannot be delivered.
Why not a hosted platform
Fulfilling a request through a hosted compliance platform means granting a third party read and delete authority across your systems. That is a large amount of new exposure to solve a problem confined to your own database — and if that third party answers to a foreign jurisdiction, you have introduced a transfer question in the course of answering one.
Source-available, and what that means for security
Erasix is source-available, not open source, and the difference is worth stating plainly. The service is licensed under the Fair Core License with an Apache-2.0 future grant: you can read it, build it, modify it, and run it inside your own organisation for nothing. The one line it draws is competing use — reselling it, or hosting it as your own rival offering. The integration packages you actually compile against are MIT.
Like everything else in the stack, it ships without warranty. That disclaims liability. It does not disclaim responsibility, and I would rather be explicit about the difference than let you find out later.
Security handling is not best-effort. Vulnerability reports get a private disclosure route straight to me. Actively exploited vulnerabilities and defects in the rights logic itself — a deletion that silently fails, an export that omits declared data — are treated as the highest priority class of work, on the free tier as much as the paid one.
A compliance component without a credible vulnerability response process is not worth running, whatever its licence says.
Feature requests, integration questions, and “how do I use this with my ORM setup” are best-effort on the public tracker, or covered under a support agreement.
Built for ASP.NET Core
Attributes on your models, one NuGet package in your app. The declarations are C#, so keeping the map of personal data current is code review, not archaeology.
Beside your app, or in the stack
A single container you run next to any deployment — or the data-subject rights component of the generated stack, arriving pre-wired with SSO and the portal routes.
Signed receipts
Every erasure closes with a cryptographically signed receipt — evidence you can produce years later, not an assertion in a closed ticket.
Free to run internally
Read it, modify it, run it inside your organisation for nothing, with each release converting to Apache-2.0 two years on. The packages your app compiles against are MIT.
Erasix is a working name, pending trademark clearance.
Interested in Erasix?
Get in touch at ryan@fortibus-consulting.com — I'm happy to talk.