Server Team Status Report — November 2025

Due to other commitments, we were only able to participate in the November community sprint. Nevertheless, it is always great to hang out and work with members of other teams, and we hope our calendars will be more accommodating next year.

Even though we did not see each other in person most of the time, our monthly remote meetings ensured that we were able to coordinate all tasks successfully.

This year, Andreas Beutel and Bastian Bringenberg left the team to devote their newly gained spare time to other interests. We would like to express our sincere thanks to Andreas and Bastian for their help and commitment over the past years!

With Steffen, who joined our team last year, and our ongoing quest to optimize our processes, our team of four remains strong, and we have been able to handle the workload without compromises.

Among many other things, we worked on and finished the following projects during remote days and community sprints:

• Streamlined the development setup for our applications. This simplifies creating local development environments for applications such as Redmine and Gerrit, which helps us and potential contributors.
• Replaced Sentry for frontend monitoring. Bugsink, an API-compatible replacement, covers all our needs with a significantly lower footprint. While Sentry requires at least 4 CPU cores and 32 GB RAM to run its 70+ containers, Bugsink consists of two containers running on a very small system with 1 CPU core and 2 GB RAM
• Introduced AI crawler firewall. This summer, we encountered multiple outages on extensions.typo3.org and forge.typo3.org. They were caused by AI crawlers making millions of requests to the same resources each hour. To filter them, we added Anubis in front of these two installations, which proved to be very effective.
• Installed numerous updates throughout the year on our systems such as Gerrit, GitLab, HedgeDoc, Mailcow, Matomo, OTOBO, and Redmine.

During the year, the TYPO3 Server Team meets in monthly video calls to coordinate our tasks. These meetings are public, and everyone is welcome to join us for questions or even just to say hello. Every few months, we meet in person at one of the community sprints or other TYPO3 events.

We aim for open communication and processes. You can follow our work in GitLab, on our Status Page, and on Mastodon.