View Articles

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.

With the arrival of Tiki 30, the new Long Term Support release expected in summer 2026 and supported until 2031, your Tiki 27 enters the final stretch of its lifecycle. While it will keep receiving security fixes until 2029, there will be no more functional fixes or improvements. The time has come to plan your migration, without rushing, but without putting it off indefinitely.

Between the two releases, two versions (28 and 29) have deeply modernised Tiki. The list is very long, too long for a single, simple article, so we offer here a concise summary, along with all the links to read the details published by the Tiki community. Important good news: there is no abrupt technological break comparable to the PHP 7 to PHP 8 jump, because that work was already absorbed by Tiki 27. The developers, mindful of user's feedback after earlier, more "muscular" upgrades, have taken particular care to build bridges and update scripts that make it far more painless. In short, the road is clear.

Since our first update in February, the shift toward European digital sovereignty has accelerated faster than in the previous five years. While EU powers are migrating millions of workstations to Linux and Brussels targets opaque recommendation algorithms, the push for sovereign tools is no longer a theory—it is a massive public sector transition to assume European digital sovereignty. Yet, as governments pivot, data vulnerabilities are peaking: three accounts are compromised every second, and major national hacks are exposing tens of millions, making Europe a primary target for global cyber-threats. Governments are moving, which is progress. But where does that leave those without a ministerial budget?

This fourth article explores the rapid evolution of the European regulatory landscape during the past four months and maps out the escalating threats of 2026. Most importantly, it provides a concrete action checklist—categorized by time and effort—designed for professionals who need to protect their data and their clients’ trust without a dedicated IT department. These are simple, scalable measures you can implement right now, within your means and at your own scale.

This guide explains how to set up a Debian 13 server with the Virtualmin hosting control panel and deploy a Tiki Wiki CMS solution using exclusively open-source software.

Built with security and digital sovereignty in mind, you will learn how to configure essential server components (ports, MariaDB, PHP versions), install Webmin and Virtualmin, secure your server with SSL certificates, and publish your Tiki Wiki site efficiently.
This tutorial is designed for intermediate system administrators and full-stack developers seeking a reliable, scalable, and sovereignty-friendly approach to deploying modern web applications.

What do you actually depend on? Which devices, servers and cloud services are outside your control, and under which jurisdiction do they operate? Do you know what your staff use beyond the officially approved tools? This third article in our series on digital sovereignty provides a practical method to audit your dependencies, assess your exposure and identify the first building blocks to reclaim.

Independent alternatives exist, they are mature and the first steps are within reach without disrupting your operations. From network hardware to servers, from hosting to cybersecurity, we detail how to lay a solid infrastructure foundation, step by step, without paralysing your activity. After storming the Bastille, you need to lay the foundations of your citadel.

The Tiki 27+ Build System marks a significant evolution in the way Tiki Wiki CMS Groupware handles its development and deployment processes. This article aims to guide you through the essential steps and provide solutions, even as the process continues to stabilize.

Introduced in Tiki 27 and refined in subsequent versions, this build system brings numerous enhancements aimed at improving efficiency, consistency, and ease of maintenance for developers and users alike. However, it requires power users and administrators to familiarize themselves with the new installation method from Gitlab (Version Control System). This guide details the updated Tiki system build and setup procedure leveraging nvm for Node version management and npm for dependency handling, including troubleshooting for frequent installation and runtime issues.