EU compliance,
finally simple.
Four agents watch your GDPR and EU AI Act obligations, turn what they find into one specific action, and wait for your approval before anything changes.
No account, and your answers never leave the page.
The reality
Why compliance
quietly rots
Most teams lack the legal budget, the in-house expertise, or the time to work out where they stand. GDPR has been in force since 2018 and fines are accelerating. The EU AI Act adds a second wave of obligations on top.
Compliance fails quietly, and it fails on the days nobody remembered to check. Kindlast turns that regulatory surface into a plain-language action plan your team can act on.
What it covers
Two regulations,
one running system
Kindlast holds a live picture of your obligations under the GDPR and the EU AI Act, and keeps checking it against what your business actually does. Nothing here waits for you to remember to open it.
- GDPR gap analysis
- Findings tied to the specific article, not a generic checklist, with the one action that closes each gap.
- EU AI Act classification
- Your AI systems sorted into risk tiers, with the obligations and deadlines that follow from the tier.
- ROPA and records
- Records of processing kept current, because the agents notice when a new activity has no entry.
- DSAR deadlines
- Every data subject request tracked against its statutory clock, with alerts before the clock runs out.
Open source
Europe shouldn’t build this twice.
Every company shipping software in the EU hits the same GDPR and AI Act questions, and almost every one of them answers from scratch. That is months of founder time spent re-deriving obligations someone already worked out.
Kindlast is AGPL-3.0 licensed, so that groundwork is shared infrastructure rather than a moat. Read it, run it yourself, or improve it for everyone.
- Auditable
- Every detector, every citation, and every database access policy is in the repository. Nothing between you and the regulation is a black box.
- Self-hostable
- Run the whole thing on your own infrastructure. Your processing records never have to leave it, and there is no vendor to add to your ROPA.
- Stays open
- AGPL section 13: anyone running a modified Kindlast as a service owes their users the corresponding source. The commons stays a commons.