Why we built it
Regulation is becoming part of product work earlier than many teams expect. Builders are not only dealing with one rule or one authority. They may need to consider AI, data protection, cybersecurity, consumer protection, financial rules, platform duties, sustainability reporting, and sector-specific obligations.
BURHUC Regulation was created as a practical orientation layer. It helps teams slow down at the right moment, identify what may apply, and work from official sources before product, technical, or commercial decisions become difficult to change.

What the resource covers
The public version brings together framework triage, deadline tracking, source references, and technical risk mapping. It is built for people who need a structured first pass: founders, product teams, technical leads, and operators preparing products under regulatory pressure.
The site includes a regulation matrix, deadline watchlist, source registry, glossary, builder map, and practical templates. The aim is not to replace legal review. The aim is to make the first questions clearer before a team asks for formal advice or commits to a build path.
A Luxembourg lens with wider coverage
The resource includes Luxembourg sources such as public authorities and official registries, while also connecting them to wider European and international frameworks. That matters for teams building from Luxembourg but operating across borders.

How we will use it
For BURHUC, this is also an internal working tool. It gives our research and product work a more disciplined way to ask regulatory questions early. It helps separate assumptions from source-backed orientation, especially when ideas move quickly and the cost of missing a constraint can be high.
The next work is to keep refining the structure, source quality, and practical usefulness of the resource as new needs appear.
Open BURHUC Regulation
Use the public resource to orient early regulatory questions before committing to a build path.
Open BURHUC Regulation