Welcome aboard!

On 11 September 2026, the Cyber Resilience Act starts requiring "manufacturers" to report any actively exploited vulnerability in their products within 24 hours. A full notification follows within 72 hours, then a final report within fourteen days. The obligation is not limited to future products: it covers the installed base, including a device shipped five years ago and still running at a customer site.

Which leaves the real question: who counts as a manufacturer? The word covers far more people than you would think. Whoever sells a plugin or a module. Whoever assembles a box with embedded software. Whoever ships an image or an appliance under their own brand. Hosting providers, integrators and end users do not qualify, and non-commercial open source falls outside the scope entirely. Here is the test that settles it, the situations where it applies, and what can still be done before the deadline.

With its 7.0 release, "Armstrong," WordPress brings artificial intelligence right into its core. The promise is appealing: connect an AI to your content in a few clicks. But that default path sends your knowledge off to models hosted by third parties.

That convenience carries a cost few users stop to weigh. Internal content, client files, strategic notes. Anything you hand to a hosted AI can be logged, reused, or placed under a foreign jurisdiction. There is another way, though, sovereign by design, and we will come to it by the end of this article.

Most Tiki Wiki maintenance tasks, from rebuilding the search index to sending notification digests, should never depend on someone remembering to click a button. The built-in Scheduler turns these chores into background jobs: set one cron entry on your server, then manage everything else from the Tiki interface.

The official documentation covers the basics in a few lines; this guide goes further, with the reasoning behind each setting and a set of tasks we actually deploy on client sites.

Your emails and online meetings contain most of your sensitive data: contracts, quotes, strategic discussions, and client files. They also represent your greatest point of exposure, and paradoxically, the area where regaining control delivers the highest return.

In this new installment of our series on digital sovereignty, we move from theory to practice.

The reality is clear. Every email sent through a U.S based service and every meeting hosted on a foreign platform falls under a legal jurisdiction that is not your own. Yet taking back control is far from an overwhelming task. Here's how to regain ownership of your communications, step by step, from simple actions anyone can take to solutions that genuinely keep your data under your control.